Error 101 connection reset after long pause on starting Virtualmin

12 posts / 0 new
Topic locked
Last post
#1 Tue, 02/05/2013 - 05:19
steamydave

Error 101 connection reset after long pause on starting Virtualmin

Hi,

We are currently getting this message Error 101 (net::ERR_CONNECTION_RESET): The connection was reset. when trying to start Virtualmin.

System updates might have recently been installed.

We have tried re-booting the server, just in case Virtualmin has got into a pickle, but still no access.

The websites/MySQL, ftp, ptty, scheduled webmin backups, usermin all seem to be working OK.

Anyone else having this problem?

Dave

Tue, 02/05/2013 - 07:46
steamydave

Just tried from home and found that there is still a problem - so coming in from a different ISP has no effect. The only difference is that the long pause has gone.

I have Virtualmin installed on 2 test servers. One of the test servers is suffering the same problem, but the other (which has webmin 1.620-1 and usermin 1.540-1 waiting to be installed) doesn't have a problem, so it looks like the problem might be in one of those 2 updates.

Dave

Tue, 02/05/2013 - 10:03
andreychek

Howdy,

Hmm, we hadn't heard any other reports of a problem like you're describing.

Are you seeing any errors in the Webmin error log when that occurs?

That log is in /var/webmin/miniserv.error.

Also, just for fun, although you did try a different ISP (which is one of the things I was going to suggest), could you also try a different browser? That would rule out a few things as well.

-Eric

Tue, 02/05/2013 - 10:05 (Reply to #3)
steamydave

Hi Eric,

I've tried IE8, Firefox and Chrome now - all the same.

I'll take a peek at the log and see.

Thanks,

Dave

Tue, 02/05/2013 - 10:21 (Reply to #4)
steamydave

Hi,

No - nothing appears id miniserv.error, no new log entries.

Dave

Tue, 02/05/2013 - 12:16
andreychek

What do these two commands show:

netstat -anlp | grep :10000
iptables -L -n
Tue, 02/05/2013 - 12:59
steamydave

Netstat didn't return anything,

iptables...

[root@server109-228-12-164 webmin]# 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:587 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 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 ACCEPT udp -- 213.171.217.173 0.0.0.0/0 state NEW udp dpt:161 ACCEPT udp -- 10.44.53.36 0.0.0.0/0 state NEW udp dpt:161 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:80 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:443 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:53 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:53 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:25 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:110 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:143 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:20 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:21 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 state NEW tcp dpt:3306 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:3306 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable

Chain FORWARD (policy ACCEPT) target prot opt source destination

Chain OUTPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state NEW

10000 is there, as is 20000. 20000 worked OK.

Something to note is that Virtualmin spotted (big yellow banner) that the OS needed to go from Centos 5.9 to 6.01. Both servers had that update. Could it be that the OS upgrade has overwritten something critical? All the updates have been done inside the Virtualmin environment.

Dave

Tue, 02/05/2013 - 13:14
andreychek

Hmm, if netstat doesn't see port 10000, that suggests that Webmin isn't running.

What output do you see if you run this command:

/etc/init.d/webmin restart

Tue, 02/05/2013 - 13:24 (Reply to #8)
steamydave

Yipeeeee!

That did the trick.

Next question, why didn't webmin starting when the server is rebooted?!

[root@server109-228-12-164 webmin]# /etc/init.d/webmin restart Stopping Webmin server in /usr/libexec/webmin cat: /var/webmin/miniserv.pid: No such file or directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] Starting Webmin server in /usr/libexec/webmin

I've restarted the server and Virtualmin HAS restarted automatically this time. Looks like there was some kind of blip in the system - possibly due to updates?!

Thank you very, very much.

Dave

Tue, 02/05/2013 - 13:32 (Reply to #9)
steamydave

I spoke too soon.

That solved in on the test server, but the other server still has the problem. I entered the restart command but it has no effect on that server.

On that server the netstat did respond with

[root@bankphb ~]# netstat -anlp | grep :10000 tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 18390/perl udp 0 0 0.0.0.0:10000 0.0.0.0:* 18390/perl

Dave

Tue, 02/05/2013 - 13:41 (Reply to #10)
steamydave

This server is missing 10000 and 20000 from the iptables.

[root@bankphb ~]# iptables -L -n Chain INPUT (policy DROP) target prot opt source destination ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 state NEW ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 state NEW ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 state NEW ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53 state NEW ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 state NEW ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:69 state NEW ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:69 state NEW ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:25 state NEW ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:110 state NEW ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:143 state NEW ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:123 state NEW ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:20 state NEW ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:21 state NEW ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:3306 state NEW ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:3306 state NEW DROP all -- 0.0.0.0/0 0.0.0.0/0 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:10000

Chain FORWARD (policy DROP) target prot opt source destination

Chain OUTPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state NEW,RELATED,ESTABLISHED

I added 10000 back in, but I still can't get anything out of Virtualmin

Dave

Tue, 02/05/2013 - 13:49
steamydave

Hi, I'm back in again.

This seems to come back to an old problem I have had with Webmin/Virtualmin

When I list the iptable at the command line, they don't match the entries in the iptables in /etc/sysconfig

In this case, calling "service iptable restart" has allowed me back in.

Its almost as if there are 2 sets of firewall rules - one that the system uses on server restart, and one used when the service is restarted?!

Dave

Topic locked