top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration
Print Preview

Problems with apache downgrade

0 votes

There was an upgrade on a couple of our servers yesterday, mid-afternoon our time, of httpd and httpd-devel, and suddenly SiteMinder (bleah) stopped working correctly, and is now pegging a cpu, according to top. So, as a last resort, I tried downgrading both of them. When I did so, the server that uses ssl *erased* mod-ssl, not downgrading it, and I'll have to find where I can get the previous version tomorrow... but that
shouldn't happen, I should think. Downgrade *should* get everything, unless it's brand new, and this isn't.

posted Jul 11, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

1 Answer

+1 vote

In a previous life we had to use SiteMinder as well. It pegs top because it's trying to dump a log file but it doesn't deal with the permissions properly. If I recall correctly it tries to dump to /var/log/httpd, but as the apache user, not as root. Once the apache user has access to write the log to where it's configured, it'll spool out the memory it's using and the load will drop after a while.

answer Jul 12, 2013 by anonymous
Similar Questions
+2 votes

Im trying to configure the proxy_balancer, but still having problems. Here is my configuration:



But when The first worker fails, request are not redirected to the failover worker. For this I have to wait for more than 7 minutes. Is this behavior normal?

+1 vote

I am getting tired of my web host changing server-wide apache config settings without warning. Then I am pulling my hair out trying to figure out why my website is not quite working as it should.

Is there a way I can use .htaccess or other method to see what the config settings are? Then I could more easily deal with what has been changed.

I realize that what I put in .htaccess will overwrite what they have put in the config, but not knowing what they are doing makes it harder for me to address the changing problems.

0 votes

Running Apache 2.4.7 and current configuration limiting access to a directory to only clients that can provide a trusted client certificate. Server is SSL host. Would like to modify configuration to allow "local" clients (, etc. as defined by Require local auth provider) to access the directory without authenticating with a client certificate. So the local host may access the directory without SSL client auth, but all others must authenticate with a client certificate or access is forbidden. What is the best/proper way to do this?

I would like to use modern directives (avoiding Allow, Deny, Order etc. from mod_access_compat) but I am not clear how to combine Require related directives with mod_ssl options like SSLVerifyClient.

Thanks in advance?

+2 votes

Is it possible to use PHP 5.2.5 with Apache/2.4.6?

I have an application that was written in WAMP5 using PHP 5.2.5, and I am trying to get the application onto a CentOS server and I can't get it to work with 5.4.16.

Are there any good tutorials on using an older version of PHP with Apache?

+1 vote

I am planning to upgrade my apache2.2 to 2.4., i have 2 questions before where i need your help.

Former SPDY Implementation conflicts with non-threadsafe Modules like mod_php. To use SPDY it is necessary to use worker-mpm and php-cgi.
Now HTTP/2 is new standard and i would like to know if HTTP/2 Implementation has same conflicts with non-threadsafe Modules like mod_php. As far as I know HTTP/2 is based on SPDY.

I have some non-standard Modules compiled and packaged for Apache2.2. Is it possible to use these Modules again on Apache2.4 or is it necessary to compile all new for new Apacheversion?

Useful Links with Similar Problem
Contact Us
+91 9880187415
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Karnataka INDIA.