After binding server to directory service lighttpd and mongrel won't start
I needed to bind my server to our organization's Active Directory domain today and after that now LightTPD and Mongrel refuse to start on reboot. I can unload, then load the LaunchDaemons for each item and things are fine, but obviously I'd rather not have to do that every time I reboot the server. I had the exact same issue last month with just LightTPD, you can see the thread here: http://lists.macosforge.org/pipermail/macports-users/2007-June/ 004009.html Now that I've added the AD to the mix I'm wondering if there is something I can try different. Any suggestions? -- Sterling Anderson http://sterlinganderson.net/ sterling_anderson[at]mac.com 608.239.8387
Sterling Anderson <sterling_anderson@mac.com> writes:
I needed to bind my server to our organization's Active Directory domain today and after that now LightTPD and Mongrel refuse to start on reboot. I can unload, then load the LaunchDaemons for each item and things are fine, but obviously I'd rather not have to do that every time I reboot the server.
I had the exact same issue last month with just LightTPD, you can see the thread here:
http://lists.macosforge.org/pipermail/macports-users/2007-June/ 004009.html
Now that I've added the AD to the mix I'm wondering if there is something I can try different. Any suggestions?
Sterling, Can you be more specific? Did inserting this into the .plist file allow the LightTPD to startup at boot or not? <string>--restart-netchange</string> Or did it work and now suddenly it fails to boot again after changing trying to authenticate against active directory? If it needs to wait after boot a bit to work, and I've seen some apps this way, you can use a wrapper shell script with a "sleep 30" in it to introduce a 30s delay. See the snort port because it does this. Mark
participants (2)
-
markd@macports.org
-
Sterling Anderson