Dear Maintainer,


sometimes my computer does not shutdown completely after logging out
from kde:

|asking all remaining processes to terminate ... done
|currently running processes are (pstree)
| ....
| tracker-extract

(see sreenshot attached)


I suppose the other processes regarding NFS are okay to be running after
/etc/init.d/sendsigs but tracker-extract should have been finished.

Shutdown remains incomplete and I have to press the power button to
force a power down. However, the file system is not unmounted cleanly
then.


The problem is not *always* reproducible but quite often.



Thanks for your consideration



Sebastian

Am 31.07.2013 22:53, schrieb Sebastian Niehaus:

Are you using NFS for your $HOME directory?

Am 31.07.2013 23:15, schrieb Michael Biebl:

No, $HOME is on the maschine's local disk.

The NFS file system however is mounted into one user's home like

/home/user1/nfs


THT,


Sebastian

Am 31.07.2013 23:41, schrieb Sebastian Niehaus:

You might want to exclude that directory from being crawled/indexed by
tracker.

Am 01.08.2013 00:08, schrieb Michael Biebl:

Looks if this made disappear the unwanted behavior. Not very good it
still can happen but quite easy to work around.



Sebastian

IMHO, the process should stop immediately at shutdown and not try
to finish its task first.

When I upgraded a machine from stable to testing in December 2023,
tracker-extract was also preventing the shutdown (always, AFAIK),
and I had no NFS, just the local disk. However, in my case,
tracker-extract (gst-plugin-scan) was yielding a crash in nouveau

2023-12-19T03:10:02.176832+01:00 qaa tracker-extract-3[1967]: nvc0_screen_create:1077 - Error allocating PGRAPH context for M2MF: -16
2023-12-19T03:10:02.177550+01:00 qaa kernel: ------------[ cut here ]------------
2023-12-19T03:10:02.177568+01:00 qaa kernel: nouveau 0000:01:00.0: timeout
[...]
2023-12-19T03:10:02.177710+01:00 qaa kernel: CPU: 3 PID: 1967 Comm: gst-plugin-scan Tainted: G        W          6.5.0-5-amd64 #1  Debian 6.5.13-1

and gst-plugin-scan even survived SIGKILL:

[...]
2023-12-19T03:13:06.240298+01:00 qaa systemd[2079]: tracker-extract-3.service: State 'final-sigterm' timed out. Killing.
2023-12-19T03:13:06.240435+01:00 qaa systemd[2079]: tracker-extract-3.service: Killing process 2150 (gst-plugin-scan) with signal SIGKILL.
2023-12-19T03:13:40.973708+01:00 qaa kernel: INFO: task gst-plugin-scan:2150 blocked for more than 120 seconds.
2023-12-19T03:13:40.973803+01:00 qaa kernel:       Tainted: G        W          6.5.0-5-amd64 #1 Debian 6.5.13-1
2023-12-19T03:13:40.973810+01:00 qaa kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
2023-12-19T03:13:40.973816+01:00 qaa kernel: task:gst-plugin-scan state:D stack:0     pid:2150  ppid:2079   flags:0x00000006
[...]
2023-12-19T03:14:36.240345+01:00 qaa systemd[2079]: tracker-extract-3.service: Processes still around after final SIGKILL. Entering failed mode.
[...]

So perhaps in this particular case, there was nothing that could
be done on the tracker-extract side, but I'm wondering.

Since then, the nouveau issue has been fixed, but I had removed
tracker-extract earlier, and I didn't try again to see whether
the problem was solved about it.

That's certainly a kernel/driver bug. In principle it should not be
possible for Tracker to cause a crash in kernel code (was this an OOPS
or a BUG message or what?), even if it wanted to do this intentionally.

If it has got sufficiently wedged in kernel code that even SIGKILL won't
delete the process, then there isn't going to be anything further that
either Tracker or systemd can do to resolve that.

    smcv

also triggered this error. This was due to missing symbolic links
in the firmware-misc-nonfree package:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058991