Topic: 502 bad gateway, whenever using server-manager through https

[csj_84]

with the topic suggested, i tried to restart the apache server

Code: [Select]

/etc/init.d/httpd restart

but only to get

Code: [Select]

Stopping httpd:                                            [  OK  ]
Starting httpd: (98)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]

so, what will be the solution?

it happened after i installed smeserver-userpanel through:

Code: [Select]

yum --enablerepo=smedev install smeserver-userpanel
given in http://forums.contribs.org/index.php?topic=35530.0

[cactus]

with the topic suggested, i tried to restart the apache server

Code: [Select]

/etc/init.d/httpd restart

but only to get

Code: [Select]

Stopping httpd:                                            [  OK  ]
Starting httpd: (98)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]

so, what will be the solution?

it happened after i installed smeserver-userpanel through:

Code: [Select]

yum --enablerepo=smedev install smeserver-userpanel
given in http://forums.contribs.org/index.php?topic=35530.0

It seems you have some problem with the httpd daemon. A reboot should fix this the easiest way I think as to me it seems to be a problem with lock files. There has been a script in the forums, bugtracker or wiki but I think a reboot should also fix this.

[raem]

csj_84

> /etc/init.d/httpd restart

wrong command, try
/etc/rc7.d/S86httpd-e-smith restart
/etc/rc7.d/S86httpd-admin restart

[william_syd]

There has been a script in the forums, bugtracker or wiki but I think a reboot should also fix this.

http://forums.contribs.org/index.php?topic=33171.0

[csj_84]

i've tried restarting the server, with:

Code: [Select]

signal-event post-upgrade; signal-event reboot
it still produces the same result - 443 port used (even though port numbers changed to 60000, 1024, and 10001)
does it have to do with upgrading the smeserver-userpanel (from smedev) and the removal of e-smith-userpanel?

[cactus]

i've tried restarting the server, with:

Code: [Select]

signal-event post-upgrade; signal-event reboot
it still produces the same result - 443 port used (even though port numbers changed to 60000, 1024, and 10001)
does it have to do with upgrading the smeserver-userpanel (from smedev) and the removal of e-smith-userpanel?

It could be... I think you should file it as a bug in the bugtracker against the smeserver-userpanel contrib. Perhaps the author of the contrib can help.

[william_syd]

Can someone explain this ?

(even though port numbers changed to 60000, 1024, and 10001)

[csj_84]

Can someone explain this ?

(even though port numbers changed to 60000, 1024, and 10001)

i tried to change the listening port number for ssl from 0.0.0.0:443 to 0.0.0.0:60000, 0.0.0.0:1024, and 0.0.0.0:10001 then restart httpd every time changes took place.

and yet, these numbers are occupied, which puzzled me

Code: [Select]

Stopping httpd:                                            [  OK  ]
Starting httpd: (98)Address already in use: make_sock: could not bind to address
 0.0.0.0:60000
no listening sockets available, shutting down
Unable to open logs
                                                           [FAILED]

Code: [Select]

Stopping httpd:                                            [  OK  ]
Starting httpd: (98)Address already in use: make_sock: could not bind to address
 0.0.0.0:10001
no listening sockets available, shutting down
Unable to open logs
                                                           [FAILED]

Code: [Select]

Stopping httpd:                                            [  OK  ]
Starting httpd: (98)Address already in use: make_sock: could not bind to address
 0.0.0.0:1024
no listening sockets available, shutting down
Unable to open logs
                                                           [FAILED]

[william_syd]

Unable to open logs

Did you check out what Cactus  said before and the link I posted?

Do they apply in any way?

[csj_84]

william_syd, cactus, i have both smeserver-userpanel and smeserver-userpanels installed.

I suspect both might caused conflict to the server, which returns 502 error.

So i've tried remove smeserver-userpanel, and it prompt me to key in username & password, then return 500 error (Internal Server Error).

so, guys, what's your opinion?

[william_syd]

Check your httpd logs ?
Remove both and see if server-manager works ?

[csj_84]

where is the httpd server log?

btw, both smeserver-userpanel & smeserver-userpanels i'd removed, but still error 500 continue to appear.

[william_syd]

where is the httpd server log?

/var/log/httpd

[cactus]

btw, both smeserver-userpanel & smeserver-userpanels i'd removed, but still error 500 continue to appear.

Look in the /var/log/messages file at the time the 500 error occured. See what information is in there and if you can not understand post the snippet here so we can help you.

[csj_84]

I installed smeserver-phpmyadmin (a contrib by dmay), contrary to server-manager, it can be accessed (with SSL).

server-manager is still giving error 500 message