Bug#910579: tracker: cannot initialize database: error in view fts_view

Hideki Yamane henrich at debian.org
Mon Oct 8 11:48:36 BST 2018


Package: tracker
Version: 2.1.4-1
Severity: important

Dear Maintainer,

 Recently, I found tracker eats lots of CPU and it shows below log.

Oct  8 19:44:14 hp systemd[2689]: Started Tracker metadata database store and lookup manager.
Oct  8 19:44:17 hp tracker-store[29155]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElement_nie:keyword_TEMP (strerror of errno (not necessarily related): そのようなファイルやディレクトリはありません)
Oct  8 19:44:17 hp systemd[2689]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  8 19:44:17 hp systemd[2689]: tracker-store.service: Failed with result 'exit-code'.
Oct  8 19:44:17 hp systemd[2689]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  8 19:44:17 hp systemd[2689]: tracker-store.service: Scheduled restart job, restart counter is at 8429.
Oct  8 19:44:17 hp systemd[2689]: Stopped Tracker metadata database store and lookup manager.
Oct  8 19:44:17 hp systemd[2689]: Starting Tracker metadata database store and lookup manager...
Oct  8 19:44:17 hp systemd[2689]: Started Tracker metadata database store and lookup manager.
Oct  8 19:44:19 hp tracker-store[29216]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElement_nie:keyword_TEMP (strerror of errno (not necessarily related): そのようなファイルやディレクトリはありません)
Oct  8 19:44:19 hp systemd[2689]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  8 19:44:19 hp systemd[2689]: tracker-store.service: Failed with result 'exit-code'.
Oct  8 19:44:20 hp systemd[2689]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  8 19:44:20 hp systemd[2689]: tracker-store.service: Scheduled restart job, restart counter is at 8430.
Oct  8 19:44:20 hp systemd[2689]: Stopped Tracker metadata database store and lookup manager.
Oct  8 19:44:20 hp systemd[2689]: Starting Tracker metadata database store and lookup manager...
Oct  8 19:44:20 hp systemd[2689]: Started Tracker metadata database store and lookup manager.
Oct  8 19:44:22 hp tracker-store[29271]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElement_nie:keyword_TEMP (strerror of errno (not necessarily related): そのようなファイルやディレクトリはありません)
Oct  8 19:44:22 hp systemd[2689]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  8 19:44:22 hp systemd[2689]: tracker-store.service: Failed with result 'exit-code'.
Oct  8 19:44:22 hp systemd[2689]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  8 19:44:22 hp systemd[2689]: tracker-store.service: Scheduled restart job, restart counter is at 8431.
Oct  8 19:44:22 hp systemd[2689]: Stopped Tracker metadata database store and lookup manager.
Oct  8 19:44:22 hp systemd[2689]: Starting Tracker metadata database store and lookup manager...
Oct  8 19:44:22 hp systemd[2689]: Started Tracker metadata database store and lookup manager.
Oct  8 19:44:25 hp tracker-store[29337]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElement_nie:keyword_TEMP (strerror of errno (not necessarily related): そのようなファイルやディレクトリはありません)
Oct  8 19:44:25 hp systemd[2689]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  8 19:44:25 hp systemd[2689]: tracker-store.service: Failed with result 'exit-code'.
Oct  8 19:44:25 hp systemd[2689]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  8 19:44:25 hp systemd[2689]: tracker-store.service: Scheduled restart job, restart counter is at 8432.
Oct  8 19:44:25 hp systemd[2689]: Stopped Tracker metadata database store and lookup manager.
Oct  8 19:44:25 hp systemd[2689]: Starting Tracker metadata database store and lookup manager...
Oct  8 19:44:25 hp systemd[2689]: Started Tracker metadata database store and lookup manager.
...

 "そのようなファイルやディレクトリはありません" is "no such file or directory" in Japanese.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tracker depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.10-1
ii  dbus-x11 [dbus-session-bus]                   1.12.10-1
ii  dconf-gsettings-backend [gsettings-backend]   0.30.0-1
ii  libc6                                         2.27-6
ii  libglib2.0-0                                  2.58.1-2
ii  libglib2.0-bin                                2.58.1-2
ii  libtracker-control-2.0-0                      2.1.4-1
ii  libtracker-sparql-2.0-0                       2.1.4-1
ii  shared-mime-info                              1.10-1

Versions of packages tracker recommends:
ii  tracker-miner-fs  2.1.4-2

tracker suggests no packages.

-- no debconf information


More information about the pkg-gnome-maintainers mailing list