We’ve had reports today from a few folks that the lastest OS update caused a problem with the installed mod_perl, which prevented apache from starting up successfully.
The error looks like this when apache tries to start
Undefined symbol Perl_Ippid_ptr in mod_perl.so
You can quickly resolve this by disabling mod_perl (assuming it isn’t needed). Do this by editing the file /etc/httpd/conf.d/perl.conf, and comment out the LoadModule line, so that it looks like this:
#LoadModule perl_module modules/mod_perl.so
Then restart the webserver:
service httpd restart
You can follow these instructions to resolve this permanently, depending on your distro.
Thanks for the post - I noticed this error, and after being notified, commented out the LoadModule line, which got the httpd back up & running. Doing a search on G didn’t turn up much apart from back in February where it stated a yum update would have fixed - obviously to no avail.
Anyway, my update wasn’t quite as successful as yours. I had to
Okay, I have grabbed expat-devel and its progressing further.
Sorted - for anyone experiencing similar - make sure expat and expat-devel are installed. This is a new’ish server so this could explain. Thanks for the pointers Paul.
I’m still tweaking my Iworx test server with a production site running on them in that clustered pair, just noticed they didn’t have mod perl compared to my other Plesk server that had been running the same scripts with improved performance/stability.
I just installed mod_perl on both Iworx and it seems to be going fairly well now. Just wondering if you left them out for any particular reason on the build/install?
For this particular cluster it’s only a single perl script.
I’m not aware of there being a special handler entry for the conf file, you just add the LoadModule line into the conf file as the mod_perl instructions say to do.
I’ve checked one of my Plesk servers running 1.99 and it only has the LoadModule line as well, so my guess is Apache passes it off to mod_perl directly.
