Hi Timothy,

Thank you so much for your help.

I was using an earlier version of supervisor that did not have syslog.

Upgrading and redoing my conf fixed the problem.

Best Regards,
Bhaskar


On Thu, Jul 25, 2013 at 6:46 PM, Timothy Jones
<[email protected]>wrote:

>  In supervisor/loggers.py:****
>
> 337     elif filename == 'syslog':****
>
> 338         handlers.append(SyslogHandler())****
>
> ** **
>
> So, two things I would check… ****
>
> **1)      **Make sure you have 3.0b1 from 10 Sep 2012 or later.
> According to this [1], that’s when this feature was released.  My team is
> still on 3.0a8 from January 2010, so I didn’t find this feature in my
> features (I know, long overdue).  The fact that you’re getting a file
> CALLED syslog makes me think maybe you using an older version, like me.***
> *
>
> **2)      **Make sure that the line that you specify ‘stdout’ doesn’t
> have any trailing spaces, and the config file is not in DOS mode (CR/LF
> line endings instead of LF only like GOD intended J )   Either of these
> things might cause the comparison in 337 to not test True.  Might want to
> just set a breakpoint in loggers.py to check the parsed value of the
> ‘filename’ variable.****
>
> ** **
>
> [1] https://pypi.python.org/pypi/supervisor#b1-2012-09-10 ****
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Bhaskar Rao
> *Sent:* Thursday, July 25, 2013 7:49 PM
> *To:* [email protected]
> *Subject:* [Supervisor-users] remote syslog with supervisor****
>
> ** **
>
> Hey All,****
>
> ** **
>
> I had a question with using supervisor.****
>
> ** **
>
> This has been asked before, but I did not see an answer in the mailing
> list, so I was hoping to ask again, and hopefully someone can shed some
> light.****
>
> ** **
>
> I put an entry in the supervisor conf file that says:****
>
> ** **
>
> *stdout_logfile=syslog*****
>
> ** **
>
> but instead sending the output to syslog supervisor writes to a file it
> creates called syslog. Which is funny, but a little sad for me, since now I
> have no idea if my scripts are running or DEAD.****
>
> ** **
>
> What am I missing.****
>
> ** **
>
> Please help.****
>
> ** **
>
> Bhaskar****
>
> ** **
>
> ** **
>
_______________________________________________
Supervisor-users mailing list
[email protected]
https://lists.supervisord.org/mailman/listinfo/supervisor-users

Reply via email to