does anyone know how to calm down 'tracker-store'?

[Patrice Duroux]

Dear all,

Two points may be related somehow to the 'tracker' services.

1. On my local laptop system (Sid) I am getting the following message in 'dmesg':

[ 3773.552252] traps: multiqueue3:src[25397] general protection ip:7f97590e5635 sp:7f972fffe570 error:0 in libgstvideo-1.0.so.0.1404.0[7f97590a9000+56000]
[ 3898.567685] traps: multiqueue3:src[25911] general protection ip:7f84fa5c2635 sp:7f84d57f1570 error:0 in libgstvideo-1.0.so.0.1404.0[7f84fa586000+56000]
[ 3900.552267] traps: multiqueue3:src[26042] general protection ip:7f04ea090635 sp:7f04d0ff8570 error:0 in libgstvideo-1.0.so.0.1404.0[7f04ea054000+56000]
[ 4023.643722] traps: multiqueue3:src[26230] general protection ip:7f8c16d7f635 sp:7f8be57f9570 error:0 in libgstvideo-1.0.so.0.1404.0[7f8c16d43000+56000]
[ 4025.595601] traps: multiqueue3:src[26361] general protection ip:7f884408f635 sp:7f87fa7f3570 error:0 in libgstvideo-1.0.so.0.1404.0[7f8844053000+56000]
[ 4027.578455] traps: multiqueue3:src[26492] general protection ip:7ff1eeee6635 sp:7ff1d57f9570 error:0 in libgstvideo-1.0.so.0.1404.0[7ff1eeeaa000+56000]
[ 4152.620136] traps: multiqueue3:src[26833] general protection ip:7f42d2a25635 sp:7f42b17f9570 error:0 in libgstvideo-1.0.so.0.1404.0[7f42d29e9000+56000]
[ 4154.548827] traps: multiqueue3:src[26983] general protection ip:7fb16d226635 sp:7fb1377fd570 error:0 in libgstvideo-1.0.so.0.1404.0[7fb16d1ea000+56000]
[ 4277.628155] traps: multiqueue3:src[27197] general protection ip:7f7c6fbcc635 sp:7f7c3f7ed570 error:0 in libgstvideo-1.0.so.0.1404.0[7f7c6fb90000+56000]
[ 4279.590925] traps: multiqueue3:src[27328] general protection ip:7fb94ee99635 sp:7fb91d7f9570 error:0 in libgstvideo-1.0.so.0.1404.0[7fb94ee5d000+56000]
[ 4281.573294] traps: multiqueue3:src[27459] general protection ip:7fb39f588635 sp:7fb35dffa570 error:0 in libgstvideo-1.0.so.0.1404.0[7fb39f54c000+56000]
[ 4406.590114] traps: multiqueue3:src[27694] general protection ip:7f6e31224635 sp:7f6e07ffe570 error:0 in libgstvideo-1.0.so.0.1404.0[7f6e311e8000+56000]
[ 4408.583093] traps: multiqueue3:src[27836] general protection ip:7fb71d558635 sp:7fb6f3ffe570 error:0 in libgstvideo-1.0.so.0.1404.0[7fb71d51c000+56000]
[ 4531.651020] traps: multiqueue3:src[28045] general protection ip:7f5bf6f1c635 sp:7f5bdd7f9570 error:0 in libgstvideo-1.0.so.0.1404.0[7f5bf6ee0000+56000]
[ 4533.562633] traps: multiqueue3:src[28176] general protection ip:7f57dc5d9635 sp:7f57b77f5570 error:0 in libgstvideo-1.0.so.0.1404.0[7f57dc59d000+56000]
[ 4535.559175] traps: multiqueue3:src[28307] general protection ip:7f58a8bf5635 sp:7f5862ffc570 error:0 in libgstvideo-1.0.so.0.1404.0[7f58a8bb9000+56000]

2. On a server (Sid also) some user sessions are filling the daemon.log as following:

