After upgrading to apache-2.0.53 and realising the issues in changing conf files/locations I downgraded to 2.0.52-r2, however, it won't start! It worked fine before the upgrade and I have removed all files relating to apache-2.0.53. Reproducible: Always Steps to Reproduce: 1. emerge =apache-2.0.52-r2 2. emerge =apache-2.0.53 3. emerge =apache-2.0.52-r2 4. /etc/init.d/apache2 start Actual Results: Syntax error on line 66 of /etc/apache2/conf/apache2.conf: Cannot load /usr/lib/apache2/modules/mod_mem_cache.so into server: /usr/lib/apache2/modules/mod_mem_cache.so: undefined symbol: apr_atomic_dec Expected Results: Started [ OK } There is a related thread in the forums: http://forums.gentoo.org/viewtopic-p-2182067.html#2182067
Please use "New -> Gentoo Linux -> Component: Ebuilds" in future. Infrastructure is not the correct addressee.
remerge apr and apr-util to fix this problem. HOWEVER! What's been the problem with apache 2.0.53? If you don't report this, we won't ever get out of unstable. Please file a bug with detailed information about :-)
"Please use "New -> Gentoo Linux -> Component: Ebuilds" in future. Infrastructure is not the correct addressee." Sorry I thought it was going into the Ebuilds category, not sure how that happened :? RE 2.0.53; The upgrade guide mentions many modules need fixing, most notably mod_php, so I thought I'd wait until it had settled down. If mod_php is working I give it a go :)
well, that's the point, actually, as we've a mod_php (deemed to be working) in ~testing branch already. This is mod_php-3.4.10-r1 for 3.4 series and mod_php-5.0.3-r1 for the 5.0 series. If you've time to test them, please emerge the one of interest for you and tell us whether you "really" have a problem with it or not. upgrade instructions: # (cleanup /etc/apache2/ as much as possible) # emerge -C apr apr-util apache php mod_php # emerge '>=net-www/apache-2.0.53' '>=dev-php/mod_php-5.0.3-r1' # etc-update downgrade (if you don't fail again) # (cleanup /etc/apache2/ as much as possible) # emerge -C apr apr-util apache php mod_php # emerge '<net-www/apache-2.0.52-r3' '<dev-php/mod_php-5.0.3-r1' # etc-update (hope this helps a bit - no garanties anyway)
Remerging apache, php, mod_php, apr & apr-util in the past had not worked, however these steps got apache-2.0.52-r2 going this time: # emerge -C apr apr-util apache php mod_php # emerge '<net-www/apache-2.0.52-r3' '<dev-php/mod_php-5.0.3-r1' # etc-update I have php5 masked and use php4, also apr & apr-util never got remerged so I've left them off the system, maybe that helped, very strange. Working though, thanks :) I'll leave apache-2.0.53 for now, I'll try it when I have time to fiddle with the confs.
BTW if your using apache-2.0.52-r2 and want php4 you'll need php-4.3.10 not 4.3.10-r1.
I had a problem where by apache's child processes were dieing on site access. This is serving simple HTML. Comment No5 fixed this problem. Thanks
Anthony, what does that mean? That you're now running the *old* or yet the *new* apache? (old is supposed to be the apache with the old config.) I presume, that got segfaults because you have had the wrong apr and apr-util libraries emerged. This may be the source of your error because the new apr/apr-util ebuilds do serve LFS (large-file-support) that irrevokably introduces runtime incompatibility. that is: each executable/library depending on apr/apr-util NEEDS to be recompiled (remerged) again.
