Apache - Starting httpd: [Mon Sep 14 11:26:09 2009] [warn] module perl_module is alre

[deronvilp]

After upgrading from FC3 to FC4 I am receiving errors when trying to start Apache


ERROR:
+++++++++++++++++++++++++++++++++++++++
Starting httpd: [Mon Sep 14 11:26:09 2009] [warn] module perl_module is already loaded, skipping
+++++++++++++++++++++++++++++++++++++++

I have reviewed a few articles describing the commenting out modules but no idea which ones to remove since the upgrade.

LOADED MODULES:
================================================== ===
LoadModule access_module modules/mod_access.so
LoadModule auth_module modules/mod_auth.so
LoadModule auth_anon_module modules/mod_auth_anon.so
LoadModule auth_dbm_module modules/mod_auth_dbm.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule auth_ldap_module modules/mod_auth_ldap.so
LoadModule include_module modules/mod_include.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule env_module modules/mod_env.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule expires_module modules/mod_expires.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule headers_module modules/mod_headers.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule asis_module modules/mod_asis.so
LoadModule info_module modules/mod_info.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule imap_module modules/mod_imap.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule cache_module modules/mod_cache.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule cgi_module modules/mod_cgi.so
================================================== ===

Help would be greatly appreciated

[syd05]

Hi,

This error normally pops up when the LoadModule directive for perl has a double entry. Ideally look for the line " LoadModule perl_module modules/mod_perl.so ". This line would be in the file /etc/httpd/conf.d/perl.conf. Also check the httpd.conf file to rule out any entry for mod_perl.so

Also check how many file named perl.* are there in the /etc/httpd/conf directory. Sometimes when the perl.conf file is modified and you then upgrade the apache package, the original file is backed up and a new file also created. Apache is so configured to call all the files in the /etc/httpd/conf.d directory.

This directive needs to be called just once and if called again pops up the said error.

--Syd

[deronvilp]

I found an entry in conf.d/perl.conf and # commented it out. I attempted to start service and got

"Failed to start apache" instead of the previous already running state.

I did not see entries anywhere. Nothing in httpd.conf

I have attached HTTPD.conf for a second look

Your help is appreciated

Thanks

[syd05]

Hi,

Could you post the output of the error_log file when you restart the httpd service?

I assume you've not made any other changes except for commenting the line in perl.conf. Uncommenting the line brings back the same perl_module loaded error?

--Syd

[deronvilp]

it is not the exact same "[warn] module perl_module is already loaded, skipping"
warning message after I comment out the perl_module in perl.conf. Instead it says "Failed to start apache"

++++++++++++++++++++++++++++
[Tue Sep 15 01:49:07 2009] [error] Can't locate Apache/compat.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.6/i386-linux-thread-multi /usr/lib/perl5/5.8.6 . /etc/httpd) at (eval 2) line 3.\n
[Tue Sep 15 01:49:07 2009] [error] Can't load Perl module Apache::compat for server automation.mgadm:0, exiting...

[syd05]

Hi,

Was there only a single instance of LoadModule in perl.conf? Could you provide the contents of perl.conf

Search for the string Apache::compat and trying changing it to Apache2::compat. With the upgrade from FC 3 to FC 4 perhaps the mod_perl package has got upgraded from v1 to v2. A file listing of mod_perl shows Apache2::compat which mite need to be referenced in place of Apache::compat.

This URLmod_perl: Apache2::compat -- 1.0 backward compatibility functions deprecated in 2.0 could perhaps give you some clue. The error is basically complaining about a missing Apache::compat.pm file

--Syd

[deronvilp]

I have attached PERL.conf

Should I continue to comment out
#LoadModule perl_module modules/mod_perl.so

[syd05]

Hi,

In perl.conf, change the line " PerlModule Apache::compat" to "PerlModule Apache2::compat " and check if apache starts without error. If it yet throws up some error, then comment out the line PerlModule Apache::compat

For now leave the LoadModule directive commented. Your perl file contains only one instance of LoadModule directive so I wonder why the module already loaded error in the first place. That's a error generated only when the module if called for twice.

--Syd

[deronvilp]

As suggeted I made the change in perl.conf to Apache2::compat but got different error after attempting to start service (see below). The error logs show the same error. I tried to restarting by leaving LoadModule perl_module modules/mod_perl.so commented out and then removed # sign but neither worked.

I reviewed the URL but not sure what steps to take. I am down hard as this box processes many automated scripts that run perl cgi scripts and provides http services for a helpdesk software. So both are down.

Any additional help would be greatly appreciated.

++++++++++++++++++++++++
[warn] The Alias directive in /etc/httpd/conf.d/perl.conf at line 32 will probably never match because it overlaps an earlier Alias.
[Tue Sep 15 08:00:52 2009] [warn] The Alias directive in /etc/httpd/conf.d/perl.conf at line 40 will probably never match because it overlaps an earlier Alias.
[FAILED]

[syd05]

Hi,

Was all of this working before the upgrade? Just needed to know since there are multiple errors popping up. I'm not that an expert, but m trying to assist you with what ever I can.

The new error means that the same alias is configured somewhere else. Alias /perl & Alias /opscontrol-bin are being called before even the perl.conf gets executed. You'll need to find out which file is calling it and check the directives. Could be one of the files in conf.d directory; you could try the command grep Alias * in the conf.d directory to find which files contain the Alias directive. If they are the same you could comment out the entries in perl.conf or else if they are different and you need both then you need to rename /change either of those.

Also provide the listing of the conf.d directory.

Post the last few line ( like 50 lines of error logs) when you get error as well as watever is output on the screen

--Syd