[Buildbot-devel] Problems with launchd

[john gale]

On Jun 27, 2008, at 7:46 AM, Daniel wrote:

> Unfortunately, googling 'buildbot twisted "no module named python"'
> returns 0 results... any idea what might be causing this error or how
> to work around it?
>
> Also, I don't understand how the specified plist is supposed to work:
> it launches /usr/local/bin/twistd, not buildbot... can someone explain
> that to me?



Hey Daniel ~

buildbot itself is essentially just a library of twistd modules, so  
that's why the "formal" command to start it calles twistd instead of  
buildbot.  Since launchd watches a process to determine whether it  
exits successfully, you can't give it the "buildbot" command, since  
that exits cleanly even though buildbot is still running in the  
background.  Launchd would then get confused as to the actual state of  
buildbot...  is it running, or isn't it?

The problem you're having sounds like it can't easily find your python  
modules.  Can you start buildbot yourself manually, or does it give  
the same error?  If you can start it yourself, then the environment  
vars in the launchd plist might be telling people to look in the wrong  
location.

Try removing this key, and the <dict> that follows it from the plist:
<key>EnvironmentVariables</key>

Then restart the process and try again (you can unload plists by using  
'launchctl unload <pathToPlist>', and then similarly 'launchctl load  
<pathToPlist>' )

Hope that helps,

	~ john

=================
support the arts!
www.smadness.com

updated October 12, 2005