Topic: Perl Error Messages - Can't locate Pod/Usage.pm in @INC

[nkevans]

I am running SME 7.3 (as an upgrade to an existing SME6 installation)

Cron daemon keeps reporting an error in the following terms:

/etc/cron.daily/00-sa_keys:

Can't locate Pod/Usage.pm in @INC  [followed by listing of @INC contents]
........


The same error (i.e. Can't locate Pod/Usage.pm in @INC) also appears repeatedly in the spamd log file which reads:

2008-03-11 12:59:12.930823500 Can't locate Pod/Usage.pm in @INC (@INC contains: /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5 /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.2/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi /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/5.8.2 /usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /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.2/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl/5.8.2 /usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl) at /usr/bin/spamd line 92.
2008-03-11 12:59:12.930869500 BEGIN failed--compilation aborted at /usr/bin/spamd line 92.
.....


I installed CPAN with a view to installing SQL-Ledger but cannot get CPAN to install successfully.  Strangely, I have been able to do it on another SME7 machine with no problem.

I have run locate Usage.pm which shows that it is installed but clearly @INC does not think so.  I presume that it is not in the right place.

Unfortunately, I do not know enough about how Perl (or CPAN) works to figure out how I can persuade the server that all is OK.

Does anyone have an idea as to how I can fix this?  I have searched extensively by reference to CPAN but without any success.

TIA


Nick

[nkevans]

Problem solved!

Since posting my earlier message, and after several weeks of frustration, I have discovered purely by chance that the directory "Pod" had been created as "pod".

A simple re-name and the error has gone away.

Nick

[CharlieBrady]

Since posting my earlier message, and after several weeks of frustration, I have discovered purely by chance that the directory "Pod" had been created as "pod".

That would indicate a corrupted perl rpm. You should verify that there are no other such errors:

rpm -V perl

Are you sure that you didn't inadvertently rename the directory?

[nkevans]

That would indicate a corrupted perl rpm. You should verify that there are no other such errors:

rpm -V perl

No errors are reported.

Are you sure that you didn't inadvertently rename the directory?

I have no recollection of doing so but it's possible.  The problem only came to my notice as a result of trying to use cpan to install the various routines required by SQL-Ledger. 

Incidentally, I have now been able to complete the relevant cpan installs as well.

Thanks for your response.

[cactus]

No errors are reported.

I have no recollection of doing so but it's possible.  The problem only came to my notice as a result of trying to use cpan to install the various routines required by SQL-Ledger. 

Incidentally, I have now been able to complete the relevant cpan installs as well.

I guess the error lies in the cpan action(s).

If you know what modules you need for SQL-ledger you should try and install them from the RPMForge repositories, you will most likely find them in Dag or ATrpms, listed as perl-module-name, installation commands for these repositories are in the wiki.

Installing using cpan is bound to give you errors.