search

munin-monitoring / contrib

Contributed stuff for munin (plugins, tools, etc...)
http://munin-monitoring.org
1.05k stars 683 forks source link

shoutcast2_multi #861

Open fiesi opened 7 years ago

fiesi commented 7 years ago

Hello,

We have several Shoutcast2 servers and would like to use the multiplugin. How can we run the plugin several times in munin?

I have the following error in the log:

2017/07/17 15:15:01 [INFO]: Starting munin-update
2017/07/17 15:15:01 [INFO] starting work in 16497 for Server01.blabla.net/127.0.0.1:4949.
2017/07/17 15:15:01 [INFO] node Server01.blabla.net advertised itself as panel.blabla.net instead.
2017/07/17 15:15:03 [WARNING] Service collision: plugin shoutcast2_multi_blabla on Server01.blabla.net/127.0.0.1:4949 reports shoutcast2_listeners which already exists on that host.  Deleting new data.
2017/07/17 15:15:03 [WARNING] Service collision: plugin shoutcast2_multi_blabla on Server01.blabla.net/127.0.0.1:4949 reports shoutcast2_active.active_sid_1 which already exists on that host.  Deleting new data.
2017/07/17 15:15:03 [WARNING] Service collision: plugin shoutcast2_multi_blabla on Server01.blabla.net/127.0.0.1:4949 reports shoutcast2_active which already exists on that host.  Deleting new data.
2017/07/17 15:15:03 [WARNING] Service collision: plugin shoutcast2_multi_blabla on Server01.blabla.net/127.0.0.1:4949 reports shoutcast2_listeners.listeners_sid_1 which already exists on that host.  Deleting new data.
2017/07/17 15:15:04 [INFO]: Munin-update finished for node blabla.net;Server01.blabla.net (3.01 sec)
2017/07/17 15:15:04 [INFO] Reaping Munin::Master::UpdateWorker<blabla.net;Server01.blabla.net>.  Exit value/signal: 0/0
2017/07/17 15:15:04 [INFO]: Munin-update finished (3.05 sec)
2017/07/17 15:20:01 [INFO]: Starting munin-update
2017/07/17 15:20:01 [INFO] starting work in 17473 for Server01.blabla.net/127.0.0.1:4949.
2017/07/17 15:20:01 [INFO] node Server01.blabla.net advertised itself as panel.blabla.net instead.
2017/07/17 15:20:03 [WARNING] Service collision: plugin shoutcast2_multi_blabla on Server01.blabla.net/127.0.0.1:4949 reports shoutcast2_active.active_sid_1 which already exists on that host.  Deleting new data.
2017/07/17 15:20:03 [WARNING] Service collision: plugin shoutcast2_multi_blabla on Server01.blabla.net/127.0.0.1:4949 reports shoutcast2_listeners which already exists on that host.  Deleting new data.
2017/07/17 15:20:03 [WARNING] Service collision: plugin shoutcast2_multi_blabla on Server01.blabla.net/127.0.0.1:4949 reports shoutcast2_listeners.listeners_sid_1 which already exists on that host.  Deleting new data.
2017/07/17 15:20:03 [WARNING] Service collision: plugin shoutcast2_multi_blabla on Server01.blabla.net/127.0.0.1:4949 reports shoutcast2_active which already exists on that host.  Deleting new data.
2017/07/17 15:20:04 [INFO]: Munin-update finished for node blabla.net;Server01.blabla.net (2.76 sec)
2017/07/17 15:20:04 [INFO] Reaping Munin::Master::UpdateWorker<blabla.net;Server01.blabla.net>.  Exit value/signal: 0/0
2017/07/17 15:20:04 [INFO]: Munin-update finished (2.81 sec)

thx vor your help

sumpfralle commented 7 years ago

Indeed the namespace of two shoutcast plugins on the same host overlap and thus cause a conflict.

I think, there are two ways for you to solve this problem:

What do you think?

fiesi commented 7 years ago

A) run the munin plugin on each shoutcast server

This ist a Bad Idea ;) We have 4 Shoutcast Server on One Server ;)

B) add an optional configurable name prefix (e.g. via an environment variable) to the shoutcast plugin (I would be happy to review your pull request)

That would be better. Then you can run the plugin several times

github-actions[bot] commented 3 years ago

Stale issue message