On Feb 16, 2007, at 6:38 PM, Richard Harding wrote:
>
> Christopher Arndt wrote:
>> Richard Harding schrieb:
>>
>>> If I remove all of the log files that get created
>>> /var/log/supervisord.log
>>> /var/log/tg-avw-supervisor.log
>>> and the tg specific /home/rharding/src/tg-avw/server.log
>>>
>>> the first two get created when I run supervisor in the background
>>> with
>>> owner root:root and permissions 644. The tg-avw-supervisor.log is
>>> empty
>>> and the supervisord.log has the same series of errors I
>>> originally posted.
>>>
>>
>> Can you establish whether supervisor runs the 'start-
>> avwsystems.py' script at
>> all when it runs in the background? Check if the script itself
>> fails (by
>> replacing it with something simple, fail-safe that write something
>> to a file)
>> or if excuting the script already fails.
>>
> I replaced start-avwsytems.py with:
> #!/usr/bin/python2.4
>
> fout = open('test.txt', 'w')
> fout.write('I have been run')
> fout.close()
Hmm, daemonized apps usually run from "/" as working directory (they
should). If supervisord is not running as root and you don't use
absloute paths for logs, etc then supervisord will try to write them
at "/" miserably failing to do so. Have you checked this is not the
case?
HTH,
Alberto
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
