Ran emerge -auv apache and it downgraded apache-1.3.33-r1 back down to apache-1.3.33 and then apache will no longer start giving an error message: Cannot load /etc/apache/extramodules/libssl.so into server: /etc/apache/extramodules/libssl.so: undefined symbol: dbm_firstkey I have tried re-emerging mod_ssl. I've seen the dbm_first key error a while back with pam so I re-emerged apache with USE="-pam". It still gives me this same error. Reproducible: Always Steps to Reproduce: 1. emerge -vu apache 2. apachectl stop 3. apachectl start Actual Results: Emerge moved it back to apache-1.3.33 from previously installed apache-1.3.33-r1. (I kept my apache config files the same). Get an error trying to start apache: Syntax error on line 62 of /etc/apache/conf/apache.conf: Cannot load /etc/apache/extramodules/libssl.so into server: /etc/apache/extramodules/libssl.so: undefined symbol: dbm_firstkey Line 62 of /etc/apche/conf/apache.conf simply is the line trying to load the libssl.so (mod_ssl) module. Expected Results: Apache should run
The apache-1.3.33-r1 is hardmasked now, I set the needed flags to force emerge to re-install apache-1.3.33-r1 and apache again works as expected. I am assuming it was moved to a hard mask area as it has flaws but I needed to get this machine running again.
That's odd. You're running on stable portage tree exclusively right? If not, what exactly not (related to apache)? Can you paste a `emerge -pv apache` please? I'm really very interested in *why* it's been downgraded, especially because I can't find that hardmask you're talking about.
1.3.33-r1 is not hardmasked anymore, see bug 86052
please reopen if you can still reproduce it
Now that 1.3.33-r1 is not hardmasked anymore it is not a problem anymore (I haven't had any problems with 1.3.33-r1, only when it got hardmasked and so it downgraded me to 1.3.33 did I have problems).
