Apache2 mod_ssl.so pointing to wrong libssl.x.x.x.dylib after ssl upgrade on Tiger

[dsmithhfx@…]

Hi,

Yesterday I made a number of new mac ports installations with the goal of having a newer version Postfix, and easier way to configure it (according to ​this guide).

So: new mac ports installations of Postfix and Webmin, with all dependencies including SSL. Note the mac ports Postfix and SSL are both newer versions than come bundled with Tiger.

Long story short, the pre-existing Apache2 (also installed via mac ports some months ago) mod_ssl.so still points to the old libssl.0.9.8.dylib, instead of the newly-installed, libssl.1.0.0.dylib, resulting in the following error message when attempting to start Apache2:

httpd: Syntax error on line 98 of /opt/local/apache2/conf/httpd.conf: Cannot load /opt/local/apache2/modules/mod_ssl.so into server: Library not loaded: /opt/local/lib/libssl.0.9.8.dylib\n  Referenced from: /opt/local/apache2/modules/mod_ssl.so\n  Reason: image not found

I was able to start Apache2 after commenting out "LoadModule ssl_module modules/mod_ssl.so" in httpd.conf.

Any chance someone could post the correct mod_ssl.so, as I can't edit and recompile(?) the binary file, even though I can open it in a text editor and plainly see references to libssl.0.9.8.dylib amongst the binary 'gibberish' ?

Or is there a better way to fix this (e.g. re-install Apache 2) ?

Thanks!

[dsmithhfx@…]

OK I fixed the SSL issue by upgrading Apache2 (which I guess means it recompiled against the new SSH), then discovered I had no MySQL connectivity (mysqld.sock was disappeared, as was my.conf), so once those things were patched up I have my dev environment running the way it was before, except postfix config is dysfunctional (the onboard postfix would at least relay mail to webmail addresses but not the company domain; the mac ports -installed postfix ain't sending nuthin' nowhere...

Defective by design, or PEBCAK? You decide.

[blb@…]

apache2 (as well as a number of other ports) had its revision increased in r69520 to force it to be rebuilt with the newer openssl port. If port installed had shown apache2 @2.2.15_2 then that would be current (revision 2) but if it were just revision 1, then a port upgrade outdated should have taken care of it.

Note that postfix was also included in that update, but not sure what may be wrong with your postfix setup.

[dsmithhfx@…]

Fair enough, but why would installing postfix and webmin nuke mysqld.sock and my.conf ?

[jmroot (Joshua Root)]

Replying to dsmithhfx@…:

Fair enough, but why would installing postfix and webmin nuke mysqld.sock and my.conf ?

The exact sequence of events here is not clear, but open separate tickets for those problems if they are reproducible.