diff options
| author | mh <mh@immerda.ch> | 2015-03-15 12:27:18 +0100 |
|---|---|---|
| committer | mh <mh@immerda.ch> | 2015-03-15 12:50:18 +0100 |
| commit | 3cf7362f383d2cfa705c3897f6199087c5ddb033 (patch) | |
| tree | 5724c1d74f8745bbc6ad981b0c957af7420d412d /manifests/munin.pp | |
| parent | 19a44ce97f59633002d844e2b37f2b26b2f1cfbc (diff) | |
exchange connections munin plugin
tor_connections started blocking and I wasn't able to find the root
cause for it nor an updated version of the plugin.
This also blocked munin itself, which had the issue that the node
disappeared within munin.
Based on https://lists.torproject.org/pipermail/tor-talk/2006-June/010486.html
it seems to more or less match the open filedescriptors and hence
we monitor rather this than rely on a unmanageable plugin.
The only drawback is that this must run as root, as non-root users
can't read the filedescriptors from proc.
Diffstat (limited to 'manifests/munin.pp')
| -rw-r--r-- | manifests/munin.pp | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/manifests/munin.pp b/manifests/munin.pp index 4412337..ef71f57 100644 --- a/manifests/munin.pp +++ b/manifests/munin.pp @@ -11,8 +11,9 @@ class tor::munin { config => "user debian-tor\n env.cookiefile /var/run/tor/control.authcookie\n env.port 19051" } munin::plugin::deploy { - 'tor_connections': - source => 'tor/munin/tor_connections'; + 'tor_openfds': + config => 'user root', + source => 'tor/munin/tor_openfds'; 'tor_routers': source => 'tor/munin/tor_routers'; 'tor_traffic': |