Koozali.org: home of the SME Server

Broken Server-manager panel

Syl20

Broken Server-manager panel
« on: July 23, 2003, 08:48:34 PM »
Please after doing this

[root@sme /]# mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/
[root@sme /]# pico -w /etc/e-smith/templates/custom/etc/httpd/conf/httpd.conf/98Sherpath

[root@sme Sherpath]# /sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf
[root@sme Sherpath]# service httpd restart
Stopping httpd:                                            [   OK   ]
Starting httpd:                                            [   OK   ]
[root@sme Sherpath]#

My server-manager is actually broken

I get this message

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /server-manager.

Reason: Could not connect to remote machine: Connection refused


Please I need help to repair server-manager

Syl20

Re: Broken Server-manager panel
« Reply #1 on: July 23, 2003, 10:46:18 PM »
OK I realise I forgot to do this

/etc/rc.d/init.d/httpd-admin restart

I'm OK now

Thanx

Krusty

Re: Broken Server-manager panel
« Reply #2 on: July 24, 2003, 11:06:14 AM »
doesn't it feel good when you fix your own problems

Kai Duebbert

Re: Broken Server-manager panel
« Reply #3 on: September 28, 2003, 08:26:32 AM »
Thanks! This fixed my problem too. :-)

(Didn't even know there was a http-admin, but I'm still new to e-smith.)

philippe peltier

Re: Broken Server-manager panel
« Reply #4 on: October 08, 2003, 12:32:52 PM »
gasp! done what you said on a 5.6, it gives :
Shutting down http-admin:                                  [   OK   ]
Starting httpd-admin: awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error
awk: cmd. line:1: fatal error: internal error


and the server-manager still does not work and bounces with :

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, admin@Q-bix.fr and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.


Where should I have a look to correct this ??

Heeeeeeelp!

Krusty

Re: Broken Server-manager panel
« Reply #5 on: October 09, 2003, 03:21:35 AM »
Sounds like you have a dodgy install or a sick hard drive too me. try doing a

fsck -T /dev/hda1 and then
fsck -T /dev/hda2 and so on for all your partitions and see if this fixes any problems that may arise if not check your logs and if this fails sounds like a reinstall is on the cards