zope.conf: effective-user breaks clean segfault handling
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zope 2 |
Invalid
|
Medium
|
Unassigned |
Bug Description
I have been hunting a segfault problem for about 6 month now and finally found a way to get deeper into it.
Situation:
A Zope server using ZMySQLDA segfaults every now and then. The mysql C-module is likely to be the hotspot. However, no core dump is every issued, and the threads that did not segfault are hanging around.
Software: Python 2.3.5, Zope 2.7.7, and some other stuff that doesn't look too suspicious.
It happens that additionally to the hanging threads, (which are described as a Python bug for a while ago) no core dump is beeing written.
I finally found that the "effective-user" switch somehow influences this.
When making the server run as the effective user immediately and not using a low port, both things work as expected: all threads are killed (and zdaemon cleanly restarts the server) and a core dump is written.
Changed in zope2: | |
importance: | Critical → High |
Is this still an issue? I haven't seen any segfaults with the latest Zope versions since about one yr. Maybe change the importance to medium.