dlandon Posted March 30, 2018 Author Share Posted March 30, 2018 57 minutes ago, Interstellar said: Hi, Sadly no dice. Creates the events/images/temp folders and then nothing. Restarted it a few times and tried it using the default setup, to an array disk, to the cache disk and finally to my intended out-of-array disk. Nothing works. From the docker side: root@eaf70ed4c604:/var/cache/zoneminder# ls -al total 0 drwxrwxrwx 5 root www-data 46 Mar 30 09:26 . drwxr-xr-x 1 root root 70 Mar 14 23:42 .. drwxr-xr-x 2 root www-data 6 Mar 29 18:44 events drwxr-xr-x 2 root www-data 6 Mar 29 18:44 images drwxr-xr-x 2 root www-data 6 Mar 29 18:44 temp From the server side: root@UnRAID:/mnt/disks/CCTV1/Front_Door# ls -al total 0 drwxrwxrwx 5 root sshd 46 Mar 30 09:26 ./ drwxrwxrwx 3 root sshd 24 Mar 29 18:38 ../ drwxr-xr-x 2 root sshd 6 Mar 29 18:44 events/ drwxr-xr-x 2 root sshd 6 Mar 29 18:44 images/ drwxr-xr-x 2 root sshd 6 Mar 29 18:44 temp/ Is that right? The permissions are not set right. There is a firstrun script that checks and then changes the permissions if they are not right. I need to see the Zoneminder log so I can see why the permissions are not being set. Just showing me the folder permissions doesn't help me solve your problem. We need to see why the permissions are not being reset. Post the Zoneminder log so I can see the Zoneminder startup. You should see the following: *** Running /etc/my_init.d/30_gen_ssl_keys.sh... using existing keys in "/config/keys" *** Running /etc/my_init.d/40_firstrun.sh... File zm.conf already exists You should see the 40_firstrun.sh entry and there should be a log entry where the permissions are changed. Quote Link to comment
Interstellar Posted March 30, 2018 Share Posted March 30, 2018 (edited) Sorry, stupid mistake not including them... here you go: Seems to be running the scripts, I'll run them again once its started... Mar 30 13:32:44 eaf70ed4c604 syslog-ng[14]: EOF on control channel, closing connection; *** Running /etc/my_init.d/20_apt_update.sh... Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Get:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [962 kB] Get:6 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [792 kB] Fetched 2060 kB in 3s (650 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. *** Running /etc/my_init.d/30_gen_ssl_keys.sh... using existing keys in "/config/keys" *** Running /etc/my_init.d/40_firstrun.sh... File zm.conf already exists Using existing ssmtp configuration Using existing mysql database Using existing skins directory Creating symbolink links usermod: no changes usermod: no changes usermod: no changes Using existing data directory for events Using existing data directory for images Using existing data directory for temp no crontab for root Setting shared memory to : 50% of 16456852 bytes Starting services * Starting MariaDB database server mysqld ...done. Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[474]: Upgrading MySQL tables if necessary. Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: Looking for 'mysql' as: /usr/bin/mysql Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: This installation of MySQL is already upgraded to 10.0.34-MariaDB, use --force if you still need to run mysql_upgrade Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[485]: Checking for insecure root accounts. Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[489]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Database already at version 1.30.4, update aborted. Freshening configuration in database Loading config from DB Saving config to DB * Starting Apache httpd web server apache2 * Starting ZoneMinder: Mar 30 13:33:11 eaf70ed4c604 zmdc[572]: ERR ['zmc -m 1' exited abnormally, exit status 255] Mar 30 13:33:11 eaf70ed4c604 zmeventnotification[612]: INF [Push enabled via FCM] success *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 642 Mar 30 13:33:12 eaf70ed4c604 cron[645]: (CRON) INFO (pidfile fd = 3) Mar 30 13:33:12 eaf70ed4c604 cron[645]: (CRON) INFO (Skipping @reboot jobs -- not system startup) success *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 642 Mar 30 13:33:12 eaf70ed4c604 cron[645]: (CRON) INFO (pidfile fd = 3) Edit: OK, ran the following after start: chown -R root:www-data /var/cache/zoneminder chmod -R go+rw /var/cache/zoneminder And it works. So it begs the question, what is changing the permissions after start? Edited March 30, 2018 by Interstellar Quote Link to comment
dlandon Posted March 30, 2018 Author Share Posted March 30, 2018 8 hours ago, Interstellar said: Sorry, stupid mistake not including them... here you go: Seems to be running the scripts, I'll run them again once its started... Mar 30 13:32:44 eaf70ed4c604 syslog-ng[14]: EOF on control channel, closing connection; *** Running /etc/my_init.d/20_apt_update.sh... Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Get:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [962 kB] Get:6 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [792 kB] Fetched 2060 kB in 3s (650 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. *** Running /etc/my_init.d/30_gen_ssl_keys.sh... using existing keys in "/config/keys" *** Running /etc/my_init.d/40_firstrun.sh... File zm.conf already exists Using existing ssmtp configuration Using existing mysql database Using existing skins directory Creating symbolink links usermod: no changes usermod: no changes usermod: no changes Using existing data directory for events Using existing data directory for images Using existing data directory for temp no crontab for root Setting shared memory to : 50% of 16456852 bytes Starting services * Starting MariaDB database server mysqld ...done. Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[474]: Upgrading MySQL tables if necessary. Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: Looking for 'mysql' as: /usr/bin/mysql Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: This installation of MySQL is already upgraded to 10.0.34-MariaDB, use --force if you still need to run mysql_upgrade Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[485]: Checking for insecure root accounts. Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[489]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Database already at version 1.30.4, update aborted. Freshening configuration in database Loading config from DB Saving config to DB * Starting Apache httpd web server apache2 * Starting ZoneMinder: Mar 30 13:33:11 eaf70ed4c604 zmdc[572]: ERR ['zmc -m 1' exited abnormally, exit status 255] Mar 30 13:33:11 eaf70ed4c604 zmeventnotification[612]: INF [Push enabled via FCM] success *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 642 Mar 30 13:33:12 eaf70ed4c604 cron[645]: (CRON) INFO (pidfile fd = 3) Mar 30 13:33:12 eaf70ed4c604 cron[645]: (CRON) INFO (Skipping @reboot jobs -- not system startup) success *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 642 Mar 30 13:33:12 eaf70ed4c604 cron[645]: (CRON) INFO (pidfile fd = 3) Edit: OK, ran the following after start: chown -R root:www-data /var/cache/zoneminder chmod -R go+rw /var/cache/zoneminder And it works. So it begs the question, what is changing the permissions after start? Don't know, but the 40_firstrun.sh script should detect the incorrect permissions and change them to the correct values. It does log that it is doing that. Do the permissions get reset each time the Docker is started? Or when unRAID is restarted? Quote Link to comment
Interstellar Posted March 30, 2018 Share Posted March 30, 2018 (edited) 1 hour ago, dlandon said: Don't know, but the 40_firstrun.sh script should detect the incorrect permissions and change them to the correct values. It does log that it is doing that. Do the permissions get reset each time the Docker is started? Or when unRAID is restarted? Not reset when re-started or restarting UnRAID. If I delete the data folder I have to do it again. Edited March 30, 2018 by Interstellar Quote Link to comment
dlandon Posted March 31, 2018 Author Share Posted March 31, 2018 (edited) I'll make a change to set permissions when the folders are created. Edited March 31, 2018 by dlandon Quote Link to comment
Shyrka973 Posted March 31, 2018 Share Posted March 31, 2018 (edited) Hi, Whenever zm docker is restarted, zm is not available for an hour or more because I have a lot of camera events. The problem comes from the script 40_firstrun.sh that positions rights on /var/cache/zoneminder. If he does not find root:www-data just on /var/cache/zoneminder directory, it positions the rights on all the tree. But the rights on this directory change. I do not know when (reboot?). Can you change these lines: # Check the ownership on the /var/cache/zoneminder directory if [ `stat -c '%U:%G' /var/cache/zoneminder` != 'root:www-data' ]; then echo "Correcting /var/cache/zoneminder ownership..." chown -R root:www-data /var/cache/zoneminder fi by these; # Check the ownership on the /var/cache/zoneminder directory if [ `stat -c '%U:%G' /var/cache/zoneminder/events` != 'root:www-data' || `stat -c '%U:%G' /var/cache/zoneminder/images` != 'root:www-data' || `stat -c '%U:%G' /var/cache/zoneminder/temp` != 'root:www-data' || ]; then echo "Correcting /var/cache/zoneminder ownership..." chown -R root:www-data /var/cache/zoneminder fi Thanks. Edited March 31, 2018 by Shyrka973 Quote Link to comment
Shyrka973 Posted March 31, 2018 Share Posted March 31, 2018 (edited) I forgot this info: # stat -c '%U:%G' /var/cache/zoneminder nobody:users Edited March 31, 2018 by Shyrka973 Quote Link to comment
dlandon Posted March 31, 2018 Author Share Posted March 31, 2018 1 hour ago, Shyrka973 said: Hi, Whenever zm docker is restarted, zm is not available for an hour or more because I have a lot of camera events. The problem comes from the script 40_firstrun.sh that positions rights on /var/cache/zoneminder. If he does not find root:www-data just on /var/cache/zoneminder directory, it positions the rights on all the tree. But the rights on this directory change. I do not know when (reboot?). Can you change these lines: # Check the ownership on the /var/cache/zoneminder directory if [ `stat -c '%U:%G' /var/cache/zoneminder` != 'root:www-data' ]; then echo "Correcting /var/cache/zoneminder ownership..." chown -R root:www-data /var/cache/zoneminder fi by these; # Check the ownership on the /var/cache/zoneminder directory if [ `stat -c '%U:%G' /var/cache/zoneminder/events` != 'root:www-data' || `stat -c '%U:%G' /var/cache/zoneminder/images` != 'root:www-data' || `stat -c '%U:%G' /var/cache/zoneminder/temp` != 'root:www-data' || ]; then echo "Correcting /var/cache/zoneminder ownership..." chown -R root:www-data /var/cache/zoneminder fi Thanks. Comment out the chown in 40_firstrun.sh and then post the ownership set on the directories. Show /var/cache/zoneminder and the event, images, and temp directories. I don't understand how the ownership is changing. I suspect I shouldn't be checking just the /var/cache/zoneminder directory. I don't see that on my system. Quote Link to comment
Shyrka973 Posted March 31, 2018 Share Posted March 31, 2018 # stat -c '%U:%G' /var/cache/zoneminder nobody:users # stat -c '%U:%G' /var/cache/zoneminder/events root:www-data # stat -c '%U:%G' /var/cache/zoneminder/images root:www-data # stat -c '%U:%G' /var/cache/zoneminder/temp root:www-data Quote Link to comment
dlandon Posted March 31, 2018 Author Share Posted March 31, 2018 28 minutes ago, Shyrka973 said: # stat -c '%U:%G' /var/cache/zoneminder nobody:users # stat -c '%U:%G' /var/cache/zoneminder/events root:www-data # stat -c '%U:%G' /var/cache/zoneminder/images root:www-data # stat -c '%U:%G' /var/cache/zoneminder/temp root:www-data Thank you. Making another adjustment in the ownership checks and adjustments. Quote Link to comment
Waltm Posted April 2, 2018 Share Posted April 2, 2018 (edited) Hi folks. I'm having a little trouble getting started with this. The docker starts but when I go to the web UI I only see the Unraid main menu bar. Manually entering the IP and port just returns a connection refused error. Any help would be greatly appreciated. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/05_set_the_time.sh... Setting the timezone to : America/New_York Current default time zone: 'America/New_York' Local time is now: Mon Apr 2 17:20:55 EDT 2018. Universal Time is now: Mon Apr 2 21:20:55 UTC 2018. Date: Mon Apr 2 17:20:55 EDT 2018 *** Running /etc/my_init.d/06_set_php_time.sh... *** Running /etc/my_init.d/10_syslog-ng.init... Apr 2 17:20:55 998a6f6b5c57 syslog-ng[33]: syslog-ng starting up; version='3.5.6' Apr 2 17:20:56 998a6f6b5c57 syslog-ng[33]: EOF on control channel, closing connection; *** Running /etc/my_init.d/20_apt_update.sh... Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Get:5 http://security.ubuntu.com/ubuntu xenial-security/main Sources [147 kB] Get:6 http://archive.ubuntu.com/ubuntu xenial-updates/main Sources [381 kB] Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe Sources [77.2 kB] Get:8 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [593 kB] Get:9 http://archive.ubuntu.com/ubuntu xenial-updates/universe Sources [250 kB] Get:10 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [428 kB] Get:11 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [962 kB] Get:12 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [793 kB] Fetched 3937 kB in 1s (2853 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. *** Running /etc/my_init.d/30_gen_ssl_keys.sh... using existing keys in "/config/keys" *** Running /etc/my_init.d/40_firstrun.sh... File zm.conf already exists Using existing ssmtp configuration Using existing mysql database Using existing skins directory Creating symbolink links Using existing data directory for events Using existing data directory for images Using existing data directory for temp no crontab for root Setting shared memory to : 50% of 32920064 bytes Starting services * Starting MariaDB database server mysqld ...done. Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[513]: Upgrading MySQL tables if necessary. Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[517]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[517]: Looking for 'mysql' as: /usr/bin/mysql Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[517]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[517]: This installation of MySQL is already upgraded to 10.0.34-MariaDB, use --force if you still need to run mysql_upgrade Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[524]: Checking for insecure root accounts. Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[528]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Database already at version 1.30.4, update aborted. Freshening configuration in database Loading config from DB Saving config to DB * Starting Apache httpd web server apache2 * Starting ZoneMinder: Apr 2 17:21:20 998a6f6b5c57 zmpkg[610]: INF [Sanity checking States table...] Apr 2 17:21:20 998a6f6b5c57 zmpkg[610]: INF [Command: start] Apr 2 17:21:21 998a6f6b5c57 zmdc[623]: INF [Server starting at 18/04/02 17:21:21] Apr 2 17:21:24 998a6f6b5c57 zmpkg[610]: INF [Single server configuration detected. Starting up services.] Apr 2 17:21:24 998a6f6b5c57 zmdc[623]: INF ['zmfilter.pl' starting at 18/04/02 17:21:24, pid = 652] Apr 2 17:21:24 998a6f6b5c57 zmdc[652]: INF ['zmfilter.pl' started at 18/04/02 17:21:24] Apr 2 17:21:24 998a6f6b5c57 zmdc[623]: INF ['zmeventnotification.pl' starting at 18/04/02 17:21:24, pid = 656] Apr 2 17:21:24 998a6f6b5c57 zmdc[656]: INF ['zmeventnotification.pl' started at 18/04/02 17:21:24] Apr 2 17:21:24 998a6f6b5c57 zmfilter[652]: INF [Scanning for events] Apr 2 17:21:24 998a6f6b5c57 zmdc[623]: INF ['zmaudit.pl -c' starting at 18/04/02 17:21:24, pid = 662] Apr 2 17:21:24 998a6f6b5c57 zmdc[662]: INF ['zmaudit.pl -c' started at 18/04/02 17:21:24] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Push enabled via FCM] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Event Notification daemon v 0.98.3 starting] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Creating /etc/private/tokens.txt] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Total event client connections: 0] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Reloading Monitors...] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Loading monitors] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [About to start listening to socket] Apr 2 17:21:24 998a6f6b5c57 zmdc[623]: INF ['zmwatch.pl' starting at 18/04/02 17:21:24, pid = 669] Apr 2 17:21:24 998a6f6b5c57 zmdc[669]: INF ['zmwatch.pl' started at 18/04/02 17:21:24] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Secure WS(WSS) is enabled...] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Web Socket Event Server listening on port 9000] Apr 2 17:21:24 998a6f6b5c57 zmdc[623]: INF ['zmupdate.pl -c' starting at 18/04/02 17:21:24, pid = 677] Apr 2 17:21:24 998a6f6b5c57 zmdc[677]: INF ['zmupdate.pl -c' started at 18/04/02 17:21:24] Apr 2 17:21:25 998a6f6b5c57 zmwatch[669]: INF [Watchdog starting] Apr 2 17:21:25 998a6f6b5c57 zmwatch[669]: INF [Watchdog pausing for 30 seconds] Apr 2 17:21:25 998a6f6b5c57 zmdc[623]: INF ['zmtelemetry.pl' starting at 18/04/02 17:21:25, pid = 683] Apr 2 17:21:25 998a6f6b5c57 zmdc[683]: INF ['zmtelemetry.pl' started at 18/04/02 17:21:25] success *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 686 Apr 2 17:21:25 998a6f6b5c57 cron[689]: (CRON) INFO (pidfile fd = 3) Apr 2 17:21:25 998a6f6b5c57 cron[689]: (CRON) INFO (Running @reboot jobs) Apr 2 17:21:29 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:21:34 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:21:39 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:21:44 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:21:49 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:21:54 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:21:59 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:22:04 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:22:09 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:22:14 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:22:19 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:22:24 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:22:29 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Edited April 2, 2018 by Waltm Updated log file after fixing Apache conflict. Quote Link to comment
dlandon Posted April 2, 2018 Author Share Posted April 2, 2018 29 minutes ago, Waltm said: Hi folks. I'm having a little trouble getting started with this. The docker starts but when I go to the web UI I only see the Unraid main menu bar. Manually entering the IP and port just returns a connection refused error. Any help would be greatly appreciated. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/05_set_the_time.sh... Setting the timezone to : America/New_York Current default time zone: 'America/New_York' Local time is now: Mon Apr 2 17:20:55 EDT 2018. Universal Time is now: Mon Apr 2 21:20:55 UTC 2018. Date: Mon Apr 2 17:20:55 EDT 2018 *** Running /etc/my_init.d/06_set_php_time.sh... *** Running /etc/my_init.d/10_syslog-ng.init... Apr 2 17:20:55 998a6f6b5c57 syslog-ng[33]: syslog-ng starting up; version='3.5.6' Apr 2 17:20:56 998a6f6b5c57 syslog-ng[33]: EOF on control channel, closing connection; *** Running /etc/my_init.d/20_apt_update.sh... Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Get:5 http://security.ubuntu.com/ubuntu xenial-security/main Sources [147 kB] Get:6 http://archive.ubuntu.com/ubuntu xenial-updates/main Sources [381 kB] Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe Sources [77.2 kB] Get:8 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [593 kB] Get:9 http://archive.ubuntu.com/ubuntu xenial-updates/universe Sources [250 kB] Get:10 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [428 kB] Get:11 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [962 kB] Get:12 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [793 kB] Fetched 3937 kB in 1s (2853 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. *** Running /etc/my_init.d/30_gen_ssl_keys.sh... using existing keys in "/config/keys" *** Running /etc/my_init.d/40_firstrun.sh... File zm.conf already exists Using existing ssmtp configuration Using existing mysql database Using existing skins directory Creating symbolink links Using existing data directory for events Using existing data directory for images Using existing data directory for temp no crontab for root Setting shared memory to : 50% of 32920064 bytes Starting services * Starting MariaDB database server mysqld ...done. Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[513]: Upgrading MySQL tables if necessary. Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[517]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[517]: Looking for 'mysql' as: /usr/bin/mysql Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[517]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[517]: This installation of MySQL is already upgraded to 10.0.34-MariaDB, use --force if you still need to run mysql_upgrade Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[524]: Checking for insecure root accounts. Apr 2 17:21:04 998a6f6b5c57 /etc/mysql/debian-start[528]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Database already at version 1.30.4, update aborted. Freshening configuration in database Loading config from DB Saving config to DB * Starting Apache httpd web server apache2 * Starting ZoneMinder: Apr 2 17:21:20 998a6f6b5c57 zmpkg[610]: INF [Sanity checking States table...] Apr 2 17:21:20 998a6f6b5c57 zmpkg[610]: INF [Command: start] Apr 2 17:21:21 998a6f6b5c57 zmdc[623]: INF [Server starting at 18/04/02 17:21:21] Apr 2 17:21:24 998a6f6b5c57 zmpkg[610]: INF [Single server configuration detected. Starting up services.] Apr 2 17:21:24 998a6f6b5c57 zmdc[623]: INF ['zmfilter.pl' starting at 18/04/02 17:21:24, pid = 652] Apr 2 17:21:24 998a6f6b5c57 zmdc[652]: INF ['zmfilter.pl' started at 18/04/02 17:21:24] Apr 2 17:21:24 998a6f6b5c57 zmdc[623]: INF ['zmeventnotification.pl' starting at 18/04/02 17:21:24, pid = 656] Apr 2 17:21:24 998a6f6b5c57 zmdc[656]: INF ['zmeventnotification.pl' started at 18/04/02 17:21:24] Apr 2 17:21:24 998a6f6b5c57 zmfilter[652]: INF [Scanning for events] Apr 2 17:21:24 998a6f6b5c57 zmdc[623]: INF ['zmaudit.pl -c' starting at 18/04/02 17:21:24, pid = 662] Apr 2 17:21:24 998a6f6b5c57 zmdc[662]: INF ['zmaudit.pl -c' started at 18/04/02 17:21:24] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Push enabled via FCM] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Event Notification daemon v 0.98.3 starting] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Creating /etc/private/tokens.txt] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Total event client connections: 0] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Reloading Monitors...] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Loading monitors] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [About to start listening to socket] Apr 2 17:21:24 998a6f6b5c57 zmdc[623]: INF ['zmwatch.pl' starting at 18/04/02 17:21:24, pid = 669] Apr 2 17:21:24 998a6f6b5c57 zmdc[669]: INF ['zmwatch.pl' started at 18/04/02 17:21:24] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Secure WS(WSS) is enabled...] Apr 2 17:21:24 998a6f6b5c57 zmeventnotification[656]: INF [Web Socket Event Server listening on port 9000] Apr 2 17:21:24 998a6f6b5c57 zmdc[623]: INF ['zmupdate.pl -c' starting at 18/04/02 17:21:24, pid = 677] Apr 2 17:21:24 998a6f6b5c57 zmdc[677]: INF ['zmupdate.pl -c' started at 18/04/02 17:21:24] Apr 2 17:21:25 998a6f6b5c57 zmwatch[669]: INF [Watchdog starting] Apr 2 17:21:25 998a6f6b5c57 zmwatch[669]: INF [Watchdog pausing for 30 seconds] Apr 2 17:21:25 998a6f6b5c57 zmdc[623]: INF ['zmtelemetry.pl' starting at 18/04/02 17:21:25, pid = 683] Apr 2 17:21:25 998a6f6b5c57 zmdc[683]: INF ['zmtelemetry.pl' started at 18/04/02 17:21:25] success *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 686 Apr 2 17:21:25 998a6f6b5c57 cron[689]: (CRON) INFO (pidfile fd = 3) Apr 2 17:21:25 998a6f6b5c57 cron[689]: (CRON) INFO (Running @reboot jobs) Apr 2 17:21:29 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:21:34 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:21:39 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:21:44 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:21:49 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:21:54 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:21:59 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:22:04 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:22:09 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:22:14 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:22:19 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:22:24 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 17:22:29 998a6f6b5c57 zmeventnotification[656]: INF [Broadcasting new events to all 0 websocket clients] Give Zoneminder a static IP. Quote Link to comment
Waltm Posted April 2, 2018 Share Posted April 2, 2018 2 hours ago, dlandon said: Give Zoneminder a static IP. Thanks, didn't know I could change IPs on dockers. Set network to br0 and gave it an IP address. Now the UI page just displays "View '' does not exist" The log file shows the php errors below each time I try to access or refresh the UI page. Apr 2 19:04:06 9389d4a44ad6 zmeventnotification[657]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 19:04:11 9389d4a44ad6 zmeventnotification[657]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 19:04:13 9389d4a44ad6 web_php[607]: ERR [Invalid skin css 'classic' setting to ] Apr 2 19:04:13 9389d4a44ad6 web_php[607]: FAT [View '' does not exist] Apr 2 19:04:16 9389d4a44ad6 zmeventnotification[657]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 19:04:21 9389d4a44ad6 zmeventnotification[657]: INF [Broadcasting new events to all 0 websocket clients] Quote Link to comment
dlandon Posted April 2, 2018 Author Share Posted April 2, 2018 10 minutes ago, Waltm said: Thanks, didn't know I could change IPs on dockers. Set network to br0 and gave it an IP address. Now the UI page just displays "View '' does not exist" The log file shows the php errors below each time I try to access or refresh the UI page. Apr 2 19:04:06 9389d4a44ad6 zmeventnotification[657]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 19:04:11 9389d4a44ad6 zmeventnotification[657]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 19:04:13 9389d4a44ad6 web_php[607]: ERR [Invalid skin css 'classic' setting to ] Apr 2 19:04:13 9389d4a44ad6 web_php[607]: FAT [View '' does not exist] Apr 2 19:04:16 9389d4a44ad6 zmeventnotification[657]: INF [Broadcasting new events to all 0 websocket clients] Apr 2 19:04:21 9389d4a44ad6 zmeventnotification[657]: INF [Broadcasting new events to all 0 websocket clients] Looks to be an installation problem. Remove the docker and reinstall it. You may have to remove the appdata/Zoneminder folder. Quote Link to comment
Waltm Posted April 2, 2018 Share Posted April 2, 2018 1 hour ago, dlandon said: Looks to be an installation problem. Remove the docker and reinstall it. You may have to remove the appdata/Zoneminder folder. That did it! I had removed and installed earlier but didn't delete the folder. Thanks again for the help. Quote Link to comment
epicurean Posted April 19, 2018 Share Posted April 19, 2018 sorry, newbie here. Where can I find the latest docker image of Zoneminder for use in Ubuntu? Quote Link to comment
dlandon Posted April 19, 2018 Author Share Posted April 19, 2018 31 minutes ago, epicurean said: sorry, newbie here. Where can I find the latest docker image of Zoneminder for use in Ubuntu? Use CA (Community Applications) to find and install the Zoneminder Docker. Quote Link to comment
Timmons Posted April 21, 2018 Share Posted April 21, 2018 My install has ZM keep going into stopped state with the process still running. Was looking at monit to get it to restart automatically. Frustrating. Anyone have advice? Quote Link to comment
dlandon Posted April 21, 2018 Author Share Posted April 21, 2018 56 minutes ago, Timmons said: My install has ZM keep going into stopped state with the process still running. Was looking at monit to get it to restart automatically. Frustrating. Anyone have advice? That is probably happening because you are stressing the server. Check to see what the cpu usage is when Zoneminder is running. You may see that the cpu utilization is running at 100%. Quote Link to comment
BilboT34Baggins Posted May 1, 2018 Share Posted May 1, 2018 On 2/15/2018 at 12:09 PM, dlandon said: Updated Docker will now create your crontab entries. Read the first post on how to create a 'cron' file and have the Docker create your crontab entries when it starts. @dlandon I've FINALLy gotten time to try to get this running, and for the life of me cannot determine what first post you're talking about here. Where do I go to tell the docker what crontab entries to create when it starts?? Quote Link to comment
dlandon Posted May 1, 2018 Author Share Posted May 1, 2018 2 hours ago, BilboT34Baggins said: @dlandon I've FINALLy gotten time to try to get this running, and for the life of me cannot determine what first post you're talking about here. Where do I go to tell the docker what crontab entries to create when it starts?? The first posting of this thread. Quote Link to comment
BilboT34Baggins Posted May 2, 2018 Share Posted May 2, 2018 19 hours ago, dlandon said: The first posting of this thread. AH! Wow, I thought about that for a long time and didn't get that. Ok so I wrote the following .cron file (named zoneminder_states.cron). # Cron script for changing zoneminder states # Monday to Friday operation 30 4 * * 1-5 /usr/bin/zmpkg.pl Come&Go 0 7 * * 1-5 /usr/bin/zmpkg.pl Daytime 0 16 * * 1-5 /usr/bin/zmpkg.pl Come&Go 30 17 * * 1-5 /usr/bin/zmpkg.pl Daytime 0 21 * * 1-5 /usr/bin/zmpkg.pl Nighttime # Saturday and Sunday operation 0 8 * * 0,6 /usr/bin/zmpkg.pl Daytime 0 22 * * 0,6 /usr/bin/zmpkg.pl Nighttime It is placed in the /mnt/user/appdata/Zoneminder folder. I restarted Zoneminder, and surprise, didn't work out. Am I using the right directory /usr/bin/zmpkg.pl? Quote Link to comment
dlandon Posted May 2, 2018 Author Share Posted May 2, 2018 5 hours ago, BilboT34Baggins said: AH! Wow, I thought about that for a long time and didn't get that. Ok so I wrote the following .cron file (named zoneminder_states.cron). # Cron script for changing zoneminder states # Monday to Friday operation 30 4 * * 1-5 /usr/bin/zmpkg.pl Come&Go 0 7 * * 1-5 /usr/bin/zmpkg.pl Daytime 0 16 * * 1-5 /usr/bin/zmpkg.pl Come&Go 30 17 * * 1-5 /usr/bin/zmpkg.pl Daytime 0 21 * * 1-5 /usr/bin/zmpkg.pl Nighttime # Saturday and Sunday operation 0 8 * * 0,6 /usr/bin/zmpkg.pl Daytime 0 22 * * 0,6 /usr/bin/zmpkg.pl Nighttime It is placed in the /mnt/user/appdata/Zoneminder folder. I restarted Zoneminder, and surprise, didn't work out. Am I using the right directory /usr/bin/zmpkg.pl? Surprise, read it again. Wrong file name. Quote Link to comment
BilboT34Baggins Posted May 2, 2018 Share Posted May 2, 2018 4 hours ago, dlandon said: Surprise, read it again. Wrong file name. Ok I re-read the first post on this thread, and decided that I needed to change the name of my 'zoneminder_states.cron' file to just 'cron'. Is that what you meant? Also that still didn't work. Quote Link to comment
dlandon Posted May 2, 2018 Author Share Posted May 2, 2018 9 hours ago, BilboT34Baggins said: Ok I re-read the first post on this thread, and decided that I needed to change the name of my 'zoneminder_states.cron' file to just 'cron'. Is that what you meant? Also that still didn't work. You have to be more specific on what didn't work. Verify that the 'cron' file was loaded properly. You can check if your 'cron' file is being loaded by getting into the Zoneminder command line: docker exec -it Zoneminder bash Then type the following command: crontab -l You should see your cron entries. If not, troubleshoot the 'cron' file name and placement. Be sure you are using a Linux type editor to create the 'cron' file. If the 'cron file is loaded properly but still not doing what you want, check that you have created the events properly. You can test that on the command line of the docker: /usr/bin/zmpkg.pl Daytime This will put Zoneminder in the Daytime mode of operation. /usr/bin/zmpkg.pl Nightime This will put Zoneminder in the Nightime mode of operation. You'll have to consult the Zoneminder documentation on configuring these different modes. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.