Topic: service httpd-admin failed

[jane]

hello,

I'm facing errors while starting the service httpd-admin.
The errors are like this:

Starting httpd-admin: Syntax error on line 771 of /etc/httpd/admin-conf/httpd.conf:
Invalid command 'sman678', perhaps mis-spelled or defined by a module not included in the server configuration

I try to solved this but failed.

Could you have any ideas/suggestions are much appreciated.

[Dan Brown]

I don't know off the top of my head, but it'd probably help to give more information.  Like, for example, what you tried to do, and exactly how it "failed".  Or what is on line 771 of your httpd.conf.  Get the picture?

[jane]

Actually I want to access the server-manager page via internet browser but the page displayed

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

I had reboot the machine and found that service http-admin is not started.(failed) probably this is the causes why I can't access the server-manager page.

line 771 of my httpd.conf shown as below:

   SetEnv IMGHDR_SRC "/e-smith-common/user-manager.jpg"
    Satisfy all

[Dan Brown]

Is that line 771 of /etc/httpd/admin-conf/httpd.conf?  It doesn't say anything about 'sman678', which suggests you're looking at the wrong file.

[jane]

yes it is in line 771 and I realized it does't say anything about 'sman678' and thats the problem. I'm thinking is it possible to restore back this file.

[Dan Brown]

I think you've missed the point of my question--I believe you have the right line, but I think you may have the wrong file (you have two httpd.conf files on your system).  In any case, you should be able to rebuild it with

/sbin/e-smith/expand-template /etc/httpd/admin-conf/httpd.conf

[Abe Loveless]

I just encountered this problem as well.  It stems from installing the e-smith-userpanel from dungog.net.  I'd be willing to bet that the "sman62", or whatever it was is actually a user on the system.  The line above the referenced line number is the "require user USER1 USER2 USER3 .... "

At least, I'm getting this same error.. it's bombing out on reading a username into the admin-conf/httpd.conf template.

Any thoughts, or a link to different thread where the solution could be found would be appreciated.  

Thanks.