NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dpcsret
Jun 26, 2024Aspirant
Accessing journalctl command on ReadyNAS 102
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-u...
- Jun 26, 2024
dpcsret wrote:
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:~#
dpcsret
Jun 26, 2024Aspirant
No real reason.. maintenance. Emptying logs so any entries are more current. Size is not an issue - only 16MB used.
Is there a reason this is not a good idea ? I have log dump zip files for prior reference if need be.
- StephenBJun 26, 2024Guru - Experienced User
dpcsret wrote:
Is there a reason this is not a good idea ?
Generally if something does go wrong, it's best to have all the information. It's easier to do this from one log zip, and not piece things together.
If you do want to clear them, you can also do this from the NAS web ui.
- dpcsretJun 26, 2024Aspirant
I did the CLEAR LOGS from the web UI. It did not clear all the logs..
I was just playing around with SSH. I can leave the logs alone.
Prepping for steps to stop ReadyCloud log activity from tying up the unit and making it occasionally unavailable (assumption).
Thanks for the quick response. I will mark it as the resolution.
- StephenBJun 26, 2024Guru - Experienced User
Try this for the leafp2p problem (logging in as root):
systemctl stop leafp2p rcbrokerd systemctl disable leafp2p rcbrokerdWait 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.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!