> Hiya, > > Not sure if others ever get this but sometimes my apache really doesn't > like being restarted. > > Looking at things when it's in this stuck state it appears to be waiting > on a mutex: > > Process 24205 attached > futex(0x7fde0090c640, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...> > > Eventually systemd gets tired waiting and kills it properly > +++ killed by SIGKILL +++ > > which is nice from a cleanliness perspective - I'm pretty sure that > before either sysvinit would have just hung or returned from the stop > job without killing things properly and then started apache again and > gotten then "failed to bind to port 80" type error I'm sure I remember > seeing. > > Anyway, don't think this is something we can easily fix just now and > it's quite sporadic (doesn't always happen). > > One of these days I'll be able to attach to it properly and get a nice > backtrace :)
this reminds me... you should try to fix the dumping of core via systemd. the other day i tried to get cores, but somehow unlimited meant 0 meant no core at all #systemd people told me that my distro's systemd isn't built with the coredump option, which may refuse to dump cores in services.
