Munin WHM plugin in 64bit CentOS 5.5

[yoachan]

Dear all,

I'm currently using cPanel 11.25.0-R46156 - WHM 11.25.0 - in CENTOS 5.5 x86_64. After installation, the munin plugin runs only for about an hour and than stopped.
is there any problem with Munin in CentOS 5.5 x64, perl 5.8.8?

It runs nicely for an hour, and then Munin stopped logging at Jul 23 22:13 though munin's service is still running.

12345 ?        Ss     0:00 /usr/sbin/munin-node

this is my munin-node.log file:

2010/07/23-21:45:02 CONNECT TCP Peer: "127.0.0.1:26639" Local: "127.0.0.1:4949"
2010/07/23-21:45:04 Plugin "mailman" exited with status 768. ----
2010/07/23-21:50:01 CONNECT TCP Peer: "127.0.0.1:48038" Local: "127.0.0.1:4949"
find: WARNING: Hard link count is wrong for /proc: this may be a bug in your filesystem driver.  Automatically turning on find's -noleaf option.  Earlier results may have failed to include directories th
at should have been searched.
2010/07/23-21:50:04 Plugin "mailman" exited with status 768. ----
2010/07/23-21:56:25 CONNECT TCP Peer: "127.0.0.1:45910" Local: "127.0.0.1:4949"
2010/07/23-21:56:37 Plugin "mailman" exited with status 768. ----
2010/07/23-22:00:02 CONNECT TCP Peer: "127.0.0.1:46026" Local: "127.0.0.1:4949"
2010/07/23-22:00:05 Plugin "mailman" exited with status 768. ----
2010/07/23-22:13:34 CONNECT TCP Peer: "127.0.0.1:29334" Local: "127.0.0.1:4949"
2010/07/23-22:13:36 Plugin "mailman" exited with status 768. ----
2010/07/23-22:13:47 Plugin timeout: exim_mailqueue : Interrupted system call
 (pid 30408)
2010/07/23-22:37:55 Server closing!
Process Backgrounded
2010/07/24-11:38:19 MyPackage (type Net::Server::Fork) starting! pid(23871)
Using default listen value of 128
Binding to TCP port 4949 on host *
Setting gid to "10 10"
2010/07/24-11:38:24 Pid_file already exists for running process (23871)... aborting

  at line 277 in file /usr/lib/perl5/site_perl/5.8.8/Net/Server.pm
2010/07/24-11:38:24 Server closing!
2010/07/24-11:38:32 Pid_file already exists for running process (23871)... aborting

  at line 277 in file /usr/lib/perl5/site_perl/5.8.8/Net/Server.pm
2010/07/24-11:38:32 Server closing!
2010/07/24-11:38:43 Pid_file already exists for running process (23871)... aborting

  at line 277 in file /usr/lib/perl5/site_perl/5.8.8/Net/Server.pm
2010/07/24-11:38:43 Server closing!
2010/07/24-11:38:52 Pid_file already exists for running process (23871)... aborting

  at line 277 in file /usr/lib/perl5/site_perl/5.8.8/Net/Server.pm
2010/07/24-11:38:52 Server closing!
2010/07/24-11:59:19 Pid_file already exists for running process (23871)... aborting

  at line 277 in file /usr/lib/perl5/site_perl/5.8.8/Net/Server.pm
2010/07/24-11:59:19 Server closing!
2010/07/24-23:01:32 Pid_file already exists for running process (23871)... aborting

  at line 277 in file /usr/lib/perl5/site_perl/5.8.8/Net/Server.pm
2010/07/24-23:01:32 Server closing!
2010/07/24-23:02:52 Server closing!
Process Backgrounded
2010/07/24-23:02:57 MyPackage (type Net::Server::Fork) starting! pid(4909)
Using default listen value of 128
Binding to TCP port 4949 on host *
Setting gid to "10 10"
2010/07/24-23:20:47 CONNECT TCP Peer: "127.0.0.1:30519" Local: "127.0.0.1:4949"
2010/07/26-18:03:36 CONNECT TCP Peer: "127.0.0.1:38231" Local: "127.0.0.1:4949"
2010/07/26-18:07:05 Server closing!
Process Backgrounded
2010/07/26-18:07:05 MyPackage (type Net::Server::Fork) starting! pid(31504)
Using default listen value of 128
Binding to TCP port 4949 on host *
Setting gid to "10 10"
Use of uninitialized value in eval {block} exit at /usr/sbin/munin-node line 452, <CHILD> line 33.
2010/07/26-18:16:54 CONNECT TCP Peer: "127.0.0.1:16587" Local: "127.0.0.1:4949"
2010/07/26-18:17:20 Connection timed out.
timeout at /usr/sbin/munin-node line 584, <STDIN> line 2.
2010/07/26-18:27:33 Server closing!
Process Backgrounded
2010/07/26-18:27:34 MyPackage (type Net::Server::Fork) starting! pid(3817)
Using default listen value of 128
Binding to TCP port 4949 on host *
Setting gid to "10 10"
Use of uninitialized value in eval {block} exit at /usr/sbin/munin-node line 452, <CHILD> line 33.
2010/07/26-22:11:05 Server closing!

and since Jul 23 22:13, munin is no longer logging, and log files other than munin-node.log (munin-graph.log, munin-html.log, munin-limits.log, munin-update.log) stays like a rock), and Munin's graph is freeze at that time too.

some one have any idea?

any help appreciated.

regards,

YoChan

[handsonhosting]

No ideas on a resolution from my end, but I can attest that Munin does work on CentOS 5.5 64-bit on our servers without issue.

Do you maybe have a script running to kill programs that have been running for "X" minutes?

[yoachan]

Thanks for the replies...

No ideas on a resolution from my end, but I can attest that Munin does work on CentOS 5.5 64-bit on our servers without issue.

Ok that's good to hear.

Do you maybe have a script running to kill programs that have been running for "X" minutes?

As far as I know, I don't have such script.
Because munin's service is keep on running though it's not logging anything.

Debian have indeed come up with a very, very good release with Etch, especially if you run a server environment. If you want something you can do anything with, Etch is your man (or woman). However, CentOS is a bit more focused on the software it uses, especially with the use of things like Xen and libvirt. Maybe that might be important to some people, especially when running servers.

I don't get it...