Reply
Highlighted
Aspirant

Can't connect to admin page (RN104 beta 10 6.2.3)

Can't connect dashboard, only progress bar and "Connecting......"
Message 1 of 16
Highlighted
Aspirant
Aspirant

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

I had same issue with the new Beta, I am rolling back to 6.2.2. I had the same issue for both 6.2.3 and 6.3.3 beta 10

_J_
Message 2 of 16
Highlighted
NETGEAR Employee Retired

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

Do you have SSH access?

If so, so some details from that as to why you are having this problem would be helpful.

If not, I could take a look.
Message 3 of 16
Highlighted
Aspirant

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

Yes, I have SSH access.
Message 4 of 16
Highlighted
NETGEAR Employee Retired

Re: Can't connect to admin page (RN104 beta 10 6.2.3)


# systemctl status -a readynasd
# systemctl status -a apache2
# journalctl -a | grep readynasd | tail -n 20
# journalctl -a | grep apache2 | tail -n 20
Message 5 of 16
Highlighted
Aspirant

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

systemctl status -a readynasd
root@FILESERVERX:~# systemctl status -a readynasd
readynasd.service - ReadyNAS System Daemon
Loaded: loaded (/lib/systemd/system/readynasd.service; enabled)
Active: activating (start) since Wed, 18 Mar 2015 16:40:58 +0400; 8s ago
Main PID: 12028 (readynasd)
Status: "Importing DB"
CGroup: name=systemd:/system/readynasd.service
└ 12028 /usr/sbin/readynasd -v 3 -t

Mar 18 16:40:58 FILESERVERX readynasd[12028]: readynasd log started
Mar 18 16:40:58 FILESERVERX readynasd[12028]: readynasd started. (restarted=0)
Mar 18 16:40:58 FILESERVERX readynasd[12028]: DB (main) schema version: 17 ==> 17
Mar 18 16:40:58 FILESERVERX readynasd[12028]: DB (queue) schema version: new ==> 0


systemctl status -a apache2
root@FILESERVERX:~# systemctl status -a apache2
apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled)
Active: active (running) since Wed, 18 Mar 2015 12:45:24 +0400; 3h 59min ago
Process: 1682 ExecStart=/usr/sbin/apache2 $OPTIONS -k start (code=exited, status=0/SUCCESS)
Process: 1151 ExecStartPre=/frontview/bin/fvapps (code=exited, status=0/SUCCESS)
Main PID: 1706 (apache2)
CGroup: name=systemd:/system/apache2.service
├ 1706 /usr/sbin/apache2 -k start
├ 1707 apache_log
├ 1769 /usr/sbin/apache2 -k start
├ 1771 /usr/sbin/apache2 -k start
├ 1772 /usr/sbin/apache2 -k start
├ 1774 /usr/sbin/apache2 -k start
├ 3035 /usr/sbin/apache2 -k start
├ 4298 /usr/sbin/apache2 -k start
├ 4322 /usr/sbin/apache2 -k start
├ 4331 /usr/sbin/apache2 -k start
├ 4332 /usr/sbin/apache2 -k start
├ 6066 /usr/sbin/apache2 -k start
└ 6165 /usr/sbin/apache2 -k start

Mar 18 12:58:11 FILESERVERX apache_access[1707]: 192.168.1.34 "POST /fsbroker/ HTTP/1.1" 200
Mar 18 12:58:11 FILESERVERX apache2[6066]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[6066]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache_access[1707]: 192.168.1.34 "POST /dbbroker HTTP/1.1" 500
Mar 18 12:58:11 FILESERVERX apache_access[1707]: 192.168.1.34 "POST /fwbroker HTTP/1.1" 200
Mar 18 12:58:11 FILESERVERX apache2[1772]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[1772]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache_access[1707]: 192.168.1.34 "POST /dbbroker HTTP/1.1" 500
Mar 18 12:58:11 FILESERVERX apache2[6165]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[6165]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
root@FILESERVERX:~#


