This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I have enabled SSH on my ReadyNAS and granted the default admin command SSH access. I can SSH to the NAS (using Putty) and logon with the admin command.
I am issuing the command journalctl --disk-usage. I am getting an error as seen in the screen print that says the account does not have permissions to access the files due to insufficient permissions.
I am issuing the command journalctl --disk-usage. I am getting an error as seen in the screen print that says the account does not have permissions to access the files due to insufficient permissions.
Log in as root, using the NAS admin password.
This command only tells you how much space the log is using.
root@NAS:~# journalctl --disk-usage
Archived and active journals take up 50.1M on disk.
root@NAS:~#
I am issuing the command journalctl --disk-usage. I am getting an error as seen in the screen print that says the account does not have permissions to access the files due to insufficient permissions.
Log in as root, using the NAS admin password.
This command only tells you how much space the log is using.
root@NAS:~# journalctl --disk-usage
Archived and active journals take up 50.1M on disk.
root@NAS:~#
Ahh.. Thanks. That did the trick. I am trying to delete old logs - I clicked the CLEAR LOGS from the admin page but when I dumped the logs I still see old entries in some log files like smdb.log and smtp.log. I was going to issue as found in this article How To Clear The systemd journal Logs (journalctl) - Linux Uprising Blog
Wait a bit (perhaps 30 minutes), and download the log zip. After you confirm that the leafp2p messages stopped, try rebooting the NAS, and then download them again with a delay. Then confirm that the fix survived the reboot.
Though you should also be able to see these messages from journalctl, so that would be another way to confirm.
There are certainly other folks with this issue - I saw it in another log zip I received today.
Are the other folks experiencing the same issue with Windows mappings dropping off ?
I don't recall the earlier one(s) well enough. But not the most recent one I've seen. However, that person has a higher-end NAS, so the service would be less likely to bog down the system.
FYI - I did run the journalctl --rotate and journalctl --vacuum-time=1s.
It did what I wanted and emptied the logs. I rebooted the NAS and dumped the logs. The leafp2p log indicates the service is still starting up.
But this is going from bad (losing mapped drives) to becoming unmanageable.
- I am getting kicked out of Putty session or get a connection refused when attempting to open a session.
- unable to open admin page.
- get prompted for credentials when running RAIDar when trying to dump the logs, run diagnostics, restart - it says the credentials are not valid - I am positive I am typing the password correctly. After I reset the NAS I am able to run these routines on RAIDar for a short period of time.
At this point I have to manually reset the NAS by removing the power and putting it back in. It will work for short while.
I purchased this in November of 2015 - not sure what the life expectancy is for these units.
Not sure if a factory reset is going to help but at this point it is pretty much useless .
