Bug 1350711

Summary: tracker-store.service: Failed at step EXEC spawning /usr/lib/tracker/tracker-store: No such file or directory
Product: [Fedora] Fedora Reporter: Vít Ondruch <vondruch>
Component: trackerAssignee: Igor Gnatenko <ignatenko>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dakingun, debarshir, ignatenko
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-28 08:26:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vít Ondruch 2016-06-28 08:16:50 UTC 
Description of problem:
Tracker is probably not working. My journal contains plenty of messages such as:

```
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[1717]: Starting Tracker metadata database store and lookup manager...
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[2821]: tracker-store.service: Failed at step EXEC spawning /usr/lib/tracker/tracker-store: No such file or directory
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[1717]: tracker-store.service: Main process exited, code=exited, status=203/EXEC
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[1717]: Failed to start Tracker metadata database store and lookup manager.
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[1717]: tracker-store.service: Unit entered failed state.
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[1717]: tracker-store.service: Failed with result 'exit-code'.
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[1717]: tracker-store.service: Service hold-off time over, scheduling restart.
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[1717]: Stopped Tracker metadata database store and lookup manager.
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[1717]: Starting Tracker metadata database store and lookup manager...
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[2823]: tracker-store.service: Failed at step EXEC spawning /usr/lib/tracker/tracker-store: No such file or directory
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[1717]: tracker-store.service: Main process exited, code=exited, status=203/EXEC
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[1717]: Failed to start Tracker metadata database store and lookup manager.
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[1717]: tracker-store.service: Unit entered failed state.
Jun 28 09:58:54 unused-4-132.brq.redhat.com systemd[1717]: tracker-store.service: Failed with result 'exit-code'.
Jun 28 09:58:55 unused-4-132.brq.redhat.com systemd[1717]: tracker-store.service: Service hold-off time over, scheduling restart.
Jun 28 09:58:55 unused-4-132.brq.redhat.com systemd[1717]: Stopped Tracker metadata database store and lookup manager.
Jun 28 09:58:55 unused-4-132.brq.redhat.com systemd[1717]: tracker-store.service: Start request repeated too quickly.
Jun 28 09:58:55 unused-4-132.brq.redhat.com systemd[1717]: Failed to start Tracker metadata database store and lookup manager.
```

Version-Release number of selected component (if applicable):
$ rpm -q tracker
tracker-1.9.0-1.fc25.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Tracker spams my journal and probably does not work.

Expected results:
Tracker works.


Additional info:
I reverted to tracker-1.8.0-3.fc25.x86_64 which appears to work correctly.
Comment 1 Igor Gnatenko 2016-06-28 08:26:23 UTC 
let's track in upstream.