https://issues.apache.org/bugzilla/show_bug.cgi?id=46942
Dan Poirier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P3 --- Comment #1 from Dan Poirier <[email protected]> 2009-06-10 13:07:17 PST --- I think I've figured out what's going on (with some help from Greg Ames). Not sure yet how to fix it. The global mutex used by mod_rewrite to serialize writing to the rewrite log is created in post_config(). So when the parent starts its graceful restart and cleans up the old configuration, it's going to clean up - destroy - that global mutex. Children still finishing up requests now have a reference to a mutex that no longer exists, hence attempts to lock the mutex fail. I think the worst effect of this is the possibility that a few rewritelog messages get intermingled in the log, which isn't too important. Still, it would be nice to figure out a way to make this work right. Maybe somebody who knows how modules work better than I knows how to do this. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
