Not really sure where to start. Upgraded from 1.34 to 1.36 using apt. Database upgrade went fine. Have no picture after the upgrade. zmwatch is continually restarting zmc. I have errors like:
Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running.
No RTSP sources
Failed to prime capture of initial monitor
Restarting capture daemon for Driveway, no image since startup. Startup time was 1648229850 - now 1648229870 > 5
In addition, when I try to turn on debug logging I get this:
Warning: error_log(/tmp/zm/zm_debug.log.1198): failed to open stream: No such file or directory in /usr/share/zoneminder/www/includes/logger.php on line 397
Any advice on what to look at first?
Upgrade from 1.34 to 1.36 on Debian broke ZM
Upgrade from 1.34 to 1.36 on Debian broke ZM
Last edited by BlueH2O on Thu Apr 07, 2022 6:39 pm, edited 1 time in total.
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Well I'm restoring this machine from backup. ZoneMinder updates are a cluster****
Last edited by BlueH2O on Thu Apr 07, 2022 6:39 pm, edited 1 time in total.
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Tried the upgrade again, doing one step at a time with snapshots.
After running zmupdate (successfully!) I have buckets of errors and no picture
04/06/2022 14:28:57.376506 zmtrigger[1516].ERR [ZoneMinder::Memory::Mapped:90] [Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running.]
04/06/2022 14:28:16.698275 zmdc[1471].WAR [ZMServer:413] [!send_stop so starting 'zmc -m 1']
04/06/2022 14:25:54.093799 zmwatch[1520].INF [main:143] [Restarting capture daemon for Driveway, shared data not valid]
04/06/22 14:28:26.800554 zmc_m1[4669].ERR-zm_remote_camera_rtsp.cpp/135 [No RTSP sources]
I would like to get this thing upgraded in such a way it actually RUNS when I'm done; surely someone has some ideas?
After running zmupdate (successfully!) I have buckets of errors and no picture
04/06/2022 14:28:57.376506 zmtrigger[1516].ERR [ZoneMinder::Memory::Mapped:90] [Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running.]
04/06/2022 14:28:16.698275 zmdc[1471].WAR [ZMServer:413] [!send_stop so starting 'zmc -m 1']
04/06/2022 14:25:54.093799 zmwatch[1520].INF [main:143] [Restarting capture daemon for Driveway, shared data not valid]
04/06/22 14:28:26.800554 zmc_m1[4669].ERR-zm_remote_camera_rtsp.cpp/135 [No RTSP sources]
I would like to get this thing upgraded in such a way it actually RUNS when I'm done; surely someone has some ideas?
Last edited by BlueH2O on Thu Apr 07, 2022 6:39 pm, edited 1 time in total.
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Checked RTSP stream with ffplay & VLC, works fine.
Tried ffmpeg source type as noted in changelog, made no difference
ZM still shows a black window with "unable to stream" or occasionally a garbled video frame.
Still getting "[Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running.]"
zmc is running, it just seems to be constantly restarting. The memory map file exists and the permission looks suitable.
What is zmMemAttach? Where does it exist?
Tried ffmpeg source type as noted in changelog, made no difference
ZM still shows a black window with "unable to stream" or occasionally a garbled video frame.
Still getting "[Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running.]"
zmc is running, it just seems to be constantly restarting. The memory map file exists and the permission looks suitable.
What is zmMemAttach? Where does it exist?
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
ZMC is crashing. Looks like it’s simply that it can’t acquire the camera stream, or doesn’t like what it gets. Might be worth running ffprobe or similar and checking the format/codec for clues.
-
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
What version of Debian?
Where did you install ZM 1.34 from? The Debian repo or the zmrepo?
Did you do the upgrade from the zmrepo?
What hardware is ZM running on?
I can set up a test machine and try to duplicate your effort. Something else you might try is to save a backup of the ZM database, wipe the main drive and install a fresh copy of Bullseye, install ZM from the instructions on the WIKI, replace the ZM database with the backup copy the upgrade the database. Yes, you will loose all the events but it should work. You can run zmaudit to clear the old events from the database and your cams and zones should work as before.
Where did you install ZM 1.34 from? The Debian repo or the zmrepo?
Did you do the upgrade from the zmrepo?
What hardware is ZM running on?
I can set up a test machine and try to duplicate your effort. Something else you might try is to save a backup of the ZM database, wipe the main drive and install a fresh copy of Bullseye, install ZM from the instructions on the WIKI, replace the ZM database with the backup copy the upgrade the database. Yes, you will loose all the events but it should work. You can run zmaudit to clear the old events from the database and your cams and zones should work as before.
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Debian 11.3 on Xen. Everything was installed from zmrepo.
I may try the rebuild approach.
I may try the rebuild approach.
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Built another VM and followed https://wiki.zoneminder.com/Debian_11_B ... der_1.36.x
Error right out of the box.
Job for zoneminder.service failed because the control process exited with error code.
See "systemctl status zoneminder.service" and "journalctl -xe" for details.
● zoneminder.service - ZoneMinder CCTV recording and surveillance system
Loaded: loaded (/lib/systemd/system/zoneminder.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2022-04-11 14:44:42 EDT; 9s ago
Process: 23510 ExecStart=/usr/bin/zmpkg.pl start (code=exited, status=1/FAILURE)
CPU: 180ms
Apr 11 14:44:42 zoneminder systemd[1]: zoneminder.service: Control process exited, code=exited, status=1/FAILURE
Apr 11 14:44:42 zoneminder systemd[1]: zoneminder.service: Failed with result 'exit-code'.
Apr 11 14:44:42 zoneminder systemd[1]: Failed to start ZoneMinder CCTV recording and surveillance system.
Apr 11 14:45:03 zoneminder systemd[1]: Failed to start ZoneMinder CCTV recording and surveillance system.
░░ Subject: A start job for unit zoneminder.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit zoneminder.service has finished with a failure.
░░
░░ The job identifier is 14243 and the job result is failed.
Error right out of the box.
Job for zoneminder.service failed because the control process exited with error code.
See "systemctl status zoneminder.service" and "journalctl -xe" for details.
● zoneminder.service - ZoneMinder CCTV recording and surveillance system
Loaded: loaded (/lib/systemd/system/zoneminder.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2022-04-11 14:44:42 EDT; 9s ago
Process: 23510 ExecStart=/usr/bin/zmpkg.pl start (code=exited, status=1/FAILURE)
CPU: 180ms
Apr 11 14:44:42 zoneminder systemd[1]: zoneminder.service: Control process exited, code=exited, status=1/FAILURE
Apr 11 14:44:42 zoneminder systemd[1]: zoneminder.service: Failed with result 'exit-code'.
Apr 11 14:44:42 zoneminder systemd[1]: Failed to start ZoneMinder CCTV recording and surveillance system.
Apr 11 14:45:03 zoneminder systemd[1]: Failed to start ZoneMinder CCTV recording and surveillance system.
░░ Subject: A start job for unit zoneminder.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit zoneminder.service has finished with a failure.
░░
░░ The job identifier is 14243 and the job result is failed.
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
I built my current Bullseye server from those install instructions and it is running very well. I am not running on a VM however and do not recommend a VM for production use with Zoneminder. I know it is done but...BlueH2O wrote: ↑Mon Apr 11, 2022 6:46 pm Built another VM and followed https://wiki.zoneminder.com/Debian_11_B ... der_1.36.x
Error right out of the box.
Job for zoneminder.service failed because the control process exited with error code.
See "systemctl status zoneminder.service" and "journalctl -xe" for details.
● zoneminder.service - ZoneMinder CCTV recording and surveillance system
Loaded: loaded (/lib/systemd/system/zoneminder.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2022-04-11 14:44:42 EDT; 9s ago
Process: 23510 ExecStart=/usr/bin/zmpkg.pl start (code=exited, status=1/FAILURE)
CPU: 180ms
Apr 11 14:44:42 zoneminder systemd[1]: zoneminder.service: Control process exited, code=exited, status=1/FAILURE
Apr 11 14:44:42 zoneminder systemd[1]: zoneminder.service: Failed with result 'exit-code'.
Apr 11 14:44:42 zoneminder systemd[1]: Failed to start ZoneMinder CCTV recording and surveillance system.
Apr 11 14:45:03 zoneminder systemd[1]: Failed to start ZoneMinder CCTV recording and surveillance system.
░░ Subject: A start job for unit zoneminder.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit zoneminder.service has finished with a failure.
░░
░░ The job identifier is 14243 and the job result is failed.
Be sure to use Mariadb and not MySQL and do not assume a step is not needed.
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Must be something in the web server group that conflicts. Works better with a minimal install.
How does one restore the database?
# mysql zm < /home/zmuser/zm.sql
ERROR 1005 (HY000) at line 232: Can't create table `zm`.`Events` (errno: 150 "Foreign key constraint is incorrectly formed")
How does one restore the database?
# mysql zm < /home/zmuser/zm.sql
ERROR 1005 (HY000) at line 232: Can't create table `zm`.`Events` (errno: 150 "Foreign key constraint is incorrectly formed")
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Well, I am basically lazy and use Webmin to backup and restore a database.
AS for VM's - I do use Virtual Box to "test" distros and sometimes an install procedure. But I feel that using a VM adds work to a system that could be used elsewhere in a production environment. Old guy...Old habits... I go back to Windows 3.1 on DOS 5
My home Bullseye Zoneminder was set up a week before 11.3 was released and I have no issues with it. Zoneminder 1.36.12 was installed on it and now has 1.36.14
As for the database, with a DB backup, from Webmin, I install a fresh OS and Zoneminder. This creates the zm database in Mariadb. Using Webmin I empty the contents of the zm database then import the backup into the zm database. The backup will be in a sql format. This has worked for me dozens of times.
AS for VM's - I do use Virtual Box to "test" distros and sometimes an install procedure. But I feel that using a VM adds work to a system that could be used elsewhere in a production environment. Old guy...Old habits... I go back to Windows 3.1 on DOS 5
My home Bullseye Zoneminder was set up a week before 11.3 was released and I have no issues with it. Zoneminder 1.36.12 was installed on it and now has 1.36.14
As for the database, with a DB backup, from Webmin, I install a fresh OS and Zoneminder. This creates the zm database in Mariadb. Using Webmin I empty the contents of the zm database then import the backup into the zm database. The backup will be in a sql format. This has worked for me dozens of times.
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Hi,
I seem to have a similar problem.
Running a Debian server which I upgraded from 9 to 11 recently. Since then I have issues with ZM. I realised that 1.36 is now the current version so I changed the zoneminder.list file to point to 1.36 bullseye.
But now it seems to be completely broken. Not sure where to start with to be honest. Here some recent messages from the logfile:
I seem to have a similar problem.
Running a Debian server which I upgraded from 9 to 11 recently. Since then I have issues with ZM. I realised that 1.36 is now the current version so I changed the zoneminder.list file to point to 1.36 bullseye.
But now it seems to be completely broken. Not sure where to start with to be honest. Here some recent messages from the logfile:
Let me know what I can provide to enable you to help me."2022-04-19 10:22:11",zmdc,,272483,INF,"'zmc -m 3' crashed, signal 6",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,272483,INF,"'zmc -m 2' starting at 22/04/19 10:22:10, pid = 288997",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,288997,INF,"'zmc -m 2' started at 22/04/19 10:22:10",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,272483,INF,"Starting pending process, zmc -m 2",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,288995,INF,"'zmc -m 3' started at 22/04/19 10:22:10",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,272483,INF,"'zmc -m 3' starting at 22/04/19 10:22:10, pid = 288995",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,272483,WAR,"!send_stop so starting 'zmc -m 3'",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,272483,INF,"Command 'zmc -m 3' removed from pending list at 22/04/19 10:22:10",zmdc.pl,'-
"2022-04-19 10:22:10",zmwatch,,272552,INF,"Restarting capture daemon for Atrium, shared data not valid",zmwatch.pl,'-
"2022-04-19 10:22:10",zmdc,,272483,INF,"'zmc -m 2' crashed, signal 6",zmdc.pl,'-
"2022-04-19 10:22:10",zmwatch,,272552,ERR,"Memory map file '/dev/shm/zm.mmap.3' does not exist in zmMemAttach. zmc might not be running.",zmwatch.pl,'-
"2022-04-19 10:22:09",zmdc,,272483,INF,"'zmc -m 2' starting at 22/04/19 10:22:09, pid = 288989",zmdc.pl,'-
"2022-04-19 10:22:09",zmdc,,288989,INF,"'zmc -m 2' started at 22/04/19 10:22:09",zmdc.pl,'-
"2022-04-19 10:22:09",zmdc,,272483,WAR,"!send_stop so starting 'zmc -m 2'",zmdc.pl,'-
"2022-04-19 10:22:09",zmdc,,272483,INF,"Command 'zmc -m 2' removed from pending list at 22/04/19 10:22:09",zmdc.pl,'-
"2022-04-19 10:22:09",zmwatch,,272552,INF,"Restarting capture daemon for Kreuzgasse, shared data not valid",zmwatch.pl,'-
"2022-04-19 10:22:09",zmwatch,,272552,ERR,"Memory map file '/dev/shm/zm.mmap.2' does not exist in zmMemAttach. zmc might not be running.",zmwatch.pl,'-
"2022-04-19 10:22:06",zmdc,,272483,INF,"'zmc -m 3' crashed, signal 6",zmdc.pl,'-
"2022-04-19 10:22:05",zmdc,,272483,INF,"'zmc -m 3' starting at 22/04/19 10:22:05, pid = 288976",zmdc.pl,'-
"2022-04-19 10:22:05",zmdc,,288976,INF,"'zmc -m 3' started at 22/04/19 10:22:05",zmdc.pl,'-
"2022-04-19 10:22:05",zmdc,,272483,INF,"Starting pending process, zmc -m 3",zmdc.pl,'-
"2022-04-19 10:22:04",zmdc,,272483,INF,"'zmc -m 2' crashed, signal 6",zmdc.pl,'-
"2022-04-19 10:22:04",zmdc,,288973,INF,"'zmc -m 2' started at 22/04/19 10:22:04",zmdc.pl,'-
"2022-04-19 10:22:04",zmdc,,272483,INF,"'zmc -m 2' starting at 22/04/19 10:22:04, pid = 288973",zmdc.pl,'-
"2022-04-19 10:22:04",zmdc,,272483,INF,"Starting pending process, zmc -m 2",zmdc.pl,'-
"2022-04-19 10:22:01",zmdc,,272483,INF,"'zmc -m 3' crashed, signal 6",zmdc.pl,'-
"2022-04-19 10:22:00",zmdc,,272483,INF,"'zmc -m 2' crashed, signal 6",zmdc.pl,'-
"2022-04-19 10:22:00",zmdc,,288965,INF,"'zmc -m 3' started at 22/04/19 10:22:00",zmdc.pl,'-
"2022-04-19 10:22:00",zmdc,,272483,INF,"'zmc -m 3' starting at 22/04/19 10:22:00, pid = 288965",zmdc.pl,'-
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
In your case I would start over with a fresh OS. Yes, wipe everything! You could remove Zoneminder and the zm database then reinstall but a fresh version of Bullseye would be better.MatzR wrote: ↑Tue Apr 19, 2022 8:23 am Hi,
I seem to have a similar problem.
Running a Debian server which I upgraded from 9 to 11 recently. Since then I have issues with ZM. I realised that 1.36 is now the current version so I changed the zoneminder.list file to point to 1.36 bullseye.
But now it seems to be completely broken. Not sure where to start with to be honest. Here some recent messages from the logfile:Let me know what I can provide to enable you to help me."2022-04-19 10:22:11",zmdc,,272483,INF,"'zmc -m 3' crashed, signal 6",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,272483,INF,"'zmc -m 2' starting at 22/04/19 10:22:10, pid = 288997",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,288997,INF,"'zmc -m 2' started at 22/04/19 10:22:10",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,272483,INF,"Starting pending process, zmc -m 2",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,288995,INF,"'zmc -m 3' started at 22/04/19 10:22:10",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,272483,INF,"'zmc -m 3' starting at 22/04/19 10:22:10, pid = 288995",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,272483,WAR,"!send_stop so starting 'zmc -m 3'",zmdc.pl,'-
"2022-04-19 10:22:10",zmdc,,272483,INF,"Command 'zmc -m 3' removed from pending list at 22/04/19 10:22:10",zmdc.pl,'-
"2022-04-19 10:22:10",zmwatch,,272552,INF,"Restarting capture daemon for Atrium, shared data not valid",zmwatch.pl,'-
"2022-04-19 10:22:10",zmdc,,272483,INF,"'zmc -m 2' crashed, signal 6",zmdc.pl,'-
"2022-04-19 10:22:10",zmwatch,,272552,ERR,"Memory map file '/dev/shm/zm.mmap.3' does not exist in zmMemAttach. zmc might not be running.",zmwatch.pl,'-
"2022-04-19 10:22:09",zmdc,,272483,INF,"'zmc -m 2' starting at 22/04/19 10:22:09, pid = 288989",zmdc.pl,'-
"2022-04-19 10:22:09",zmdc,,288989,INF,"'zmc -m 2' started at 22/04/19 10:22:09",zmdc.pl,'-
"2022-04-19 10:22:09",zmdc,,272483,WAR,"!send_stop so starting 'zmc -m 2'",zmdc.pl,'-
"2022-04-19 10:22:09",zmdc,,272483,INF,"Command 'zmc -m 2' removed from pending list at 22/04/19 10:22:09",zmdc.pl,'-
"2022-04-19 10:22:09",zmwatch,,272552,INF,"Restarting capture daemon for Kreuzgasse, shared data not valid",zmwatch.pl,'-
"2022-04-19 10:22:09",zmwatch,,272552,ERR,"Memory map file '/dev/shm/zm.mmap.2' does not exist in zmMemAttach. zmc might not be running.",zmwatch.pl,'-
"2022-04-19 10:22:06",zmdc,,272483,INF,"'zmc -m 3' crashed, signal 6",zmdc.pl,'-
"2022-04-19 10:22:05",zmdc,,272483,INF,"'zmc -m 3' starting at 22/04/19 10:22:05, pid = 288976",zmdc.pl,'-
"2022-04-19 10:22:05",zmdc,,288976,INF,"'zmc -m 3' started at 22/04/19 10:22:05",zmdc.pl,'-
"2022-04-19 10:22:05",zmdc,,272483,INF,"Starting pending process, zmc -m 3",zmdc.pl,'-
"2022-04-19 10:22:04",zmdc,,272483,INF,"'zmc -m 2' crashed, signal 6",zmdc.pl,'-
"2022-04-19 10:22:04",zmdc,,288973,INF,"'zmc -m 2' started at 22/04/19 10:22:04",zmdc.pl,'-
"2022-04-19 10:22:04",zmdc,,272483,INF,"'zmc -m 2' starting at 22/04/19 10:22:04, pid = 288973",zmdc.pl,'-
"2022-04-19 10:22:04",zmdc,,272483,INF,"Starting pending process, zmc -m 2",zmdc.pl,'-
"2022-04-19 10:22:01",zmdc,,272483,INF,"'zmc -m 3' crashed, signal 6",zmdc.pl,'-
"2022-04-19 10:22:00",zmdc,,272483,INF,"'zmc -m 2' crashed, signal 6",zmdc.pl,'-
"2022-04-19 10:22:00",zmdc,,288965,INF,"'zmc -m 3' started at 22/04/19 10:22:00",zmdc.pl,'-
"2022-04-19 10:22:00",zmdc,,272483,INF,"'zmc -m 3' starting at 22/04/19 10:22:00, pid = 288965",zmdc.pl,'-