Re: [munin-users] rrdcached_socket ignored?

[Andrei-Florian S. <and...@gm...>]

Hello again,

I seem to have found out the cause, but I don't know the solution:
RHEL 6 comes with rrdtool 1.3.8, which does not support the --daemon
option; so no data gets passed to rrdcached.
On the system in question, I also have OMD installed, which has rrdtool
1.4.7 in /opt/omd/versions/default/bin/rrdtool
How can i "convince" munin to use that rrdtool, instead of the default one?
Maybe without recompiling? :D

Thanks.


On Thu, May 30, 2013 at 2:29 PM, Andrei-Florian Staicu <
and...@gm...> wrote:

> Hi all,
>
> I have a new installation of Munin 2.0.12 on RHEL 6. Everything works
> perfectly from the rpms, including cgi and async integration. However, I'm
> not sure that the rrdcached_socket option is really in use.
> Right now, I have in /etc/munin/munin.conf
> rrdcached_socket /opt/munin/munin_run/rrdcached.sock
>
> Rrdcached is started with
> /opt/omd/versions/default/bin/rrdcached -g -w 3600 -z 1800 -f 7200 -s
> rrdcached -m 660 -l unix:/opt/munin/munin_run/rrdcached.sock -p
> /opt/munin/munin_run/rrdcached.pid -j /opt/munin/munin_run/rrdcached -b
> /opt/munin/munin_db
> and show only this:
> starting up
> checking for journal files
> started new journal
> /opt/munin/munin_run/rrdcached/rrd.journal.1369899064.805892
> journal processing complete
> listening for connections
>
> Also, stracing the rrdcached shows only this:
> strace -p `pgrep rrdcached`
> Process 9688 attached - interrupt to quit
> restart_syscall(<... resuming interrupted call ...>) = 0
> poll([{fd=4, events=POLLIN|POLLPRI}], 1, 1000) = 0 (Timeout)
> poll([{fd=4, events=POLLIN|POLLPRI}], 1, 1000) = 0 (Timeout)
> poll([{fd=4, events=POLLIN|POLLPRI}], 1, 1000) = 0 (Timeout)
> poll([{fd=4, events=POLLIN|POLLPRI}], 1, 1000) = 0 (Timeout)
>
> And grep rrdcached /var/log/munin* returns no results.
> Any idea on how I could verify that rrdcached is _really_ used?
>
> Thanks.
>



-- 
Beware of programmers who carry screwdrivers!