Python 2.1.2 causes Error code 6?
Hi, A routine move to Python 2.1.2 this morning has resulted in one of our Zope instances continually dying with the following: zdaemon: Mon Jan 28 13:45:45 2002: Aiieee! 18724 exited with error code: 6 Some questions: 1. What does Error Code 6 mean? 2. How can I find out what these error codes eman in general? 3. How can I fix this problem? cheers, Chris PS: Zope 2.4.2 ZEO 1.0b4 No DA's or other non-standard C-based extensions.
At 28.01.2002 13:55 +0000, Chris Withers wrote:
1. What does Error Code 6 mean?
#define ENXIO 6 /* No such device or address */
2. How can I find out what these error codes eman in general?
Look into /usr/include/asm/errno.h
3. How can I fix this problem?
Make the device or address available ;-) Cheers, Stefan
stefan holek wrote:
1. What does Error Code 6 mean?
#define ENXIO 6 /* No such device or address */
2. How can I find out what these error codes eman in general?
Look into /usr/include/asm/errno.h
3. How can I fix this problem?
Make the device or address available ;-)
And how can i find out what device or address isn't available? ;-) cheers, Chris
On Mon, 2002-01-28 at 12:29, stefan holek wrote:
At 28.01.2002 13:55 +0000, Chris Withers wrote:
1. What does Error Code 6 mean?
#define ENXIO 6 /* No such device or address */
Actually, it means the Zope process exited because of a signal, and the signal was 6, meaning SIGABRT or SIGABORT (check "kill -l" on your nearest unix prompt). However, I have no idea what could cause a SIGABORT. -- Ideas don't stay in some minds very long because they don't like solitary confinement.
At 28.01.2002 12:58 -0200, Leonardo Rochael Almeida wrote:
On Mon, 2002-01-28 at 12:29, stefan holek wrote:
At 28.01.2002 13:55 +0000, Chris Withers wrote:
1. What does Error Code 6 mean?
#define ENXIO 6 /* No such device or address */
Actually, it means the Zope process exited because of a signal, and the signal was 6, meaning SIGABRT or SIGABORT (check "kill -l" on your nearest unix prompt). However, I have no idea what could cause a SIGABORT.
oops ;-)
Leonardo Rochael Almeida wrote:
Actually, it means the Zope process exited because of a signal, and the signal was 6, meaning SIGABRT or SIGABORT (check "kill -l" on your nearest unix prompt). However, I have no idea what could cause a SIGABORT.
Hmmm... how would I go about finding out? I am rather disturbed by the fact that a third point update to python suddenly starts causing Zope to keel over :-( I tracked it down to a python script that returned a data structure consisting of nested lists and dictionaries. Now, I remember there being a bug in RestrictedPython that would affect Zope 2.4.2, but why would the upgrade of Python suddenly trigger this? confusedly, Chris
On Mon, 28 Jan 2002, Chris Withers wrote:
I tracked it down to a python script that returned a data structure consisting of nested lists and dictionaries. Now, I remember there being a bug in RestrictedPython that would affect Zope 2.4.2, but why would the upgrade of Python suddenly trigger this?
Well, my understanding is the new python is catching memory corruption bugs the old one wasn't, and that the compiler for python scripts in 2.4.2 has bugs...so maybe you were just lucky zope wasn't crashing before? --RDM
stefan holek wrote:
At 28.01.2002 13:55 +0000, Chris Withers wrote:
1. What does Error Code 6 mean?
#define ENXIO 6 /* No such device or address */
Bzzt. The error code comes from waitpid(), which the Python library doco says has the same return code as wait(). The low eight bits are a signal, so we actually got a signal 6, not an exit code 6. Signal 6 is SIGABRT.
Chris Withers writes:
A routine move to Python 2.1.2 this morning has resulted in one of our Zope instances continually dying with the following:
zdaemon: Mon Jan 28 13:45:45 2002: Aiieee! 18724 exited with error code: 6
Some questions:
1. What does Error Code 6 mean? Signal 6, SIGABRT (ABORT), used by the C runtime function "abort"
Probably a failing assertion. Check standard error. You may find some hints. Dieter
This is probably caused by the assertion error raised by Python 2.1.2 in the case of a miscomputed stack size. See my previous message. Dieter Maurer wrote:
Chris Withers writes:
A routine move to Python 2.1.2 this morning has resulted in one of our Zope instances continually dying with the following:
zdaemon: Mon Jan 28 13:45:45 2002: Aiieee! 18724 exited with error code: 6
Some questions:
1. What does Error Code 6 mean? Signal 6, SIGABRT (ABORT), used by the C runtime function "abort"
Probably a failing assertion. Check standard error. You may find some hints.
Dieter
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
participants (7)
-
Chris McDonough -
Chris Withers -
Dieter Maurer -
Leonardo Rochael Almeida -
Matt Behrens -
R. David Murray -
stefan holek