November 28, 20232 yr Author 30 minutes ago, garydlb said: I am getting exactly the same after the last update Force update the docker container.
December 18, 20232 yr @dlandoncan you add notifications also for telegram? Something like this pip install python-telegram-bot ############################# from telegram import Bot, InputFile # Add the following function to send notifications to Telegram def send_telegram_notification(token, chat_id, message, image_path=None): bot = Bot(token) # Check if an image is provided if image_path: # Send photo along with the message with open(image_path, 'rb') as photo: bot.send_photo(chat_id, photo, caption=message) else: # Send only the message bot.send_message(chat_id, message) # Modify the section where you read parameters from secrets or set them manually if not param_dict['token'] or not param_dict['user']: # read from secrets secrets = read_secrets() if not param_dict['token']: param_dict['token'] = secrets.get('TELEGRAM_BOT_TOKEN') # Replace with your secret key zmlog.Debug(1, "eid:{} Reading token from secrets".format(eid)) if not param_dict['user']: param_dict['user'] = secrets.get('TELEGRAM_CHAT_ID') # Replace with your secret key zmlog.Debug(1, "eid:{} Reading user from secrets".format(eid)) # Replace the Pushover-specific code with the Telegram notification code param_dict['title'] = '{} Alarm ({})'.format(mname, eid) param_dict['message'] = cause + datetime.now().strftime(' at %I:%M %p, %b-%d') if event_type == 'event_end': param_dict['title'] = 'Ended:' + param_dict['title'] disp_param_dict = param_dict.copy() disp_param_dict['token'] = '<removed>' disp_param_dict['user'] = '<removed>' zmlog.Debug(1, "eid:{} Telegram payload: data={} files={}".format(eid, disp_param_dict, files)) send_telegram_notification(param_dict['token'], param_dict['user'], param_dict['message'], image_path) zmlog.close()
December 19, 20232 yr Author On 12/18/2023 at 8:18 AM, snoopy86 said: can you add notifications also for telegram? This is something that would be best added to Zoneminder itself. Ask the developers if it can be added.
January 9, 20242 yr Got a question, not sure where to ask, but since it pertains to Zoneminder I'll ask here... I have the Appdata Backup Plugin installed, and the plugin turns off the docker, backs it up, then turns it back on. Is the Zoneminder shutdown script/process safe even while it's recording an alarm? I have a lot of issues and db corruption at random points, and I have had to dump, drop, recreate and restore the zm database quite a few times, not sure what the cause is, but it started when I upgraded from 6.9.2 to 6.12.6... I know this got really bad when I left the NO_START_ZM set to 1 and since I have figured out it doesn't do a normal startup or shutdown, I have set it to 0 and this has "stopped for now" but want to make sure it is safe, otherwise I would skip it on the backup and manually back it up myself. Thanks in advance.
February 25, 20242 yr The latest Version, v1.36.33, has performance issues. Is there currently a way to roll back to an earlier version?
February 25, 20242 yr Author 42 minutes ago, Sforget said: The latest Version, v1.36.33, has performance issues. Is there currently a way to roll back to an earlier version? There is no way to roll back because the Zoneminder Docker Container always installs the latest version of Zoneminder. Try getting support for your issue at Zoneminder support.
April 15, 20242 yr @dlandoni'm getting this errors with the DB and the container does not work properly. Any ideas?
April 15, 20242 yr Author 2 hours ago, snoopy86 said: @dlandoni'm getting this errors with the DB and the container does not work properly. Any ideas? Try doing a force update to refresh the docker container.
April 29, 20242 yr Hello, I am trying to install this docker and get it to work with my TP-LINK c430 camera. This is my 1st time setting up CCTV so I am just experimenting with every setting. Now some weird thing happened. Here is the story. I was able to install the container and run it as network type: bridge. I was able to access its webUI and tweak camera(monitor) settings. Yet I was not abble to get it to connect to my camera. My bright idea was that maybe docker bridge is isolating the container from my external network thus I switched to Custom: br0 - This should expose the container to the network. Container worked fine. But no camera access same as before. Lots of tweaking and curisng TP-link for not using default ONVIF or webui ports later I found the correct URI for ONVIF and RTSP. Yay everything works - I see my camera and can record. Hello World! But then I had this bright idea: Wait... Maybe the problem was actually the URI and ports instead of the network type? Lets Test! Switched back to bridge... RIP... No more web UI... Now it redirects to my login screen. BUT WHY?! Found that in the advanced settings for container the WEB UI url was set to https://[IP]:[PORT:443]/zm instead of https://[IP]:[PORT:8443] for bridging the ports? Fine fixed that now. Still nothing... And this is where my ideas ended. I see this error in logs as well: These are my container settings: I realize I might be doing something stupid and completely unrelated to this container but maybe some one can spot what it is? Edited April 29, 20242 yr by Laov
May 18, 20242 yr Hey Dlandon, Is there a GPU enabled version of this anywhere? I've seen people talking about using passthrough to encode/decode etc, figured it might knock my CPU usage down a bit. There is mention in this topic but I don't seem to be able to find it anywhere
May 18, 20242 yr Author 5 hours ago, Addy said: Hey Dlandon, Is there a GPU enabled version of this anywhere? I've seen people talking about using passthrough to encode/decode etc, figured it might knock my CPU usage down a bit. There is mention in this topic but I don't seem to be able to find it anywhere I was working on a docker years ago, but gave it up as it ended up taking way too much time. Someone may have forked it, but I don't know.
May 23, 20242 yr Sorry, i couldn't find the answer to my problem in this thread. Problably iam just overseeing something since iam relativlely new to unraid: i installed Zoneminder. i chose an unassigned device as my data path (for testing its just a USB drive, which will later be replaced by something stable). The "data folders" are created in the USB drive. here is my problem: When i open the WEB GUI some symbols are not shown: the logs in zoneminder look like this: If i install Zoneminder in default settings, the symbols show normal. What am i missing? Thank you in advance!
May 24, 20242 yr regarding my question above: i found this in the Zoneminder forum. i think this might be the solution, but since my linux knowledge is limited unfortunately, iam not not sure how to translate this to my setup
September 3, 20241 yr On 4/29/2024 at 5:48 PM, Laov said: Hello, I am trying to install this docker and get it to work with my TP-LINK c430 camera. This is my 1st time setting up CCTV so I am just experimenting with every setting. Now some weird thing happened. Here is the story. I was able to install the container and run it as network type: bridge. I was able to access its webUI and tweak camera(monitor) settings. Yet I was not abble to get it to connect to my camera. My bright idea was that maybe docker bridge is isolating the container from my external network thus I switched to Custom: br0 - This should expose the container to the network. Container worked fine. But no camera access same as before. Lots of tweaking and curisng TP-link for not using default ONVIF or webui ports later I found the correct URI for ONVIF and RTSP. Yay everything works - I see my camera and can record. Hello World! But then I had this bright idea: Wait... Maybe the problem was actually the URI and ports instead of the network type? Lets Test! Switched back to bridge... RIP... No more web UI... Now it redirects to my login screen. BUT WHY?! Found that in the advanced settings for container the WEB UI url was set to https://[IP]:[PORT:443]/zm instead of https://[IP]:[PORT:8443] for bridging the ports? Fine fixed that now. Still nothing... And this is where my ideas ended. I see this error in logs as well: These are my container settings: I realize I might be doing something stupid and completely unrelated to this container but maybe some one can spot what it is? Exact the same problem here, can anybody Help us (Reinstall runs into the same Problem) Change ports does not help
September 3, 20241 yr Author 20 minutes ago, MatixOne said: Exact the same problem here, can anybody Help us (Reinstall runs into the same Problem) Change ports does not help Use Bridge mode for networking and the URL is https://IP:8443/zm. The /zm is required. Port 443 is probably already used on your system. That's why the Docker Container changes it to 8443. Make sure 8443 is not used by another Docker Container.
November 5, 20241 yr On 5/18/2024 at 1:39 AM, Addy said: Is there a GPU enabled version of this anywhere? I've seen people talking about using passthrough to encode/decode etc, figured it might knock my CPU usage down a bit. There is mention in this topic but I don't seem to be able to find it anywhere I got iGPU enabled, for intel/vaapi. Personally I don't have much need for it, as I write only alarms via camera passthrough; encoding just puts more load on the server. But if someone has a need for it, below may help you enable it. Note when the docker image is updated your changes will be overwritten and you'll have to do this again so you may consider disabling auto updates for Zoneminder if you're going to use this. This assumes you have all the i915 gpu bits in place on your host server (check with lsmod | grep i915 or confirm /dev/dri/renderD128 is there) First, edit Docker->Zoneminder to add a device with value /dev/dri Then open console for Zoneminder and run these commands (this is what worked for me and your mileage may vary): apt install -y vainfo apt install -y intel-media-va-driver-non-free groupadd -g 110 render usermod -a -G video www-data usermod -a -G render www-data check to see if it works with: vainfo Then configure your cameras in Zoneminder under Source: DecoderHWAccelName : vaapi DecoderHWAccelDevice : /dev/dri/renderD128 Then under Storage: Video Writer: Encode and pick your flavor of vaapi encoding.
November 11, 20241 yr So i'm getting this, even after a force update. Quote Starting services... * Starting Apache httpd web server apache2 * * Stopping MariaDB database server mysqld ...done. * Starting MariaDB database server mysqld ...fail! Nov 11 17:23:12 ec7cfa545f99 zmupdate[25080]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] Nov 11 17:23:12 ec7cfa545f99 zmupdate[25080]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] i was having problems before this but it brought down my unraid server, thankfully the server is fine now but the DB is corrupt. How can i tell if the DB is local or if its on my instance of MariaDB? I looked at the databases on my Maria install and dont see any db there that could be zoneminder. I do have backups of the appdata folder. Can i rebuild? Or worst case, can i export/save my settings for a reinstall?
December 12, 20241 yr Is there an option to add a variable to take advance of a GPU card for zoneminder container (similar to what Plex has ?)
December 12, 20241 yr Author 25 minutes ago, abidu99 said: Is there an option to add a variable to take advance of a GPU card for zoneminder container (similar to what Plex has ?) Yes, add a Device:
December 21, 20241 yr i have the same problem. deleted docker / image, but problem remains: * Starting Apache httpd web server apache2 * * Stopping MariaDB database server mysqld ...done. * Starting MariaDB database server mysqld ...fail! DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. Unable to connect to DB. ZM Cannot continue. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 150. Compilation failed in require at /usr/bin/zmupdate.pl line 74. BEGIN failed--compilation aborted at /usr/bin/zmupdate.pl line 74. Dec 21 19:42:45 65425e020f89 zmupdate[12715]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] Dec 21 19:42:45 65425e020f89 zmupdate[12715]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. Unable to connect to DB. ZM Cannot continue. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 150. Compilation failed in require at /usr/bin/zmupdate.pl line 74. BEGIN failed--compilation aborted at /usr/bin/zmupdate.pl line 74. Dec 21 19:42:45 65425e020f89 zmupdate[12716]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] Dec 21 19:42:45 65425e020f89 zmupdate[12716]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] best regards
January 7, 20251 yr On 12/21/2024 at 7:45 PM, pika said: i have the same problem. deleted docker / image, but problem remains: * Starting Apache httpd web server apache2 * * Stopping MariaDB database server mysqld ...done. * Starting MariaDB database server mysqld ...fail! DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. Unable to connect to DB. ZM Cannot continue. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 150. Compilation failed in require at /usr/bin/zmupdate.pl line 74. BEGIN failed--compilation aborted at /usr/bin/zmupdate.pl line 74. Dec 21 19:42:45 65425e020f89 zmupdate[12715]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] Dec 21 19:42:45 65425e020f89 zmupdate[12715]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. Unable to connect to DB. ZM Cannot continue. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 150. Compilation failed in require at /usr/bin/zmupdate.pl line 74. BEGIN failed--compilation aborted at /usr/bin/zmupdate.pl line 74. Dec 21 19:42:45 65425e020f89 zmupdate[12716]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] Dec 21 19:42:45 65425e020f89 zmupdate[12716]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] best regards Got the same problem over here. Tried force update and removing the container + image, no dice. Edited January 7, 20251 yr by SolidFyre
January 7, 20251 yr For both of you mysql is failing to start for some reason. If you follow the instructions here and try and start mysql manually it should hopefully give you more info on why it isn't starting.
January 8, 20251 yr root@be13dde773f2:/# service mysql start * Starting MariaDB database server mysqld [fail] root@be13dde773f2:/# service zoneminder start Starting ZoneMinder: DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. 01/08/25 22:11:45.513210 zmpkg[16605].ERR [ZoneMinder::Database:114] [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] 01/08/25 22:11:45.513415 zmpkg[16605].ERR [ZoneMinder::Database:114] [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. 01/08/25 22:11:45.513804 zmpkg[16605].ERR [ZoneMinder::Database:114] [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] Unable to connect to DB. ZM Cannot continue. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 150. Compilation failed in require at /usr/share/perl5/ZoneMinder.pm line 33. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder.pm line 33. Compilation failed in require at /usr/bin/zmpkg.pl line 34. BEGIN failed--compilation aborted at /usr/bin/zmpkg.pl line 34. ZoneMinder failed to start root@be13dde773f2:/# that's it.
January 9, 20251 yr On 1/7/2025 at 5:30 PM, Phoenix26 said: For both of you mysql is failing to start for some reason. If you follow the instructions here and try and start mysql manually it should hopefully give you more info on why it isn't starting. On 1/8/2025 at 10:12 PM, pika said: root@be13dde773f2:/# service mysql start * Starting MariaDB database server mysqld [fail] root@be13dde773f2:/# service zoneminder start Starting ZoneMinder: DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. 01/08/25 22:11:45.513210 zmpkg[16605].ERR [ZoneMinder::Database:114] [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] 01/08/25 22:11:45.513415 zmpkg[16605].ERR [ZoneMinder::Database:114] [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. 01/08/25 22:11:45.513804 zmpkg[16605].ERR [ZoneMinder::Database:114] [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] Unable to connect to DB. ZM Cannot continue. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 150. Compilation failed in require at /usr/share/perl5/ZoneMinder.pm line 33. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder.pm line 33. Compilation failed in require at /usr/bin/zmpkg.pl line 34. BEGIN failed--compilation aborted at /usr/bin/zmpkg.pl line 34. ZoneMinder failed to start root@be13dde773f2:/# that's it. So, it appears lots of tables in InnoDB got corrupted somehow. I found clues in /var/log/mysql/error.log I tried to force an InnoDB recovery but never got it to work. Instead I bypassed InnoDB by skipping it using "skip-innodb" and "default-storage-engine = myisam" under [mysqld] in my.cf and mysql finally starts, however, is seems ZoneMinder is reliant on InnoDB and wont start because of it. I guess it's possible to do a backup now since mysql is started, but I will instead just try and delete the whole thing and reinstall from scratch since my ZM install isn't that big. Edit: My issue is solved. I deleted /appdata/ZoneMinder/mysql in the docker image and redeployed and now everything starts fine. Edited January 10, 20251 yr by SolidFyre
January 24, 20251 yr Hello! i went today to pull some footage from zoneminder however the web ui does not load, if i remove the /zm apache shows its running there are no updates so its on the latest version upon checking the logs i see the below error if i move the mysql folder from the appdata, then let it rebuild it again zm webui works however it does not have any config for the cameras,events, schedule etc it is still recording the events when i browse to the folders manually, however it would be nice to have the ui working again is there a way to repair the telemtry server via shell or file editing? cheers! Jan 24 19:11:08 0042f633213e syslog-ng[20]: syslog-ng starting up; version='3.25.1' Performing updates... Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease Hit:4 http://ppa.launchpad.net/iconnor/zoneminder-1.36/ubuntu focal InRelease Hit:5 http://ppa.launchpad.net/ondrej/apache2/ubuntu focal InRelease Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease Hit:7 http://security.ubuntu.com/ubuntu focal-security InRelease 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... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Using existing keys in "/config/keys" Using existing conf folder File zm.conf already copied File zmeventnotification.ini already moved File secrets.ini already moved Event notification server already moved Pushover api already moved Using existing ssmtp folder Using existing mysql database folder Copy /config/control/ scripts to /usr/share/perl5/ZoneMinder/Control/ Copy /config/conf/ scripts to /etc/zm/conf.d/ 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 Using existing data directory for cache Starting services... * Starting Apache httpd web server apache2 * * Stopping MariaDB database server mysqld ...done. * Starting MariaDB database server mysqld ...done. Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[892]: Upgrading MySQL tables if necessary. Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[898]: Looking for 'mysql' as: /usr/bin/mysql Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[898]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[898]: This installation of MariaDB is already upgraded to 10.3.39-MariaDB. Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[898]: There is no need to run mysql_upgrade again for 10.3.39-MariaDB. Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[898]: You can use --force if you still want to run mysql_upgrade Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[905]: Checking for insecure root accounts. Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[909]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Initiating database upgrade to version 1.36.35 from version 1.36.35 Upgrading database to version 1.36.35 Database upgrade to version 1.36.35 successful. Freshening configuration in database Migratings passwords, if any... Loading config from DB 227 entries Saving config to DB 227 entries Starting ZoneMinder: ZoneMinder started successfully Jan 24 19:11:35 0042f633213e cron[1043]: (CRON) INFO (pidfile fd = 3) Jan 24 19:11:35 0042f633213e cron[1043]: (CRON) INFO (Skipping @reboot jobs -- not system startup) Jan 24 19:11:36 0042f633213e zmtelemetry[1030]: WAR [Telemetry server returned HTTP POST error code: 301] Jan 24 19:11:36 0042f633213e zmc_m1[994]: WAR [zmc_m1] [Monitor dimensions are 2560x1440 but camera is sending 4608x1728] Jan 24 19:17:01 0042f633213e CRON[1061]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
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.