On Thu, Sep 22, 2011 at 3:02 PM, Jörg Schulz <firstname.lastname@example.org>
You can log a bug ticket at https://sourceforge.net/apps/trac/shinken/newticket for geting help
Back trace of it: Traceback (most recent call last):
File "/usr/local/lib64/python2.6/site-packages/shinken/daemons/arbiterdaemon.py", line 411, in main
File "/usr/local/lib64/python2.6/site-packages/shinken/daemons/arbiterdaemon.py", line 246, in load_config_file
TypeError: exit expected at most 1 arguments, got 2
What I did was to copy the " shinken-specific-high-availability.cfg" > shinken-specific.cfg , maybe wrong ?
I followed the " http://www.shinken-monitoring.org/wiki/setup_high_availability_shinken" scenario
It's a bug. The message it is trying to raise is :
Error: I cannot find my own Arbiter object, I bail out. "
"To solve it, please change the host_name parameter in "
"the object Arbiter in the file shinken-specific.cfg. "
"With the value BLABLA Thanks"
(with BLABLA the hostname value)
Thanks for reporting it, I'm fixing this :)
For your installation, it means that the host_name parameters in your shinken-specific.cfg file are not configured correctly. You should put in the arbiters objects the host_name value that you got with a hostname command, so the arbiter will got a way to find which arbiter object it is :)
Local is no problem