often can't login to :10000

flameproof · January 8, 2009, 10:13pm

Since 2 days I often can’t login to virtualmin’s address at https://###.###.###.###:10000

I get timeouts. It only works after I stop and restart the VPS.

What can that be?

flameproof · January 8, 2009, 10:17pm

One more note:

web pages and emails works fine.

After I restart the VPS login is no problem. But I see that BIND isn’t working. When manually start BIND I get: Failed to start service : Failed to start BIND : Starting named: named: already running[FAILED]

I haven’t that before.

Eric · January 8, 2009, 10:23pm

So everything on your server by Virtualmin works? The Websites are up, SSH is working, and such?

If so, my guess is that either:

Webmin is stopped for some reason, and needs to be restarted. You can do so by logging in over SSH, and typing: /etc/init.d/webmin restart
A firewall rule is blocking it; If you run "iptables -L -n", is the firewall enabled? And if so, is there a rule allowing port 10000?

Regarding BIND – where are you seeing that it isn’t working?

If you’re seeing a BIND error from within Virtualmin, my guess is that the status page there is incorrect.

You can manually make sure DNS is working by running something like "host google.com" from the command line – it should return an IP address to you.
-Eric

flameproof · January 8, 2009, 10:51pm

virtualmin just stopped responding in the middle of creating an email user of a new domain. First 2 mail boxes were fine.

>The Websites are up, SSH is working, and such?

Yes. Just logged in SSH

>by typing: /etc/init.d/webmin restart

Stopping Webmin server in /usr/libexec/webmin
/etc/webmin/stop: line 4: kill: (11724) - No such process
Starting Webmin server in /usr/libexec/webmin

After that I can login again.

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
[root@vps-1006512-323 ~]#[/b]

Looks OK, or?

>Regarding BIND – where are you seeing that it isn’t working?

After the SSH restart just now on the login screen I see not working:

Bind
Postfix
Dovecot (pop3 mailbox are accessible)
ProFTPd (however I FTP something right now to the VPS)

>host google.com
google.com has address 72.14.205.100
google.com has address 74.125.45.100
google.com has address 209.85.171.100
google.com mail is handled by 10 smtp1.google.com.
google.com mail is handled by 10 smtp2.google.com.
google.com mail is handled by 10 smtp3.google.com.
google.com mail is handled by 10 smtp4.google.com.

Eric · January 8, 2009, 11:54pm

Okay, so BIND is actually working fine.

But for some reason, Virtualmin/Webmin seems to be stopping or dieing.

Does anything interesting show up in /var/webmin/miniserv.error?
-Eric

flameproof · January 9, 2009, 12:08am

one time today I had a timeout with usermin, I got it back with
/etc/init.d/usermin restart

>Does anything interesting show up in /var/webmin/miniserv.error?

I have no /var/webmin/ - I do have /var/usermin/miniserv.error

Here it is:

