[support] dlandon - Zoneminder 1.36

[dlandon]

27 minutes ago, tucansam said:

Docker -> ZM Icon -> "WebGUI"

 

Also tried directly inputting the URL and port, both http and https

 

No change, does not work.  Same error.

Look at the docker container log and see if there are any errors.

 

Did you make any changes to the docker container template?

[tucansam]

Got it working, not sure how.

 

But MAN, this is WAY more complicated than it was a decade ago when I ran an old version on an old linux.  I have no idea how to begin doing this.  I've managed to set up the source, an can see it.  The camera itself handles motion detection, and films in 30s clips, which is fine.  I literally just need the camera to write videos to my unraid server instead of the SD card in it.  Nothing more complicated than that.  

[turt1e]

If anyone is trying to get this Zoneminder docker working with the Nginx Proxy Manager docker instead of the SWAG docker below is the important config that needs to be added to the advanced tab when creating a new proxy host.

 

 location = / {
    rewrite ^ https://zm.mydomain.com/zm/ permanent;
}

 

That tidbit above makes Zoneminder pesky use of the trailing /zm in the URL work with Nginx Proxy Manager. Pay particular care to make sure the ending"/" in  https://zm.mydomain.com/zm/ is present because https://zm.mydomain.com/zm does not work for me.

Edited February 2, 2023 by turt1e

[Nano]

Anyone managed to get ZMNINJA event server working - Got it saying connected in App and I can see via console it can see and send an event when I manually start an alarm but nothing is showing on the APP/Phone. Any tips!?

 

I can see the Console is saying the following, Is this a setting im missing? 

 

I feel like im close @dlandon can you comment on the last bit here 

 

No rules found for Monitor, allowing:2. - is this something basic im missing???

 

BG-2:2023-02-05,22:04:47 PARENT: checkEvents() new events found=1
DBG-2:2023-02-05,22:04:47 PARENT: There are 1 new Events to process
DBG-2:2023-02-05,22:04:47 PARENT: ---------->Tick END (active forks:1, total forks:1, active hooks: 0)<--------------
DBG-1:2023-02-05,22:04:47 PARENT: Forked process:1281 to handle alarm eid:38
INF:2023-02-05,22:04:47 |----> FORK:Front Porch 1080 (2), eid:38 use hooks/start hook not being used, going to directly send out a notification if checks pass
02/05/23 22:04:47.266417 zmeventnotification[1281].INF [main:1044] [|----> FORK:Front Porch 1080 (2), eid:38 use hooks/start hook not being used, going to directly send out a notification if checks pass]
DBG-2:2023-02-05,22:04:49 |----> FORK:Front Porch 1080 (2), eid:38 rules: Checking rules for alarm caused by eid:38, monitor:2, at: Sun Feb  5 22:04:49 2023 with cause:Forced Web
DBG-1:2023-02-05,22:04:49 |----> FORK:Front Porch 1080 (2), eid:38 rules: No rules found for Monitor, allowing:2
DBG-1:2023-02-05,22:04:49 |----> FORK:Front Porch 1080 (2), eid:38 Matching alarm to connection rules...

Edited February 5, 2023 by Nano

[grants169]

My setup is a 250 GB disk dedicated to ZM.  I save events until the disk is 85% full and it purges the oldest.  Been doing this for years, moving it from an old bare metal server to unraid.  The disk holds roughly 300,000 events using 7 cameras.  Basically overkill as I rarely go back in time the 4 months of events that it holds.  But, my problem is I can't go back in time if I'm trying to query about 60,000 events from the console.  From the console, clicking on "events" with a camera with 40k events, they pop up just fine.  Other cameras with 60k events all I'm presented with is a message "Loading, please wait..." and nothing more happens; it's the same thing with all 3 cameras I have with greater than 60k events.  Clicking on the total events, with 300k, it's obviously the same thing.

 

My thinking it's some limitation with mysql, but there's nothing in error logs and I'm not sure what I can do to increase the number of events that can be queried.  My old server was able to do it just fine with what was essentially a stock ZM install, using the same 250GB hard disk and I don't recall modifying mysql outside of what ZM requires... Any thoughts?

