Reboot kills Web UI. Full shutdown, power-down and power-up brings it back to life?

Reboot kills Web UI. Full shutdown, power-down and power-up brings it back to life?

The reason I did the reboot is because the drive stopped going to sleep (aquired a system log dump from the Web UI’s support page before the reboot) and yet again on reboot the Web UI died but because I got SSH enabled I used Linux’s shutdown command to shutdown the operating system, halt and power-down so I have not simply yanked out the power.

Removed power and reapplied, My MBL has started uo and the Web UI is functional.

Why did the Web UI vanish?

The MBL has a reserved IP on the router so the NAS’s IP address won’t suddenly change to another IP  so it can’t be that.

Something I did notice.  In user.log what is the REST API error?  That happened after reboot.  Notice that logging of the drive sleeping and waking up had totally stopped.

NAS:/var/log# tail -n 70 user.logSep 14 23:13:11 localhost logger: exit standby after 1351Sep 14 23:24:18 localhost logger: Enter standbySep 15 00:17:52 localhost logger: exit standby after 3214Sep 15 00:36:01 localhost logger: Enter standbySep 15 00:44:49 localhost logger: exit standby after 528Sep 21 11:23:29 localhost apache2: 172.16.0.1 WebUI::session_start()Sep 21 11:23:29 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:23:30 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:24:55 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:26:55 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:26:55 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:28:44 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:29:18 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:29:22 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:30:52 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:30:57 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:31:33 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:31:42 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:32:57 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:33:46 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 21 11:33:47 localhost apache2: 172.16.0.1 WebUI::session_id=fc60117bc4fe4daa1c88d9b37fe06089Sep 23 17:57:09 localhost apache2: 172.16.0.1 WebUI::session_start()Sep 23 17:57:09 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 17:58:36 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 17:59:25 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:00:36 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:00:36 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:00:49 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:03:08 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:03:08 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:03:27 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:04:06 localhost shutdown[23445]: shutting down for system rebootSep 23 18:04:27 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:04:33 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:04:39 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:04:41 localhost logger: Wait for system ready - skipping start of forked-daapd service..Sep 23 18:04:43 localhost logger: Wait for system ready - skipping start of orion services..Sep 23 18:04:49 localhost logger: /etc/rc.local: currentRootDevice = /dev/md1Sep 23 18:04:52 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:04:58 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:05:03 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:05:09 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:05:12 localhost logger: Starting orion services: miocrawlerd, mediacrawlerd, communicationmanagerdSep 23 18:05:12 localhost logger: WD NAS: Email alerts REST API failed to return SuccessSep 23 18:14:33 localhost shutdown[7410]: shutting down for system haltSep 23 18:19:25 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:19:30 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:19:37 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:19:38 localhost logger: Wait for system ready - skipping start of forked-daapd service..Sep 23 18:19:41 localhost logger: Wait for system ready - skipping start of orion services..Sep 23 18:19:45 localhost logger: /etc/rc.local: currentRootDevice = /dev/md1Sep 23 18:19:49 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:19:55 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:20:01 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:20:06 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready..Sep 23 18:20:07 localhost logger: Starting orion services: miocrawlerd, mediacrawlerd, communicationmanagerdSep 23 18:20:10 localhost logger: WD NAS: Email alerts sent OKSep 23 18:20:34 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:30:53 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:31:09 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:33:09 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:33:09 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:35:10 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:35:39 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:37:11 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:37:53 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:38:45 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:39:12 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:40:07 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7Sep 23 18:41:13 localhost apache2: 172.16.0.1 WebUI::session_id=cdfb6eb3ac91b9e42b55f52e9991bba7

(My advise to everyone who get a MyBook Live is to enable SSH access irrespective of if you’ll use it or not. By all means change the root account password from welc0me to something else if security is a bit of an issue, as it it for me.)

I’ll try to replicate this on mine.

No issues on mine…  I had to reboot mine twice yesterday for unrelated reasons and didn’t have any problems with the UI either time.

Strange. And internally nothing has been done that could make the Apache2 to fail. Can still access the NAS by SSH so it has correctly acquired the IP address from the router and it will always obtain the same IP address. I thought it was a fault with the previous version.

This started to happen when Western Digital decided to forbid access to the Web UI from outside of the local subnet. That I am sure of.