Submitted by velvetpixel on Mon, 07/06/2009 - 13:28
I am getting the following error in /var/webmin/miniserv.error What do I need to do to fix it?
[05/Jul/2009:10:27:29 -0700] miniserv.pl started [05/Jul/2009:10:27:29 -0700] Perl module Authen::PAM needed for PAM is not installed : Can't locate Authen/PAM.pm in @INC (@INC contains: /usr/libexec/webmin /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /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.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /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.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at (eval 10) line 1. BEGIN failed--compilation aborted at (eval 10) line 1. [05/Jul/2009:10:27:29 -0700] Continuing without the Authen::PAM perl module
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Mon, 07/06/2009 - 15:23 Comment #1
On a typical system where users are stored in /etc/passwd, you can pretty much ignore this.
Are you seeing any errors logging into Virtualmin though?
Alternately, you can go to Webmin -> Others -> Perl Modules, and install Authen::PAM from CPAN
Submitted by velvetpixel on Mon, 07/06/2009 - 15:32 Comment #2
Thanks Jamie!
No errors logging into Virtualmin.
Submitted by JamieCameron on Mon, 07/06/2009 - 15:51 Comment #3
In that case, you can either ignore this, or just install the Authen::PAM perl module. On CentOS, the command for this is :
yum install perl-Authen-PAM
Submitted by Issues on Mon, 07/20/2009 - 17:18 Comment #4
Automatically closed -- issue fixed for 2 weeks with no activity.