[grants169]

On 2/9/2023 at 3:29 PM, grants169 said:

My setup is a 250 GB disk dedicated to ZM.  I save events until the disk is 85% full and it purges the oldest.  Been doing this for years, moving it from an old bare metal server to unraid.  The disk holds roughly 300,000 events using 7 cameras.  Basically overkill as I rarely go back in time the 4 months of events that it holds.  But, my problem is I can't go back in time if I'm trying to query about 60,000 events from the console.  From the console, clicking on "events" with a camera with 40k events, they pop up just fine.  Other cameras with 60k events all I'm presented with is a message "Loading, please wait..." and nothing more happens; it's the same thing with all 3 cameras I have with greater than 60k events.  Clicking on the total events, with 300k, it's obviously the same thing.

 

My thinking it's some limitation with mysql, but there's nothing in error logs and I'm not sure what I can do to increase the number of events that can be queried.  My old server was able to do it just fine with what was essentially a stock ZM install, using the same 250GB hard disk and I don't recall modifying mysql outside of what ZM requires... Any thoughts?

 

Found the culprit.  In case anyone else has the "Loading, please wait.." message after attempting to load a large dataset (camera with a lot of events), the fix is to log on to console and increase memory limit from 'memory_limit = 128M' to something like 512M in /etc/php/7.4/apache2/php.ini. 

[drx]

Good Afternoon! I just updated my zoneminder docker and now I am getting permission denied errors, and I am not sure what changed within the docker to affect permissions. I am still on 6.9.2, and I know that 6.10 and up introduced docker permission issues. Im curious if that is the issue here. Does any of this make sense to anyone?

 

Quote

Mar 6 13:39:30 77963088ba6b zmu[1155]: ERR [zmu] [Can't open memory map file /dev/shm/zm.mmap.1: No such file or directory]
Mar 6 13:39:30 77963088ba6b zmu[1155]: ERR [zmu] [Can't connect to capture daemon: 1 Front Door]
Mar 6 13:39:30 77963088ba6b zmu[1155]: ERR [zmu] [Can't run query INSERT INTO `Logs` ( `TimeKey`, `Component`, `ServerId`, `Pid`, `Level`, `Code`, `Message`, `File`, `Line` ) VALUES ( 1678131570.099178, 'zmu', 0, 1155, -2, 'ERR', 'Can\'t open memory map file /dev/shm/zm.mmap.1: No such file or directory', 'zm_monitor.cpp', 927 ): Lost connection to MySQL server during query]
Mar 6 13:39:30 77963088ba6b zmu[1155]: ERR [zmu] [Can't run query INSERT INTO `Logs` ( `TimeKey`, `Component`, `ServerId`, `Pid`, `Level`, `Code`, `Message`, `File`, `Line` ) VALUES ( 1678131570.099343, 'zmu', 0, 1155, -2, 'ERR', 'Can\'t connect to capture daemon: 1 Front Door', 'zmu.cpp', 512 ): Lost connection to MySQL server during query]
Mar 6 13:39:30 77963088ba6b zms[1201]: ERR [zms] [fopen() for ./zms.log, error = Permission denied]

 

 

EDIT: So, since I was getting permission denied, I went ahead and let the docker run with privilege to see how it would respond, and now I am getting this

 

DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/ZoneMinder/Logger.pm line 627.

DBD::mysql::st execute failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/bin/zmpkg.pl line 325.

