You have a core file from the "zdaemon" process.. it's sorta useless as a result. If you want to get a meaningful core file, run Zope without ZDaemon (pass "-Z ''" to the start script). That said, we've confirmed "crashbug" problems in an installation with mysqlda in at least one customer site. Can you make this problem happen without mysqlda? Ahsan Imam wrote:
Applied the db.py patch and no success. Currently dowloaded and installed the Zope 2.4.4 beta 1
Python Version python 2.1.2
ZMySQLDA
Here is a little excerpt from gdb Would the following output have any special meaning?
gdb python core
#0 0x4008c8a5 in __sigsuspend (set=0x415cf19c) at ../sysdeps/unix/sysv/linux/sigsuspend.c:45 45 ../sysdeps/unix/sysv/linux/sigsuspend.c: No such file or directory. in ../sysdeps/unix/sysv/linux/sigsuspend.c
"Matthew T. Kromer" <matt@zope.com> 01/25/02 15:13 PM >>>
Ahsan Imam wrote:
Setting the variable did not help. I downloaded and built Python 2.1.2 yesterday.
Products: zope-tinytable-0.8.2-2 zope-zmysqlda-2.0.7-5
"Chris McDonough" <chrism@zope.com> 01/24/02 12:22 PM >>>
Sigh. Can you try to start Zope with the environment variable ZOPE_SECURITY_POLICY=PYTHON set to see if the problem continues?
Are you using any database adapters or other C extensions?
Are you sure that Zope is using the Python 2.1.2 that you installed?
Try applying this patch to db.py in ZMySQLDA.
It makes it so MySQLDA database connections reopen themselves when the DA object migrates between threads.
_______________________________________________ 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 )