top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Problems with apache downgrade

0 votes
189 views

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 LinkedIn 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:

BalancerMember http://172.16.14.81:80 
retry=120 
timeout=10 

BalancerMember http://172.16.14.82:80 
retry=1 
timeout=10 
status=+H

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.

+1 vote

I am facing the issue while building apache on Window machine with the help of apache source code and got below error

[ 92%] Building C object CMakeFiles/mod_ssl.dir/modules/ssl/ssl_engine_init.c.obj 
ssl_engine_init.c 
C:apacheBuildapache2.4buildhttpd-2.4.33modulessslssl_engine_init.c(33) : fatal error C1083: Cannot open include file: 'mod_md.h': No such file or directory 
NMAKE : fatal error U1077: 'c:PROGRA~2MICROS~2.0VCbinamd64cl.exe' : return code '0x2' 
Stop. 

I did some investigation and found that with new version of apache we added a new module called MOD_MD which is experimental basis, I don't know why experimental module added as a dependency and it will cause a build failure,

Can you please help me out to fix above issue?

0 votes

I started apache server which has worker as mpm in debug mode. I killed the process with kill -9 then it kills the process and stop debug. But when I am using kill -term PID then it is not killing process. Whereas kill -term PID is woking with prefork debug.Â
If I want to use kill -term PID in debug mode of worker then how to do that.

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 (127.0.0.1, 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?

...