https://issues.apache.org/bugzilla/show_bug.cgi?id=55449
--- Comment #3 from Andre W. <[email protected]> --- Hello everyone, i invested a little bit more of investigation on that topic, because the problem came up more often. After that investigations I also found that open bug, which describes nearly the same problem, by creating a key that already exists: https://issues.apache.org/bugzilla/show_bug.cgi?id=53996 I think the problem comes up from the ftok(3) call inside unixd_set_shm_perms() (modules/slotmem/mod_slotmem_shm.c). The second argument there is the INT projid, which is constant value 1. Due to the fact that the creation of the ftok-key may not be random (the keys should be reproducable), there should be an additionl option to varify the key (i.e. an addtional parameter on startup, which can be different for each apache instance? e.g. the port number -c Listen <port>). Due to the fact that only the last 8 bits of the projid are used, maybe the 16 bit port number can also be hashed? This would not solve the problem compleatly but i think it would reduce the amount of collisons which are coming up. The only work arround I currently found is the following: 1) rename existing *.shm 2) restart apache 3) if slotmem_create failure still occurs inside Error-Log, back to 1) 4) delete old files after apache2 has started Best regards, André -- 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]
