Thanks. This is helpful info. I'm getting the hang of this. One more related question:
I have a tempermental app that is not happy with Apache. Apache is freezing up every 40 minutes or so. As a band-aid, while I debug, Supervisord is restarting apache every time it sees that it's locked up. Question: What advantage do I get by using TERM rather than KILL for restarting apache after it locks up like that? Thanks so much. -Brad On Thu, May 6, 2010 at 7:10 PM, [email protected] <[email protected]>wrote: > > On May 6, 2010, at 6:35 PM, Brad Flora wrote: > > Hi, Chris, > > Thanks for the assistance. I'm new to sysadmin stuff so please excuse my > ignorance here. > > I can restart supervisord in dubgging mode, but waiting for it to tail > doesn't make sense. If apache is in FATAL mode, hasn't it already failed? > My site is showing 404 at the moment. When I try to start or restart apache > in supervisord I get messages saying "ERROR (abnormal termination)" > > So I'm not sure how to get apache going again so I can debug the problem. > > > First, get a list of all httpd's running: > > # ps aux | grep httpd > > And supervisords: > > # ps aux | grep supervisord > > Kill any of the ones you need killed with: > > # kill <the pid # from the list> > > Yes, there are cleverer ways with killall, but it would probably be a good > idea to see what-all's running and you might have other supervisords doing > other things you don't want killed. > > Then you should be able to try to restart Apache, without supervisord for > the moment, and at least get your site online. > > Try: > > # apachectl -S > > to check the config file for virtual host problems. > > S > > > > > -Brad > > On Thu, May 6, 2010 at 5:27 PM, Chris McDonough <[email protected]> wrote: > >> You can indeed do a start, restart, or stop on Apache in that >> configuration when its in the FATAL state. Doing so just won't do much, >> however, because the program can't start up in the first place. >> >> Try to debug the actual problem by starting supervisord with debugging >> logging in foreground mode: >> >> supervisord -n -edebug >> >> Then wait for it to fail. While it's in foreground mode, it should >> print the stdout and stderr streams of all processes started by >> supervisord. Often once you see the thing failing, it becomes obvious >> what needs to change to make things better. >> >> - C >> >> >> On Thu, 2010-05-06 at 17:05 -0500, Brad Flora wrote: >> > Hi there, >> > >> > A friend just set up Supervisord the other day on my slice and we're >> > using it to restart apache when it freezes. About an hour ago, Apache >> > slipped into full-blown FATAL mode. I read in the docs that a process >> > in FATAL mode must be restarted manually. >> > >> > How do I do that? I can't seem to run START, RESTART, or even STOP on >> > apache. Sounds like I need to fire it up some other way. How do I do >> > that? >> > >> > Cheers! >> > >> > -Brad >> > _______________________________________________ >> > Supervisor-users mailing list >> > [email protected] >> > http://lists.supervisord.org/mailman/listinfo/supervisor-users >> >> >> > > > -- > Brad Flora > Founder, WindyCitizen.com > 210 W. Hill Street #3 | Chicago, IL 60610 > Ph: 269-861-5280 > Web: http://windycitizen.com/bradflora > Twitter: @bradflora > _______________________________________________ > Supervisor-users mailing list > [email protected] > http://lists.supervisord.org/mailman/listinfo/supervisor-users > > > -- Brad Flora Founder, WindyCitizen.com 210 W. Hill Street #3 | Chicago, IL 60610 Ph: 269-861-5280 Web: http://windycitizen.com/bradflora Twitter: @bradflora
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
