[Zope] zope timeouts

[Jens Vagelpohl]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Michele,

I would consider the coincience with strace "reviving" the process a red
herring. When strace runs it does not influence the process you are
watching with it, except for telling you what OS-level calls are made.

The most common reason for such timeouts are problems with software that
tries to use other network resources during the running request to talk
to services like RDBMS systems, LDAP, etc. If these background
connections hang for some reason you'll end up with a hanging Zope
thread. Enough of them and Zope itself appears to hang.

When your process hangs you should be able to attach to it using "gdb"
and printing a stack trace for each thread. That may give you a big clue
where the problem is.

jens


On 7/20/10 13:53 , Michele Marcionelli wrote:
> Hello
> 
> I'm running an old version of Zope which is required by our corporate design using also an older version of the CMS Silva:
> 
>     Linux Distribution: Red Hat Enterprise Linux Server release 5.5
>     Linux Kernel: 2.6.18-194.8.1.el5PAE
>     Zope: 2.8.9.1
>     Python: 2.3.6 (with several modules, like: ldap, pil, mysql, pyxml, ...)
>     Silva: 1.5.13
> 
> My problem ist that my zope server hat timeouts on displaying pages after a while that it has been started (currently this "while" is approx. 15 minutes). The only thing that helps is restarting zope.
> 
> By accident I discovered about two month ago, that running an "strace -f" on the zope process, "reactivated" it... so I could live with this hack until yesterday.
> 
> Now I'm running "strace" permanently (with all the disadvantages) and zope works "fine" for about 1 to 1.5 hours.
> 
> Here is a short recurring output of "strace":
> 
>> [pid 13408] <... futex resumed> )       = 0
>> [pid 13406] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
>> [pid 13405] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
>> [pid 13408] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
>> [pid 13407] <... futex resumed> )       = 0
>> [pid 13405] <... futex resumed> )       = 1
>> [pid 13408] <... futex resumed> )       = 1
>> [pid 13405] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
>> [pid 13408] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
>> [pid 13406] <... futex resumed> )       = 0
>> [pid 13406] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
>> [pid 13407] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1) = 1
>> [pid 13405] <... futex resumed> )       = 0
>> [pid 13407] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
>> [pid 13405] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
>> [pid 13408] <... futex resumed> )       = 0
>> [pid 13407] <... futex resumed> )       = 1
>> [pid 13407] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
>> [pid 13405] <... futex resumed> )       = -1 EAGAIN (Resource temporarily unavailable)
> 
> 
> I need definitively help... Any idea?
> 
> Thx,
> Michele
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkxFnHQACgkQRAx5nvEhZLIZTgCfdU00UhqXAwXxsXxypv+wSsPR
VSEAn3UXIACBeAuClfi23jo/+MSWDdJB
=Cvv7
-----END PGP SIGNATURE-----