This is what the log shows. I don't know what else to look for.
[27/Dec/2010:22:57:24 -0500] Perl module Authen::PAM needed for PAM is not installed : Can't locate Authen/PAM.pm in @INC (@INC contains: /usr/libexec/webmin /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at (eval 10) line 1. BEGIN failed--compilation aborted at (eval 10) line 1.
Failed to initialize SSL connection Failed to initialize SSL connection Temp file clearing is disabled [27/Dec/2010:23:12:41 -0500] miniserv.pl started [27/Dec/2010:23:12:41 -0500] Perl module Authen::PAM needed for PAM is not installed : Can't locate Authen/PAM.pm in @INC (@INC contains: /usr/libexec/webmin /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at (eval 10) line 1. BEGIN failed--compilation aborted at (eval 10) line 1.
Howdy,
Actually, your log looks okay -- that message is only a notice, Virtualmin will use /etc/passwd for usernames if PAM isn't available.
What happens when you try to connect to port 10000 on the machine running Virtualmin? Does it help to restart the daemon with "/etc/init.d/webmin restart"?
-Eric
It just tries to connect, then goes Internet Explorer cannot display the webpage. I already tried to restart webmin. It didn't work.
I looked around on the forum and didn't find a fix. But I saw where others looked for errors.
Her is my secure log.
$ Dec 27 22:57:24 static1 webmin[8382]: Webmin starting Dec 27 22:57:42 static1 runuser: pam_unix(runuser-l:session): session opened for user postgres by (uid=$ Dec 27 22:57:48 static1 runuser: pam_unix(runuser-l:session): session closed for user postgres Dec 27 22:57:48 static1 runuser: pam_unix(runuser-l:session): session opened for user postgres by (uid=$ Dec 27 22:57:48 static1 runuser: pam_unix(runuser-l:session): session closed for user postgres Dec 27 22:57:50 static1 su: pam_unix(su:session): session opened for user postgres by (uid=0) Dec 27 22:57:50 static1 su: pam_unix(su:session): session closed for user postgres Dec 27 22:57:50 static1 runuser: pam_unix(runuser-l:session): session opened for user postgres by (uid=$ Dec 27 22:57:50 static1 runuser: pam_unix(runuser-l:session): session closed for user postgres Dec 27 23:00:03 static1 su: pam_unix(su:session): session opened for user postgres by (uid=0) Dec 27 23:00:04 static1 su: pam_unix(su:session): session closed for user postgres Dec 27 23:05:01 static1 su: pam_unix(su:session): session opened for user postgres by (uid=0) Dec 27 23:05:01 static1 su: pam_unix(su:session): session closed for user postgres
It just doesn't load at all.
Hmm, that almost looks like some sort of firewall problem.
Could your server have port 10000 firewalled off? Or, could your ISP be blocking connections to port 10000?
A few things you may want to review --
What does the command "netstat -an | grep :10000" show on your server?
What do you see if you type: "iptables -L -n"?
-Eric
Weird thing is I can't ping my server externally. I could before. i can still SSH to it but I can't even ping it. I can ping it from the SSH console but not my Command line on my computer. I could before I installed VM.
Here is the netstat.
tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN udp 0 0 0.0.0.0:10000 0.0.0.0:*
IPtables shows
[root@static1 network-scripts]# iptables -L -n Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:20 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:21 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:20000 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:10000 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:993 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:143 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:995 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:110 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:20 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:21 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:25 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22
Chain FORWARD (policy ACCEPT) target prot opt source destination
Chain OUTPUT (policy ACCEPT) target prot opt source destination
Nevermind I fixed it. My own fault with the IP addresses.