Re: [Trac] Long timeout when modifying a ticket

Jun Omae <[email protected]> Mon, 9 Mar 2026 07:30:45 +0900
Newsgroups gmane.comp.version-control.subversion.trac.general
Message-ID <CAEVLMahgUtj-duoYL8YxVX+=yQATVZVA_WGhrsUnj=8zegyEWA@mail.gmail.com>
On Mon, Mar 9, 2026 at 6:36=E2=80=AFAM 'Jean-Marc Lasgouttes' via Trac User=
s
<trac-users-/[email protected]> wrote:
>
> Le 04/03/2026 =C3=A0 00:25, Jun Omae a =C3=A9crit :
> > Hmm, I have not encountered similar issues.
> >
> > Please describe your environment which Trac is running with:
> >
> >   * Trac version
> >   * Python version
> >   * Database and the version
> >   * Version control (svn, git, hg)
> >   * Installed plugins and enabled plugins
> >
> > Please share entire of trac.ini and trac.log after enabling logging
> > with DEBUG and reproducing it, if possible.
>
> Hello,
>
> Thanks for your answer, and sorry for my own timeout. Here is some
> information
>
> Server is: Ubuntu 24.04.4 LTS (GNU/Linux 6.8.0-101-generic x86_64)
>
> trac version 1.6
>
> Python 3.12.3
>
> root@www:/home/lyx/www# file trac/db/trac.db
> trac/db/trac.db: SQLite 3.x database, last written using SQLite version
> 3045001, page size 1024, file counter 6603671, database pages 478423,
> 1st free page 351893, free pages 4643, cookie 0x3d, schema 1, UTF-8,
> version-valid-for 6603671
>
> version control is git
>
> Enabled plugins are indicated here if I am not mistaken. I am not sure
> what the correct information is
> [components]
> acct_mgr.admin.* =3D enabled
> acct_mgr.api.* =3D enabled
> acct_mgr.db.sessionstore =3D disabled
> acct_mgr.guard.accountguard =3D enabled
> acct_mgr.htfile.htdigeststore =3D disabled
> acct_mgr.htfile.htpasswdstore =3D enabled
> acct_mgr.http.* =3D disabled
> acct_mgr.notification.* =3D enabled
> acct_mgr.pwhash.* =3D disabled
> acct_mgr.register.* =3D disabled
> acct_mgr.register.basiccheck =3D enabled
> acct_mgr.register.bottrapcheck =3D enabled
> acct_mgr.register.emailcheck =3D enabled
> acct_mgr.register.emailverificationmodule =3D enabled
> acct_mgr.register.regexpcheck =3D enabled
> acct_mgr.register.registrationmodule =3D disabled
> acct_mgr.register.usernamepermcheck =3D enabled
> acct_mgr.web_ui.* =3D enabled
> acct_mgr.web_ui.resetpwstore =3D disabled
> trac.web.auth.loginmodule =3D disabled
> trackeywords.web_ui.* =3D enabled
> tracopt.ticket.deleter =3D enabled
> tracopt.versioncontrol.git.* =3D enabled
>
>
> trac.ini is in attachment and trac.log (which is quite large) is at
> https://who.paris.inria.fr/Jean-Marc.Lasgouttes/trac.log.xz
>
> This has been obtained by adding a single comment to a ticket. It looks
> like trac restarted >100K times!
>
> I hope that this information makes sense to you.
>
> Regards,
> JMarc

Thanks for the sharing trac.ini and trac.log. Investigating the
trac.log, I found many "OperationalError: database is locked" in the
log.

First, I consider that "PRAGMA journal_mode WAL" and "PRAGMA
synchronous NORMAL" might help it. The parameters can be set in [trac]
database option like the following:

[trac]
database =3D sqlite:db/trac.db?journal_mode=3Dwal&synchronous=3Dnormal

I recommend to use PostgreSQL rather than SQLite for internet-facing Trac.

--=20
Jun Omae <[email protected]> (=E5=A4=A7=E5=89=8D =E6=BD=A4)

--=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/=
CAEVLMahgUtj-duoYL8YxVX%2B%3DyQATVZVA_WGhrsUnj%3D8zegyEWA%40mail.gmail.com.