Re: [Trac] Long timeout when modifying a ticket
Clemens Feige <c.feige-OaXy4Qdpe4n2eFz/[email protected]> Fri, 10 Apr 2026 13:10:12 +0200
| Newsgroups | gmane.comp.version-control.subversion.trac.general |
|---|---|
| Organization | Osypka Medical |
| Message-ID | <[email protected]> |
'Jean-Marc Lasgouttes' via Trac Users wrote on 03.04.2026 at 13:20: > Le 03/04/2026 =C3=A0 12:17, Clemens Feige a =C3=A9crit=C2=A0: >> >> 'Jean-Marc Lasgouttes' via Trac Users wrote on 03.03.2026 at 16:38: >>> Daer Trac users, >>> >>> We have a trac installation that worked well until fairly recently.=20 >>> Now, every time one tries to modify a ticket, nothing happens for a=20 >>> minute or so, and then the modification is done. >>> >>> This is not a matter of load on the server, it looks more like a=20 >>> timeout somewhere. >>> >>> I see nothing of interest in trac.log. Have you already experienced=20 >>> such a situation? Where should I look?> >> In our TRAC (on Linux) we can sometimes (not always) see long delays=20 >> on ticket creation / modification which seem to be related to TRAC=20 >> notification via e-mail. >> >> Check if you have enabled notification via e-mail or "CC" field in=20 >> your ticket. >=20 > Thank you for your answer that makes me follow up on this subject as I=20 > should have done earlier. It turned out that the issue was that >=20 > It seems the "lock" was a mailing problem, i.e., for whatever reason > smtp.osuosl.org started to be resolved in ipv6 way, that freezes > for 10=C2=A0mins and then switches back to ipv4. >=20 > We switched the glibc resolver to prefer IPv4 over IPv6 for > all applications. Mail seems to work fine again and trac is back. >=20 > Sorry for not letting you know earlier. Thanks to Jun for suggesting=20 > creating a fill debug log, that was useful. >=20 > JMarc So we can conclude that TRAC may "hang" or appear "locked" for a longer=20 time period (minutes) in case of certain e-mail issues when attempting=20 to send ticket notifications via mail. Of course the mail problems are not the fault of TRAC. But I would=20 expect that the TRAC server should not be blocked in such cases. I am not a TRAC developer and cannot judge if this is worth a ticket.=20 Also I do not know how to reproduce. Clemens --=20 You received this message because you are subscribed to the Google Groups "= Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to trac-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected] To view this discussion visit https://groups.google.com/d/msgid/trac-users/= 7d2f94cc-cc96-4bfb-9658-adc6427dbad6%40osypkamed.com.