GNOME Bugzilla – Bug 793027
tracker-store.service does not terminate when logging out or shutting down
Last modified: 2021-05-26 22:25:19 UTC
I get a 90 seconds delay when shutting down. First I thought this is a systemd problem, but then I saw that the tracker service (of my user) is still active after logging out, which led me to think that this might be the culprit. When I run "systemd-cgls" after logging out, I can see that the tracker-store.service of the logged out user is still running. See this post here: https://github.com/systemd/systemd/issues/1615#issuecomment-351433148
In my case tracker-store.service also takes a while to terminate after the user instance of systemd tries to stop it. It seems that it doesn't detect the SIGTERM signal sent by systemd immediately. For example, see these logs: Feb 01 22:34:20 desktop systemd[3489]: Stopping Tracker metadata database store and lookup manager... Feb 01 22:35:15 desktop tracker-store[4394]: Received signal:15->'Terminated' Feb 01 22:35:15 desktop tracker-store[4394]: OK Feb 01 22:35:15 desktop systemd[3489]: Stopped Tracker metadata database store and lookup manager. It can be seen that it takes 55 seconds for tracker-store to detect the SIGTERM (15) signal. It takes less than 90 seconds in my case so the service still stops "cleanly" at shutdown without forceful termination by systemd, although it has this noticeable delay. Tracker 2.0.2 GNOME 3.26.2 Arch Linux systemd 236.81
Created attachment 367960 [details] Tracker shutdown log I have managed to reproduce this bug with the debug log level enabled for tracker-store. It seems that the step that is slowing down the shutdown of the tracker-store service is the VACUUM operation for the database, which seems to take a while when the database is big.
*** Bug 794009 has been marked as a duplicate of this bug. ***
How this can be solved? I don't want to stop /remove tracker-store
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/tracker/-/issues/ Thank you for your understanding and your help.