Ok, about every 5 minutes, collectinfo.pl runs and it basically slams the CPU, and load. Load will be at about 0.45 and jump to 20.00+ when collectinfo.pl starts running. It seems to lock everything up until it is finished.

Perusing through the code, the only assumption I can come up with is that it is locking a file(s) somewhere that is needed by httpd, such as a log or conf file..

Never had much of a problem with it before.. Last night I upgraded webmin, then virtualmin to the latest versions in hopes this would stop.

Is there some sort of log file it is choking on? Anything to look for?

It is getting to the point where I might just disable the job because it is bringing all the sites down..

Anyone?

Howdy Jafo,

It's not locking any files that would prevent web service. I'm guessing it's just overloading your box. I believe 3.49 should have made collectinfo.pl less demanding rather than more...nice is used to run it at the least demanding priority.

Any chance memory is a problem? If Apache gets pushed out to swap, it could make service quite slow.

collectinfo.pl has failed a few times lately on my box. I will make a note of the error email report next time it happens.

Any chance memory is a problem? If Apache gets pushed out to swap, it could make service quite slow.

Thanks, I really appreciate your reply!

It is possible, however this would be a new thing as it has run fine for about 6 months now. Really have not added anything new to the server and traffic is within normal parameters.

I disabled the cron job last night and my load stats are back to normal.

What adverse affects will this have on virtualmin if it is not running?

Any adverse effects?

Not really any adverse effects, except you won't have useful data on the system information page. collectinfo.pl is what gathers that data on a regular basis. This includes the historic graphs.

Here's a couple of recently botched cron jobs.

From root@--.net (Cron Daemon)
To root@--.net
Date Wed, 19 Dec 2007 07:15:13 -0500 (EST)
Subject Cron <root@--> /etc/webmin/virtual-server/collectinfo.pl

Message text

Error: Failed to query Postfix config command to get the current value of parameter
process_id_directory: <tt></tt>
Error
-----
Failed to query Postfix config command to get the current value of parameter process_id_directory:
<tt></tt>
-----


From root@--.net (Cron Daemon)
To root@--.net
Date Tue, 18 Dec 2007 00:10:03 -0500 (EST)
Subject Cron <root@--> /etc/webmin/status/monitor.pl

Message text

postfix::is_postfix_running failed : Failed to query Postfix config command to get
the current value of parameter process_id_directory: <tt></tt> at ../web-lib-funcs.pl
line 980.

Any chance this is a virtuozzo virtual server?

My server is not. It's a fairly unburdened dual Xeon with 4 gigs RAM.

I'm not experiencing the same collectinfo.pl freakout as the guy above, but I am getting daily failures of Cron jobs. The 4:00am ones I would normally write off because that's when my backups are scheduled -- but the others are happening when there's really no burden... though sometimes during a hammering or brute force.

Date Mon, 24 Dec 2007 09:45:17 -0500 (EST)
Subject Cron <root@asdf> /etc/webmin/virtual-server/collectinfo.pl

Message text

sh: line 1: 13706 Segmentation fault "/usr/sbin/httpd" -l 2>/dev/null
Date Mon, 24 Dec 2007 14:35:02 -0500 (EST)
Subject Cron <root@asdf> /etc/webmin/status/monitor.pl

Message text

postfix::is_postfix_running failed : Failed to query Postfix config command to get
the current value of parameter queue_directory: <tt></tt> at ../web-lib-funcs.pl
line 980.


Date Sun, 23 Dec 2007 08:10:03 -0500 (EST)
Subject Cron <root@asdf> /etc/webmin/status/monitor.pl

Message text

sh: line 1: 31307 Segmentation fault su postgres -c /usr/bin/psql
-U postgres -c '' template1 2>&1


Date Sun, 23 Dec 2007 04:02:13 -0500 (EST)
Subject Cron <root@asdf> run-parts /etc/cron.daily

Message text

/etc/cron.daily/logrotate:

[Sun Dec 23 04:02:10 2007] [warn] VirtualHost 66.129.2.84:80 overlaps with VirtualHost
66.129.2.84:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Dec 23 04:02:10 2007] [warn] NameVirtualHost 66.129.2.83:80 has no VirtualHosts
[Sun Dec 23 04:02:10 2007] [warn] VirtualHost 66.129.2.84:80 overlaps with VirtualHost
66.129.2.84:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Dec 23 04:02:10 2007] [warn] NameVirtualHost 66.129.2.83:80 has no VirtualHosts
[Sun Dec 23 04:02:10 2007] [warn] VirtualHost 66.129.2.84:80 overlaps with VirtualHost
66.129.2.84:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Dec 23 04:02:10 2007] [warn] NameVirtualHost 66.129.2.83:80 has no VirtualHosts
[Sun Dec 23 04:02:10 2007] [warn] VirtualHost 66.129.2.84:80 overlaps with VirtualHost
66.129.2.84:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Dec 23 04:02:10 2007] [warn] NameVirtualHost 66.129.2.83:80 has no VirtualHosts
[Sun Dec 23 04:02:11 2007] [warn] VirtualHost 66.129.2.84:80 overlaps with VirtualHost
66.129.2.84:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Dec 23 04:02:11 2007] [warn] NameVirtualHost 66.129.2.83:80 has no VirtualHosts
[Sun Dec 23 04:02:11 2007] [warn] VirtualHost 66.129.2.84:80 overlaps with VirtualHost
66.129.2.84:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Dec 23 04:02:11 2007] [warn] NameVirtualHost 66.129.2.83:80 has no VirtualHosts
[Sun Dec 23 04:02:11 2007] [warn] VirtualHost 66.129.2.84:80 overlaps with VirtualHost
66.129.2.84:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Dec 23 04:02:11 2007] [warn] NameVirtualHost 66.129.2.83:80 has no VirtualHosts
[Sun Dec 23 04:02:11 2007] [warn] VirtualHost 66.129.2.84:80 overlaps with VirtualHost
66.129.2.84:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Dec 23 04:02:11 2007] [warn] NameVirtualHost 66.129.2.83:80 has no VirtualHosts
[Sun Dec 23 04:02:12 2007] [warn] VirtualHost 66.129.2.84:80 overlaps with VirtualHost
66.129.2.84:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Dec 23 04:02:12 2007] [warn] NameVirtualHost 66.129.2.83:80 has no VirtualHosts
[Sun Dec 23 04:02:12 2007] [warn] VirtualHost 66.129.2.84:80 overlaps with VirtualHost
66.129.2.84:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Dec 23 04:02:12 2007] [warn] NameVirtualHost 66.129.2.83:80 has no VirtualHosts
[Sun Dec 23 04:02:12 2007] [warn] VirtualHost 66.129.2.84:80 overlaps with VirtualHost
66.129.2.84:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Dec 23 04:02:12 2007] [warn] NameVirtualHost 66.129.2.83:80 has no VirtualHosts
[Sun Dec 23 04:02:13 2007] [warn] VirtualHost 66.129.2.84:80 overlaps with VirtualHost
66.129.2.84:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Dec 23 04:02:13 2007] [warn] NameVirtualHost 66.129.2.83:80 has no VirtualHosts