Hi all,

 

I do have a problem getting the scheduler daemon to run on a satellite.

Main server with the daemons are running correctly. (Arbiter, broker,
etc.)

 

When trying to start the scheduler on a satellite I receive the
following error in the debug file.

 

We are now fully daemonized :) pid=25220

The Arbiter Interface is at:
PYRO://192.168.10.50:7768/0a28806462824ad753b310a6e4e1a815

Waiting for initial configuration

Traceback (most recent call last):

  File "/usr/local/shinken/bin/../bin/shinken-scheduler", line 117, in ?

    daemon.main()

  File "./shinken/daemons/schedulerdaemon.py", line 344, in main

  File "./shinken/daemon.py", line 154, in do_mainloop

  File "./shinken/daemons/schedulerdaemon.py", line 231, in do_loop_turn

  File "./shinken/daemon.py", line 596, in wait_for_initial_conf

  File "./shinken/log.py", line 63, in log

IOError: [Errno 9] Bad file descriptor

close failed: [Errno 9] Bad file descriptor

 

 

I have tested this on RHEL5 and RHEL6 systems, means with Python 2.4 and
2.6 environments, also with easy install (just copying the dir) and with
full install, but In both cases same error. Just as a side note these
systems are running in virtual environments which shouldn't have an
impact though.

 

One additional question I do have as well. How does the scheduler know
where or better who the arbiter is, or is that daemon just waiting for
connection from it ?

 

Also in line two of the debug it says the Arbiter interface is at
192.168.10.50 which is the IP of the satellite, not the one of the
Arbiter, but that might be correct or a misunderstanding from my side.

 

Michael

 

 

 

 

 

 


**********************
** LEGAL DISCLAIMER **
**********************

This E-mail message and any attachments may contain 
legally privileged, confidential or proprietary 
information. If you are not the intended recipient(s),
or the employee or agent responsible for delivery of 
this message to the intended recipient(s), you are 
hereby notified that any dissemination, distribution 
or copying of this E-mail message is strictly 
prohibited. If you have received this message in 
error, please immediately notify the sender and 
delete this E-mail message from your computer.
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel

Reply via email to