No GUI after update from 6.1.9 to 6.2.0 #24266805

[Toskache]

After the update to 6.2.0 the GUI is not available any more.
SSH works. I did a

nmap localhost

with the following result:

root@NAS:/var/log# nmap localhost

Starting Nmap 6.00 ( http://nmap.org ) at 2014-11-26 21:52 CET
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000038s latency).
Other addresses for localhost (not scanned): 127.0.0.1
Not shown: 991 closed ports
PORT STATE SERVICE
22/tcp open ssh
53/tcp open domain
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
548/tcp open afp
2049/tcp open nfs
3306/tcp open mysql
3493/tcp open nut

Nmap done: 1 IP address (1 host up) scanned in 0.34 seconds

So there is no service on port 80 or 443. Than I tried to restart apache with

/etc/init.d/apache2 start

And I get

root@NAS:/var/log# /etc/init.d/apache2 start
[....] Starting apache2 (via systemctl): apache2.serviceJob failed. See system journal and 'systemctl status' for details.
failed!

So apache is not able to start. But why? Any suggestions?

[vandermerwe]

Have you contacted support?
Do you have any apps on the nas?
What happens when you try to access the GUI using https://ipaddressofnas ?
Can you access shares?

Do you have a backup?

[Toskache]

All shares are accessible, so I am not in big trouble. 😉
I have no other "apps" on the NAS.
NAS is full with 10TB, and it is my backup.

As I have described it: There is no service for Port 80. So I get a connection error in the browser.
Support is not involved, yet.

[vandermerwe]

While you wait for further advice here, you have nothing to lose by filling in an online support request form. Netgear need to know about these problems too.

[Toskache]

OK, I will do that!

[Toskache]

Toskache wrote:
OK, I will do that!

Done. 😉

[vandermerwe]

Add the case number to the thread title.

[mdgm-ntgr]

# df -h
# btrfs fi show
# btrfs fi df /data
# systemctl status apache2
# systemctl status readynasd
# journalctl -a | grep readynasd | tail -n 20
# journalctl -a | grep apache2 | tail -n 20
# systemctl restart apache2
# journalctl -a | grep apache2

[Toskache]

journalctl -a | grep apache2 | tail -n 20

There was a web server config using a share as document-root which I had removed a few weeks ago.
So the config was broken. A restart under 6.1.9 would have caused the same error. It is NOT a bug in 6.2.0. it was a bug in my brain.

Thank you for the support!

PS: I will close the support-case also!

[vandermerwe]

Good that it's fixed.
I had not realised that you are running OS6 on an ultra. I suspect support would not have helped you. Although this is your backup, it's a lot of data, is it worth running OS6? You may not get out of a situation like this so easily in future. It will happen.