Forum Moderators: phranque

Message Too Old, No Replies

(38)Function not implemented

         

liquidcool

1:12 pm on Oct 7, 2004 (gmt 0)

10+ Year Member



Hi There,

I am having issues with my newly compiled apache2 server. I am running version 2.0.45 on a kernel version of 2.6.8.1. everytime I try to run httpd start or even apachectl I get this error in the error_logs :
(38)Function not implemented: Couldn't create accept lock

Has anyone come across this and if so has anyone resolved this? I have trawled all over the web and cannot find anything with a solution to this problem.

Thanks in Advance

Regards

Jason

jdMorgan

2:27 pm on Oct 7, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Jason,

Welcome to WebmasterWorld!

> newly compiled apache2 server

I'm just guessing, but this may have to do with file-locking. If so, there are many variations in how file-locking is accomplished on various CPU/OS platforms. Make sure the platform you compiled for is exactly what you are trying to run it on.

Jim

liquidcool

9:44 am on Oct 8, 2004 (gmt 0)

10+ Year Member



Hi Jim,

It is a standard build of Linux. Pretty much stripped down to a minimal installation. Everything else seems to work that I have installed on it : Bind, Webmin, linuxconf.

I think it does mention something about file locking. How do I go about fixing it?

Thanks

Jason

liquidcool

9:45 am on Oct 8, 2004 (gmt 0)

10+ Year Member



Just one other thing.

The OS is Redhat 9
CPU is a PIII 700.

Pretty standard stuff really ... nothing out of the ordinary.

Cheers

Jason

jdMorgan

5:06 pm on Oct 8, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



You said you had a "freshly-compiled" server. So, I suspect that the options used to compile it are incorrect for the platform you are trying to run it on. This is not my area of expertise, but file locking and "atomic operations" such as "Test and Set" are two areas of platform-dependence that often cause problems.

The documentation of certain scripting languages, such as PERL carries warnings that file-locking semantics differ across platforms, and so the language's built-in file-locking mechanism's may work differently on various platforms. PERL has nothing to do with your problem, but the warning might.

I assumed that you compiled the server. If not, look to the source of your compiled "package" for support. Your chances of finding others with the same problem are better there than here, where we have a small group of contributors whose server platforms and configurations are all different.

Jim

liquidcool

1:59 pm on Oct 12, 2004 (gmt 0)

10+ Year Member



Hey JD,

I figured it out....

To compile apache with a newer kernel you must compile it with the newer kernel headers folder of the new kernel. Also you must make sure you have System V IPC compiled into your kernel.

Also trying to run in it in xinetd seems to cause the issue as well .... so I just ran it from init.

All seems to be working like a charm now.

Cheers

Jason