Mar 6 14:40:29 713ba0e3f727 zmpkg[1108]: ERR [Can't execute log entry 'INSERT INTO Logs ( TimeKey, Component, ServerId, Pid, Level, Code, Message, File, Line ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, NULL )': Lost connection to MySQL server during query]
Mar 6 14:40:29 713ba0e3f727 zmpkg[1108]: FAT [Can't execute: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)]
ZoneMinder failed to start


*** /etc/my_init.d/40_firstrun.sh failed with status 255

 

Edited March 6, 2023 by drx

[drx]

Sorry, just got back from dinner and was able to do some more testing. I set the env variable "NO_START_ZM="1"", then started the MySQL server and it was fine. When I start zoneminder I get an error:

 

execute failed: Lost connection to MySQL server during query at /usr/share/perl5/ZoneMinder/Logger.pm line 627.

and

execute failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/bin/zmpkg.pl line 325.

 

So, I went to those lines and this is what they say:

 

Logger.pm Line 610-634

 

 610       my $sql = 'INSERT INTO Logs ( TimeKey, Component, ServerId, Pid, Level, Code, Message, File, Line ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, NULL )';
    611       $this->{sth} = $ZoneMinder::Database::dbh->prepare_cached($sql) if ! $this->{sth};
    612       if ( !$this->{sth} ) {
    613         $this->{databaseLevel} = NOLOG;
    614         Error("Can't prepare log entry '$sql': ".$ZoneMinder::Database::dbh->errstr());
    615         return;
    616       }
    617
    618       my $res = $this->{sth}->execute(
    619         $seconds+($microseconds/1000000.0),
    620            $this->{id},
    621            ($ZoneMinder::Config::Config{ZM_SERVER_ID} ? $ZoneMinder::Config::Config{ZM_SERVER_ID} : undef),
    622            $$,
    623            $level,
    624            $codes{$level},
    625            $string,
    626            $this->{fileName},
    627           );
    628       if ( !$res ) {
    629         $this->{databaseLevel} = NOLOG;
    630         Error("Can't execute log entry '$sql': ".$ZoneMinder::Database::dbh->errstr());
    631       }
    632     } # end if doing db logging
    633   } # end if level < effectivelevel
    634 }

 

zmpkg.pl

 

  320 
    321 # PP - First, make sure default exists and there is only one
    322   my $sql = 'SELECT `Name` FROM `States` WHERE `Name`=?';
    323   my $sth = $dbh->prepare_cached($sql)
    324     or Fatal("Can't prepare '$sql': ".$dbh->errstr());
    325   my $res = $sth->execute('default')
    326     or Fatal("Can't execute: ".$sth->errstr());
    327 

 

 

I am not sure what these lines are telling me, this is above my head unfortunately

 

[dlandon]

16 hours ago, drx said:

Good Afternoon! I just updated my zoneminder docker and now I am getting permission denied errors, and I am not sure what changed within the docker to affect permissions

Nothing in the update affected permissions.  You should restore your appdata from a backup.

[tvd1]

For what its worth, I woke up and found my Zoneminder docker was stopped.  I tried to restart and watched the logs and it kept restarting, many database errors. I have restored to a backup but looks like theres an issue with the update. I would recommend people holding off until this is addressed. Unfortunately, I didnt capture the errors before restoring. 

[dlandon]

4 hours ago, tvd1 said:

For what its worth, I woke up and found my Zoneminder docker was stopped.  I tried to restart and watched the logs and it kept restarting, many database errors. I have restored to a backup but looks like theres an issue with the update. I would recommend people holding off until this is addressed. Unfortunately, I didnt capture the errors before restoring. 

Force an update to the docker.

[MrLinux]

How do I change the path from https://1.2.3.4/zm to https://1.2.3.4 ?

[dlandon]

On 4/24/2023 at 4:36 AM, MrLinux said:

How do I change the path from https://1.2.3.4/zm to https://1.2.3.4 ?

You can't.

[mcraidy]

Just noticed and installed the latest upgrade and now get the same error when trying to manually start zoneminder.

 