Nov 26 20:13:59 kappa2 systemd[6105]: tracker-store.service: Scheduled restart job, restart counter is at 14742.
Nov 26 20:13:59 kappa2 systemd[6105]: Stopped Tracker metadata database store and lookup manager.
Nov 26 20:13:59 kappa2 systemd[6105]: Starting Tracker metadata database store and lookup manager...
Nov 26 20:13:59 kappa2 systemd[13510]: tracker-store.service: Failed to execute command: No such file or directory
Nov 26 20:13:59 kappa2 systemd[13510]: tracker-store.service: Failed at step EXEC spawning /usr/lib/tracker/tracker-store: No such file or directory
Nov 26 20:13:59 kappa2 systemd[6105]: tracker-store.service: Main process exited, code=exited, status=203/EXEC
Nov 26 20:13:59 kappa2 systemd[6105]: tracker-store.service: Failed with result 'exit-code'.
Nov 26 20:13:59 kappa2 systemd[6105]: Failed to start Tracker metadata database store and lookup manager.
Nov 26 20:13:59 kappa2 systemd[6105]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Nov 26 20:13:59 kappa2 systemd[6105]: tracker-store.service: Scheduled restart job, restart counter is at 14743.
Nov 26 20:13:59 kappa2 systemd[6105]: Stopped Tracker metadata database store and lookup manager.
Nov 26 20:13:59 kappa2 systemd[6105]: Starting Tracker metadata database store and lookup manager...
Nov 26 20:13:59 kappa2 systemd[13511]: tracker-store.service: Failed to execute command: No such file or directory
Nov 26 20:13:59 kappa2 systemd[13511]: tracker-store.service: Failed at step EXEC spawning /usr/lib/tracker/tracker-store: No such file or directory
Nov 26 20:13:59 kappa2 systemd[6105]: tracker-store.service: Main process exited, code=exited, status=203/EXEC
Nov 26 20:13:59 kappa2 systemd[6105]: tracker-store.service: Failed with result 'exit-code'.
Nov 26 20:13:59 kappa2 systemd[6105]: Failed to start Tracker metadata database store and lookup manager.
Nov 26 20:14:00 kappa2 systemd[6105]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Nov 26 20:14:00 kappa2 systemd[6105]: tracker-store.service: Scheduled restart job, restart counter is at 14744.
Nov 26 20:14:00 kappa2 systemd[6105]: Stopped Tracker metadata database store and lookup manager.
Nov 26 20:14:00 kappa2 systemd[6105]: tracker-store.service: Start request repeated too quickly.
Nov 26 20:14:00 kappa2 systemd[6105]: tracker-store.service: Failed with result 'exit-code'.
Nov 26 20:14:00 kappa2 systemd[6105]: Failed to start Tracker metadata database store and lookup manager.

So its log file is growing quite quickly.

I suspect that those annoying messages are due to 'tracker', indirectly for case 1. and directly for case 2. Is there a way to inactive 'tracker' at least on a session server without uninstalling it (otherwise some dependencies then would be broken)?

Thanks,

Patrice

[Carl Fink]

I became so frustrated by tracker-store that I just uninstalled it. I
never use
desktop search anyway, so no loss.

--
Carl Fink ca...@finknetwork.com
Thinking and logic and stuff at Reasonably Literate
http://reasonablyliterate.com

[Reco]

Hi.

On Mon, Nov 26, 2018 at 08:36:47PM +0100, Patrice Duroux wrote:
> Dear all,
>
> Two points may be related somehow to the 'tracker' services.
>
> 1. On my local laptop system (Sid) I am getting the following message in
> 'dmesg':
>
> [ 3773.552252] traps: multiqueue3:src[25397] general protection
> ip:7f97590e5635 sp:7f972fffe570 error:0 in
> libgstvideo-1.0.so.0.1404.0[7f97590a9000+56000]

Install debugging symbols for the packages affected, get a core dump,
try to extract a backtrace with gdb from it.
By itself these messages only show us that libgstvideo-1.0.so was used
and it was done poorly.

> 2. On a server (Sid also) some user sessions are filling the daemon.log as
> following:
>
> Nov 26 20:13:59 kappa2 systemd[6105]: tracker-store.service: Scheduled
> restart job, restart counter is at 14742.
> Nov 26 20:13:59 kappa2 systemd[6105]: Stopped Tracker metadata database
> store and lookup manager.
> Nov 26 20:13:59 kappa2 systemd[6105]: Starting Tracker metadata database
> store and lookup manager...
> Nov 26 20:13:59 kappa2 systemd[13510]: tracker-store.service: Failed to
> execute command: No such file or directory

Assuming that's a 'system' service:

systemctl stop tracker-store.service
systemctl mask tracker-store.service

But if it's the 'user' service, you have to do:

systemctl --user stop tracker-store.service
systemctl --user mask tracker-store.service

Reco

[Patrice Duroux]

Hi,

On the server :

1. impossible to remove the tracker package unless to remove other ones:

dpkg: dependency problems prevent removal of tracker:
tracker-miner-fs depends on tracker (>= 2.1.0).
tracker-extract depends on tracker (>= 2.1.0).
rygel-tracker depends on tracker (>= 0.8).
nautilus depends on tracker.
gnome-photos depends on tracker.
gnome-music depends on tracker (>= 2.0).
gnome-documents depends on tracker (>= 1.99).
gnome-core depends on tracker; however:
Package tracker is to be removed.
gnome-boxes depends on tracker (>= 2.0).

dpkg: error processing package tracker (--purge):
dependency problems - not removing
Errors were encountered while processing:
tracker

2. I was trying to find a way to do it globally and 'silently' without asking
all the users to do in their session a set of 'systemctl' commands that they
never heard about. ;-)
Finally I have renamed the binary so at least to stop the log invasion.

3. For the laptop, I will try to chase the bug and install the debugging symbols
but for which packages precisely is not clear to me. I will start with the
gstreamer ones then.

Thanks!
Patrice

[Patrice Duroux]

