DaFr0n Posted November 12, 2021 Share Posted November 12, 2021 5 hours ago, dlandon said: Remove the Docker container and delete the /appdata/Zoneminder folder and start over. Hi dlandon Tried that still the same error, deleted Docker, template and appdata/zoneminder folder same error occurs Quote Link to comment
dlandon Posted November 12, 2021 Author Share Posted November 12, 2021 4 hours ago, DaFr0n said: Hi dlandon Tried that still the same error, deleted Docker, template and appdata/zoneminder folder same error occurs Are you using an external database? If not, you haven’t removed the /app data/zoneminder folder completely. Quote Link to comment
DaFr0n Posted November 12, 2021 Share Posted November 12, 2021 5 hours ago, dlandon said: Are you using an external database? If not, you haven’t removed the /app data/zoneminder folder completely. Database is default, data is set as per my disk share. /mnt/user/appdata does not have a zoneminder folder, this was deleted. Quote Link to comment
dlandon Posted November 12, 2021 Author Share Posted November 12, 2021 8 minutes ago, DaFr0n said: Database is default, data is set as per my disk share. /mnt/user/appdata does not have a zoneminder folder, this was deleted. Check your path assignments. Zoneminder seems to be finding a previous database. Quote Link to comment
dlandon Posted November 12, 2021 Author Share Posted November 12, 2021 Just added a fresh Zoneminder to my test server and it worked fine. Quote Link to comment
dlandon Posted November 12, 2021 Author Share Posted November 12, 2021 When you delete the container, be sure to remove the image also. Quote Link to comment
DaFr0n Posted November 12, 2021 Share Posted November 12, 2021 Job sorted, brilliant. Its now up and running without the user shares being automatically created. Thanks again 😀 Quote Link to comment
MorgothCreator Posted November 28, 2021 Share Posted November 28, 2021 (edited) Someone know why zoneminder create several event directory when begin a new video all under 1MB with the timesize from 2 seconds to sometime 2 hours that is a still image with up to 2 seconds moving image at the end, only the marked directory from the below print screen have the one hour length as I set it, but sometime the video is only 15 minutes, other times is 2 hour, the rest have the same 2 seconds to 2 hour video for each hour under 1MB in size, sometime only artefacts, the directory for that date is full of such kind of event folders, at each good video 10-20 event directory's are under 1MB video. I disabled detection on Mocord, I enable it and the same result, on other modes is more than a mess, no one can distinguish what is doing The machine is an Intel 7700 with 16GB RAM, storing on a 3TB WD HDD total RAM usage about 31%, the setup is No encoding/pass thru, minimum buffer 3 maximum 20, with decoding for monitoring, cameras setup to output 10FPS's at 1080p h264, 8 cameras + one that is h265AI because has no h264 option pass thru as well. This issue appeared in about last two updates, I used the same cameras in older versions and no issue like that encountered, only that last several releases after each update the database is corrupted and need a fresh reinstall. The Unraid version is: 6.9.2 stable Edited November 28, 2021 by MorgothCreator Quote Link to comment
blaine07 Posted December 26, 2021 Share Posted December 26, 2021 Zoneminder won’t start today; seeing this in logs: Dec 25 17:56:24 9158f1bee996 zmupdate[17233]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] Dec 25 17:56:24 9158f1bee996 zmupdate[17233]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] Using the included database and haven’t made any changes to Zoneminder other than maybe it updated? Any ideas 1 Quote Link to comment
blaine07 Posted January 9, 2022 Share Posted January 9, 2022 Can someone share their redacted subdomain.conf for using ZM with Swag reverse proxy(that works with ZM Ninja app) please? Quote Link to comment
sibi78 Posted January 13, 2022 Share Posted January 13, 2022 (edited) Hi All, I had been using Zoneminder docker with Unraid for quite a while. It was an older version. I upgraded to the recent version, and things stopped working. Is there a way to revert back to an older version of Zoneminder docker? I'd like to revert back for the short term (and debug why things stopped working in the long term). Could someone provide any pointers for reverting back to the old version? Also, whenever we upgrade Zoneminder, there was a suggestion to delete Zoneminder appdata and then, reconfigure. Did I understand this right? Thanks. Edited January 14, 2022 by sibi78 Fixed a typo Quote Link to comment
Auxilium Posted January 28, 2022 Share Posted January 28, 2022 On 12/26/2021 at 1:00 AM, blaine07 said: Zoneminder won’t start today; seeing this in logs: Dec 25 17:56:24 9158f1bee996 zmupdate[17233]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] Dec 25 17:56:24 9158f1bee996 zmupdate[17233]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] Using the included database and haven’t made any changes to Zoneminder other than maybe it updated? Any ideas My Zoneminder instance also stopped working recently: root@5e51f9e7d397:/# service mysql status * /usr/bin/mysqladmin Ver 9.1 Distrib 10.3.32-MariaDB, for debian-linux-gnu on x86_64 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Server version 10.3.32-MariaDB-0ubuntu0.20.04.1 Protocol version 10 Connection Localhost via UNIX socket UNIX socket /var/run/mysqld/mysqld.sock Uptime: 2 min 44 sec Threads: 6 Questions: 2 Slow queries: 0 Opens: 18 Flush tables: 1 Open tables: 11 Queries per second avg: 0.012 root@5e51f9e7d397:/# service zoneminder start Starting ZoneMinder: 01/29/22 00:22:11.848938 zmpkg[9316].INF [main:310] [Sanity checking States table...] DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/ZoneMinder/Logger.pm line 600. 01/29/22 00:22:12.004642 zmpkg[9316].ERR [ZoneMinder::Logger:603] [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 317. 01/29/22 00:22:12.005063 zmpkg[9316].FAT [main:317] [Can't execute: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)] ZoneMinder failed to start root@5e51f9e7d397:/# service mysql status * /usr/bin/mysqladmin Ver 9.1 Distrib 10.3.32-MariaDB, for debian-linux-gnu on x86_64 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Server version 10.3.32-MariaDB-0ubuntu0.20.04.1 Protocol version 10 Connection Localhost via UNIX socket UNIX socket /var/run/mysqld/mysqld.sock Uptime: 2 sec Threads: 6 Questions: 2 Slow queries: 0 Opens: 18 Flush tables: 1 Open tables: 11 Queries per second avg: 1.000 It seems like SQL server crashes and restarts 2022-01-29 00:22:11 0x1498c00c4700 InnoDB: Assertion failure in file /build/mariadb-10.3-ym4QNJ/mariadb-10.3-10.3.32/storage/innobase/fsp/fsp0fsp.cc line 1620 InnoDB: Failing assertion: n != ULINT_UNDEFINED InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/ InnoDB: about forcing recovery. 220129 0:22:11 [ERROR] mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.3.32-MariaDB-0ubuntu0.20.04.1 key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=1 max_threads=153 thread_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467428 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x149860000c48 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x1498c00c3dd8 thread_stack 0x49000 /usr/sbin/mysqld(my_print_stacktrace+0x32)[0x5574421125e2] /usr/sbin/mysqld(handle_fatal_signal+0x55d)[0x557441c07ced] /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x1498c3ccc3c0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x1498c3b0b18b] /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x1498c3aea859] /usr/sbin/mysqld(+0x4ee39d)[0x55744192439d] /usr/sbin/mysqld(+0x506444)[0x55744193c444] /usr/sbin/mysqld(+0xa8830a)[0x557441ebe30a] /usr/sbin/mysqld(+0xa88611)[0x557441ebe611] /usr/sbin/mysqld(+0xa8b724)[0x557441ec1724] /usr/sbin/mysqld(+0xa72982)[0x557441ea8982] /usr/sbin/mysqld(+0xab15c4)[0x557441ee75c4] /usr/sbin/mysqld(+0xa13509)[0x557441e49509] /usr/sbin/mysqld(+0xa14801)[0x557441e4a801] /usr/sbin/mysqld(+0xa15001)[0x557441e4b001] /usr/sbin/mysqld(+0xa255ce)[0x557441e5b5ce] /usr/sbin/mysqld(+0x977d89)[0x557441dadd89] /usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0x91)[0x557441c13a81] /usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x1ad)[0x5574419e74ad] /usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xb97)[0x5574419f14e7] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1673)[0x557441a193b3] /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x1f3)[0x557441a1fe33] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1065)[0x557441a22205] /usr/sbin/mysqld(_Z10do_commandP3THD+0x12d)[0x557441a241bd] /usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1fa)[0x557441b0760a] /usr/sbin/mysqld(handle_one_connection+0x3f)[0x557441b077df] /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609)[0x1498c3cc0609] /lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x1498c3be7293] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x14986000f8a0): INSERT INTO Logs ( TimeKey, Component, ServerId, Pid, Level, Code, Message, File, Line ) VALUES ( '1643412131.84894', 'zmpkg', NULL, '9316', '0', 'INF', 'Sanity checking States table...', 'zmpkg.pl', NULL ) Connection ID (thread ID): 10 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains information that should help you find out what is causing the crash. Writing a core file... Working directory at /config/mysql Resource Limits: Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size unlimited unlimited bytes Max core file size 0 0 bytes Max resident set unlimited unlimited bytes Max processes 386033 386033 processes Max open files 40960 40960 files Max locked memory unlimited unlimited bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 386033 386033 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us Core pattern: core 220129 00:22:12 mysqld_safe Number of processes running now: 0 220129 00:22:12 mysqld_safe mysqld restarted 2022-01-29 0:22:12 0 [Note] /usr/sbin/mysqld (mysqld 10.3.32-MariaDB-0ubuntu0.20.04.1) starting as process 9346 ... 2022-01-29 0:22:12 0 [Note] InnoDB: Using Linux native AIO 2022-01-29 0:22:12 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-01-29 0:22:12 0 [Note] InnoDB: Uses event mutexes 2022-01-29 0:22:12 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2022-01-29 0:22:12 0 [Note] InnoDB: Number of pools: 1 2022-01-29 0:22:12 0 [Note] InnoDB: Using SSE2 crc32 instructions 2022-01-29 0:22:12 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2022-01-29 0:22:12 0 [Note] InnoDB: Completed initialization of buffer pool 2022-01-29 0:22:12 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2022-01-29 0:22:12 0 [Note] InnoDB: The log sequence number 25264289813 in the system tablespace does not match the log sequence number 25264290316 in the ib_logfiles! 2022-01-29 0:22:12 0 [ERROR] InnoDB: Page [page id: space=0, page number=6] log sequence number 29038180169 is in the future! Current system log sequence number 25264290325. 2022-01-29 0:22:12 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. When attempting `mysqlcheck --all-databases`, it crashes too and this can be found in the logs 2022-01-29 0:28:39 10 [ERROR] InnoDB: Corruption of an index tree: table `zm`.`Events_Month` index `PRIMARY`, father ptr page no 169, child page no 170 Quote Link to comment
Addy Posted February 11, 2022 Share Posted February 11, 2022 Hey, is there a link to the GPU enabled container somewhere? or a guide? I can't seem to find it Quote Link to comment
MorgothCreator Posted February 11, 2022 Share Posted February 11, 2022 (edited) I moved the Zoneminder from Unraid to Synology DSM on a DS1815+ box, I believe that is the best package, I see that you stop the support to 1.34, anyway, thank you for the work you put in to create the package, is working fine with 3.5GB of total RAM used and nine 1080p pass through cameras I will always be afraid to upgrade it, due to database corruption, but don't care, never upgrade , has all I need. Excellent work. Edited February 11, 2022 by MorgothCreator Quote Link to comment
blaine07 Posted April 3, 2022 Share Posted April 3, 2022 On 2/11/2022 at 5:46 AM, MorgothCreator said: I moved the Zoneminder from Unraid to Synology DSM on a DS1815+ box, I believe that is the best package, I see that you stop the support to 1.34, anyway, thank you for the work you put in to create the package, is working fine with 3.5GB of total RAM used and nine 1080p pass through cameras I will always be afraid to upgrade it, due to database corruption, but don't care, never upgrade , has all I need. Excellent work. Speaking of upgrade… in Unraid I have been ignoring its beckons for me to update it for a few weeks. Anyone have any idea If update is solid and or what update addresses? Quote Link to comment
Waltm Posted April 10, 2022 Share Posted April 10, 2022 It would appear I broke my ZM install. It has been down for a while waiting for a new data drive. I replaced the drive, set the mount name in the docker to match but when I tried to start ZM it just crashes. It appears to be an issue with the database connection. Is there a way to repair this? ZM startup log below. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/05_set_the_time.sh... *** Running /etc/my_init.d/06_set_php_time.sh... *** Running /etc/my_init.d/07_set_dri_permissions.sh... Granting permissions on /dev/dri/* devices... *** Running /etc/my_init.d/10_syslog-ng.init... Apr 10 15:25:18 d98319459b45 syslog-ng[20]: syslog-ng starting up; version='3.25.1' *** Running /etc/my_init.d/20_apt_update.sh... Performing updates... Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB] Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease Hit:3 http://ppa.launchpad.net/iconnor/zoneminder-1.36/ubuntu focal InRelease Get:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Hit:5 http://ppa.launchpad.net/ondrej/apache2/ubuntu focal InRelease Get:6 http://archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB] Hit:7 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease Fetched 336 kB in 2s (177 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... 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... 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 no crontab for root Starting services... * 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' (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. Apr 10 15:26:05 d98319459b45 zmupdate[1153]: ERR [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. 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. Apr 10 15:26:05 d98319459b45 zmupdate[1153]: ERR [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. 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. Apr 10 15:26:05 d98319459b45 zmupdate[1155]: ERR [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. 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. Apr 10 15:26:05 d98319459b45 zmupdate[1155]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] 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. Apr 10 15:26:16 d98319459b45 zmpkg[1166]: ERR [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. 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. Apr 10 15:26:16 d98319459b45 zmpkg[1166]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] ZoneMinder failed to start *** /etc/my_init.d/40_firstrun.sh failed with status 255 *** Killing all processes... Apr 10 15:26:16 d98319459b45 syslog-ng[20]: syslog-ng shutting down; version='3.25.1' Quote Link to comment
dlandon Posted April 10, 2022 Author Share Posted April 10, 2022 1 hour ago, Waltm said: Is there a way to repair this? Did you copy your old configuration to the new disk? Quote Link to comment
Simmer Posted April 11, 2022 Share Posted April 11, 2022 How can I disable the https requirement? I am putting this through nginx (swag) and it is balking at the http. I'm guessing this is an apache2 setting but I'm not sure how to access the right file to edit. I think I'm close with the index.php file within /www/ but don't want to break it. Thanks! Quote Link to comment
Kuleinc Posted April 14, 2022 Share Posted April 14, 2022 I had to shutdown my unraid server today to replace some cooling fans in the server case. My wife uses Zoneminder daily to keep track of visitors to our property. When I brought the server back online zone minder kinda starts but doesnt. I'm getting this in the log, seem slike an update error for linux? *** Running /etc/my_init.d/20_apt_update.sh... Performing updates... Hit:1 http://ppa.launchpad.net/iconnor/zoneminder-1.36/ubuntu focal InRelease Get:2 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB] Hit:3 http://archive.ubuntu.com/ubuntu focal InRelease Get:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Hit:5 http://ppa.launchpad.net/ondrej/apache2/ubuntu focal InRelease Get:6 http://archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB] Hit:7 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease Fetched 336 kB in 1s (262 kB/s) Reading package lists... E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. *** /etc/my_init.d/20_apt_update.sh failed with status 100 Quote Link to comment
Kuleinc Posted April 17, 2022 Share Posted April 17, 2022 I fixed it by forcing an update and then starting the docker. Quote Link to comment
Mlatx Posted April 20, 2022 Share Posted April 20, 2022 On 1/8/2022 at 11:10 PM, blaine07 said: Can someone share their redacted subdomain.conf for using ZM with Swag reverse proxy(that works with ZM Ninja app) please? server { listen 443 ssl; listen [::]:443 ssl; server_name your_subdomain*; include /config/nginx/ssl.conf; client_max_body_size 0; location /zm { include /config/nginx/proxy.conf; proxy_pass https://your_internal_ip:your_port/zm; } } 1 Quote Link to comment
kysdaddy Posted May 6, 2022 Share Posted May 6, 2022 Hello, I am sorry to keep beating this horse, but it is so frustrating. I love Zoneminder. I just can't understand why the database is so fragile it seems every time that my server has a bad shutdown, I lose the database and have to completely reinstall. I get it I should shut it down correctly, I really do get it but sometimes *(%^%* happens. Most recently I was using Tdarr to transition to h265 and my cache filled up, couldn't do a clean shutdown. rebooted, 20 dockers still worked no issues, Plex all of the arr's, calibre, my homeassistant VM all worked fine, Zoneminder toast! That was 2 weeks ago, I decided to try shinobi again, don't get me wrong, there are some things in shinobi that I love, the reduced resource use for one, but I still like Zoneminder more. Yesterday I reinstalled and set ZM up again, but used my head. I set it up then shut it down and copied the app data folder to another drive. About an hour ago, a storm knocked my power out. Guess what? Yep everything came right back except ZM. This time it wasn't too bad, pasted the copied files to zm app data, overwrote the existing and ZM started. The old images aren't seen by Zm but because it was only a day, easy to delete. OK I know this has been quite a rant, my question is this. Is there something that I am missing, is the data base really this fragile? If I used a separate database, would it help? CA Backup and restore only allows one instance per machine, correct, IOW I backup and restore all or some but I can't set up one session to backup ZM and another to do all others Correct? Is there a script anywhere that shuts down a specific docker, and copies its app data to a mapped location? Rant complete. Thanks for any answers provided. Quote Link to comment
Kuleinc Posted May 26, 2022 Share Posted May 26, 2022 On 5/6/2022 at 4:03 PM, kysdaddy said: Hello, I am sorry to keep beating this horse, but it is so frustrating. I love Zoneminder. I just can't understand why the database is so fragile it seems every time that my server has a bad shutdown, I lose the database and have to completely reinstall. I get it I should shut it down correctly, I really do get it but sometimes *(%^%* happens. Most recently I was using Tdarr to transition to h265 and my cache filled up, couldn't do a clean shutdown. rebooted, 20 dockers still worked no issues, Plex all of the arr's, calibre, my homeassistant VM all worked fine, Zoneminder toast! That was 2 weeks ago, I decided to try shinobi again, don't get me wrong, there are some things in shinobi that I love, the reduced resource use for one, but I still like Zoneminder more. Yesterday I reinstalled and set ZM up again, but used my head. I set it up then shut it down and copied the app data folder to another drive. About an hour ago, a storm knocked my power out. Guess what? Yep everything came right back except ZM. This time it wasn't too bad, pasted the copied files to zm app data, overwrote the existing and ZM started. The old images aren't seen by Zm but because it was only a day, easy to delete. OK I know this has been quite a rant, my question is this. Is there something that I am missing, is the data base really this fragile? If I used a separate database, would it help? CA Backup and restore only allows one instance per machine, correct, IOW I backup and restore all or some but I can't set up one session to backup ZM and another to do all others Correct? Is there a script anywhere that shuts down a specific docker, and copies its app data to a mapped location? Rant complete. Thanks for any answers provided. I too just had this problem. I couldnt get zoneminder to work. I renamed the appdata zoneminder folder to zoneminder.backup and reinstalled the docker image and zoneminder will now start. But none of my cameras or settings are there. Is it possible to copy something from the old folder to the new one to get my settings back or? What am I doing wrong here? Quote Link to comment
kysdaddy Posted July 18, 2022 Share Posted July 18, 2022 (edited) I have found that once the data base craps the bed your best bet is to rebuild from scratch. That being said, once you have rebuilt, shut down ZM and copy the entire appdata folder to another drive. Now when the database fails, damn near every time the system shuts down unclean. All I have to do is copy the appdata folder back to the original folder. All of my cameras come back with a restart. If you copy the folder without shutting ZM down it doesn't work. Chas Edited July 18, 2022 by kysdaddy Quote Link to comment
DaFr0n Posted August 17, 2022 Share Posted August 17, 2022 Anyone had a issue regarding login? I can get to the login screen fine, upon entering my login details I get the following error: HTTP ERROR 500 Log shows: Aug 17 18:43:33 256ff5990435 zmstats[1044]: ERR [Failed DELETE FROM `Logs` WHERE `TimeKey` < unix_timestamp(now() - interval 2 day) LIMIT 100 :Table 'zm.Logs' doesn't exist in engine] 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.