× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

update firmware via ssh? Case #19355863

buchhla
Aspirant

update firmware via ssh? Case #19355863

Hi, I have a NV+ v2 that I have been unable to get the web interface working on for some time now. I think support is running out of ideas on what to look for short of remote access to the machine, but since I am living on a boat in Fiji without real internet access, that is not possible. I do have SSH access, so for now I start up the machine, access it via CIFS/AFP/FTP and then have to ssh into the machine to shut it down. I am fine doing that, but my partner is not a linux nerd and that is beyond what I want her to be doing.

Is there anyway either upgrade to 5.3.6 via ssh, since I can't do it via the web interface, or maybe uninstall frontview ( assume the web interface is the frontview daemon) and reinstall it via APT or something similar? I do not have 8TB of space laying around to back the machine up to do a factory install.

Thanks!
Message 1 of 12
mdgm-ntgr
NETGEAR Employee Retired

Re: update firmware via ssh? Case #19355863

Please post the output of the following:

# tail /var/log/frontview/error.log


Also see if this restarts Frontview:


# /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf -t && /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf -k graceful
Message 2 of 12
buchhla
Aspirant

Re: update firmware via ssh? Case #19355863

Frontview log

[Fri Sep 07 12:19:46 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Fri Sep 07 12:20:12 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Fri Sep 07 12:20:12 2012] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Fri Sep 07 12:20:23 2012] [notice] caught SIGTERM, shutting down
[Fri Sep 07 12:20:38 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Fri Sep 07 12:20:54 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Fri Sep 07 12:20:54 2012] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Fri Sep 07 12:53:41 2012] [notice] caught SIGTERM, shutting down
[Sat Sep 08 16:53:26 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sat Sep 08 16:54:01 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sat Sep 08 16:54:01 2012] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Sat Sep 08 16:56:57 2012] [error] [client 192.168.1.150] AuthExtern pwauth [/usr/bin/pwauth]: Failed (2) for user admin
[Sat Sep 08 16:56:57 2012] [error] [client 192.168.1.150] user admin: authentication failure for "/admin/": Password Mismatch
[Sat Sep 08 16:57:05 2012] [error] [client 192.168.1.150] AuthExtern pwauth [/usr/bin/pwauth]: Failed (2) for user admin
[Sat Sep 08 16:57:05 2012] [error] [client 192.168.1.150] user admin: authentication failure for "/admin/": Password Mismatch
[Sat Sep 08 16:57:13 2012] [error] [client 192.168.1.150] AuthExtern pwauth [/usr/bin/pwauth]: Failed (2) for user admin
[Sat Sep 08 16:57:13 2012] [error] [client 192.168.1.150] user admin: authentication failure for "/admin/": Password Mismatch
[Sat Sep 08 16:57:21 2012] [error] [client 192.168.1.150] access to /admin/ failed, reason: user 'root' does not meet 'require'ments for user/valid-user to be allowed access
[Sat Sep 08 17:11:17 2012] [notice] caught SIGTERM, shutting down
[Sat Sep 08 20:53:19 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sat Sep 08 20:53:43 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sat Sep 08 20:53:43 2012] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Sat Sep 08 21:05:50 2012] [notice] caught SIGTERM, shutting down
[Tue Sep 11 12:14:37 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Tue Sep 11 12:15:16 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Tue Sep 11 12:15:16 2012] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Tue Sep 11 14:12:12 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Tue Sep 11 14:12:58 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Tue Sep 11 14:12:59 2012] [warn] pid file /var/log/frontview/apache-ssl.pid overwritten -- Unclean shutdown of previous Apache run?
[Tue Sep 11 14:12:59 2012] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Sat Sep 22 12:14:36 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sat Sep 22 12:15:02 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sat Sep 22 12:15:02 2012] [warn] pid file /var/log/frontview/apache-ssl.pid overwritten -- Unclean shutdown of previous Apache run?
[Sat Sep 22 12:15:02 2012] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Sat Sep 22 12:36:19 2012] [notice] caught SIGTERM, shutting down
[Sat Sep 22 12:44:05 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sat Sep 22 12:44:28 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sat Sep 22 12:44:28 2012] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Sat Sep 22 13:33:01 2012] [notice] Graceful restart requested, doing restart
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.1.150 for ServerName
[Sat Sep 22 13:33:32 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sat Sep 22 13:33:33 2012] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Sat Sep 22 13:33:52 2012] [notice] Graceful restart requested, doing restart
[Sat Sep 22 13:33:52 2012] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.1.150 for ServerName
[Sat Sep 22 13:34:31 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sat Sep 22 13:34:31 2012] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Sat Sep 22 14:22:14 2012] [notice] caught SIGTERM, shutting down
[Sat Sep 22 14:23:56 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sat Sep 22 14:24:18 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sat Sep 22 14:24:18 2012] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Sat Sep 22 14:42:45 2012] [notice] caught SIGTERM, shutting down
[Sun Sep 23 16:19:13 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sun Sep 23 16:19:57 2012] [warn] RSA server certificate CommonName (CN) `192.168.1.200' does NOT match server name!?
[Sun Sep 23 16:19:57 2012] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations


I also restarted the service, no errors other then the certifcate error that you see in the log above, but frontview still show device is offline. Some things do work, it does show correct volume space and a few other things, but most of the site is broken.

I did poke around the other logs in /var/logs and didn't see anything there that looks strange.
Message 3 of 12
mdgm-ntgr
NETGEAR Employee Retired

Re: update firmware via ssh? Case #19355863

Have support suggested and have you tried an OS Re-install: http://www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu

What version of RAIDiator is on the unit? You can check via

# cat /var/log/raidiator_version
Message 4 of 12
buchhla
Aspirant

Re: update firmware via ssh? Case #19355863

I am on 5.3.5. Yes, I have tried os reinstall, and no change.
Message 5 of 12
mdgm-ntgr
NETGEAR Employee Retired

Re: update firmware via ssh? Case #19355863

Any add-ons installed?
Message 6 of 12
buchhla
Aspirant

Re: update firmware via ssh? Case #19355863

no. I did have readynas photos installed when I was back on 5.3.4, but I think it broke when I upgraded to 5.3.5. I was only using it for mysql though. outside of that, it was stock. Just had CIFS/AFP enabled and that was it.
Message 7 of 12
mdgm-ntgr
NETGEAR Employee Retired

Re: update firmware via ssh? Case #19355863

If you like try:

# cd /tmp
# wget http://www.readynas.com/download/RAIDiator-arm/5.3.6/RAIDiator-arm-5.3.6
# echo /tmp/RAIDiator-arm-5.3.6 > /.cf_update_in_progress
# reboot
Message 8 of 12
buchhla
Aspirant

Re: update firmware via ssh? Case #19355863

Thanks, I will give that a try in the morning and let you know what I find... My batteries are down because it has been cloudy all day and I run the entire system off of solar.
Message 9 of 12
buchhla
Aspirant

Re: update firmware via ssh? Case #19355863

That worked! Thanks a ton, not sure what was wrong before, and the log files all look pretty much the same, but the update fixed everything, including mysql!
Message 10 of 12
chirpa
Luminary

Re: update firmware via ssh? Case #19355863

Did support ever get back to you?
Message 11 of 12
buchhla
Aspirant

Re: update firmware via ssh? Case #19355863

nope. We did a few rounds of back and forth, but nobody seemed to have any ideas. MDGM's update visa SSH did fix it though.
Message 12 of 12
Top Contributors
Discussion stats
  • 11 replies
  • 7645 views
  • 1 kudo
  • 3 in conversation
Announcements