NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Linda2
May 15, 2012Aspirant
How to Reboot ReadyNAS Pro 4 through command line?
Hi, I have a ReadyNAS Pro 4, which was working fine since yesterday and now from a server on the same network I can ping my readynas IP and I can ssh into the ReadyNAS as well, but I don't get the ...
Linda2
May 16, 2012Aspirant
Just before restarting the ReadyNAS This is the result of tail .../frontview/error.log
ReadyNAS IP is 192.168.1.30 and the server I use to connect to NAS has the IP 192.168.1.10
The result of df -h is:
Now that the backup is working fine, I prefere not to touch the apache-ssl for now. But if the frontView goes down again I'll try restarting apache-ssl rather than restarting the NAS. Keep you updated on that...
Tried the SSH tunnel, it works fine now. I should try that when the frontview is down.
Would be great to hear your comments on the last error log I inserted above.
Thanks for the help.
[Wed May 16 09:33:01 2012] [notice] Graceful restart requested, doing restart
[Wed May 16 09:33:02 2012] [error] [client 192.168.1.10] shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory, referer: https://192.168.1.30/admin/
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.1.30 for ServerName
[Wed May 16 09:33:03 2012] [warn] RSA server certificate CommonName (CN) `192.168.168.168' does NOT match server name!?
[Wed May 16 09:33:03 2012] [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/0.9.8c DAV/2 mod_apreq2-20051231/2.6.0 mod_perl/2.0.2 Perl/v5.8.8 configured -- resuming normal operations
[Wed May 16 09:33:32 2012] [error] [client 192.168.1.10] File does not exist: /frontview/ui/resource/html/images, referer: https://192.168.1.30/admin/
[Wed May 16 09:34:35 2012] [error] [client 192.168.1.10] File does not exist: /frontview/ui/resource/html/images, referer: https://192.168.1.30/admin/
ReadyNAS IP is 192.168.1.30 and the server I use to connect to NAS has the IP 192.168.1.10
The result of df -h is:
Filesystem Size Used Avail Use% Mounted on
/dev/md0 4.0G 715M 3.1G 19% /
tmpfs 16K 0 16K 0% /USB
/dev/c/c 2.7T 754G 2.0T 28% /c
tmpfs 50M 0 50M 0% /var/replicate/shm
/dev/sdf1 1.9T 777G 1.1T 42% /USB/USB_HDD_1
Now that the backup is working fine, I prefere not to touch the apache-ssl for now. But if the frontView goes down again I'll try restarting apache-ssl rather than restarting the NAS. Keep you updated on that...
Tried the SSH tunnel, it works fine now. I should try that when the frontview is down.
Would be great to hear your comments on the last error log I inserted above.
Thanks for the help.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!