root@5f53b929773d:/# service zoneminder start
Starting ZoneMinder:
05/08/23 12:05:00.692778 zmpkg[1515].INF [main:318] [Sanity checking States table...]
DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/ZoneMinder/Logger.pm line 627.
05/08/23 12:05:00.757360 zmpkg[1515].ERR [ZoneMinder::Logger:630] [Can't execute log entry 'INSERT INTO Logs ( TimeKey, Component, ServerId, Pid, Level, Code, Message, File, Line ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, NULL )': Lost connection to MySQL server during query]
DBD::mysql::st execute failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/bin/zmpkg.pl line 325.
05/08/23 12:05:00.757747 zmpkg[1515].FAT [main:325] [Can't execute: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)]
ZoneMinder failed to start

root@5f53b929773d:/# 

 

DB starts fine and I can connect successfully from the CLI using the credentials in /etc/zm/zm.conf

I'll try take a better look later this evening, but FYI the latest update seems to do something funky

 

Edited May 8, 2023 by mcraidy

[dlandon]

There were no changes in the latest Zoneminder container.  It was to catch up the Ubuntu updates and refresh the docker container.

 

That problem normally happens with database issues.  I've kept up with all the updates on my own Zoneminder and never had an issue with the DB.  Restore the database from a backup and see if it doesn't fix it.

[mcraidy]

Thanks - interestingly just tried a mysqldump and got

mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `Logs` at row: 130429

 

There seemed to be something weird in the Logs table so I truncated the table.... service starts again.

 

[mcraidy]

On 4/24/2023 at 9:36 PM, MrLinux said:

How do I change the path from https://1.2.3.4/zm to https://1.2.3.4 ?

 

I set up a redirect from / to /zm via Nginx Proxy Manager - added the following to advanced config

location = / {
    return 301 https://cctv.home.local.dom/zm/;
}

 

[DaFr0n]

I'm having similar issues with Zoneminder not starting:

 

root@30404418888a:/# service mysql start
 * Starting MariaDB database server mysqld                                                                                                 [ OK ] 
root@30404418888a:/# service zoneminder start
Starting ZoneMinder:
06/24/23 10:38:06.166412 zmpkg[22796].INF [main:318] [Sanity checking States table...]
DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/ZoneMinder/Logger.pm line 627.
06/24/23 10:38:06.234656 zmpkg[22796].ERR [ZoneMinder::Logger:630] [Can't execute log entry 'INSERT INTO Logs ( TimeKey, Component, ServerId, Pid, Level, Code, Message, File, Line ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, NULL )': Lost connection to MySQL server during query]
DBD::mysql::st execute failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/bin/zmpkg.pl line 325.
06/24/23 10:38:06.234864 zmpkg[22796].FAT [main:325] [Can't execute: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)]
ZoneMinder failed to start

[kysdaddy]

Hello, I have been running ZM for several years in Unraid docker. My home system works great no issues at all right now. I have a system that is located remotely in another state that is killing me. I recently lost a hard drive and had to travel to replace it. While onsite, I replaced some cameras and updated the ZM and Unraid systems. Unfortunately, once I updated ZM, the next am, it tossed the SQL error "[Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]"and would not start. I have had to deal with the SQL failure in the past on my home system so I simply deleted and rebuilt "Bad Move" the system keeps maxing out ram and CPU on my system. All of the options are the same on both of my systems, I could have messed something up but I have double and tripple checked and I can not find a vatiance.  I have battled through and cleared all of the errors that I see in the logs, I see very little color in the logs , every now and then I get a warning but most log entries are "[L25-L24-K100: 2800 - Capturing at 9.75 fps, capturing bandwidth 73063bytes/sec Analysing at 0.00 fps]"

Even when the cpu and the ram are maxed out the logs clean.

I start at 18% gpu and 18% ram, the ram starts increasing and stabilizes at 26% for quite a while then starts growing again until in about an hour it hits 95% and freezes up.

 

I see this in the logs but assume that this is normal. "Jun 26 21:16:15 86da4b3382f5 zmc_m28[1181]: INF [zmc_m28] [Trailer Parking lot S111: 9054 - Closing event 12680, section end forced 1687828575 - 1687827670 = 905 >= 300]

Jun 26 21:16:15 86da4b3382f5 zmc_m28[1181]: INF [zmc_m28] [some options not used, turn on debugging for a list.]

 

I am at a complete loss as to what the problem is or how to fix it.

 

Also, I have developed a defense against the SQL issue but I assume that there is a better solution. I currently turn of the docker, copy the zoneminder appdata folder and save it to a storage folder, when the machine tosses the SQL error I copy the zoneminder folder back to the appdata folder. I still lose access to all of the data between when I copied and when I restore it. Is there a better way? Is there a way to save a camera configuration file by itself? I am attaching the diagnostics from the unraid server, not sure if that will help.

 

Chas

tower-diagnostics-20230626-2130.zip

[Brianara3]

I'm having an issue starting this docker. Brand new install never run before and the mysql server won't start. I get the following errors in the mysql error.log. I have verified permissions in the container and the mysql data directories are full r/w to the mysql user and group. I have tried running the container with privileged option and get same result. I have also tried completely removing the container and appdata directories and reinstalling with no change.

 

Quote

2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=292] log sequence number 2631023 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=415] log sequence number 2631023 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=293] log sequence number 2631067 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=416] log sequence number 2631067 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=294] log sequence number 2631111 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=417] log sequence number 2631111 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=295] log sequence number 2631155 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=418] log sequence number 2631155 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=296] log sequence number 2631215 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=419] log sequence number 2631215 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=297] log sequence number 2631259 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=420] log sequence number 2631259 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=298] log sequence number 2631303 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=421] log sequence number 2631303 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=299] log sequence number 2631347 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=422] log sequence number 2631347 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=300] log sequence number 2631391 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=423] log sequence number 2631391 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=0] log sequence number 2630847 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=8] log sequence number 2104786 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=10] log sequence number 1887967 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=342] log sequence number 1887967 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=12] log sequence number 2104683 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=307] log sequence number 2104724 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=302] log sequence number 2104582 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=303] log sequence number 2101620 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=304] log sequence number 2101672 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=308] log sequence number 2104663 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=305] log sequence number 2104541 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-10-03 23:24:24 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-10-03 23:24:24 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2023-10-03 23:24:24 0 [Note] InnoDB: Waiting for purge to start
2023-10-03 23:24:24 1 [ERROR] InnoDB: Page [page id: space=0, page number=9] log sequence number 2096755 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Page [page id: space=19, page number=0] log sequence number 1827003 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Page [page id: space=0, page number=343] log sequence number 1897590 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Page [page id: space=19, page number=3] log sequence number 2645762 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Page [page id: space=19, page number=1] log sequence number 1825915 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 1878936 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 1878936 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 2643677 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 3 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 2643361 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 2 [ERROR] InnoDB: Page [page id: space=5, page number=0] log sequence number 2595289 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 2 [ERROR] InnoDB: Page [page id: space=5, page number=3] log sequence number 2622397 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 2 [ERROR] InnoDB: Page [page id: space=5, page number=14] log sequence number 2635616 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 3 [ERROR] InnoDB: Page [page id: space=5, page number=12] log sequence number 2637396 is in the future! Current system log sequence number 1626133.
2023-10-03 23:24:24 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-10-03 23:24:24 0 [Note] InnoDB: 10.3.38 started; log sequence number 1626124; transaction id 1101
2023-10-03 23:24:24 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql//ib_buffer_pool
2023-10-03 23:24:24 0 [Note] InnoDB: Cannot open '/var/lib/mysql//ib_buffer_pool' for reading: Permission denied
2023-10-03 23:24:24 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-10-03 23:24:24 0 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables
2023-10-03 23:24:24 0 [ERROR] Aborting

