The logs from mod_slotmem_shm are the most interesting, so "LogLevel slotmem_shm:debug" should be enough (to limit debug logging to this module). This should show which shared memories paths (i.e. .../slotmem-shm-*.shm) are created/reused/attached by which instance, and figure out what kind of duplicates there may be..
On Sun, Dec 6, 2020 at 8:21 PM Wendell Hatcher <wendellhatcher1...@gmail.com> wrote: > > Let me gather this information from one of our servers next week. I will > provide a little more background information tomorrow as well. > > On Sat, Dec 5, 2020, 7:08 PM Yann Ylavic <ylavic....@gmail.com> wrote: >> >> On Fri, Dec 4, 2020 at 7:45 PM Wendell Hatcher >> <wendellhatcher1...@gmail.com> wrote: >> > >> > This has nothing to do with underlying SHM stuff and everything to do with >> > how multiple balancers, global and outside of virtual hosts, are >> > initialized and sometimes persisted. This was changed greatly in >> > 2.4.29.You should find the minimal set of balancers that reproduces the >> > error and It is likely related to duplicate virtual hosts or duplicate >> > proxy "workers". >> >> Could you please provide the full error_log (with LogLevel debug) of >> the httpd startup failure? >> If there are multiple instances (and potential duplicates), the >> error_log of all the instances may help too (with LogLevel debug, >> still). >> >> Regards; >> Yann. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org >> For additional commands, e-mail: users-h...@httpd.apache.org >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
