I was setting up a Cobalt RaQ4i from rackshack that would be dedicated to a single website. I needed to install a separate httpd enabled mod_perl for it, but after I installed mod_perl, httpd refused to start properly and complained about the version of Apache.pm being different (it wanted 1.26, I had 1.27).

I said "screw it" and reinstalled the normal httpd as well, killing the control panel. Muhahahaha! It feels kind of good to break something that I don't need. :/

Seriously though, has anyone ever installed mod_perl without breaking the RaQ4i control panel? It doesn't matter on this machine since I only have one site, but I have another machine where the control panel is needed.

Did you compile apache with mod_perl built-in or as a module?
Run /usr/sbin/httpd -l to get a list of modules.

Did you restart the admserver?


Post the error messages and maybe somebody can help.

I compiled mod_perl on a separate Apache with --target=perlhttpd, so it didn't affect /usr/sbin/httpd.

I think the problem occured when it upgraded /usr/lib/perl5/site_perl/5.005/i386-linux/Apache.pm to a newer version; the old httpd didn't like that for some reason. I don't have the exact error message anymore, but it said that it needed version 1.26 of Apache.pm but I had 1.27.

What's an admserver? Do you mean that the Apache on port 81 is called admserver and is separate from the Apache on port 80? I can't find it though---"locate admserver" doesn't show anything.

It should be admserv not admserver. It is usually located in /etc/admserv
It is nothing more than a separate instance of apache with its own config files -- it does use that same apache binary though.
This is for a Raq4. I do not know about other Raqs.

Now I understand your mod_perl problem. Mod_Perl and mod_ssl should always be compiled together and in sync. These products are pretty tightly co-ordinated, so updating one often causes problems to the other. I think mod_perl actually patches part of the Apache distribution, this would explain why your admin interface is done. You should try to start your server using the newly compiled binary -- just make a backup copy of it. Copy the new binary to /usr/sbin/httpd and try to see if you get your admin panels back.

eth0:0

:o

*waves sheepishly at RS-Zach*