Help requested: Upgrade from Apache 2.2 to 2.4 - Mutex?

[D. Stussy]

I've upgraded my software from 2.2.22 to 2.4.3, and as a result, I have had to
make changes to my run-time configuration. It was the "usual" renaming of
directives, deleting the named-virtual-host directives (since it's implied
now), but I'm having problems with the Mutex command (which didn't exist
previously). So I added:

Mutex default default

That took care of the problem with the ssl-cache mutex, but now it's bitching
about a rewrite-map mutex. However, the 2.4 documentation online makes no
reference to a mutex for the rewrite-map; not even in the 2.2 -> 2.4 upgrade
page. I also tried:

Mutex none rewrite-map

...But it doesn't like that either. I'm running under a Linux 3.6.8 kernel.
So, WTF do I need to do?

[Pritchie]

Post by D. Stussy
I've upgraded my software from 2.2.22 to 2.4.3, and as a result, I have
had to make changes to my run-time configuration. It was the "usual"
renaming of directives, deleting the named-virtual-host directives
(since it's implied now), but I'm having problems with the Mutex command
Mutex default default
That took care of the problem with the ssl-cache mutex, but now it's
bitching about a rewrite-map mutex. However, the 2.4 documentation
online makes no reference to a mutex for the rewrite-map; not even in
Mutex none rewrite-map
...But it doesn't like that either. I'm running under a Linux 3.6.8
kernel. So, WTF do I need to do?

Hi Stussy,

Have you read
http://httpd.apache.org/docs/trunk/rewrite/rewritemap.html
look for mutex under "prg: External Rewriting Program"
"...
When a MapType of prg is used, the MapSource is a filesystem path to an
executable program which will providing the mapping behavior.
...
This feature utilizes the rewrite-map mutex, which is required for
reliable communication with the program. The mutex mechanism and lock
file can be configured with the Mutex directive.
..."

and
http://httpd.apache.org/docs/trunk/mod/core.html#mutex
especially "table documents the names of mutexes"

Are you using an external program for a RewriteMap?

I would try
- commenting out "Mutex default default" statement and running "$ httpd
-v" to see if this shows the default mechanism selected by APR for
"rewrite-map". You may be changing this with "Mutex default default"
with an invalid mechanism for "rewrite-map". Though as default is
suppose to be the mechanism selected by APR. This is a long shot.

(my 2.4 VMS is off line at the moment so I cannot test any of this for you)

I hope this helps

Pritchie

[D. Stussy]

Post by D. Stussy
I've upgraded my software from 2.2.22 to 2.4.3, and as a result, I have
had to make changes to my run-time configuration. It was the "usual"
renaming of directives, deleting the named-virtual-host directives
(since it's implied now), but I'm having problems with the Mutex command
Mutex default default
That took care of the problem with the ssl-cache mutex, but now it's
bitching about a rewrite-map mutex. However, the 2.4 documentation
online makes no reference to a mutex for the rewrite-map; not even in
Mutex none rewrite-map
...But it doesn't like that either. I'm running under a Linux 3.6.8
kernel. So, WTF do I need to do?

Hi Stussy,
==============
At least respect my surname as one.
==============

Have you read
http://httpd.apache.org/docs/trunk/rewrite/rewritemap.html
look for mutex under "prg: External Rewriting Program"
"...
When a MapType of prg is used, the MapSource is a filesystem path to an
executable program which will providing the mapping behavior.
...
This feature utilizes the rewrite-map mutex, which is required for
reliable communication with the program. The mutex mechanism and lock
file can be configured with the Mutex directive.
..."

and
http://httpd.apache.org/docs/trunk/mod/core.html#mutex
especially "table documents the names of mutexes"

Are you using an external program for a RewriteMap?

I would try
- commenting out "Mutex default default" statement and running "$ httpd
-v" to see if this shows the default mechanism selected by APR for
"rewrite-map". You may be changing this with "Mutex default default"
with an invalid mechanism for "rewrite-map". Though as default is
suppose to be the mechanism selected by APR. This is a long shot.

(my 2.4 VMS is off line at the moment so I cannot test any of this for you)

I hope this helps
===============

Yes, I have read those. No, it doesn't help.

The configuration file runs just fine under Apache 2.2

If I were to comment out the mutex default statement, I get errors bitching
about the ssl-cache mutex not being defined.
BTW, I have no rewrite map programs. It's bitching about something I don't
even use.

There were also several other changes I had to make to my files that were NOT
documented in the 2.2->2.4 conversion page.