Httpd spelling errors causing apache failure

rupdog

Active Member
May 18, 2002
35
0
306
Hi,
On one of my server every week now ot then, the apache fails and restarting also fails as I see this error:
=======
[~]# service httpd restart
/etc/init.d/httpd restart: httpd not running, trying to start
Syntax error on line 3807 of /usr/local/apache/conf/httpd.conf:
Invalid command 'ÓerverName', perhaps mis-spelled or defined by a module not included in the server configuration
/etc/init.d/httpd restart: httpd could not be started
======
this happens quite frequently, like when someone adds a domain or does something related to editing apache and the spelling error at the time of editing by cpanel is causng apchae to fail.
In most time correcting the spelling and restarting apache works fine but some time, even after I correct the wrong spelling I cant start apache and I get the following error:
====

[Thu Dec 26 19:23:24 2002] [crit] (98)Address already in use: make_sock: could not bind to port 80

========
I do not know yet to correct this issue I had to reboot server each time this above error happens.

Does anyone else having this issue, can Cpanel shed some light on it ? PleaSe

Thanks
 

dgbaker

Well-Known Member
PartnerNOC
Sep 20, 2002
2,531
10
343
Toronto, Ontario Canada
cPanel Access Level
DataCenter Provider
I don't why it is happening, but some things to possible look at..

Language is there a language being used that is not supported?

Have you tried to run easyapache to resetup the apache server?

What cpanel/whm build are you using?

What theme? It is plausible it could be a theme issue.

Have you submitted a support ticket to cpanel?

These are some things to possibly look into.
 

Tim Greer

Well-Known Member
Aug 11, 2002
59
0
156
[quote:8ca2a3dead][i:8ca2a3dead]Originally posted by rupdog[/i:8ca2a3dead]

Hi,
On one of my server every week now ot then, the apache fails and restarting also fails as I see this error:
=======
[~]# service httpd restart
/etc/init.d/httpd restart: httpd not running, trying to start
Syntax error on line 3807 of /usr/local/apache/conf/httpd.conf:
Invalid command 'ÓerverName', perhaps mis-spelled or defined by a module not included in the server configuration
/etc/init.d/httpd restart: httpd could not be started
======
this happens quite frequently, like when someone adds a domain or does something related to editing apache and the spelling error at the time of editing by cpanel is causng apchae to fail.
In most time correcting the spelling and restarting apache works fine but some time, even after I correct the wrong spelling I cant start apache and I get the following error:
====

[Thu Dec 26 19:23:24 2002] [crit] (98)Address already in use: make_sock: could not bind to port 80

========
I do not know yet to correct this issue I had to reboot server each time this above error happens.

Does anyone else having this issue, can Cpanel shed some light on it ? PleaSe

Thanks[/quote:8ca2a3dead]

ÓerverName = ServerName. The directive is mispelled. About the already in use on port 80, make sure all current instances are killed.
 

rupdog

Active Member
May 18, 2002
35
0
306
I have tried everything to find the second instance of use of port 80 but I cant find it in Ps command or any other I know of. In the end i had to reboot server and do manual fsck :(

But I am not sure why when someone deltes a site on server the cpanel misspells the conf file. Today again i had to reboot as it misses 'c' in front of cgi-bin in the httpd.conf file and i edited it and it gave the same error upon restarting apache:
[crit] (98)Address already in use: make_sock: could not bind to port 80,
 

LucasVanzin

Well-Known Member
Jan 21, 2004
45
0
156
Brazil
This is driving me nuts, i have the same problem here and nobody knows how to fix.

I open a ticket on cPanel and they keep recompiling apache with and the problem persists.

If it helps i work only with resellers.
 

aurigus

Member
Apr 30, 2003
7
0
151
Have you checked the memory or disk? It almost sounds like there could be an error in there which causes these errors while writing the config file.
 

LucasVanzin

Well-Known Member
Jan 21, 2004
45
0
156
Brazil
Seems like the problem was solved, the problem was with the logs of 2 domains that was too big (aprox 3Gb). Since file was excluded apache is ok.