MorgothCreator

Members
  • Posts

    29
  • Joined

  • Last visited

Everything posted by MorgothCreator

  1. 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.
  2. 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
  3. With fresh install (appdata deleted, image deleted and data deleted ) still the same issue, But still need to update the database from a version to another, and that seem that need some time or corrupt the database: Get:29 http://ppa.launchpad.net/iconnor/zoneminder-1.36/ubuntu focal/main amd64 zoneminder-doc all 1.36.10-focal1 [4957 kB] Preconfiguring packages ... Fetched 40.0 MB in 14s (2773 kB/s) Preparing to unpack .../00-distro-info-data_0.43ubuntu1.9_all.deb ... Unpacking distro-info-data (0.43ubuntu1.9) over (0.43ubuntu1.8) ... Preparing to unpack .../01-tzdata_2021e-0ubuntu0.20.04_all.deb ... Unpacking tzdata (2021e-0ubuntu0.20.04) over (2021a-2ubuntu0.20.04) ... Preparing to unpack .../02-alsa-ucm-conf_1.2.2-1ubuntu0.11_all.deb ... Unpacking alsa-ucm-conf (1.2.2-1ubuntu0.11) over (1.2.2-1ubuntu0.10) ... Preparing to unpack .../03-php7.4-readline_7.4.25-1+ubuntu20.04.1+deb.sury.org+1_amd64.deb ... Unpacking php7.4-readline (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) over (7.4.24-1+ubuntu20.04.1+deb.sury.org+1) ... Preparing to unpack .../04-php7.4-opcache_7.4.25-1+ubuntu20.04.1+deb.sury.org+1_amd64.deb ... Unpacking php7.4-opcache (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) over (7.4.24-1+ubuntu20.04.1+deb.sury.org+1) ... Preparing to unpack .../05-php7.4-mysql_7.4.25-1+ubuntu20.04.1+deb.sury.org+1_amd64.deb ... Unpacking php7.4-mysql (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) over (7.4.24-1+ubuntu20.04.1+deb.sury.org+1) ... Preparing to unpack .../06-php7.4-json_7.4.25-1+ubuntu20.04.1+deb.sury.org+1_amd64.deb ... Unpacking php7.4-json (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) over (7.4.24-1+ubuntu20.04.1+deb.sury.org+1) ... Preparing to unpack .../07-php7.4-gd_7.4.25-1+ubuntu20.04.1+deb.sury.org+1_amd64.deb ... Unpacking php7.4-gd (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) over (7.4.24-1+ubuntu20.04.1+deb.sury.org+1) ... Preparing to unpack .../08-php7.4-fpm_7.4.25-1+ubuntu20.04.1+deb.sury.org+1_amd64.deb ... Unpacking php7.4-fpm (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) over (7.4.24-1+ubuntu20.04.1+deb.sury.org+1) ... Preparing to unpack .../09-libapache2-mod-php7.4_7.4.25-1+ubuntu20.04.1+deb.sury.org+1_amd64.deb ... Unpacking libapache2-mod-php7.4 (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) over (7.4.24-1+ubuntu20.04.1+deb.sury.org+1) ... Preparing to unpack .../10-php7.4-cli_7.4.25-1+ubuntu20.04.1+deb.sury.org+1_amd64.deb ... Unpacking php7.4-cli (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) over (7.4.24-1+ubuntu20.04.1+deb.sury.org+1) ... Preparing to unpack .../11-php7.4-common_7.4.25-1+ubuntu20.04.1+deb.sury.org+1_amd64.deb ... Unpacking php7.4-common (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) over (7.4.24-1+ubuntu20.04.1+deb.sury.org+1) ... Preparing to unpack .../12-libcaca0_0.99.beta19-2.1ubuntu1.20.04.2_amd64.deb ... Unpacking libcaca0:amd64 (0.99.beta19-2.1ubuntu1.20.04.2) over (0.99.beta19-2.1ubuntu1.20.04.1) ... Preparing to unpack .../13-libegl-mesa0_21.0.3-0ubuntu0.3~20.04.3_amd64.deb ... Unpacking libegl-mesa0:amd64 (21.0.3-0ubuntu0.3~20.04.3) over (21.0.3-0ubuntu0.3~20.04.2) ... Preparing to unpack .../14-libgbm1_21.0.3-0ubuntu0.3~20.04.3_amd64.deb ... Unpacking libgbm1:amd64 (21.0.3-0ubuntu0.3~20.04.3) over (21.0.3-0ubuntu0.3~20.04.2) ... Preparing to unpack .../15-libgl1-mesa-dri_21.0.3-0ubuntu0.3~20.04.3_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (21.0.3-0ubuntu0.3~20.04.3) over (21.0.3-0ubuntu0.3~20.04.2) ... Preparing to unpack .../16-libglx-mesa0_21.0.3-0ubuntu0.3~20.04.3_amd64.deb ... Unpacking libglx-mesa0:amd64 (21.0.3-0ubuntu0.3~20.04.3) over (21.0.3-0ubuntu0.3~20.04.2) ... Preparing to unpack .../17-libglapi-mesa_21.0.3-0ubuntu0.3~20.04.3_amd64.deb ... Unpacking libglapi-mesa:amd64 (21.0.3-0ubuntu0.3~20.04.3) over (21.0.3-0ubuntu0.3~20.04.2) ... Preparing to unpack .../18-libmysqlclient21_8.0.27-0ubuntu0.20.04.1_amd64.deb ... Unpacking libmysqlclient21:amd64 (8.0.27-0ubuntu0.20.04.1) over (8.0.26-0ubuntu0.20.04.3) ... Preparing to unpack .../19-libntlm0_1.5-2ubuntu0.1_amd64.deb ... Unpacking libntlm0:amd64 (1.5-2ubuntu0.1) over (1.5-2) ... Preparing to unpack .../20-libpulse0_1%3a13.99.1-1ubuntu3.12_amd64.deb ... Unpacking libpulse0:amd64 (1:13.99.1-1ubuntu3.12) over (1:13.99.1-1ubuntu3.11) ... Preparing to unpack .../21-mesa-va-drivers_21.0.3-0ubuntu0.3~20.04.3_amd64.deb ... Unpacking mesa-va-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.3) over (21.0.3-0ubuntu0.3~20.04.2) ... Preparing to unpack .../22-mesa-vdpau-drivers_21.0.3-0ubuntu0.3~20.04.3_amd64.deb ... Unpacking mesa-vdpau-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.3) over (21.0.3-0ubuntu0.3~20.04.2) ... Preparing to unpack .../23-mesa-vulkan-drivers_21.0.3-0ubuntu0.3~20.04.3_amd64.deb ... Unpacking mesa-vulkan-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.3) over (21.0.3-0ubuntu0.3~20.04.2) ... Preparing to unpack .../24-php7.4_7.4.25-1+ubuntu20.04.1+deb.sury.org+1_all.deb ... Unpacking php7.4 (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) over (7.4.24-1+ubuntu20.04.1+deb.sury.org+1) ... Preparing to unpack .../25-php8.0-mysql_8.0.12-1+ubuntu20.04.1+deb.sury.org+1_amd64.deb ... Unpacking php8.0-mysql (8.0.12-1+ubuntu20.04.1+deb.sury.org+1) over (8.0.11-1+ubuntu20.04.1+deb.sury.org+1) ... Preparing to unpack .../26-php8.0-common_8.0.12-1+ubuntu20.04.1+deb.sury.org+1_amd64.deb ... Unpacking php8.0-common (8.0.12-1+ubuntu20.04.1+deb.sury.org+1) over (8.0.11-1+ubuntu20.04.1+deb.sury.org+1) ... Preparing to unpack .../27-zoneminder_1.36.10-focal1_amd64.deb ... Unpacking zoneminder (1.36.10-focal1) over (1.36.8-focal2) ... Preparing to unpack .../28-zoneminder-doc_1.36.10-focal1_all.deb ... Unpacking zoneminder-doc (1.36.10-focal1) over (1.36.8-focal2) ... Setting up mesa-vulkan-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.3) ... Setting up mesa-vdpau-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.3) ... Setting up libmysqlclient21:amd64 (8.0.27-0ubuntu0.20.04.1) ... Setting up php7.4-common (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... Setting up libcaca0:amd64 (0.99.beta19-2.1ubuntu1.20.04.2) ... Setting up php7.4-mysql (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... Setting up libgbm1:amd64 (21.0.3-0ubuntu0.3~20.04.3) ... Setting up alsa-ucm-conf (1.2.2-1ubuntu0.11) ... Setting up libpulse0:amd64 (1:13.99.1-1ubuntu3.12) ... Setting up distro-info-data (0.43ubuntu1.9) ... Setting up php7.4-readline (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... Setting up tzdata (2021e-0ubuntu0.20.04) ... Current default time zone: 'Europe/Athens' Local time is now: Fri Oct 29 12:34:06 EEST 2021. Universal Time is now: Fri Oct 29 09:34:06 UTC 2021. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up libntlm0:amd64 (1.5-2ubuntu0.1) ... Setting up libglapi-mesa:amd64 (21.0.3-0ubuntu0.3~20.04.3) ... Setting up php8.0-common (8.0.12-1+ubuntu20.04.1+deb.sury.org+1) ... Setting up zoneminder-doc (1.36.10-focal1) ... Setting up php7.4-opcache (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... Setting up mesa-va-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.3) ... Setting up php7.4-gd (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... Setting up php7.4-json (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... Setting up php8.0-mysql (8.0.12-1+ubuntu20.04.1+deb.sury.org+1) ... Setting up libgl1-mesa-dri:amd64 (21.0.3-0ubuntu0.3~20.04.3) ... Setting up php7.4-cli (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... Setting up libegl-mesa0:amd64 (21.0.3-0ubuntu0.3~20.04.3) ... Setting up zoneminder (1.36.10-focal1) ... invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of stop. Oct 29 12:34:12 b8458a0935fc /etc/mysql/debian-start[13528]: Upgrading MySQL tables if necessary. Oct 29 12:34:12 b8458a0935fc /etc/mysql/debian-start[13533]: Looking for 'mysql' as: /usr/bin/mysql Oct 29 12:34:12 b8458a0935fc /etc/mysql/debian-start[13533]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Oct 29 12:34:12 b8458a0935fc /etc/mysql/debian-start[13533]: This installation of MySQL is already upgraded to 10.3.31-MariaDB, use --force if you still need to run mysql_upgrade Oct 29 12:34:12 b8458a0935fc /etc/mysql/debian-start[13555]: Checking for insecure root accounts. Checking for db Oct 29 12:34:12 b8458a0935fc /etc/mysql/debian-start[13561]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Db exists. Updating permissions for user zmuser@localhost Initiating database upgrade to version 1.36.10 from version 1.36.8 Upgrading database to version 1.36.10 Loading config from DB 221 entries Saving config to DB 221 entries Upgrading DB to 1.36.9 from 1.36.8 Database successfully upgraded to version 1.36.9. Database upgrade to version 1.36.10 successful. Freshening configuration in database Migratings passwords, if any... Loading config from DB 221 entries Saving config to DB 221 entries Done Updating Setting up libapache2-mod-php7.4 (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... libapache2-mod-php7.4: not switching MPM - already enabled Oct 29 12:34:14 b8458a0935fc libapache2-mod-php7.4: libapache2-mod-php7.4: not switching MPM - already enabled Setting up libglx-mesa0:amd64 (21.0.3-0ubuntu0.3~20.04.3) ... Setting up php7.4-fpm (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... NOTICE: Not enabling PHP 7.4 FPM by default. NOTICE: To enable PHP 7.4 FPM in Apache2 do: Oct 29 12:34:15 b8458a0935fc php7.4-fpm: NOTICE: Not enabling PHP 7.4 FPM by default. Oct 29 12:34:15 b8458a0935fc php7.4-fpm: NOTICE: To enable PHP 7.4 FPM in Apache2 do: NOTICE: a2enmod proxy_fcgi setenvif Oct 29 12:34:15 b8458a0935fc php7.4-fpm: NOTICE: a2enmod proxy_fcgi setenvif NOTICE: a2enconf php7.4-fpm Oct 29 12:34:15 b8458a0935fc php7.4-fpm: NOTICE: a2enconf php7.4-fpm NOTICE: You are seeing this message because you have apache2 package installed. Oct 29 12:34:15 b8458a0935fc php7.4-fpm: NOTICE: You are seeing this message because you have apache2 package installed. invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of restart. Setting up php7.4 (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... Processing triggers for libc-bin (2.31-0ubuntu9.2) ... Processing triggers for systemd (245.4-4ubuntu3.13) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for php7.4-cli (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... Processing triggers for libapache2-mod-php7.4 (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... Processing triggers for php7.4-fpm (7.4.25-1+ubuntu20.04.1+deb.sury.org+1) ... invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of restart. NOTICE: Not enabling PHP 7.4 FPM by default. NOTICE: To enable PHP 7.4 FPM in Apache2 do: Oct 29 12:34:15 b8458a0935fc php7.4-fpm: NOTICE: Not enabling PHP 7.4 FPM by default. Oct 29 12:34:15 b8458a0935fc php7.4-fpm: NOTICE: To enable PHP 7.4 FPM in Apache2 do: NOTICE: a2enmod proxy_fcgi setenvif Oct 29 12:34:15 b8458a0935fc php7.4-fpm: NOTICE: a2enmod proxy_fcgi setenvif NOTICE: a2enconf php7.4-fpm Oct 29 12:34:15 b8458a0935fc php7.4-fpm: NOTICE: a2enconf php7.4-fpm NOTICE: You are seeing this message because you have apache2 package installed. Oct 29 12:34:15 b8458a0935fc php7.4-fpm: NOTICE: You are seeing this message because you have apache2 package installed. 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... generating self-signed keys in /config/keys, you can replace these with your own keys if required Generating a RSA private key ..........................+++++ ........+++++ writing new private key to '/config/keys/cert.key' ----- *** Running /etc/my_init.d/40_firstrun.sh... Creating conf folder Copying zm.conf to config folder Moving zmeventnotification.ini Moving secrets.ini Moving the event notification server Moving the pushover api Moving ssmtp to config folder Moving mysql to config folder Creating control folder in config folder Copy /config/conf/ scripts to /etc/zm/conf.d/ Creating symbolink links Using existing data directory for events Correcting /var/cache/zoneminder/events permissions... Using existing data directory for images Correcting /var/cache/zoneminder/images permissions... Using existing data directory for temp Correcting /var/cache/zoneminder/temp permissions... Using existing data directory for cache Correcting /var/cache/zoneminder/cache permissions... no crontab for root Starting services... * Starting Apache httpd web server apache2 * * Starting MariaDB database server mysqld ...done. DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. Oct 29 12:34:21 b8458a0935fc zmupdate[15744]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' 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. Oct 29 12:34:21 b8458a0935fc zmupdate[15744]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. Oct 29 12:34:21 b8458a0935fc zmupdate[15745]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' 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. Oct 29 12:34:21 b8458a0935fc zmupdate[15745]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] Starting ZoneMinder: DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. Oct 29 12:34:31 b8458a0935fc zmpkg[15756]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' 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. Oct 29 12:34:31 b8458a0935fc zmpkg[15756]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] ZoneMinder failed to start *** /etc/my_init.d/40_firstrun.sh failed with status 255 *** Killing all processes... After that, I start it again and successfully started not needing to update the database, reporting that the database is has the desired version, so my conclusion is: Because on some updates the database need to be upgraded, the upgrade need some time and somehow ZM does not have access to the database in time even if MariaDB is successfully starting and the error kill all running processes, but the upgrade process have enough time to upgrade the database, if databse have other data than the default when you install ZM and you do an update that change the database version, will try to upgrade the database, but somehow the database is not upgraded, and every time you start the ZM will try to update the DB ending up in the same place where ZM can not access the database, the result being the killing of all processes including, maybe, the database upgrade process that end up in not having enough time to upgrade the database. Maybe that have some sense...
  4. This is quit anoying, two updates in a road to redo everything gain, there is nothing to do to fix it automatically, or at last to retain the most important settings like camera settings and other manual settings and the database to be reset automatically? Or provide a script to reset only the database and let the manual settings untouched, most people don't want to have these issues, and mostly, more probably at every update 😔 Or at last to warning that the update can broke the database and everything will need to be setup again.
  5. Second time when after update is broken, this time even after fresh install: Starting services... * Starting Apache httpd web server apache2 * * Starting MariaDB database server mysqld ...done. DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. Oct 27 15:08:08 b40778ecb6fd zmupdate[15709]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' 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. Oct 27 15:08:08 b40778ecb6fd zmupdate[15709]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. Oct 27 15:08:08 b40778ecb6fd zmupdate[15710]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' 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. Oct 27 15:08:08 b40778ecb6fd zmupdate[15710]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] * Starting MariaDB database server mysqld ...done. DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. Oct 27 15:08:08 b40778ecb6fd zmupdate[15709]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' 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. Oct 27 15:08:08 b40778ecb6fd zmupdate[15709]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. Oct 27 15:08:08 b40778ecb6fd zmupdate[15710]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' 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. Oct 27 15:08:08 b40778ecb6fd zmupdate[15710]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] Starting ZoneMinder: DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' at /usr/share/perl5/ZoneMinder/Database.pm line 110. Oct 27 15:08:18 b40778ecb6fd zmpkg[15721]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Unknown database 'zm' 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. Oct 27 15:08:18 b40778ecb6fd zmpkg[15721]: ERR [Error reconnecting to db: errstr:Unknown database 'zm' error val:] ZoneMinder failed to start *** /etc/my_init.d/40_firstrun.sh failed with status 255 *** Killing all processes... Oct 27 15:08:18 b40778ecb6fd syslog-ng[39]: syslog-ng shutting down; version='3.25.1'
  6. Wats happening, after the last update, UnRaid 1.9.1: Mar 26 18:00:00 ecaace443c98 zmdc[1516]: INF ['zma -m 6' started at 21/03/26 18:00:00] Mar 26 18:00:00 ecaace443c98 zmdc[850]: INF ['zma -m 6' crashed, signal 6] Mar 26 18:00:01 ecaace443c98 zmdc[850]: INF [Starting pending process, zmc -m 2] Mar 26 18:00:01 ecaace443c98 zmdc[850]: INF ['zmc -m 2' starting at 21/03/26 18:00:01, pid = 1517] Mar 26 18:00:01 ecaace443c98 zmdc[1517]: INF ['zmc -m 2' started at 21/03/26 18:00:01] Mar 26 18:00:01 ecaace443c98 zmdc[850]: INF [Starting pending process, zma -m 2] Mar 26 18:00:01 ecaace443c98 zmdc[850]: INF ['zma -m 2' starting at 21/03/26 18:00:01, pid = 1518] Mar 26 18:00:01 ecaace443c98 zmdc[1518]: INF ['zma -m 2' started at 21/03/26 18:00:01] Mar 26 18:00:01 ecaace443c98 zmdc[850]: INF [Starting pending process, zma -m 11] Mar 26 18:00:01 ecaace443c98 zmc_m2[1517]: INF [zmc_m2] [Not enabling ffmpeg logs, as LOG_FFMPEG and/or LOG_DEBUG is disabled in options, or this monitor is not part of your debug targets] Mar 26 18:00:01 ecaace443c98 zmdc[1519]: INF ['zma -m 11' started at 21/03/26 18:00:01] Mar 26 18:00:01 ecaace443c98 zmdc[850]: INF ['zma -m 11' starting at 21/03/26 18:00:01, pid = 1519] Mar 26 18:00:02 ecaace443c98 zmdc[850]: INF [Starting pending process, zma -m 9] Mar 26 18:00:02 ecaace443c98 zma_m2[1518]: ERR [zma_m2] [Shared data not initialised by capture daemon for monitor CAM6] Mar 26 18:00:02 ecaace443c98 zmdc[1520]: INF ['zma -m 9' started at 21/03/26 18:00:02] Mar 26 18:00:02 ecaace443c98 zmdc[850]: INF ['zma -m 9' starting at 21/03/26 18:00:02, pid = 1520] Mar 26 18:00:02 ecaace443c98 zmdc[850]: INF [Starting pending process, zma -m 8] Mar 26 18:00:02 ecaace443c98 zmdc[850]: INF ['zma -m 8' starting at 21/03/26 18:00:02, pid = 1521] Mar 26 18:00:02 ecaace443c98 zmdc[1521]: INF ['zma -m 8' started at 21/03/26 18:00:02] Mar 26 18:00:02 ecaace443c98 zmdc[850]: ERR ['zma -m 2' exited abnormally, exit status 255] Mar 26 18:00:02 ecaace443c98 zmdc[850]: INF ['zmc -m 2' crashed, signal 6] Mar 26 18:00:02 ecaace443c98 zmdc[850]: INF ['zma -m 11' crashed, signal 6] Mar 26 18:00:03 ecaace443c98 zmdc[850]: INF ['zma -m 8' crashed, signal 6] Mar 26 18:00:03 ecaace443c98 zmdc[850]: INF ['zma -m 9' crashed, signal 6] Mar 26 18:00:21 ecaace443c98 web_php[594]: ERR [Potentially invalid value for ZM_LOG_DATABASE_LIMIT: 30 day] Mar 26 18:01:22 ecaace443c98 web_php[1072]: ERR [Potentially invalid value for ZM_LOG_DATABASE_LIMIT: 30 day] Mar 26 18:01:23 ecaace443c98 zmdc[850]: INF [Starting pending process, zmc -m 2] Mar 26 18:01:23 ecaace443c98 zmdc[850]: INF ['zmc -m 2' starting at 21/03/26 18:01:23, pid = 1535] Mar 26 18:01:23 ecaace443c98 zmdc[1535]: INF ['zmc -m 2' started at 21/03/26 18:01:23] Mar 26 18:01:23 ecaace443c98 zmdc[850]: INF [Starting pending process, zma -m 2] Mar 26 18:01:23 ecaace443c98 zmdc[850]: INF ['zma -m 2' starting at 21/03/26 18:01:23, pid = 1536] Mar 26 18:01:23 ecaace443c98 zmdc[1536]: INF ['zma -m 2' started at 21/03/26 18:01:23] Mar 26 18:01:23 ecaace443c98 zmc_m2[1535]: INF [zmc_m2] [Not enabling ffmpeg logs, as LOG_FFMPEG and/or LOG_DEBUG is disabled in options, or this monitor is not part of your debug targets] Mar 26 18:01:23 ecaace443c98 zmdc[850]: INF ['zmc -m 2' crashed, signal 6] Mar 26 18:01:23 ecaace443c98 zma_m2[1536]: ERR [zma_m2] [Shared data not initialised by capture daemon for monitor CAM6] Mar 26 18:01:23 ecaace443c98 zmdc[850]: ERR ['zma -m 2' exited abnormally, exit status 255]
  7. Ohh, I will give a try when I will have the occasion 😀👍
  8. The more you fix things, the more broken they are 🤦‍♂️. Now Gitlab does not even start: Upgrading PostgreSQL to 11.7 cp /opt/gitlab/embedded/service/gitlab-rails/public/deploy.html /opt/gitlab/embedded/service/gitlab-rails/public/index.html ok: down: gitaly: 0s, normally up ok: down: logrotate: 1s, normally up ok: down: registry: 0s, normally up ok: down: sidekiq: 1s, normally up ok: down: sshd: 0s, normally up There was an error fetching locale and encoding information from the database Please ensure the database is running and functional before running pg-upgrade STDOUT: STDERR: psql: FATAL: the database system is starting up == Fatal error == Please check error logs == Reverting == ok: down: postgresql: 0s, normally up ok: run: postgresql: (pid 722) 0s == Reverted == == Reverted to 10.12. Please check output for what went wrong == rm -f /opt/gitlab/embedded/service/gitlab-rails/public/index.html ok: run: gitaly: (pid 744) 1s ok: run: logrotate: (pid 808) 0s ok: run: registry: (pid 821) 0s ok: run: sidekiq: (pid 832) 1s ok: run: sshd: (pid 838) 0s Upgrading the existing database failed and was reverted. Please check the output, and open an issue at: https://gitlab.com/gitlab-org/omnibus-gitlab/issues If you would like to restart the instance without attempting to upgrade, add the following to your docker command: -e GITLAB_SKIP_PG_UPGRADE=true
  9. Hi, is the forth or fifth update and the issue was not fixed The issue is that when I click to a file link will go to "https://git.devboard.tech:9443/tips/linux/-/blob/master/crontab-check-start-app.md" instead of "https://git.devboard.tech/tips/linux/-/blob/master/crontab-check-start-app.md" for example. This behaviour is valid for all files on the gitlab. The git is up and running, you can check it. The rest if pages are OK. This issue has appeared about five updates ago, I do not changed any configuration file, I do not touch anything, after the update I see this behaviour.......
  10. Hi what happened to the last update, After the update all work fine except when I want to access the individual file, the gitlab insert the internal port 9433 to the link and and the browser does not want to load the file, check it here for example: https://git.devboard.tech/boot-loaders/fpga-risc-v If you navigate the directories all OK, when you load file the issue appear.
  11. Same here, What happen if I kill him or restart him from time to time? 😀
  12. I see that has only support for mem, not for memmap. Ehh maybe in future the Syslinux guys will add support for memmap, or Unraid will use Grub, maybe both, Maybe Unraid can introduce a way to select between the two bootloaders 😀, is a cool feature because like in my case because of one bit you need to throw away an entire stick of RAM (and is part of a kit of four Corsair Dominator Platinum 3000Mhz ( now I see that are not so platinum how they tell ) 😪) . Of course I removed it immediately after I tested it 😀 Merry Christmas and best regards.
  13. Ohh, so is no chance for skipping that bit :((, poor 16GB stick. Thank you very much.
  14. Hi I discovered that one of my four 16 GB sticks has only one bit stick to '1' logic, this was from when I bought them, but I have been gone out of my country for two years. Now I am home and make the memtest86 test and see this bit, this bit has bothering me for all that two years, because the Unraid never crash, only see some disk corruption. First I used BTRFS and partitions begin to be corrupted in several days and give me IO errors when try to copy large files, the rest of corruption was silent. After that I used XFS, but because XFS has no check summing, all corruption was silent. After that I put ZFS, and here I begin to see that something was seriously wrong, because each day ZFS reported me around 10 crc errors, at a traffic of around 200GB/day on SSD's. Now that i tested the ram I know where is the problem, one bit out of 64GB stick to '1' :)))))))))) I navigate some DuckDuckGo and find this: https://help.ubuntu.com/community/BadRAM that warm my day, because the ram was bought from another country, and to use warranty will take around two months and for sure I will need to send the entire kit, not only the bad RAM :) The problem is that in Unraid does not exist this file: "/etc/default/grub", the directory exist, but not the file. Someone has an idea how can I setup BADRAM and if is supported by Unraid grub? Thank you
  15. The problem seems to be from tar application. I decompress the ova archive using tar from Synology DSM on the VM, after that, I copied the vmdk image to the Unraid machine and convert it to qcow2 with qemu-img on the Unraid, and the conversion was done successfully. So, something is wrong with tar application working with large files on the Unraid OS.
  16. I see that the problem is on writing to the disk, not on reading, because the error on the file is happening at the same sector when I read the same write file, and the sector change if I rewrite the file and try to read it again. I mentioned that I have a VM with 4 pass-through disks that never had problems, so all components are working properly. The system does not report any other problem, does not freeze, or have strange behavior, being up and running for several weeks in a road. The problem is only when working with big files, like image disks and large videos. On some rare occasions when VM virtual disk is edited by the VM machine the entire disk is corrupted ( happened one time ). When the Windows7 VM has corrupted the disk, when has been shut down by me, the Unraid web page stop responding because has stuck on waiting the disk to respond, but the other VM's and docker run normally ( working on other disks ), when I open the web terminal, has opened normally and I can send commands, the disk was mounted and was navigable, only after Unraid (unclean off course, because after several hours the system refuse to restart ) restart the corruption of the disk was observable. I think that is something with FS arbitration between multiple app's writting on the same disk or something like that.
  17. I know that here are some topics with the same issue, but this issue need to never happen on a server system. So, the story is that some time I want to move data around from a disk to another, to compress some data, to decompress it etc. But on large files some time is getting me Input/Output read error and I am tired of this error on a paid OS. The btrfs check is with no errors, and this Input/Output error is getting me on both , on array and on unassigned devices. Mention is that I virtualized a Synology DSM with pass through and that system is working without any errors, so I know that is not a device fault, but something with FS implementation. Another mention is that the machine is on a semiprofessional UPS, so, can not be a power fault. Last time I try to convert a 70GB image and this is the result: qemu-img convert -f vmdk -O qcow2 SomeFile-disk1.vmdk SomeFile.qcow2 qemu-img: error while reading sector 7978112: Invalid argument And the conversion can not pass this sector. The same error some time give me tar application on large files. The mv and cp never fail or report IO issues but I see sometime artifacts on videos, so the issue is present even in mv and cp, so in one sentence, about all my large files are corrupted to put it like that. I see it on transmission when is reporting disk error and I need to put it to check the file multiple times, and transmission use a virtualized docker disk. When I recreate the source file and try the same above command, will give error on another sector or some time no error. One time an entire disk was corrupted when I powered down a Windows7 VM, and that disk was unrecoverable, needed format. The system is: Thredripper 1950X liquid cooled, with 64GB matched RAM kit on a ASROCK Taichi X399 motherboard, Power source 1200W, UPS APC Smart-UPS C 1000VA LCD the OS is 1.7.2. All rotated disks are from WD, The SSD's are from Samsung and are PRO or Evo, a single SSD is from Intel and is a 120GB and never give me a error because, I suppose that I never transferred large files on it. What is happening???????????
  18. ...... I want to centralize all servers around my house to a single one, a Threadripper 1950X with 64GB RAM 😀, and for this I need to mount a IMG usb disk image with the VID:PID instead of using the physical USB device, because the OS can not run if does not detect the expected VID:PID.
  19. Hy, Is there a way to pass to a VM an img virtual usb disk with VID and PID attached to it?
  20. Same error here on a Threadripper 1950x a ASRock X399 Taichi board and Nvidia GTX1080TI and Unraid 6.7.2
  21. Ahh, sorry, I am new to unRaid and I do not come to this part until now and I assumed that use VirtualBox :D, my bad. But it seems that there are the same limitations
  22. All my VM's from above disertation are on a bare metal unRaid machine. I only compared unRaid OS with Synolgy DSM OS that both use Virtual Box. Who can think to virtualize inside another virtualized enviroment :))))
  23. I talking about unRaid. Virtual box is used in unRaid and Synology DSM, so the limitations are the same. The only difference is that Synologi DSM does not let you allocate virtual cores more than double the threads of the processor.