1812533 – tracker-store crashloops after F27-F29 upgrade; also present in RHEL 8

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1812533 - tracker-store crashloops after F27-F29 upgrade; also present in RHEL 8

Summary: tracker-store crashloops after F27-F29 upgrade; also present in RHEL 8

Keywords:
Status:	CLOSED WONTFIX
Alias:	None
Product:	Red Hat Enterprise Linux 8
Classification:	Red Hat
Component:	tracker
Sub Component:
Version:	8.4
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	medium
Target Milestone:	rc
Target Release:	8.0
Assignee:	Carlos Garnacho
QA Contact:	Desktop QE
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2020-03-11 14:18 UTC by R P Herrold
Modified:	2021-09-11 07:26 UTC (History)
CC List:	7 users (show)
Fixed In Version:
Doc Type:	---
Doc Text:
Clone Of:	1662340
Environment:
Last Closed:	2021-09-11 07:26:55 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Description R P Herrold 2020-03-11 14:18:47 UTC

+++ This bug was initially created as a clone of Bug #1662340 +++

Description of problem:

tracker-store continually crashes/restarts after upgrade from F27->F29
also present in RHEL 8

[herrold@centos-8 pw]$ rpm -q tracker
tracker-2.1.5-1.el8.x86_64
[herrold@centos-8 pw]$ 


.
Mar 11 10:17:09 centos-8 journal[22940]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElement_nie:keyword_TEMP (strerror of errno (not necessarily related): No such file or directory)
Mar 11 10:17:09 centos-8 systemd[3069]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Mar 11 10:17:09 centos-8 systemd[3069]: tracker-store.service: Failed with result 'exit-code'.
Mar 11 10:17:09 centos-8 systemd[3069]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Mar 11 10:17:09 centos-8 systemd[3069]: tracker-store.service: Scheduled restart job, restart counter is at 317.
Mar 11 10:17:09 centos-8 systemd[3069]: Stopped Tracker metadata database store and lookup manager.
Mar 11 10:17:09 centos-8 systemd[3069]: Starting Tracker metadata database store and lookup manager...
Mar 11 10:17:09 centos-8 systemd[3069]: Started Tracker metadata database store and lookup manager.





Version-Release number of selected component (if applicable):
Installed Packages
mesa-libxatracker.x86_64                                                                                       18.2.6-3.fc29                                                                                @System
tracker.x86_64                                                                                                 2.1.5-2.fc29                                                                                 @System
tracker-miners.x86_64 


How reproducible:
100%

Steps to Reproduce:
1. boot system


Actual results:
Dec 27 15:13:27 t460.festive.local systemd[1857]: Stopped Tracker metadata database store and lookup manager.                                                                                                     
Dec 27 15:13:27 t460.festive.local systemd[1857]: Starting Tracker metadata database store and lookup manager...                                                                                                  
Dec 27 15:13:27 t460.festive.local systemd[1857]: Started Tracker metadata database store and lookup manager.                                                                                                     
Dec 27 15:13:29 t460.festive.local tracker-store[13071]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElement_nie:keyword_TEMP (strerror of errno (not necessarily relate
d): No such file or directory)                                                                                                                                                                                    
Dec 27 15:13:29 t460.festive.local systemd[1857]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE                                                                                       
Dec 27 15:13:29 t460.festive.local systemd[1857]: tracker-store.service: Failed with result 'exit-code'.                                                                                                          
Dec 27 15:13:30 t460.festive.local systemd[1857]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.                                                                                    
Dec 27 15:13:30 t460.festive.local systemd[1857]: tracker-store.service: Scheduled restart job, restart counter is at 4945.                                                                                       
Dec 27 15:13:30 t460.festive.local systemd[1857]: Stopped Tracker metadata database store and lookup manager.                                                                                                     
Dec 27 15:13:30 t460.festive.local systemd[1857]: Starting Tracker metadata database store and lookup manager...                                                                                                  
Dec 27 15:13:30 t460.festive.local systemd[1857]: Started Tracker metadata database store and lookup manager.                                                                                                     
Dec 27 15:13:32 t460.festive.local tracker-store[13109]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElement_nie:keyword_TEMP (strerror of errno (not necessarily relate
d): No such file or directory)                                                                                                                                                                                    
Dec 27 15:13:32 t460.festive.local systemd[1857]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE                                                                                       
Dec 27 15:13:32 t460.festive.local systemd[1857]: tracker-store.service: Failed with result 'exit-code'.                                                                                                          
Dec 27 15:13:32 t460.festive.local systemd[1857]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.                                                                                    
Dec 27 15:13:32 t460.festive.local systemd[1857]: tracker-store.service: Scheduled restart job, restart counter is at 4946.                                                                                       
Dec 27 15:13:32 t460.festive.local systemd[1857]: Stopped Tracker metadata database store and lookup manager.                                                                                                     
Dec 27 15:13:32 t460.festive.local systemd[1857]: Starting Tracker metadata database store and lookup manager...                                                                                                  
Dec 27 15:13:32 t460.festive.local systemd[1857]: Started Tracker metadata database store and lookup manager. 

Expected results:
not this.


Additional info:
https://ask.fedoraproject.org/en/question/9822/how-do-i-disable-tracker-in-gnome/

Tried disabling search and the gsettings and neither stopped the crash looping.

Also tried `tracker daemon stop` to no avail.

looks like I finally had to "tracker reset -r -c" to get it to stop after having tried all the other things.

--- Additional comment from Ben Cotton on 2019-05-02 20:05:58 UTC ---

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

--- Additional comment from Ben Cotton on 2019-05-28 23:29:26 UTC ---

Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 1 R P Herrold 2020-03-11 14:42:45 UTC

This may have been clocking in the systemd, another process.  I removed the offending package and its chain, and a new process (the man rebuild) started working

to quell noise, had to: 
        [herrold@centos-8 pw]$ sudo rpm -e tracker tracker-miners 
                gnome-online-miners gnome-boxes brasero grilo-plugins 
                nautilus  evince-nautilus gnome-classic-session totem 
                brasero-nautilus totem-nautilus


it seemed to have blocked:
   
Mar 11 10:20:24 centos-8 systemd[3069]: Stopped Tracker metadata database store and lookup manag
Mar 11 10:20:24 centos-8 systemd[3069]: tracker-store.service: Start request repeated too quickl
Mar 11 10:20:24 centos-8 systemd[3069]: tracker-store.service: Failed with result 'exit-code'.
Mar 11 10:20:24 centos-8 systemd[3069]: Failed to start Tracker metadata database store and look
Mar 11 10:20:28 centos-8 systemd[1]: Started /usr/bin/systemctl start man-db-cache-update.
Mar 11 10:20:28 centos-8 systemd[1]: cgroup compatibility translation between legacy and unified
Mar 11 10:20:28 centos-8 systemd[1]: Starting man-db-cache-update.service...
Mar 11 10:20:31 centos-8 systemd[1]: Started man-db-cache-update.service.
   
Mar 11 10:23:03 centos-8 NetworkManager[1538]: <info>  [1583936583.9104] dhcp4 (enp0s25): state
Mar 11 10:23:03 centos-8 systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 11 10:23:03 centos-8 dbus-daemon[1333]: [system] Activating via systemd: service name='org.f

Comment 4 RHEL Program Management 2021-09-11 07:26:55 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Note You need to log in before you can comment on or make changes to this bug.