On Fri, Sep 23, 2011 at 1:09 PM, Denis GERMAIN <dt.germ...@gmail.com> wrote:
> 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
Hi,
You can also look at the address parameter of your arbiter object. It should
be a valid name so the network stack will now which interface to open. By
default ti's localhost, but in a HA installation it's of course not a good
idea, because the other daemon will not know the real address. If unsure,
look if you got your own address entry in /etc/hosts, and not for 127.0.0.1
but the real LAN entry.
Jean
------------------------------------------------------------------------------
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