[color=#FF0000][08/Jan/2009:00:45:53 -0600] miniserv.pl started
[08/Jan/2009:00:45:53 -0600] Perl module Authen::PAM needed for PAM is not installed : Can’t locate Authen/PAM.pm in @INC (@INC contains: /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 9) line 1.
BEGIN failed–compilation aborted at (eval 9) line 1.

restarting miniserv
[08/Jan/2009:00:46:17 -0600] Restarting
[08/Jan/2009:00:46:18 -0600] miniserv.pl started
[08/Jan/2009:00:46:18 -0600] Perl module Authen::PAM needed for PAM is not installed : Can’t locate Authen/PAM.pm in @INC (@INC contains: /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 9) line 1.
BEGIN failed–compilation aborted at (eval 9) line 1.

[08/Jan/2009:05:15:51 -0600] miniserv.pl started
[08/Jan/2009:05:15:51 -0600] Perl module Authen::PAM needed for PAM is not installed : Can’t locate Authen/PAM.pm in @INC (@INC contains: /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 9) line 1.
BEGIN failed–compilation aborted at (eval 9) line 1.

[08/Jan/2009:05:18:28 -0600] miniserv.pl started
[08/Jan/2009:05:18:28 -0600] Perl module Authen::PAM needed for PAM is not installed : Can’t locate Authen/PAM.pm in @INC (@INC contains: /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 9) line 1.
BEGIN failed–compilation aborted at (eval 9) line 1.

[08/Jan/2009:05:33:05 -0600] miniserv.pl started
[08/Jan/2009:05:33:05 -0600] Perl module Authen::PAM needed for PAM is not installed : Can’t locate Authen/PAM.pm in @INC (@INC contains: /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 9) line 1.
BEGIN failed–compilation aborted at (eval 9) line 1.

[08/Jan/2009:07:22:32 -0600] miniserv.pl started
[08/Jan/2009:07:22:32 -0600] Perl module Authen::PAM needed for PAM is not installed : Can’t locate Authen/PAM.pm in @INC (@INC contains: /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 9) line 1.
BEGIN failed–compilation aborted at (eval 9) line 1.

[08/Jan/2009:20:10:18 -0600] miniserv.pl started
[08/Jan/2009:20:10:18 -0600] Perl module Authen::PAM needed for PAM is not installed : Can’t locate Authen/PAM.pm in @INC (@INC contains: /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 9) line 1.
BEGIN failed–compilation aborted at (eval 9) line 1.

[08/Jan/2009:20:57:49 -0600] miniserv.pl started
[08/Jan/2009:20:57:49 -0600] Perl module Authen::PAM needed for PAM is not installed : Can’t locate Authen/PAM.pm in @INC (@INC contains: /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 9) line 1.
BEGIN failed–compilation aborted at (eval 9) line 1.

Failed to initialize SSL connection
[08/Jan/2009:21:00:09 -0600] miniserv.pl started
[08/Jan/2009:21:00:09 -0600] Perl module Authen::PAM needed for PAM is not installed : Can’t locate Authen/PAM.pm in @INC (@INC contains: /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 9) line 1.
BEGIN failed–compilation aborted at (eval 9) line 1.

[08/Jan/2009:21:00:09 -0600] Reloading configuration
[08/Jan/2009:21:16:21 -0600] miniserv.pl started
[08/Jan/2009:21:16:21 -0600] Perl module Authen::PAM needed for PAM is not installed : Can’t locate Authen/PAM.pm in @INC (@INC contains: /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 9) line 1.
BEGIN failed–compilation aborted at (eval 9) line 1.

[08/Jan/2009:21:16:21 -0600] Reloading configuration
[/color]

Seems he looks for Pam…

sgrayban · January 9, 2009, 5:12am

Failed to start BIND : Starting named: named: already running[FAILED]

killall -9 named

/etc/init.d/bind restart

Can't locate Authen/PAM.pm

yum install perl-Authen-PAM.i386

flameproof · January 10, 2009, 7:58am

Thanks for the help.

I also did a virtualmin modul recheck and was asked ask to add 127.0.0.1 to Bind’s server list (which I didn’t do so far). I will observe it that was the reason.

Joe · January 10, 2009, 5:11pm

Note that the Authen::PAM error is merely a warning. It’s a caught “exception”, so to speak, as that’s the only way to see if a module is present. If it is, Webmin uses it, if not is hits passwd/shadow directly. Either one works, as long as you don’t need Webmin to authenticate to LDAP or NIS or other PAM supported auth types.

flameproof · January 12, 2009, 11:45pm

I am still having this problem once in a while.

Just now again, webmin and usermin stopped responding and I got the timeout page.

op3 checking of mail boxes stopped too.

I did a /ect/init.d/webmin restart and /ect/init.d/usermin restart via SSH.

After login virtualmin showed that dovecot was running, but going to webmin>servers>dovecot it had the "start dovecot" button, so was probably down. After starting it pop3 access was normal again.

named is also sometimes stalling, but website access stays normal then.

How can I trace that stalling problems?

Eric · January 12, 2009, 11:48pm

Does anything show up in any of the logs in /var/log – /var/log/messages and perhaps /var/log/syslog?

How much RAM is in your system? Can you paste in the output of the command "free"?
-Eric

flameproof · January 13, 2009, 12:38am

Hi,
I have no /var/log/syslog but have /var/log/messages. I have 256 RAM and run 5 virtual domains with a shared IP. All are low activity.

[code:1]$free
total used free shared buffers cached
Mem: 292864 122752 170112 0 0 0
-/+ buffers/cache: 122752 170112
Swap: [/code:1] 0 0 0

/var/log/messages

[code:1]
Jan 11 04:02:13 vps syslogd 1.4.1: restart.
Jan 11 04:58:37 vps named[24329]: starting BIND 9.3.4-P1 -u named
Jan 11 04:58:37 vps named[24329]: found 8 CPUs, using 8 worker threads
Jan 11 04:58:37 vps named[24329]: loading configuration from ‘/etc/named.conf’
Jan 11 04:58:37 vps named[24329]: no IPv6 interfaces found
Jan 11 04:58:37 vps named[24329]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 11 04:58:37 vps named[24329]: listening on IPv4 interface venet0:0, 216...#53
Jan 11 04:58:37 vps named[24329]: command channel listening on 127.0.0.1#953
Jan 11 04:58:37 vps named[24329]: zone domain1.com/IN: loaded serial 1231398868
Jan 11 04:58:37 vps named[24329]: zone domain6.com/IN: loaded serial 1231467503
Jan 11 04:58:37 vps named[24329]: zone domain7.com/IN: loaded serial 1231558382
Jan 11 04:58:37 vps named[24329]: zone domain3.com/IN: loaded serial 1231399116
Jan 11 04:58:37 vps named[24329]: zone domain2.com.hk/IN: loaded serial 1231399071
Jan 11 04:58:37 vps named[24329]: running
Jan 11 05:30:15 vps proftpd[3970]: myVPShost.com (219.77.15.178[219.77.15.178]) - FTP session opened.
Jan 11 05:31:06 vps named[24329]: lame server resolving ‘130.226.158.66.in-addr.arpa’ (in ‘226.158.66.in-addr.arpa’?): 66.193.237.2#53
Jan 11 05:31:06 vps named[24329]: lame server resolving ‘130.226.158.66.in-addr.arpa’ (in ‘226.158.66.in-addr.arpa’?): 66.158.192.110#53
Jan 11 05:31:07 vps named[24329]: lame server resolving ‘130.226.158.66.in-addr.arpa’ (in ‘226.158.66.in-addr.arpa’?): 66.193.237.2#53
Jan 11 05:31:07 vps named[24329]: lame server resolving ‘130.226.158.66.in-addr.arpa’ (in ‘226.158.66.in-addr.arpa’?): 66.158.192.110#53
Jan 11 05:31:09 vps named[24329]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 129.250.35.229#53
Jan 11 05:31:09 vps named[24329]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 129.250.31.21#53
Jan 11 05:31:09 vps named[24329]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.94.123.4#53
Jan 11 05:31:09 vps named[24329]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 69.36.249.35#53
Jan 11 05:31:10 vps named[24329]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 213.130.47.21#53
Jan 11 05:31:10 vps named[24329]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.95.61.36#53
Jan 11 05:31:10 vps named[24329]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.95.61.4#53
Jan 11 05:31:10 vps named[24329]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 61.213.162.88#53
Jan 11 05:31:10 vps named[24329]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.94.123.36#53
Jan 11 05:31:10 vps named[24329]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 129.250.35.229#53
Jan 11 05:31:10 vps named[24329]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 129.250.31.21#53
Jan 11 05:31:10 vps named[24329]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 69.36.249.35#53
Jan 11 05:31:10 vps named[24329]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 213.130.47.21#53
Jan 11 05:31:11 vps named[24329]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.95.61.4#53
Jan 11 05:31:11 vps named[24329]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 61.213.162.88#53
Jan 11 05:31:11 vps named[24329]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.94.123.4#53
Jan 11 05:31:11 vps named[24329]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.94.123.36#53
Jan 11 05:31:11 vps named[24329]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.95.61.36#53
Jan 11 05:31:12 vps named[24329]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 11 05:31:12 vps named[24329]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 11 05:31:12 vps named[24329]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 11 05:31:12 vps named[24329]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 11 05:31:12 vps named[24329]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 11 05:31:12 vps named[24329]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 11 05:31:13 vps named[24329]: lame server resolving ‘47.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 11 05:31:13 vps named[24329]: lame server resolving ‘47.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 11 05:31:13 vps named[24329]: lame server resolving ‘47.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 11 05:31:15 vps named[24329]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 11 05:31:15 vps named[24329]: lame server resolving ‘51.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 11 05:31:15 vps named[24329]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 11 05:31:15 vps named[24329]: lame server resolving ‘51.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 11 05:31:15 vps named[24329]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 11 05:31:15 vps named[24329]: lame server resolving ‘51.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 11 05:31:16 vps named[24329]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 11 05:31:16 vps named[24329]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 11 05:31:16 vps named[24329]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 11 05:31:16 vps named[24329]: lame server resolving ‘214.107.213.74.in-addr.arpa’ (in ‘107.213.74.in-addr.arpa’?): 206.248.79.244#53
Jan 11 05:31:16 vps named[24329]: lame server resolving ‘214.107.213.74.in-addr.arpa’ (in ‘107.213.74.in-addr.arpa’?): 206.248.95.194#53
Jan 11 05:31:17 vps named[24329]: lame server resolving ‘214.107.213.74.in-addr.arpa’ (in ‘107.213.74.in-addr.arpa’?): 206.248.95.194#53
Jan 11 05:31:17 vps named[24329]: lame server resolving ‘214.107.213.74.in-addr.arpa’ (in ‘107.213.74.in-addr.arpa’?): 206.248.79.244#53
Jan 11 05:31:18 vps named[24329]: lame server resolving ‘47.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 11 05:31:18 vps named[24329]: lame server resolving ‘47.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 11 05:31:18 vps named[24329]: lame server resolving ‘47.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 11 05:31:20 vps named[24329]: lame server resolving ‘51.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 11 05:31:20 vps named[24329]: lame server resolving ‘51.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 11 05:31:21 vps named[24329]: lame server resolving ‘51.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 11 05:31:21 vps named[24329]: lame server resolving ‘254.44.255.194.in-addr.arpa’ (in ‘44.255.194.in-addr.arpa’?): 194.19.152.2#53
Jan 11 05:31:23 vps named[24329]: lame server resolving ‘202.200/29.195.160.12.in-addr.arpa’ (in ‘200/29.195.160.12.in-addr.arpa’?): 192.5.6.33#53
Jan 11 05:31:23 vps named[24329]: lame server resolving ‘202.200/29.195.160.12.in-addr.arpa’ (in ‘200/29.195.160.12.in-addr.arpa’?): 192.42.93.33#53
Jan 11 05:31:25 vps named[24329]: lame server resolving ‘254.44.255.194.in-addr.arpa’ (in ‘44.255.194.in-addr.arpa’?): 212.130.1.68#53
Jan 11 05:31:25 vps named[24329]: lame server resolving ‘254.44.255.194.in-addr.arpa’ (in ‘44.255.194.in-addr.arpa’?): 212.130.1.67#53
Jan 11 05:31:26 vps named[24329]: lame server resolving ‘254.44.255.194.in-addr.arpa’ (in ‘44.255.194.in-addr.arpa’?): 194.19.152.2#53
Jan 11 05:31:26 vps named[24329]: lame server resolving ‘254.44.255.194.in-addr.arpa’ (in ‘44.255.194.in-addr.arpa’?): 212.130.1.68#53
Jan 11 05:31:27 vps named[24329]: lame server resolving ‘254.44.255.194.in-addr.arpa’ (in ‘44.255.194.in-addr.arpa’?): 212.130.1.67#53
Jan 11 05:31:27 vps named[24329]: lame server resolving ‘227.194.201.65.in-addr.arpa’ (in ‘194.201.65.in-addr.arpa’?): 208.118.144.48#53
Jan 11 05:31:27 vps named[24329]: lame server resolving ‘227.194.201.65.in-addr.arpa’ (in ‘194.201.65.in-addr.arpa’?): 208.7.165.10#53
Jan 11 05:31:27 vps named[24329]: lame server resolving ‘227.194.201.65.in-addr.arpa’ (in ‘194.201.65.in-addr.arpa’?): 208.7.165.10#53
Jan 11 05:31:27 vps named[24329]: lame server resolving ‘227.194.201.65.in-addr.arpa’ (in ‘194.201.65.in-addr.arpa’?): 208.118.144.48#53
Jan 11 05:31:28 vps named[24329]: lame server resolving ‘202.200/29.195.160.12.in-addr.arpa’ (in ‘200/29.195.160.12.in-addr.arpa’?): 192.5.6.33#53
Jan 11 05:31:28 vps named[24329]: lame server resolving ‘202.200/29.195.160.12.in-addr.arpa’ (in ‘200/29.195.160.12.in-addr.arpa’?): 192.42.93.33#53
Jan 11 05:46:08 vps named[24329]: unexpected RCODE (REFUSED) resolving ‘dns.npptt.fj.cn/A/IN’: 202.101.115.55#53
Jan 11 05:46:08 vps named[24329]: unexpected RCODE (REFUSED) resolving ‘190.193.79.125.in-addr.arpa/PTR/IN’: 202.101.115.55#53
Jan 11 06:59:59 vps yum: Installed: patch - 2.5.4-29.2.2.i386
Jan 11 07:00:54 vps named[24329]: shutting down
Jan 11 07:00:54 vps named[24329]: stopping command channel on 127.0.0.1#953
Jan 11 07:00:54 vps named[24329]: no longer listening on 127.0.0.1#53
Jan 11 07:00:54 vps named[24329]: no longer listening on 216...#53
Jan 11 07:00:54 vps named[24329]: exiting
Jan 11 07:43:08 vps named[11984]: starting BIND 9.3.4-P1 -u named
Jan 11 07:43:08 vps named[11984]: found 8 CPUs, using 8 worker threads
Jan 11 07:43:08 vps named[11984]: loading configuration from ‘/etc/named.conf’
Jan 11 07:43:08 vps named[11984]: no IPv6 interfaces found
Jan 11 07:43:08 vps named[11984]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 11 07:43:08 vps named[11984]: listening on IPv4 interface venet0:0, 216...#53
Jan 11 07:43:08 vps named[11984]: command channel listening on 127.0.0.1#953
Jan 11 07:43:08 vps named[11984]: zone domain1.com/IN: loaded serial 1231398868
Jan 11 07:43:08 vps named[11984]: zone domain6.com/IN: loaded serial 1231467503
Jan 11 07:43:08 vps named[11984]: zone domain7.com/IN: loaded serial 1231558382
Jan 11 07:43:08 vps named[11984]: zone domain3.com/IN: loaded serial 1231399116
Jan 11 07:43:08 vps named[11984]: zone domain2.com.hk/IN: loaded serial 1231399071
Jan 11 07:43:08 vps named[11984]: running
Jan 11 07:43:08 vps proftpd[12033]: myVPShost.com - ProFTPD 1.3.0a (stable) (built Thu May 10 20:04:39 EDT 2007) standalone mode STARTUP
Jan 11 07:44:07 vps shutdown[13587]: shutting down for system halt
Jan 11 07:44:07 vps init: Switching to runlevel: 0
Jan 11 07:44:09 vps proftpd[12033]: myVPShost.com - ProFTPD killed (signal 15)
Jan 11 07:44:09 vps proftpd[12033]: myVPShost.com - ProFTPD 1.3.0a standalone mode SHUTDOWN
Jan 11 07:44:11 vps xinetd[15920]: Exiting…
Jan 11 07:44:11 vps named[11984]: shutting down: flushing changes
Jan 11 07:44:11 vps named[11984]: stopping command channel on 127.0.0.1#953
Jan 11 07:44:11 vps named[11984]: no longer listening on 127.0.0.1#53
Jan 11 07:44:11 vps named[11984]: no longer listening on 216...#53
Jan 11 07:44:11 vps named[11984]: exiting
Jan 11 07:44:14 vps exiting on signal 15
Jan 11 07:44:27 vps syslogd 1.4.1: restart.
Jan 11 07:44:27 vps kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jan 11 07:44:27 vps named[16349]: starting BIND 9.3.4-P1 -u named
Jan 11 07:44:27 vps named[16349]: found 8 CPUs, using 8 worker threads
Jan 11 07:44:27 vps named[16349]: loading configuration from ‘/etc/named.conf’
Jan 11 07:44:27 vps named[16349]: no IPv6 interfaces found
Jan 11 07:44:27 vps named[16349]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 11 07:44:27 vps named[16349]: listening on IPv4 interface venet0:0, 216...#53
Jan 11 07:44:27 vps named[16349]: command channel listening on 127.0.0.1#953
Jan 11 07:44:27 vps named[16349]: zone domain1.com/IN: loaded serial 1231398868
Jan 11 07:44:27 vps named[16349]: zone domain6.com/IN: loaded serial 1231467503
Jan 11 07:44:27 vps named[16349]: zone domain7.com/IN: loaded serial 1231558382
Jan 11 07:44:27 vps named[16349]: zone domain3.com/IN: loaded serial 1231399116
Jan 11 07:44:27 vps named[16349]: zone domain2.com.hk/IN: loaded serial 1231399071
Jan 11 07:44:27 vps named[16349]: running
Jan 11 07:44:27 vps xinetd[17413]: xinetd Version 2.3.14 started with libwrap loadavg labeled-networking options compiled in.
Jan 11 07:44:27 vps xinetd[17413]: Started working: 0 available services
Jan 11 07:44:32 vps proftpd[17727]: myVPShost.com - ProFTPD 1.3.0a (stable) (built Thu May 10 20:04:39 EDT 2007) standalone mode STARTUP
Jan 11 07:44:34 vps saslauthd[17786]: detach_tty : master pid is: 17786
Jan 11 07:44:34 vps saslauthd[17786]: ipc_init : listening on socket: /var/run/saslauthd/mux
Jan 11 07:44:50 vps init: no more processes left in this runlevel
Jan 11 07:44:50 vps named[16349]: shutting down
Jan 11 07:44:50 vps named[16349]: stopping command channel on 127.0.0.1#953
Jan 11 07:44:50 vps named[16349]: no longer listening on 127.0.0.1#53
Jan 11 07:44:50 vps named[16349]: no longer listening on 216...#53
Jan 11 07:44:51 vps named[16349]: exiting
Jan 11 07:48:56 vps named[19910]: starting BIND 9.3.4-P1 -u named
Jan 11 07:48:56 vps named[19910]: found 8 CPUs, using 8 worker threads
Jan 11 07:48:56 vps named[19910]: loading configuration from ‘/etc/named.conf’
Jan 11 07:48:56 vps named[19910]: no IPv6 interfaces found
Jan 11 07:48:56 vps named[19910]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 11 07:48:56 vps named[19910]: listening on IPv4 interface venet0:0, 216...#53
Jan 11 07:48:56 vps named[19910]: command channel listening on 127.0.0.1#953
Jan 11 07:48:56 vps named[19910]: zone domain1.com/IN: loaded serial 1231398868
Jan 11 07:48:56 vps named[19910]: zone domain6.com/IN: loaded serial 1231467503
Jan 11 07:48:56 vps named[19910]: zone domain7.com/IN: loaded serial 1231558382
Jan 11 07:48:56 vps named[19910]: zone domain3.com/IN: loaded serial 1231399116
Jan 11 07:48:56 vps named[19910]: zone domain2.com.hk/IN: loaded serial 1231399071
Jan 11 07:48:56 vps named[19910]: running
Jan 11 07:48:57 vps proftpd[19956]: myVPShost.com - ProFTPD 1.3.0a (stable) (built Thu May 10 20:04:39 EDT 2007) standalone mode STARTUP
Jan 12 04:29:09 vps named[19910]: lame server resolving ‘130.226.158.66.in-addr.arpa’ (in ‘226.158.66.in-addr.arpa’?): 66.193.237.2#53
Jan 12 04:29:09 vps named[19910]: lame server resolving ‘130.226.158.66.in-addr.arpa’ (in ‘226.158.66.in-addr.arpa’?): 66.158.192.110#53
Jan 12 04:29:09 vps named[19910]: lame server resolving ‘54.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 04:29:09 vps named[19910]: lame server resolving ‘48.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 04:29:09 vps named[19910]: lame server resolving ‘54.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 04:29:09 vps named[19910]: lame server resolving ‘48.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 04:29:10 vps named[19910]: lame server resolving ‘54.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 04:29:10 vps named[19910]: lame server resolving ‘48.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 04:29:11 vps named[19910]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 04:29:11 vps named[19910]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 04:29:11 vps named[19910]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 04:29:12 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘5.106.131.88.in-addr.arpa/PTR/IN’: 193.0.0.193#53
Jan 12 04:29:12 vps named[19910]: lame server resolving ‘130.226.158.66.in-addr.arpa’ (in ‘226.158.66.in-addr.arpa’?): 66.193.237.2#53
Jan 12 04:29:12 vps named[19910]: lame server resolving ‘130.226.158.66.in-addr.arpa’ (in ‘226.158.66.in-addr.arpa’?): 66.158.192.110#53
Jan 12 04:29:14 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘5.0-26.106.131.88.in-addr.arpa/PTR/IN’: 89.150.224.1#53
Jan 12 04:29:15 vps named[19910]: lame server resolving ‘48.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 04:29:15 vps named[19910]: lame server resolving ‘48.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 04:29:15 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘5.0-26.106.131.88.in-addr.arpa/PTR/IN’: 89.150.192.1#53
Jan 12 04:29:15 vps named[19910]: lame server resolving ‘48.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 04:29:15 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘5.0-26.106.131.88.in-addr.arpa/PTR/IN’: 89.150.192.1#53
Jan 12 04:29:15 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘5.0-26.106.131.88.in-addr.arpa/PTR/IN’: 89.150.224.1#53
Jan 12 04:29:16 vps named[19910]: lame server resolving ‘54.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 04:29:16 vps named[19910]: lame server resolving ‘54.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 04:29:16 vps named[19910]: lame server resolving ‘54.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 04:29:17 vps named[19910]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 04:29:17 vps named[19910]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 04:29:17 vps named[19910]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 04:29:17 vps named[19910]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 04:29:17 vps named[19910]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 04:29:17 vps named[19910]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 04:29:18 vps named[19910]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 04:29:18 vps named[19910]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 04:29:18 vps named[19910]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 05:29:12 vps named[19910]: lame server resolving ‘131.200.32.210.in-addr.arpa’ (in ‘200.32.210.in-addr.arpa’?): 210.32.200.10#53
Jan 12 05:29:12 vps named[19910]: lame server resolving ‘131.200.32.210.in-addr.arpa’ (in ‘200.32.210.in-addr.arpa’?): 210.32.200.10#53
Jan 12 05:31:02 vps named[19910]: lame server resolving ‘130.226.158.66.in-addr.arpa’ (in ‘226.158.66.in-addr.arpa’?): 66.193.237.2#53
Jan 12 05:31:02 vps named[19910]: lame server resolving ‘130.226.158.66.in-addr.arpa’ (in ‘226.158.66.in-addr.arpa’?): 66.158.192.110#53
Jan 12 05:31:02 vps named[19910]: lame server resolving ‘130.226.158.66.in-addr.arpa’ (in ‘226.158.66.in-addr.arpa’?): 66.193.237.2#53
Jan 12 05:31:02 vps named[19910]: lame server resolving ‘130.226.158.66.in-addr.arpa’ (in ‘226.158.66.in-addr.arpa’?): 66.158.192.110#53
Jan 12 05:31:04 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.95.61.4#53
Jan 12 05:31:04 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.94.123.36#53
Jan 12 05:31:04 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.95.61.36#53
Jan 12 05:31:04 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.94.123.4#53
Jan 12 05:31:05 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.95.61.4#53
Jan 12 05:31:05 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.95.61.36#53
Jan 12 05:31:05 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 129.250.35.229#53
Jan 12 05:31:05 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.94.123.36#53
Jan 12 05:31:05 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 213.130.47.21#53
Jan 12 05:31:05 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘200.28.52.216.in-addr.arpa/PTR/IN’: 64.94.123.4#53
Jan 12 05:31:05 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 61.213.162.88#53
Jan 12 05:31:05 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 69.36.249.35#53
Jan 12 05:31:05 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 129.250.31.21#53
Jan 12 05:31:06 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 129.250.31.21#53
Jan 12 05:31:06 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 129.250.35.229#53
Jan 12 05:31:06 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 69.36.249.35#53
Jan 12 05:31:06 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 213.130.47.21#53
Jan 12 05:31:06 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘16.9.174.140.in-addr.arpa/PTR/IN’: 61.213.162.88#53
Jan 12 05:31:09 vps named[19910]: lame server resolving ‘51.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 05:31:09 vps named[19910]: lame server resolving ‘51.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 05:31:09 vps named[19910]: lame server resolving ‘51.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 05:31:10 vps named[19910]: lame server resolving ‘214.107.213.74.in-addr.arpa’ (in ‘107.213.74.in-addr.arpa’?): 206.248.79.244#53
Jan 12 05:31:10 vps named[19910]: lame server resolving ‘214.107.213.74.in-addr.arpa’ (in ‘107.213.74.in-addr.arpa’?): 206.248.95.194#53
Jan 12 05:31:10 vps named[19910]: lame server resolving ‘47.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 05:31:10 vps named[19910]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 05:31:10 vps named[19910]: lame server resolving ‘47.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 05:31:10 vps named[19910]: lame server resolving ‘214.107.213.74.in-addr.arpa’ (in ‘107.213.74.in-addr.arpa’?): 206.248.79.244#53
Jan 12 05:31:10 vps named[19910]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 05:31:10 vps named[19910]: lame server resolving ‘214.107.213.74.in-addr.arpa’ (in ‘107.213.74.in-addr.arpa’?): 206.248.95.194#53
Jan 12 05:31:10 vps named[19910]: lame server resolving ‘47.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 05:31:11 vps named[19910]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 05:31:11 vps named[19910]: lame server resolving ‘254.44.255.194.in-addr.arpa’ (in ‘44.255.194.in-addr.arpa’?): 194.19.152.2#53
Jan 12 05:31:11 vps named[19910]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 05:31:12 vps named[19910]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 05:31:12 vps named[19910]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 05:31:13 vps named[19910]: lame server resolving ‘254.44.255.194.in-addr.arpa’ (in ‘44.255.194.in-addr.arpa’?): 212.130.1.68#53
Jan 12 05:31:14 vps named[19910]: lame server resolving ‘254.44.255.194.in-addr.arpa’ (in ‘44.255.194.in-addr.arpa’?): 212.130.1.67#53
Jan 12 05:31:15 vps named[19910]: lame server resolving ‘51.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 05:31:15 vps named[19910]: lame server resolving ‘51.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 05:31:15 vps named[19910]: lame server resolving ‘254.44.255.194.in-addr.arpa’ (in ‘44.255.194.in-addr.arpa’?): 194.19.152.2#53
Jan 12 05:31:15 vps named[19910]: lame server resolving ‘51.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 05:31:15 vps named[19910]: lame server resolving ‘254.44.255.194.in-addr.arpa’ (in ‘44.255.194.in-addr.arpa’?): 212.130.1.67#53
Jan 12 05:31:15 vps named[19910]: lame server resolving ‘254.44.255.194.in-addr.arpa’ (in ‘44.255.194.in-addr.arpa’?): 212.130.1.68#53
Jan 12 05:31:16 vps named[19910]: lame server resolving ‘47.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 05:31:16 vps named[19910]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 05:31:16 vps named[19910]: lame server resolving ‘47.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 05:31:16 vps named[19910]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 05:31:16 vps named[19910]: lame server resolving ‘47.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 05:31:16 vps named[19910]: lame server resolving ‘45.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 05:31:16 vps named[19910]: lame server resolving ‘202.200/29.195.160.12.in-addr.arpa’ (in ‘200/29.195.160.12.in-addr.arpa’?): 192.5.6.33#53
Jan 12 05:31:16 vps named[19910]: lame server resolving ‘202.200/29.195.160.12.in-addr.arpa’ (in ‘200/29.195.160.12.in-addr.arpa’?): 192.42.93.33#53
Jan 12 05:31:17 vps named[19910]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 05:31:17 vps named[19910]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 05:31:17 vps named[19910]: lame server resolving ‘34.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 05:31:17 vps named[19910]: lame server resolving ‘202.200/29.195.160.12.in-addr.arpa’ (in ‘200/29.195.160.12.in-addr.arpa’?): 192.42.93.33#53
Jan 12 05:31:17 vps named[19910]: lame server resolving ‘202.200/29.195.160.12.in-addr.arpa’ (in ‘200/29.195.160.12.in-addr.arpa’?): 192.5.6.33#53
Jan 12 05:31:17 vps named[19910]: lame server resolving ‘227.194.201.65.in-addr.arpa’ (in ‘194.201.65.in-addr.arpa’?): 208.7.165.10#53
Jan 12 05:31:17 vps named[19910]: lame server resolving ‘227.194.201.65.in-addr.arpa’ (in ‘194.201.65.in-addr.arpa’?): 208.118.144.48#53
Jan 12 05:31:22 vps named[19910]: lame server resolving ‘227.194.201.65.in-addr.arpa’ (in ‘194.201.65.in-addr.arpa’?): 208.7.165.10#53
Jan 12 05:31:22 vps named[19910]: lame server resolving ‘227.194.201.65.in-addr.arpa’ (in ‘194.201.65.in-addr.arpa’?): 208.118.144.48#53
Jan 12 05:31:26 vps named[19910]: lame server resolving ‘52.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 05:31:26 vps named[19910]: lame server resolving ‘52.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 05:31:26 vps named[19910]: lame server resolving ‘52.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 05:31:26 vps named[19910]: lame server resolving ‘52.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.66.53#53
Jan 12 05:31:26 vps named[19910]: lame server resolving ‘52.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.67.53#53
Jan 12 05:31:27 vps named[19910]: lame server resolving ‘52.194.80.208.in-addr.arpa’ (in ‘194.80.208.in-addr.arpa’?): 204.15.69.53#53
Jan 12 05:31:28 vps named[19910]: lame server resolving ‘144.0.171.72.in-addr.arpa’ (in ‘171.72.in-addr.arpa’?): 66.82.4.12#53
Jan 12 05:31:28 vps named[19910]: lame server resolving ‘144.0.171.72.in-addr.arpa’ (in ‘171.72.in-addr.arpa’?): 66.82.4.12#53
Jan 12 05:31:28 vps named[19910]: lame server resolving ‘245.61.209.141.in-addr.arpa’ (in ‘61.209.141.in-addr.arpa’?): 141.209.2.22#53
Jan 12 05:31:28 vps named[19910]: lame server resolving ‘245.61.209.141.in-addr.arpa’ (in ‘61.209.141.in-addr.arpa’?): 141.209.1.22#53
Jan 12 05:31:34 vps named[19910]: lame server resolving ‘245.61.209.141.in-addr.arpa’ (in ‘61.209.141.in-addr.arpa’?): 141.209.1.22#53
Jan 12 05:31:34 vps named[19910]: lame server resolving ‘245.61.209.141.in-addr.arpa’ (in ‘61.209.141.in-addr.arpa’?): 141.209.2.22#53
Jan 12 05:31:34 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘2.16.106.97.in-addr.arpa/PTR/IN’: 66.75.164.5#53
Jan 12 05:31:35 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘2.16.106.97.in-addr.arpa/PTR/IN’: 24.30.200.3#53
Jan 12 05:31:35 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘2.16.106.97.in-addr.arpa/PTR/IN’: 24.30.201.3#53
Jan 12 05:31:37 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘2.16.106.97.in-addr.arpa/PTR/IN’: 65.24.0.171#53
Jan 12 05:32:02 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘2.16.106.97.in-addr.arpa/PTR/IN’: 24.30.199.7#53
Jan 12 08:08:10 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘ns2.bta.net.cn/A/IN’: 202.106.196.233#53
Jan 12 08:08:10 vps named[19910]: unexpected RCODE (REFUSED) resolving ‘ns.bta.net.cn/A/IN’: 202.106.196.233#53
Jan 12 12:06:36 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘84.157.36.84.in-addr.arpa/PTR/IN’: 80.75.163.20#53
Jan 12 20:10:48 vps named[19910]: unexpected RCODE (SERVFAIL) resolving ‘11.67.150.211.in-addr.arpa/PTR/IN’: 211.150.124.82#53
Jan 12 21:24:57 vps named[32462]: starting BIND 9.3.4-P1 -u named
Jan 12 21:24:57 vps named[32462]: found 8 CPUs, using 8 worker threads
Jan 12 21:24:57 vps named[32462]: loading configuration from ‘/etc/named.conf’
Jan 12 21:24:57 vps named[32462]: no IPv6 interfaces found
Jan 12 21:24:57 vps named[32462]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 12 21:24:57 vps named[32462]: listening on IPv4 interface venet0:0, 216...#53
Jan 12 21:24:57 vps named[32462]: command channel listening on 127.0.0.1#953
Jan 12 21:24:57 vps named[32462]: zone domain1.com/IN: loaded serial 1231398868
Jan 12 21:24:57 vps named[32462]: zone domain6.com/IN: loaded serial 1231467503
Jan 12 21:24:57 vps named[32462]: zone domain7.com/IN: loaded serial 1231558382
Jan 12 21:24:57 vps named[32462]: zone domain3.com/IN: loaded serial 1231399116
Jan 12 21:24:57 vps named[32462]: zone domain2.com.hk/IN: loaded serial 1231399071
Jan 12 21:24:57 vps named[32462]: running
Jan 12 21:34:25 vps named[32462]: shutting down
Jan 12 21:34:25 vps named[32462]: stopping command channel on 127.0.0.1#953
Jan 12 21:38:33 vps named[9736]: starting BIND 9.3.4-P1 -u named
Jan 12 21:38:33 vps named[9736]: found 8 CPUs, using 8 worker threads
Jan 12 21:38:33 vps named[9736]: loading configuration from ‘/etc/named.conf’
Jan 12 21:38:33 vps named[9736]: no IPv6 interfaces found
Jan 12 21:38:33 vps named[9736]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 12 21:38:33 vps named[9736]: listening on IPv4 interface venet0:0, 216...***#53
Jan 12 21:38:33 vps named[9736]: command channel listening on 127.0.0.1#953
Jan 12 21:38:33 vps named[9736]: zone domain1.com/IN: loaded serial 1231398868
Jan 12 21:38:33 vps named[9736]: zone domain6.com/IN: loaded serial 1231467503
Jan 12 21:38:33 vps named[9736]: zone domain7.com/IN: loaded serial 1231558382
Jan 12 21:38:33 vps named[9736]: zone domain3.com/IN: loaded serial 1231399116
Jan 12 21:38:33 vps named[9736]: zone domain2.com.hk/IN: loaded serial 1231399071
Jan 12 21:38:33 vps named[9736]: running[/code:1]

Eric · January 13, 2009, 12:55am

Ahh, it’s possible that you’re seeing a low-memory problem.

I ran into something quite similar recently, where services just unexpectedly disappeared.

I’d look into this document here:

http://www.virtualmin.com/documentation/id,virtualmin_on_low_memory_systems/

Specifically, look into the first set of steps there to disable pre-loading of Webmin libraries. That should help free up some RAM for other programs.
-Eric

flameproof · January 15, 2009, 1:25am

Typically I use 105000 to 160000 Mb RAM. No idea if thre are some bursts. I did some tweaking according to the link above. Still, sometimes stalls one of them: Postfix, Dovecot, Webmin, Usermin

Is there a way to find out who is using what memory so I can identify the memory hogs?

Eric · January 15, 2009, 8:18pm

Well, if multiple services on your server are having problems, it’s not a Virtualmin specific issue.

However, I’d make sure you’re keeping an eye out in /var/log/messages for any odd messages that your daemons or the kernel are giving, as well as in the “dmesg” output.

You can use “top”, “ps auxw”, and tools such as that to get a view of the current memory usage, though maybe you need an automated tool to take snapshots for you throughout the day. Virtualmin can do that, you might want to see it’s take on the matter – try logging into Virtualmin, and clicking System Statistics on the bottom-left, and having it show you RAM and swap usage graphs.
-Eric

flameproof · January 15, 2009, 10:56pm

"top", "ps auxw" are both nice tools.

For:
virtualmin > System Information > Running processes > Memory

I get a current snapshot only similar to the 2 commands above. Biggest user is collectinfo.pl with 17%, about 50Mb. Clamscan is using sometimes 20% resources. I wonder if I really need that, Spamassin does also do some filtering, right? I will keep Clamav only for some higher risk domains.

Eric · January 15, 2009, 11:10pm

Collectinfo should only run every 30 minutes. Knowing that it means certain statistics won’t be as up to date, I edited root’s crontab, and made it run less often (every 2-3 hours or so).

For Clamscan, yeah, that can take up a bunch of resources. SpamAssassin does in fact do filtering, but it looks for spam, ClamAV is looking for viruses.

If your users run virus scanners on their desktops, then perhaps you could get away with not running it on your server, sure.
-Eric

flameproof · February 1, 2009, 11:42pm

The stalling is still with me. Sometimes I have to manually restart service several times within a few Minutes. In such a moment just now I tried the command "TOP" and saw that all my RAM was used up, mainly by lookup-domain.pl - which brought me here:

FS#4553 - lookup-domain.pl crash my server
http://www.virtualmin.com/index.php?option=com_flyspray&Itemid=82&do=details&task_id=4553

I did make Spamassassin start at boot. I don’t use ClamAV.

I will report back how it goes…

flameproof · February 2, 2009, 2:05am

I will report back how it goes…

No change. Still stalling.

Eric · February 2, 2009, 10:50am

Can you run "ps auxw > ps.txt" – and attach ps.txt to this thread?

Also, what is the output of the "free" command?

Thanks,
-Eric