journalctl -a | grep readynasd | tail -n 20
root@FILESERVERX:~# journalctl -a | grep readynasd | tail -n 20
Mar 18 16:45:51 FILESERVERX readynasd[13541]: dba import failed
Mar 18 16:45:51 FILESERVERX systemd[1]: readynasd.service: main process exited, code=exited, status=255
Mar 18 16:45:51 FILESERVERX systemd[1]: Unit readynasd.service entered failed state.
Mar 18 16:45:51 FILESERVERX systemd[1]: readynasd.service holdoff time over, scheduling restart.
Mar 18 16:45:51 FILESERVERX readynasd[13616]: readynasd log started
Mar 18 16:45:51 FILESERVERX readynasd[13616]: readynasd started. (restarted=0)
Mar 18 16:45:51 FILESERVERX readynasd[13616]: DB (main) schema version: 17 ==> 17
Mar 18 16:45:51 FILESERVERX readynasd[13616]: DB (queue) schema version: new ==> 0
Mar 18 16:46:05 FILESERVERX readynasd[13616]: Unknown driver nutdrv_atcl_usb
Mar 18 16:46:05 FILESERVERX readynasd[13616]: rndb_ups_import() ==> 1 (3ms)
Mar 18 16:46:05 FILESERVERX readynasd[13616]: rndb_import() ==> 1 (14026ms)
Mar 18 16:46:05 FILESERVERX readynasd[13616]: Error rndb_import() ==> rc=1
Mar 18 16:46:05 FILESERVERX readynasd[13616]: dba import failed
Mar 18 16:46:05 FILESERVERX systemd[1]: readynasd.service: main process exited, code=exited, status=255
Mar 18 16:46:05 FILESERVERX systemd[1]: Unit readynasd.service entered failed state.
Mar 18 16:46:05 FILESERVERX systemd[1]: readynasd.service holdoff time over, scheduling restart.
Mar 18 16:46:05 FILESERVERX readynasd[13690]: readynasd log started
Mar 18 16:46:05 FILESERVERX readynasd[13690]: readynasd started. (restarted=0)
Mar 18 16:46:05 FILESERVERX readynasd[13690]: DB (main) schema version: 17 ==> 17
Mar 18 16:46:05 FILESERVERX readynasd[13690]: DB (queue) schema version: new ==> 0
root@FILESERVERX:~#


journalctl -a | grep apache2 | tail -n 20
root@FILESERVERX:~# journalctl -a | grep apache2 | tail -n 20
Mar 18 12:58:11 FILESERVERX apache2[4331]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[4331]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[1773]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[1773]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[1771]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[1771]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[4332]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[4332]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[4322]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[4322]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[4298]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[4298]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[3035]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[3035]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[6066]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[6066]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[1772]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[1772]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[6165]: [error] [client 192.168.1.34] Connect rddclient failed, referer: https://192.168.1.37/admin/
Mar 18 12:58:11 FILESERVERX apache2[6165]: [error] [client 192.168.1.34] Premature end of script headers: dbbroker.cgi, referer: https://192.168.1.37/admin/
root@FILESERVERX:~#
Message 6 of 16
Highlighted
NETGEAR Employee Retired

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

Nick19007 wrote:


Mar 18 16:46:05 FILESERVERX readynasd[13616]: Unknown driver nutdrv_atcl_usb
Mar 18 16:46:05 FILESERVERX readynasd[13616]: rndb_ups_import() ==> 1 (3ms)
Mar 18 16:46:05 FILESERVERX readynasd[13616]: rndb_import() ==> 1 (14026ms)
Mar 18 16:46:05 FILESERVERX readynasd[13616]: Error rndb_import() ==> rc=1
Mar 18 16:46:05 FILESERVERX readynasd[13616]: dba import failed
Mar 18 16:46:05 FILESERVERX systemd[1]: readynasd.service: main process exited, code=exited, status=255
Mar 18 16:46:05 FILESERVERX systemd[1]: Unit readynasd.service entered failed state.
Mar 18 16:46:05 FILESERVERX systemd[1]: readynasd.service holdoff time over, scheduling restart.


There is a fix for this problem coming in the next 6.2.3 build.
Message 7 of 16
Highlighted
Aspirant

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

Watch out for firmware updates and install beta 11 ?
Message 8 of 16
Highlighted
NETGEAR Employee Retired

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

Message 9 of 16
Highlighted
Aspirant

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

Many thanks, will report how will the update.
Message 10 of 16
Highlighted
NETGEAR Employee Retired

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

In the meantime you may wish to disconnect the USB cable from the UPS temporarily and enter these commands:

# echo > /etc/nut/ups.conf
# systemctl restart readynasd
Message 11 of 16
Highlighted
Aspirant

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

I don't have SSH to mine, not sure what to do.

 

I can ftp and connect using windows explorer but I cannot access the web interface page.

Message 12 of 16
Highlighted
Guru

Re: Can't connect to admin page (RN104 beta 10 6.2.3)


@A2D2RAS wrote:

I don't have SSH to mine, not sure what to do.

 

I can ftp and connect using windows explorer but I cannot access the web interface page.


You can contact support.  If you were affected by the 6.2.2 uninstall bug they should fix it for free.  Otherwise they will charge.

 

If you want to avoid contacting support, you can back up your data to an external drive.  

 

From there you can do a factory reset, and restore your data from backup.  There is also a trick you can try if you have a scratch disk handy, but you should make the backup first.

 

Message 13 of 16
Highlighted
Aspirant

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

I have 4 hard drives in there, can I just take them out reset the NAS then put the 4 hard drives back in?

 

Mine is a RN31400, not sure what version firmware it is running..

Message 14 of 16
Highlighted
Guru

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

You can reset the NAS with the drives in, but you will lose all the data.

 

The OS is on the disks, so it is impossible to reset the NAS with the drives out.

 

RAIDar should be able to tell you the firmware version.

Message 15 of 16
Highlighted
Aspirant

Re: Can't connect to admin page (RN104 beta 10 6.2.3)

Installed the app and it is in fact 6.2.2

 

Thank you so much StephenB

Message 16 of 16
Discussion stats
  • 15 replies
  • 5422 views
  • 1 kudo
  • 5 in conversation
Announcements