It was mini-bug in pre-release and it will be fixed for official release. Please run from UNIX shell "svcadm enable -rs apache2" and try again.

So, I'll ask again in this thread.

Why is the 'testing' repository updating me to alpha software?

Setup appliance upgrade brought me up to 3.0.4, which according to the front page it's alpha stage.

I have the same issue after upgrading today. running "svcadm enable -rs apache2" from the unix shell did not do anything immediately or after a restart.

that command fixed it for me, you have to be in a !bash shell, not the nmc shell they stick you into at first.

this worked perfectly for me after i got into the !bash shell. for those of you that are unaware of how to get to the bash shell you just do this:

https://www.nexenta.com/corp/component/option,com_fireboard/Itemid,44/func,view/id,43/catid,8/

Just in case anyone is wondering (since I ran into this issue for a bit)

To get bash shell

Login as the admin user (instead of root) and then su

That'll give you bash shell.

[WARNINGS]
link-id not found -  jul 26 12:29:09 enabled. 

I have run command "svcadm enable -rs apache2" , however, apache2 posted the following error:

[ Jul 26 12:29:09 Leaving maintenance because clear requested. ] [ Jul 26 12:29:09 Enabled. ] [ Jul 26 12:29:09 Executing start method ("/lib/svc/method/apache2 start"). ] Starting web server: apache2apache2: Could not reliably determine the server's fully qualified domain name, using 192.168.1.3 for ServerName (125)Address already in use: make_sock: could not bind to address [::]:443 (125)Address already in use: make_sock: could not bind to address 0.0.0.0:443 no listening sockets available, shutting down Unable to open logs failed! [ Jul 26 12:29:09 Method "start" exited with status 95. ]

[WARNINGS]
link-id not found -  jul 26 12:29:09 enabled. 

Konstantin Borovik wrote:

I have run command "svcadm enable -rs apache2" , however, apache2 posted the following error:

[ Jul 26 12:29:09 Leaving maintenance because clear requested. ] [ Jul 26 12:29:09 Enabled. ] [ Jul 26 12:29:09 Executing start method ("/lib/svc/method/apache2 start"). ] Starting web server: apache2apache2: Could not reliably determine the server's fully qualified domain name, using 192.168.1.3 for ServerName (125)Address already in use: make_sock: could not bind to address [::]:443 (125)Address already in use: make_sock: could not bind to address 0.0.0.0:443 no listening sockets available, shutting down Unable to open logs failed! [ Jul 26 12:29:09 Method "start" exited with status 95. ]

Can you please post here the content of /etc/apache2/ports.conf file

Pavel,

I have reverted to 3.0.3 and cannot easily reboot backup into 3.0.4. Can I mount checkpoint and read file from there?

Nexenta 3.0.3 does not require apache2 to run HTTP Web GUI. Why in 3.0.4 I need to run apache2 to get HTTP web GUI working?

Konstantin Borovik wrote:

Pavel,

I have reverted to 3.0.3 and cannot easily reboot backup into 3.0.4. Can I mount checkpoint and read file from there?

Nexenta 3.0.3 does not require apache2 to run HTTP Web GUI. Why in 3.0.4 I need to run apache2 to get HTTP web GUI working?

You can post the file from 3.0.3 too. In such case the current version make no sence.

About Apache2. It works great in 3.0.4, increase perfomance and major improvement - 100% stable HTTPS. That why we are using it.

root@storage:/volumes# cat /etc/apache2/ports.conf

Listen 443 Listen 443 root@storage:/volumes#

Screenshot.

Konstantin Borovik wrote:

root@storage:/volumes# cat /etc/apache2/ports.conf

Listen 443 Listen 443 root@storage:/volumes#

Run from NMC: "setup network service webdav-server configure" and disable secure HTTP. Then upgrade to 3.0.4, enable the Apache2 service from UNIX shell and go back to NMC to enable secure HTTP. After that you can use NMV.

Works. Thank you very much.

I'm having a similar problem, except while debugging i did a2dissite nmd-something

apparently that site's not in available-sites so i can't re enable it =/