NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Web interface stops responding after a while
I have a ReadyNas Duo
Name: RAIDiator
Version: 4.1.7
Date: Sat Nov 6 00:09:53 2010
(actually, I have two, at different locations, on different networks).
I have noticed that after some time (not sure how long, maybe hours or days) I get no response when trying to log in to the web interface on either box. I've tried it from various PCs and different browsers.
I can ping the NAS box successfully (it has a static IP address) and I can still access the shares from windows and I can still stream media no problem. Same goes for the other NAS box.
Just can't access the web interface.
If I hold the blue button on the front to restart the box, once it stops flashing, the web interface works again. For a while.
It seems the web server goes to sleep after a while and stops responding. The firmware is nearly a year old. Perhaps there should be an update due out by now that might fix this problem.
Is this a known problem?
Brian
Name: RAIDiator
Version: 4.1.7
Date: Sat Nov 6 00:09:53 2010
(actually, I have two, at different locations, on different networks).
I have noticed that after some time (not sure how long, maybe hours or days) I get no response when trying to log in to the web interface on either box. I've tried it from various PCs and different browsers.
I can ping the NAS box successfully (it has a static IP address) and I can still access the shares from windows and I can still stream media no problem. Same goes for the other NAS box.
Just can't access the web interface.
If I hold the blue button on the front to restart the box, once it stops flashing, the web interface works again. For a while.
It seems the web server goes to sleep after a while and stops responding. The firmware is nearly a year old. Perhaps there should be an update due out by now that might fix this problem.
Is this a known problem?
Brian
22 Replies
Replies have been turned off for this discussion
- Try to perform an OS re-install. Please follow the steps below:
http://www.readynas.com/?page_id=5029 - Thanks, I've looked over the relevant document after you kindly pointed it out to me.
I shall do a bit more diagnosis and try the o/s reinstall if the problem recurs. - You are welcome! You may also try conctacting support if the problem will still persist.
- Brian,
My ReadyNAS Duo has the same problem - at seemingly random intervals, the web server stops responding. It's been doing this for months. Presumably, the web process has died. A reboot of the Duo restores the web server, until it dies again.
When the web server (ie FrontView) is not responding, the unit's file shares are still available, and the SSH daemon is active. I'm wondering if I can SSH into the box and restart the web process via terminal commands. That would be less disruptive than rebooting.
I am very hesitant to reinstall the firmware nd risk loss of all my data, and/or have to reconfigure the system from scratch. - A simple way to restart the web server in case it crashed is to disconnect the network cable and reconnect it after some seconds. This should trigger a restart of the web server. Of course you can also try to restart from an SSH shell using the command
apache-ssl -f /etc/frontview/apache/httpd.conf -k restart
-Stefan - @Stefan,
Danke!
I had no idea that disconnect/reconnecting the LAN cable would restart anything.
I will file away your tips for future reference, and try them the next time my apache dies. I also followed your link to your project downloads. Lots of neat stuff, which I will have to explore when I get some time.
Dave - I guess the major reason for restarting not only the web server but some other stuff as well after loss and regaining of network connectivity is that the IP address might have changed. So it makes a lot of sense to automatically restart dependent services - and that's what the network hotplug script does, at least last time i looked ;)
-Stefan - @Stephan,
Thanks for the explantion about the hotplug. Makes sense.
My apache process conked out again yesterday - that's the 3rd time in a week. Your shell command restarted it successfully :-)
I looked at the httpd error log to see if I could determine why it is crashing. As best as I can tell (and I know very little about Linux), it appears that somebody is sending it a SIGTERM.[Fri Sep 02 08:33:29 2011] [notice] caught SIGTERM, shutting down
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
I looked back in the log: every instance of the SIGTERM notice is followed by 2 or more of the Bad free() messages. Any suggestions what other logs I might look at to figure out why it's getting killed?
Danke. - I don' t know where the SIGTERM comes from but I would assume it's from some scheduled process. So you might want to check cron.log as well as system.log and messages but I fear the won't be much useful info in there. As for the bad frees: I noticed them, too. I believe it started somewhere around 4.2.17 but since they're all happening in the encrypted perl library for Frontview functions there's no way to debug those.
-Stefan - FWIW, I upgraded my Duo from 4.1.7 to 4.1.8 last week, and since then the apache process has been rock solid. I have not had to restart it since the upgrade. This may be purely coincidence, or it may be that a latent bug in Radiator that affected the apache process was fixed in 4.1.8
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