2023-10-03 23:24:24 0 [ERROR] InnoDB: Cannot open '/var/lib/mysql//ib_buffer_pool.incomplete' for writing: Permission denied
Warning: Memory not freed: 520
231003 23:24:26 mysqld_safe mysqld from pid file /run/mysqld/mysqld.pid ended
root@46711921fcdd:/config# mysqlcheck --all-databases
mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) when trying to connect

 

Edited October 4, 2023 by Brianara3

[dlandon]

8 hours ago, Brianara3 said:

I'm having an issue starting this docker. Brand new install never run before and the mysql server won't start. I get the following errors in the mysql error.log. I have verified permissions in the container and the mysql data directories are full r/w to the mysql user and group. I have tried running the container with privileged option and get same result. I have also tried completely removing the container and appdata directories and reinstalling with no change.

Remove the docker and then add it back.  At the bottom of the template click on 'Show more settings'  Confirm that the appdata mappings make sense for your system.

[Siruscool]

Hi all,

 

is it possible to get Nvidia GPU support for that container under unraid?

 

I have installed the Nvidia driver package on my Unraid server --- ok

 

I have passthrough my Nvidia card to the docker container.

 

The card is visible / available inside the container but when i compile opencv i get the message --- please download CUDA_PIN

 

What does it mean? 

 

