Web lists-archives.com

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




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