Did this restarting problem start with Zope 2.4.x? Was is there in 2.3.x because were are thinking of downgrading to 2.3.x? Thanks for your help
Chris McDonough <chrism@zope.com> 01/28/02 21:26 PM >>> Hmm. This doesn't look any better. ;-) I'm not sure how to tell you to
get more relevant information from gdb. Ahsan Imam wrote:
Our site is so heavily dependent on the mysql connection that it would lose majority of the functionality.
I added the -Z"''" option and here is the command ps axww | grep z2 looks like:
/usr/bin/python /usr/local/zope/z2.py -z /usr/local/zope -a zslave2.newtimes.com -Z '' -t 7 -w 8080 -p - -f - -m - -F 8889 -l /usr/local/zslave2/var/zope.log
gdb #0 0x4008c8a5 in __sigsuspend (set=0x415cefbc) 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
Chris McDonough <chrism@zope.com> 01/28/02 16:45 PM >>>
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