Unable to connection to webmin via browser

Hi

I'm running a standard installation of webmin on Centos5. Yesterday some of the services stopped running on the server, the problem turn out that there was no space on one of the mounted drives.

Anyway I have freed up some space on the drive but I'm unable to now get access to the webmin portal in the browser.

I have tried to restart webmin but i get this error in the /var/webmin/miniserv.error log

[10/Sep/2010:06:27:04 +0100] miniserv.pl started
[10/Sep/2010:06:27:04 +0100] 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.

[10/Sep/2010:06:27:04 +0100] Continuing without the Authen::PAM perl module

Can anybody help or give me an indication of what I need to do

Thanks

Status: 
Closed (fixed)

Comments

What error are you getting in your browser exactly?

Those messages in the logs are pretty harmless ..

When I try to access the default port :10000 it just times out. I get a standard browser

'Safari can’t open the page “https://fantasticsolutionsdns.co.uk:10000/” because the server where this page is located isn’t responding.'

I have webmin and usermin installed but I get the same response from both modules on ports 10000 and 20000

When I try to connect to that URL, I can't even open the TCP connection. You should check if there is a firewall blocking ports 10000 and 20000.

When I run the command

iptables -L n

I get

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

The rules relating to iptable config are as follows

-A INPUT -p tcp -m tcp --dport 20000 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 10000 -j ACCEPT

Unfortunately I'm still unable to connect to the webmin service.

Could there perhaps be another firewall blocking access, such as on a router or gateway in front of your system?

Also, what output do you get if you run the following command :

wget -O /dev/null https://localhost:10000/

on your Webmin system

OK

I run this command

wget --no-check-certificate -O /dev/nul https://localhost:10000

I get

--2010-09-10 18:12:11--  https://localhost:10000/
Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:10000... connected.
WARNING: cannot verify localhost's certificate, issued by `/O=Webmin Webserver on server88-208-237-33.live-servers.net/CN=*/emailAddress=root@server88-208-237-33.live-servers.net':
  Self-signed certificate encountered.
HTTP request sent, awaiting response... 200 Document follows
Length: unspecified [text/html]
Saving to: `/dev/nul'

    [ <=>                                                                                                                                                  ] 5,265       --.-K/s   in 0.03s  

2010-09-10 18:12:11 (190 KB/s) - `/dev/nul' saved [5265]

When I open the file that is downloaded it is the login page.

Could it be that my IP address in restricted? The funny thing is that I was able to access port 10000 before the partition was filled up.

My computer does not have the firewall on and I'm pretty sure there are no firewall settings on the router

Ok, so it looks like Webmin is responding when you connect locally, but not when you connect from outside. It seems unlikely that a lack of disk space would cause this .. usually the reason is a firewall or network issue.

How is your machine connected to the internet? Directly, or behind some NAT gateway?

I don't know.

How would I check that?

That is the strangest thing but I'm able to connect now.

I have done nothing but the issue seams to have resolved itself. Very weird but a great relief.

Thank Jamie for all your help, I really appreciate it.

Ok, cool .. please re-open this if you see the error again.

Automatically closed -- issue fixed for 2 weeks with no activity.