It is sure, I'm missing something, but can't figure out, what.
I try start zonemindei in my Fedora 20, but I get:
systemctl status zoneminder.service -l
zoneminder.service - Video security and surveillance system
Loaded: loaded (/usr/lib/systemd/system/zoneminder.service; enabled)
Active: failed (Result: exit-code) since ke 2014-08-27 08:04:01 GMT; 3s ago
Process: 9097 ExecStart=/usr/bin/zmpkg.pl start (code=exited, status=1/FAILURE)
Main PID: 31902 (code=exited, status=255)
elo 27 08:04:00 oh1rdf.ampr.org systemd[1]: Starting Video security and surveillance system...
elo 27 08:04:00 oh1rdf.ampr.org zmpkg[9097]: INF [Command: start]
elo 27 08:04:00 oh1rdf.ampr.org su[9104]: (to apache) root on none
elo 27 08:04:00 oh1rdf.ampr.org su[9107]: (to apache) root on none
elo 27 08:04:01 oh1rdf.ampr.org systemd[1]: zoneminder.service: control process exited, code=exited status=1
elo 27 08:04:01 oh1rdf.ampr.org systemd[1]: Failed to start Video security and surveillance system.
elo 27 08:04:01 oh1rdf.ampr.org systemd[1]: Unit zoneminder.service entered failed state.
Anyone familiar with this?
Jarmo
Zm wont start
-
knight-of-ni
- Posts: 2406
- Joined: Thu Oct 18, 2007 1:55 pm
- Location: Shiloh, IL
Re: Zm wont start
My assumption is that you have already created a new database or updated your existing database with zmupdate.pl. If you haven't then do that now.
The root cause of this issue is that zoneminder does not yet support systemd.
I've got an open pull request that solves this, which should fix thigns for good:
https://github.com/ZoneMinder/ZoneMinder/pull/502
In the meantime, the way to avoid issues with starting and stopping zoneminder is to always use systemctl. Do not start/stop zoneminder from the web UI. Do not start/stop zoneminder by calling zmpkg directly from the command line.
If you start/stop zoneminder using anything other than systemctl, systemd marks the zoneminder service as failed (even though it really hasn't), which you can see in the output you posted. As long as systemd has flagged the service as failed, it will prevent you from (re)starting it until it is cleared.
To reset things back to normal, just reboot the machine and start the service with systemctl if it doesn't start automatically on boot. It will start fine the very first time you issue the start command.
The root cause of this issue is that zoneminder does not yet support systemd.
I've got an open pull request that solves this, which should fix thigns for good:
https://github.com/ZoneMinder/ZoneMinder/pull/502
In the meantime, the way to avoid issues with starting and stopping zoneminder is to always use systemctl. Do not start/stop zoneminder from the web UI. Do not start/stop zoneminder by calling zmpkg directly from the command line.
If you start/stop zoneminder using anything other than systemctl, systemd marks the zoneminder service as failed (even though it really hasn't), which you can see in the output you posted. As long as systemd has flagged the service as failed, it will prevent you from (re)starting it until it is cleared.
To reset things back to normal, just reboot the machine and start the service with systemctl if it doesn't start automatically on boot. It will start fine the very first time you issue the start command.
Visit my blog for ZoneMinder related projects using the Raspberry Pi, Orange Pi, Odroid, and the ESP8266
All of these can be found at https://zoneminder.blogspot.com/
All of these can be found at https://zoneminder.blogspot.com/
Re: Zm wont start
Any other idea?knnniggett wrote:My assumption is that you have already created a new database or updated your existing database with zmupdate.pl. If you haven't then do that now.
Yes done that....
start/stop zoneminder from the web UI. Do not start/stop zoneminder by calling zmpkg directly from the command line.
Not working rebooting either....
systemctl status zoneminder.service -l
zoneminder.service - Video security and surveillance system
Loaded: loaded (/usr/lib/systemd/system/zoneminder.service; enabled)
Active: failed (Result: resources) since ke 2014-08-27 16:37:56 GMT; 13s ago
Process: 1501 ExecStart=/usr/bin/zmpkg.pl start (code=exited, status=0/SUCCESS)
elo 27 16:37:37 oh1rdf.ampr.org zmpkg[1501]: INF [Command: start]
elo 27 16:37:47 oh1rdf.ampr.org su[1558]: (to apache) root on none
elo 27 16:37:49 oh1rdf.ampr.org su[1614]: (to apache) root on none
elo 27 16:37:51 oh1rdf.ampr.org su[1626]: (to apache) root on none
elo 27 16:37:54 oh1rdf.ampr.org su[1643]: (to apache) root on none
elo 27 16:37:56 oh1rdf.ampr.org systemd[1]: PID file /run/zoneminder/zm.pid not readable (yet?) after start.
elo 27 16:37:56 oh1rdf.ampr.org systemd[1]: Failed to start Video security and surveillance system.
elo 27 16:37:56 oh1rdf.ampr.org systemd[1]: Unit zoneminder.service entered failed state.
systemctl start zoneminder.service
Job for zoneminder.service failed. See 'systemctl status zoneminder.service' and 'journalctl -xn' for details.
systemctl status zoneminder.service -l
zoneminder.service - Video security and surveillance system
Loaded: loaded (/usr/lib/systemd/system/zoneminder.service; enabled)
Active: failed (Result: exit-code) since ke 2014-08-27 16:39:46 GMT; 4s ago
Process: 1763 ExecStart=/usr/bin/zmpkg.pl start (code=exited, status=1/FAILURE)
elo 27 16:39:45 oh1rdf.ampr.org systemd[1]: Starting Video security and surveillance system...
elo 27 16:39:46 oh1rdf.ampr.org zmpkg[1763]: INF [Command: start]
elo 27 16:39:46 oh1rdf.ampr.org su[1770]: (to apache) root on none
elo 27 16:39:46 oh1rdf.ampr.org su[1773]: (to apache) root on none
elo 27 16:39:46 oh1rdf.ampr.org systemd[1]: zoneminder.service: control process exited, code=exited status=1
elo 27 16:39:46 oh1rdf.ampr.org systemd[1]: Failed to start Video security and surveillance system.
elo 27 16:39:46 oh1rdf.ampr.org systemd[1]: Unit zoneminder.service entered failed state.
As you see, in reboot "systemctl" calls /usr/bin/zmpkg.pl also.... Now was, that couldn't find PID file. Ok this is permission problem, think... I changed /run/zoneminder into 777 and then from console, not with command "systemctl"
If you start/stop zoneminder using anything other than systemctl, systemd marks the zoneminder service as failed (even though it really hasn't), which you can see in the output you posted. As long as systemd has flagged the service as failed, it will prevent you from (re)starting it until it is cleared.
Ok, but as you see, no worky... there's something else here in my server...
To reset things back to normal, just reboot the machine and start the service with systemctl if it doesn't start automatically on boot. It will start fine the very first time you issue the start command.
Jarmo
Re: Zm wont start
Yes done that....
start/stop zoneminder from the web UI. Do not start/stop zoneminder by calling zmpkg directly from the command line.
Ok
Made direct command from console, zmpkg start and got it running... Added monitors there and they strted
making recordings.
Ok, now I have this web issue... Can't watch monirors... I get into log...
socket_sendto( /var/lib/zoneminder/sock/zms-565696s.sock ) failed: No such file or directory
/usr/share/zoneminder/www/includes/functions.php
This was earlier in version 1.25 also, is it Fedora specifig?
Any solution for this?
Jarmo
start/stop zoneminder from the web UI. Do not start/stop zoneminder by calling zmpkg directly from the command line.
Ok
Made direct command from console, zmpkg start and got it running... Added monitors there and they strted
making recordings.
Ok, now I have this web issue... Can't watch monirors... I get into log...
socket_sendto( /var/lib/zoneminder/sock/zms-565696s.sock ) failed: No such file or directory
/usr/share/zoneminder/www/includes/functions.php
This was earlier in version 1.25 also, is it Fedora specifig?
Any solution for this?
Jarmo