Hi again,

Then here is my current situation (after a LZ4 decompression,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914934):

root@hp-dark:/var/lib/systemd/coredump# file core.tracker-extract.1000.273d78802abc412f8e7a360fd7509e52.14743.1543436892000000
core.tracker-extract.1000.273d78802abc412f8e7a360fd7509e52.14743.1543436892000000: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from '/usr/lib/tracker/tracker-extract', real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000, execfn: '/usr/lib/tracker/tracker-extract', platform: 'x86_64'
root@hp-dark:/var/lib/systemd/coredump# gdb core.tracker-extract.1000.273d78802abc412f8e7a360fd7509e52.14743.1543436892000000
GNU gdb (Debian 8.2-1) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>;.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>;.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/var/lib/systemd/coredump/core.tracker-extract.1000.273d78802abc412f8e7a360fd7509e52.14743.1543436892000000": not in executable format: file format not recognized
(gdb) quit


I have installed:
ii libde265-0-dbgsym:amd64 1.0.3-1+b1 amd64 debug symbols for libde265-0
ii libdvdcss2-dbgsym:amd64 1.4.2-1~local amd64 debug symbols for libdvdcss2
ii tracker-extract-dbgsym 2.1.5-3 amd64 debug symbols for tracker-extract

because by another way (looking at /tmp/tracker-extract-files.XXXXX) I have found that the error is due to a Matroska video file.
Finally I tried to look at https://wiki.debian.org/HowToGetABacktrace but it does not mention systemd-coredump at all, and then it is not clear when the need is for a user or session daemon/service debugging because in my case it is not explicitly launching a specific command to get the error.

Regards,
Patrice

[Patrice Duroux]

Hi,
Not sure to got it exactly but here is finally the 'coredumpctl info' output.
Where to address it if needed?
Thanks,
Patrice

[Reco]

Hi.

On Wed, Nov 28, 2018 at 11:03:28PM +0100, Patrice Duroux wrote:
>
> Hi,
> Not sure to got it exactly but here is finally the 'coredumpctl info' output.
> Where to address it if needed?

Install reportbug if you haven't already.
Run 'reportbug tracker-extract'.
Copy this part of the backtrace into it:

Stack trace of thread 32070:
#0 0x00007f4db09e1635 gst_video_codec_frame_ref (libgstvideo-1.0.so.0)
#1 0x00007f4dae1c134e _gst_libde265_return_image (libgstde265.so)
#2 0x00007f4dae1c17a5 gst_libde265_dec_handle_frame (libgstde265.so)
#3 0x00007f4db09cfe4b gst_video_decoder_decode_frame (libgstvideo-1.0.so.0)
#4 0x00007f4db09d2964 gst_video_decoder_chain_forward (libgstvideo-1.0.so.0)
#5 0x00007f4db09d3042 gst_video_decoder_chain (libgstvideo-1.0.so.0)
#6 0x00007f4db0adcc3a gst_pad_chain_data_unchecked (libgstreamer-1.0.so.0)
#7 0x00007f4db0ae4ed2 gst_pad_push (libgstreamer-1.0.so.0)
#8 0x00007f4db08a7dfd gst_base_transform_chain (libgstbase-1.0.so.0)
#9 0x00007f4db0adcc3a gst_pad_chain_data_unchecked (libgstreamer-1.0.so.0)
#10 0x00007f4db0ae4ed2 gst_pad_push (libgstreamer-1.0.so.0)
#11 0x00007f4db088c9c8 gst_base_parse_push_frame (libgstbase-1.0.so.0)
#12 0x00007f4db088da35 gst_base_parse_chain (libgstbase-1.0.so.0)
#13 0x00007f4db0adcc3a gst_pad_chain_data_unchecked (libgstreamer-1.0.so.0)
#14 0x00007f4db0ae4ed2 gst_pad_push (libgstreamer-1.0.so.0)
#15 0x00007f4daea5fa8d gst_single_queue_push_one (libgstcoreelements.so)
#16 0x00007f4db0b11f41 gst_task_func (libgstreamer-1.0.so.0)
#17 0x00007f4df35daad3 n/a (libglib-2.0.so.0)
#18 0x00007f4df35da135 n/a (libglib-2.0.so.0)
#19 0x00007f4df3501f2a start_thread (libpthread.so.0)
#20 0x00007f4df3434edf __clone (libc.so.6)

This gdb output is mangled as it does not show source lines, but it
should do.

Reco

[Reco]

Hi.

On Wed, Nov 28, 2018 at 10:20:22PM +0100, Patrice Duroux wrote:
> root@hp-dark:/var/lib/systemd/coredump# gdb core.tracker-extract.1000.273d78802abc412f8e7a360fd7509e52.14743.1543436892000000

It's always 'gdb <executable> <core>'.

Reco

[Patrice Duroux]

Hi,

That is done under #915042.
I hope improving a bit the output by using 'coredumpctl debug' and adding some
other debugging symbol packages.

Many thanks!