Re-installing the libapr at the same level seems to have solved the problem, 
though I am at a loss to figure out what could have damaged it in the
first place. Now the person who actually owns the apache2 instance is going to 
put things back the way they configured it in the first place and see
if everything works.




             "Post, Mark K" <[EMAIL PROTECTED]>
             Sent by: Linux on 390 Port
             <[email protected]>                                          
                                                                   To
                                                                     
[email protected]
                                                                                
                                                                   cc
             11/14/2006 03:30 PM
                                                                                
                                                              Subject
                                                                     Re: 
Strangeness with Apache2
                            Please respond to
               Linux on 390 Port <[email protected]>








There are also indications that libapr, or glibc may be at fault.  What
specific versions are apache and those packages at?


Mark Post

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
James Melin
Sent: Tuesday, November 14, 2006 3:50 PM
To: [email protected]
Subject: Strangeness with Apache2

Greetings.

We have an internal department that has one of the virtual penguins on
our z/box using Apache2. For all of our other servers (Websphere anyway)
We use
the IBMIHS server there.

In any case, I have not messed with the Apache configuration and nobody
else with access has admitted to it.  The only recent change was a 50
meg
reduction in memory allocated to the z/VM guest.

The message Apache2 is throwing when it fails to start is:

[error] (38)Function not implemented: Cannot create SSLMutex
Configuration Failed

I've looked at thinks like the prefork thread handler. Enabling that
didn't help.  Some other threads for intel indicate 2.52 is the release
of apache
we need, but I am not sure that applies.

Anyone got any ideas about this error?

Thanks!

-J

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to