Hi,
Are you really sure that nothing is listening on this port? When using
restart, I sometimes have some issues with shinken processes not being
killed as they should. That's why most of the time I use stop/start rather
than restart, and I check for remaining processes before doing the start.
Sorry if you already tried that (you speak of netstat), but you could try to
search for shinken processes with *ps -fu shinken* and for listening
processes on Pyro ports with *lsof -i ":7770"*?
Regards,
Denis GERMAIN
2011/9/23 Jörg Schulz <jorg.sch...@lnu.se>
> Hello
>
> OK , i got it , i could start shinken on SITE A , the I copied the same
> config to Site B, restart shinken ☹ the bad_start_arbiter log shows
> shinken.pyro_wrapper.PortNotFree: Sorry, the port 7770 is not free:
> Couldn't start Pyro daemon: [Errno 99] Cannot assign requested address
> But told me that he is the slave arbiter !
> but 7770 is free and not showing up in netstat
>
>
> Loading configuration
> Opening configuration file /etc/shinken/nagios.cfg
> Processing object config file
> '/usr/local/nagios/etc/objects/Default_collector/extended_host_info.cfg'
> Processing object config file
> '/usr/local/nagios/etc/objects/Default_collector/hosts.cfg'
> Processing object config file
> '/usr/local/nagios/etc/objects/Default_collector/hostgroups.cfg'
> Processing object config file
> '/usr/local/nagios/etc/objects/Default_collector/servicegroups.cfg'
> Processing object config file
> '/usr/local/nagios/etc/objects/Default_collector/services.cfg'
> Processing object config file
> '/usr/local/nagios/etc/objects/Default_collector/extended_service_info.cfg'
> Processing object config file
> '/usr/local/nagios/etc/objects/global/timeperiods.cfg'
> Processing object config file
> '/usr/local/nagios/etc/objects/global/service_templates.cfg'
> Processing object config file
> '/usr/local/nagios/etc/objects/global/contacts.cfg'
> Processing object config file
> '/usr/local/nagios/etc/objects/global/host_templates.cfg'
> Processing object config file
> '/usr/local/nagios/etc/objects/global/checkcommands.cfg'
> Processing object config file
> '/usr/local/nagios/etc/objects/global/misccommands.cfg'
> Processing object config file
> '/usr/local/nagios/etc/objects/global/contactgroups.cfg'
> Processing object config file '/etc/shinken/resource.cfg'
> Opening configuration file /etc/shinken/shinken-specific.cfg
> Warning : I autogenerated some Arbiter modules, please look at your
> configuration
> Warning : the module NamedPipe-Autogenerated is autogenerated
> I am the spare Arbiter : Arbiter-slave
> My own modules : NamedPipe-Autogenerated
> Warning in importing module : No module named redis
> Warning in importing module : No module named memcache
> Get a Named pipe module for plugin NamedPipe-Autogenerated
> I correctly loaded the modules : [NamedPipe-Autogenerated]
> All : (in/potential) (schedulers:2) (pollers:1/2) (reactionners:1/2)
> (brokers:1/2) (receivers:0/0)
> Running pre-flight check on configuration data...
> Checking global parameters...
> Checking hosts...
> Checked 308 hosts
> Checking hostgroups...
> Checked 27 hostgroups
> Checking contacts...
> Checked 1 contacts
> Checking contactgroups...
> Checked 31 contactgroups
> Checking notificationways...
> Checked 1 notificationways
> Checking escalations...
> Checked 0 escalations
> Checking services...
> Checked 102 services
> Checking servicegroups...
> Checked 0 servicegroups
> Checking timeperiods...
> Checked 7 timeperiods
> Checking commands...
> Checked 48 commands
> Checking servicedependencies...
> Checked 0 servicedependencies
> Checking hostdependencies...
> Checked 0 hostdependencies
> Checking arbiterlinks...
> Checked 2 arbiterlinks
> Checking schedulerlinks...
> Checked 2 schedulerlinks
> Checking reactionners...
> Checked 2 reactionners
> Checking pollers...
> Checked 2 pollers
> Checking brokers...
> Checked 2 brokers
> Checking receivers...
> Checked 0 receivers
> Checking resultmodulations...
> Checked 1 resultmodulations
> Checking discoveryrules...
> Checked 0 discoveryrules
> Checking discoveryruns...
> Checked 0 discoveryruns
> Checking criticitymodulations...
> Checked 0 criticitymodulations
> Cutting the hosts and services into parts
> Creating packs for realms
> Number of hosts in the realm All : 308
> Things look okay - No serious problems were detected during the pre-flight
> check
> Configuration Loaded
>
> Successfully changed to workdir: /var/lib/shinken
> opening pid file: /var/lib/shinken/arbiterd.pid
> /var/lib/shinken/arbiterd.pid
> stale pidfile exists (no or invalid or unreadable content). reusing it.
> CRITICAL ERROR : I got an non recovarable error. I must exit
> 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 413, in main
> self.do_daemon_init_and_start()
> File "/usr/local/lib64/python2.6/site-packages/shinken/daemon.py", line
> 429, in do_daemon_init_and_start
> self.setup_pyro_daemon()
> File "/usr/local/lib64/python2.6/site-packages/shinken/daemon.py", line
> 470, in setup_pyro_daemon
> self.pyro_daemon = pyro.ShinkenPyroDaemon(self.host, self.port,
> ssl_conf.use_ssl)
> File "/usr/local/lib64/python2.6/site-packages/shinken/pyro_wrapper.py",
> line 77, in __init__
> raise PortNotFree(msg)
> PortNotFree: Sorry, the port 7770 is not free: Couldn't start Pyro daemon:
> [Errno 99] Cannot assign requested address
>
> Traceback (most recent call last):
> File "/usr/local/bin/shinken-arbiter", line 100, in <module>
> daemon.main()
> File
> "/usr/local/lib64/python2.6/site-packages/shinken/daemons/arbiterdaemon.py",
> line 413, in main
> self.do_daemon_init_and_start()
> File "/usr/local/lib64/python2.6/site-packages/shinken/daemon.py", line
> 429, in do_daemon_init_and_start
> self.setup_pyro_daemon()
> File "/usr/local/lib64/python2.6/site-packages/shinken/daemon.py", line
> 470, in setup_pyro_daemon
> self.pyro_daemon = pyro.ShinkenPyroDaemon(self.host, self.port,
> ssl_conf.use_ssl)
> File "/usr/local/lib64/python2.6/site-packages/shinken/pyro_wrapper.py",
> line 77, in __init__
> raise PortNotFree(msg)
> shinken.pyro_wrapper.PortNotFree: Sorry, the port 7770 is not free:
> Couldn't start Pyro daemon: [Errno 99] Cannot assign requested address
>
>
>
> Jörg Schulz
>
> From: nap [mailto:napar...@gmail.com]
> Sent: den 22 september 2011 15:25
> To: shinken-devel@lists.sourceforge.net
> Subject: Re: [Shinken-devel] HA config
>
>
> On Thu, Sep 22, 2011 at 3:02 PM, Jörg Schulz <jorg.sch...@lnu.se> wrote:
> Hi
> [...]
> 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
> self.load_config_file()
> File
> "/usr/local/lib64/python2.6/site-packages/shinken/daemons/arbiterdaemon.py",
> line 246, in load_config_file
> "Thanks.")
> 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
> Hi,
>
> 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 :)
>
> Regards,
>
>
> Jean
>
> Local is no problem
>
> Cheers
> /J
>
>
> Jörg Schulz
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> Shinken-devel mailing list
> Shinken-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
