Apache-2.0.35 Startup Errors

Apache-2.0.35 Startup Errors

[David Jackson]

I compiled apache-2.0.35 without errors on Slackare-8.8, but when running
apachectl start it fails with the followning erors:


[Wed May 01 06:11:04 2002] [emerg] (22)Invalid argument: Couldn't set permission                s on cross-process lock
[Wed May 01 07:16:25 2002] [warn] pid file /usr/local/http/logs/httpd.pid overwr                itten -- Unclean shutdown of previous Apache run?
[Wed May 01 07:16:25 2002] [emerg] (22)Invalid argument: Couldn't set permission                s on cross-process lock


TIA,
David

Re: Apache-2.0.35 Startup Errors

[Christopher Slater]

I'm guessing here, but that sounds like Apache is set to use a lock
file  in a directory that doesn't exist...

What do you get from a ls -l of /usr/local/http/logs/httpd.pid.

What about ls -ld /usr/local/http/logs

If the directory doesn't exist then try making it and see if it will
run then...  Or get into your conf file and specify a different lock
file...

HTH,

Chris

--- David Jackson <david.jay.jackson@wcox.com> wrote:
> I compiled apache-2.0.35 without errors on Slackare-8.8, but when
> running
> apachectl start it fails with the followning erors:
> 
> 
> [Wed May 01 06:11:04 2002] [emerg] (22)Invalid argument: Couldn't set
> permission                s on cross-process lock
> [Wed May 01 07:16:25 2002] [warn] pid file
> /usr/local/http/logs/httpd.pid overwr                itten -- Unclean
> shutdown of previous Apache run?
> [Wed May 01 07:16:25 2002] [emerg] (22)Invalid argument: Couldn't set
> permission                s on cross-process lock
> 
> 
> TIA,
> David
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 


__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com

Re: Apache-2.0.35 Startup Errors

[David Jackson]

Chris --
Actually the problem was the problem was I needed
to change httpd.conf to use "nobody" fro user and group. Slackware didn't accept "-1" group.

Thanks for your reply.
David