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.
After update to 6.6.0, can't access anything on Admin page
After updating my ReadyNAS 2100 from firmware 6.5.1 to 6.6.0 this morning, I can no loger access anything on the admin page. IF I can get the admin page to load after login, the page is blank. If I click a tab (Shares for example), it will try to load the page for a couple of minutes then try to reconnect to the admin page (Connecting to the ReadyNAS Admin Page...). Nothing ever comes up. I have tried Firefox and IE11. I have rebooted the NAS via the admin page (which I can still do and seems to be the only thing that works after the upgrade) and cycled the power as well. Nothing seems to help. I can connect to each of the networks shares on the NAS via Windows Explorer so I know something is working properly. Everything was working fine before the update. Anyone else have this issue or a possible solution?
I have 4 more ReadyNAS devices deployed accross my network at remote sites and this makes me very hesitant to update to 6.6.0 on any of those devices.
Re: After update to 6.6.0, can't access anything on Admin page
Hi guys, just an update here. The issue I had after the 6.6.0 update turned out to be a permissions issue with the ReadyNAS users. Apparently there were some orphaned accounts (ui's as the tech called them) created by the ReadyNAS OS (which I still don't understand how), but 2 1/2 hours with support fixed the issue. Just as a side note, I had the exact same issue on the same device when I did the update to 6.5.1 some time back. Again, support fixed that issue as well, so I'm still confused as to how this could happen again when no changes have been made since the last firmware update. Wish I could give a little more info on this, but the technician closed the chat log before I got a chance to copy it for my records. Thanks to all who posted replys to this thread.
Re: After update to 6.6.0, can't access anything on Admin page
No and no.
As I stated, everything was fine until the 6.6.0 update this morning. I can still access the network shares via Windows Explorer, it's just the Admin page that won't work. IF I can get past the splash screen, everything is blank. For the most part it just sits at the splash screen for 4 -5 minutes then tries to reconnect to the admin page. Once it starts that, all I can do is a power cycle to get past it. Only then will it allow me to the actual admin screen, but nothing can be done once there (except reboot). If I try to access another section of the admin page, it will just spin until it times out. At that point if will try to reconnect to the admin page again. Once finished with that, it displays the splash screen until it tries to reconnect to the splash screen again. It's like an indefinite loop....splash screen, reconnect, splash screen, reconnect...
Re: After update to 6.6.0, can't access anything on Admin page
There are three basic causes for the behavior you are getting:
-Some corruption in the OS partition
-a filling OS partition
-a process running on the NAS that is hogging the CPU
the Web UI runs at a lower priority than SMB access (which is why the third option generally affects the Web UI most).
I'd suggest Netgear support on this (without ssh there's not a lot of options). If you are the original purchaser, and bought the NAS between 1 June 2014 and 31 May 2016 then you have lifetime chat support.
Re: After update to 6.6.0, can't access anything on Admin page
I have the same problem on RN104 16TB, I cannot access admin page after 6.6.0.
I have read that taking out drives and lableing them then rebboting with another scratch drive and doing afactory reset may solve the problem but I think if the drives were put back in wouldn't they just revert back to the operating system that is on them. I am not sure if it would wipe all the disks and reformat. I also do not have SSH turned on, although I can access the shares.
Re: After update to 6.6.0, can't access anything on Admin page
Hi guys, just an update here. The issue I had after the 6.6.0 update turned out to be a permissions issue with the ReadyNAS users. Apparently there were some orphaned accounts (ui's as the tech called them) created by the ReadyNAS OS (which I still don't understand how), but 2 1/2 hours with support fixed the issue. Just as a side note, I had the exact same issue on the same device when I did the update to 6.5.1 some time back. Again, support fixed that issue as well, so I'm still confused as to how this could happen again when no changes have been made since the last firmware update. Wish I could give a little more info on this, but the technician closed the chat log before I got a chance to copy it for my records. Thanks to all who posted replys to this thread.
Re: After update to 6.6.0, can't access anything on Admin page
Thank you for your help. I see Remote support in the RAIDar application is it correct? How to close the support session? Everything seems to be working now. Regards,
Thank you for your help. I see Remote support in the RAIDar application is it correct? How to close the support session? Everything seems to be working now. Regards,
You can disable it from the GUI -- System -> Settings -> Support, uncheck Secure Diagnostic Mode.
root@nas-ag1:~# uname -a Linux nas-ag1 4.1.30.alpine.1 #1 SMP Thu Sep 22 16:34:49 PDT 2016 armv7l GNU/Linux
2.) My problem was that Apache2 wasn't running
root@nas-ag1:~# systemctl start apache2 Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.
root@nas-ag1:~# systemctl status apache2.service ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2016-10-15 11:26:38 CEST; 27s ago Process: 7320 ExecStart=/usr/sbin/apache2 $OPTIONS -k start (code=exited, status=203/EXEC) Process: 7244 ExecStartPre=/frontview/bin/fvapps (code=exited, status=0/SUCCESS) Main PID: 2300 (code=exited, status=0/SUCCESS)
Oct 15 11:26:38 nas-ag1 systemd[1]: Starting The Apache HTTP Server... Oct 15 11:26:38 nas-ag1 systemd[7320]: apache2.service: Failed at step EXEC spawning /usr/sbin/apache2: No such file or dire ctory Oct 15 11:26:38 nas-ag1 systemd[1]: apache2.service: Control process exited, code=exited status=203 Oct 15 11:26:38 nas-ag1 systemd[1]: Failed to start The Apache HTTP Server. Oct 15 11:26:38 nas-ag1 systemd[1]: apache2.service: Unit entered failed state. Oct 15 11:26:38 nas-ag1 systemd[1]: apache2.service: Triggering OnFailure= dependencies. Oct 15 11:26:38 nas-ag1 systemd[1]: apache2.service: Failed with result 'exit-code'.
root@nas-ag1:~# ls -lisa /usr/lib/apache2/mpm-worker/ total 8 7326 4 drwxr-xr-x 2 root root 4096 Sep 23 20:36 . 5908 4 drwxr-xr-x 5 root root 4096 Oct 15 11:14 ..
=> Therefore there was no file for Apache2 service to start, however, regardless proper APT package (apache2-mpm-worker) was installed.
root@nas-ag1:~# dpkg --list | grep apache2 ii apache2 2.2.31-0.netgear2 armel Apache HTTP Server metapackage ii apache2-mpm-worker 2.2.31-0.netgear2 armel Apache HTTP Server - high speed threaded model ii apache2-utils 2.4.10-10+deb8u7 armel Apache HTTP Server (utility programs for web servers) ii apache2.2-bin 2.2.31-0.netgear2 armel Apache HTTP Server common binary files ii apache2.2-common 2.2.31-0.netgear2 armel Apache HTTP Server common files ii libapache2-mod-auth-token 1.0.6 armel mod_auth_token is a famous apache module that allows you to rc libapache2-mod-authnz-external 3.2.6-1.netgear1 armel authenticate Apache against external authentication services ii libapache2-mod-authz-unixgroup 1.0.3-1.netgear2 armel access control based on on unix group membership for Apache
3.) I tried re-installing both apache2 and apache2-mpm-worker.
Same result.
It's also interesting, that there is apache2 binary for prefork apache alternative (regardless the prefork is not installed)
root@nas-ag1:/usr/lib/apache2/mpm-prefork# ls -lisa /usr/lib/apache2/mpm-prefork total 372 5909 4 drwxr-xr-x 2 root root 4096 Oct 15 10:30 . 5908 4 drwxr-xr-x 5 root root 4096 Oct 15 11:14 .. 7230 364 -rwxr-xr-x 1 root root 368828 Sep 23 20:54 apache2
4.) Anyway, the missing file should come from APT package apache2.2-bin:
