CPAN conflict issue - vs ModPerl::Registry

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View

Recently, I installed ModPerl::Registry on a Fedora Core Server, as
regular ModPerl didn't want to install, due to some janky Fedora Core
I wrote some CGI scripts, and all was well. Peace reigned, and my perl
scripts ran happily in the meadows, alongside unicorns and fairies.

Then, one day, for some foolish reason, I went to install on a
friday evening. The install went well, and I went home.
On monday morning, when I went to run some CGI scripts, they had
broken! (oh noes!)
A close inspection (or a `tail -1 /var/log/httpd/error_log` , actually)
revealed the following...

Can't locate in @INC (@INC contains: ...

Now, I have no idea why installing has broken my scripts. Is
there a way of uninstalling a module, and, more importantly, would that
be likely to fix it?

My first thought upon looking at the error_log error, was to install, but that only results in the following error during 'make

/httpd -f `pwd`/t/conf/httpd.conf -X -d `pwd`/t &
/bin/sh: /httpd: No such file or directory
httpd listening on port 8529
will write error_log to: t/logs/error_log
letting apache warm up...\c
/usr/bin/perl t/TEST 0
still waiting for server to warm up...............not ok
server failed to start! (please examine t/logs/error_log) at t/TEST
line 95.
make: *** [run_tests] Error 111
  /usr/bin/make test -- NOT OK
Running make install
  make test had returned bad status, won't install without force

Is 'httpd' a utility I need to install in order to install

Aside from CPAN, and failing to install (probably due to some
FC oddity), what I don't understand is how installing managed to
break my existing install which was using ModPerl::Registry. I mean, I
didn't change any of my code, nor did I change my httpd.conf file...
PerlModule ModPerl::Registry
<Directory "/home/media/mod_perl/">
      SetHandler perl-script
      PerlResponseHandler ModPerl::Registry
      PerlOptions +ParseHeaders
      #PerlOptions -GlobalRequest
      Options +ExecCGI +Indexes

The only thing I can think of is (3.23) broke something with the
ModPerl::Registry working...

So, is there a way of uninstalling a module, and, if so, would that be
likely to repair my problem?

Re: CPAN conflict issue - vs ModPerl::Registry

Gabriel wrote:
Quoted text here. Click to load it

What do you mean by "regular ModPerl"?

What version of Apache and what version of mod_perl are you running?

IIRC ModPerl::Registry is part of mod_perl2 (which runs with Apache 2)

Quoted text here. Click to load it

Well it would help to know what line was generating that error.

Quoted text here. Click to load it

No. No backups of the overwritten files are kept.

Quoted text here. Click to load it

Uninstalling the you installed and putting back the version that
was there previously probably would fix it.

Quoted text here. Click to load it

Yes, httpd is Apache. You can't install (aka mod_perl)
without Apache installed. However at various stages thoughout the
evolution of mod_perl there where some fairly major renamings of the
Perl modules that comprise mod_perl.

Also interacts rather closely with mod_perl.

You really need to be sure that your versions of Apache, mod_perl and are all interoperable versions.

Quoted text here. Click to load it

Did your code call ?

Site Timeline