Bug 1255933 - Zoneminder does not start at boot time
Zoneminder does not start at boot time
Product: Fedora
Classification: Fedora
Component: zoneminder (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Charles R. Anderson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-08-21 21:38 EDT by Derek Atkins
Modified: 2016-07-19 15:56 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 15:56:00 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Derek Atkins 2015-08-21 21:38:06 EDT
Description of problem:

Zoneminder would not start at boot time.  Once the system is up and running I can run "systemctl start zoneminder.service" and it starts just fine, but during the boot up sequence it does not start.  This is due to zoneminder (at least in my configuration) requiring network to be up and running before it will work.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. set up mysql on a remote system
2. configure zm.conf to use the remote-system mysql
3. set up zoneminder to boot (systemctl enable zoneminder.service)
4. reboot
5. log in and systemctl status -l zoneminder

Actual results:
The app crashes in Zoneminder/Config.pm  (unfortunately I don't have the error message anymore becuase I have a proposed fix).

Expected results:
Zoneminder should start up.

Additional info:

I fixed this by pulling an explicit dependency on network-online.target into /usr/lib/systemd/system/zoneminder.service:

After=network.target network-online.target

With this change zoneminder now works properly.
Comment 1 Fedora End Of Life 2016-07-19 15:56:00 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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

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

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