Le 8 mars 2011 15:12, Henti Smith a écrit :
> > just make sure to get also the change in the next commit I just pushed :
> >
> http://shinken.git.sourceforge.net/git/gitweb.cgi?p=shinken/shinken;a=commit;h=531ddcda7bc7e86f52edb6127e7df551e163406f
> > otherwise you'll still get a slight problem ;)
Le 8 mars 2011 14:41, Grégory Starck a écrit :
> Le 8 mars 2011 14:33, Grégory Starck a écrit :
>
> 2011/3/8 Henti Smith
>>
>>> > effectively. but the solution is I think to found how/to what changed
>>> > delegateTo() with Pyro4 ; I'm looking,
>>> > should provide a real fix soon..
>>> > greg
Le 8 mars 2011 14:41, Grégory Starck a écrit :
> Le 8 mars 2011 14:33, Grégory Starck a écrit :
>
> 2011/3/8 Henti Smith
>>
>>> > effectively. but the solution is I think to found how/to what changed
>>> > delegateTo() with Pyro4 ; I'm looking,
>>> > should provide a real fix soon..
>>> > greg
Le 8 mars 2011 14:33, Grégory Starck a écrit :
> 2011/3/8 Henti Smith
>
>> > effectively. but the solution is I think to found how/to what changed
>> > delegateTo() with Pyro4 ; I'm looking,
>> > should provide a real fix soon..
>> > greg.
>>
>>
>> No problem. I'm happy to assist where I can.
>
2011/3/8 Henti Smith
> > effectively. but the solution is I think to found how/to what changed
> > delegateTo() with Pyro4 ; I'm looking,
> > should provide a real fix soon..
> > greg.
>
>
> No problem. I'm happy to assist where I can.
>
> H
>
yes thanks for that :)
Can you please try with f
> effectively. but the solution is I think to found how/to what changed
> delegateTo() with Pyro4 ; I'm looking,
> should provide a real fix soon..
> greg.
No problem. I'm happy to assist where I can.
H
--
What You Don
2011/3/8 nap
>
> On Tue, Mar 8, 2011 at 9:38 AM, Henti Smith wrote:
>
>> On Tue, Mar 8, 2011 at 10:33 AM, Hartmut Goebel
>> wrote:
>> > Am 08.03.2011 08:42, schrieb Henti Smith:
>> > try this:
>> >
>> > cd /usr/local/shinken
>> > bin/launch_all.sh
>>
>>
>>
> Traceback (most recent call last):
On Tue, Mar 8, 2011 at 3:16 PM, nap wrote:
> Hi,
>
> Not today sorry :(
>
> Can you try to launch with bin/launch_all_debug.sh instead of launch_all.sh
> ? You will have debug output for each daemon in /tmp.
arbiter.debug
We are now fully daemonized :) pid=58620
Traceback (most recent call last):
Hi,
Not today sorry :(
Can you try to launch with bin/launch_all_debug.sh instead of launch_all.sh
? You will have debug output for each daemon in /tmp.
Jean
On Tue, Mar 8, 2011 at 2:03 PM, Henti Smith wrote:
> On Tue, Mar 8, 2011 at 2:52 PM, nap wrote:
> > Hi,
> >
> > Thanks. This time it
On Tue, Mar 8, 2011 at 2:52 PM, nap wrote:
> Hi,
>
> Thanks. This time it sounds good. Can you look at the shinken.log file (in
> var if you keep the default configuration and start all daemons too)?
No log file in /var/log or /usr/local/shinken/var
nor are any processes actually running.
Are y
Hi,
Thanks. This time it sounds good. Can you look at the shinken.log file (in
var if you keep the default configuration and start all daemons too)?
Jean
On Tue, Mar 8, 2011 at 1:50 PM, Henti Smith wrote:
> > Hi,
> >
> > It sounds as a bug with Pyro4. Can you try to comment in
> shinken/daem
> Hi,
>
> It sounds as a bug with Pyro4. Can you try to comment in shinken/daemon.py
> the line
> self.pyro_obj.delegateTo(self)
> and restart?
Output at pastebin : http://pastebin.com/kAKY5e6g
Henti
--
What You Don't K
On Tue, Mar 8, 2011 at 9:38 AM, Henti Smith wrote:
> On Tue, Mar 8, 2011 at 10:33 AM, Hartmut Goebel
> wrote:
> > Am 08.03.2011 08:42, schrieb Henti Smith:
> > try this:
> >
> > cd /usr/local/shinken
> > bin/launch_all.sh
>
> /usr/local/shinken/bin
> Launching Scheduler (that is only in charge o
On Tue, Mar 8, 2011 at 10:33 AM, Hartmut Goebel
wrote:
> Am 08.03.2011 08:42, schrieb Henti Smith:
> try this:
>
> cd /usr/local/shinken
> bin/launch_all.sh
/usr/local/shinken/bin
Launching Scheduler (that is only in charge of the scheduling)
Using Pyro 4.1
modulemanager file ./shinken/modulesman
Am 08.03.2011 08:42, schrieb Henti Smith:
I followed the guide on
http://www.shinken-monitoring.org/wiki/installation_simple_configuration_and_first_launch
to test out shinken.
Thanks for point out, that there is a problem with this instruction.
try this:
cd /usr/local/shinken
bin/launch_all.s
Good day.
I followed the guide on
http://www.shinken-monitoring.org/wiki/installation_simple_configuration_and_first_launch
to test out shinken.
I'm running a freebsd system with python 2.6.6 and pyro 4.1
I tried statring shinken as the shinken user :
/usr/local/shinken/bin
Launching Scheduler
16 matches
Mail list logo
