Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'd suggest just doing a full stop and start to get around the error until fixed. I never do graceful restarts with apache, never seems to do the job accurately.
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Original Poster
Rep:
Quote:
Originally Posted by trickykid
Do you get the same error if you do a stop and start?
Hmmmm ... nope:
Code:
[Tue Oct 23 12:20:13 2007] [notice] caught SIGTERM, shutting down
[Tue Oct 23 12:20:15 2007] [notice] Apache/2.2.6 (Unix) mod_ssl/2.2.6 OCOL configured -- resuming normal operations
Interesting! Not good, but interesting.
Quote:
Originally Posted by trickykid
I'd suggest just doing a full stop and start to get around the error until fixed. I never do graceful restarts with apache, never seems to do the job accurately.
I think you're right. That bug seems familiar. I've been using "graceful" for some time, because I was told it's the "right" way to restart. But as you said, there seem to be lots of reasons for doing a hard stop/start instead.
The bug page you linked included a patch file. Do you think it's worth trying such a patch? Does Apache follow up on such bugs quickly?
Apache seems to stay updated but I think they try to roll a lot of changes and fixes in at once, so they're not rolling out new fixes every other day. That would put a strain on admins.
I'd say wait for a release, if it's not security related and there's a work around, that's how I deal with such things.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.