Bug 1350711 - tracker-store.service: Failed at step EXEC spawning /usr/lib/tracker/tracker-store: No such file or directory
Summary: tracker-store.service: Failed at step EXEC spawning /usr/lib/tracker/tracker-...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: tracker
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Igor Gnatenko
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-28 08:16 UTC by Vít Ondruch
Modified: 2016-06-28 08:26 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-06-28 08:26:23 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 768127 0 None None None 2016-06-28 08:21:51 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.