I use the ---dlandon/zoneminder.machine.learning--- image for my test.

 

Thanks guys for help!

 

 

Edited October 20, 2023 by Siruscool

[tvd1]

Have had zoneminder working for months, no major changes in performance.  Had to restart my docker today as something spiked RAM.  Everything came up clean aside from ZM.  No new version was installed or any major updates.  I can connect to the DB via command line.  Any thoughts?

 

Starting services...
 * Starting Apache httpd web server apache2
 * 
 * Stopping MariaDB database server mysqld
   ...done.
 * Starting MariaDB database server mysqld
   ...fail!
Nov 26 22:04:47 9be1460457ca zmupdate[1149]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Nov 26 22:04:47 9be1460457ca zmupdate[1149]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Nov 26 22:04:47 9be1460457ca zmupdate[1150]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Nov 26 22:04:47 9be1460457ca zmupdate[1150]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Starting ZoneMinder:
Nov 26 22:04:57 9be1460457ca zmpkg[1161]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Nov 26 22:04:57 9be1460457ca zmpkg[1161]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
ZoneMinder failed to start

 

 

 

Edited November 27, 2023 by tvd1
new info

[garydlb]

On 11/27/2023 at 3:26 AM, tvd1 said:

Have had zoneminder working for months, no major changes in performance.  Had to restart my docker today as something spiked RAM.  Everything came up clean aside from ZM.  No new version was installed or any major updates.  I can connect to the DB via command line.  Any thoughts?

 

Starting services...
 * Starting Apache httpd web server apache2
 * 
 * Stopping MariaDB database server mysqld
   ...done.
 * Starting MariaDB database server mysqld
   ...fail!
Nov 26 22:04:47 9be1460457ca zmupdate[1149]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Nov 26 22:04:47 9be1460457ca zmupdate[1149]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Nov 26 22:04:47 9be1460457ca zmupdate[1150]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Nov 26 22:04:47 9be1460457ca zmupdate[1150]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Starting ZoneMinder:
Nov 26 22:04:57 9be1460457ca zmpkg[1161]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Nov 26 22:04:57 9be1460457ca zmpkg[1161]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
ZoneMinder failed to start

 

 

 

I am getting exactly the same after the last update

 

[dlandon]

On 11/26/2023 at 9:26 PM, tvd1 said:

Have had zoneminder working for months, no major changes in performance.  Had to restart my docker today as something spiked RAM.  Everything came up clean aside from ZM.  No new version was installed or any major updates.  I can connect to the DB via command line.  Any thoughts?

 

Starting services...
 * Starting Apache httpd web server apache2
 * 
 * Stopping MariaDB database server mysqld
   ...done.
 * Starting MariaDB database server mysqld
   ...fail!
Nov 26 22:04:47 9be1460457ca zmupdate[1149]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Nov 26 22:04:47 9be1460457ca zmupdate[1149]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Nov 26 22:04:47 9be1460457ca zmupdate[1150]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Nov 26 22:04:47 9be1460457ca zmupdate[1150]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Starting ZoneMinder:
Nov 26 22:04:57 9be1460457ca zmpkg[1161]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Nov 26 22:04:57 9be1460457ca zmpkg[1161]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
ZoneMinder failed to start

 

 

 

Force udate the docker container.