ZoneMinder Forums

Previous versions work..

1.34 isn't working for me.... Can't seem to load anything

"ERROR 1932 (42S02) at line 15: Table 'zm.Logs' doesn't exist in engine
Output:
Command 'mysql -hlocalhost -uzmuser -p"zmpass" zm < /usr/share/zoneminder/db/zm_update-1.33.12.sql' exited with status: 1"


*** 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/10_syslog-ng.init...
Jan 19 09:56:26 c6570ff7876c syslog-ng[16]: syslog-ng starting up; version='3.13.2'
*** Running /etc/my_init.d/20_apt_update.sh...
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://ppa.launchpad.net/iconnor/zoneminder-1.34/ubuntu bionic InRelease
Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
*** 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 moved
File zmeventnotification.ini already moved
File secrets.ini already moved
Event notification server 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
Setting shared memory to : 50% of 16344776 bytes
Starting services...
* Starting MariaDB database server mysqld
...done.
Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[733]: Upgrading MySQL tables if necessary.
Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[737]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[737]: Looking for 'mysql' as: /usr/bin/mysql
Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[737]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[737]: This installation of MySQL is already upgraded to 10.1.43-MariaDB, use --force if you still need to run mysql_upgrade
Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[744]: Checking for insecure root accounts.
Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[748]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables

Initiating database upgrade to version 1.34.0 from version 1.32.3

Upgrading database to version 1.34.0
Loading config from DB 230 entries
Saving config to DB 230 entries
Upgrading DB to 1.33.0 from 1.32.3

Database successfully upgraded to version 1.33.0.
Upgrading DB to 1.33.1 from 1.32.3

Database successfully upgraded to version 1.33.1.
Upgrading DB to 1.33.2 from 1.32.3

Database successfully upgraded to version 1.33.2.
Upgrading DB to 1.33.3 from 1.32.3

Database successfully upgraded to version 1.33.3.
Upgrading DB to 1.33.4 from 1.32.3

Database successfully upgraded to version 1.33.4.
Upgrading DB to 1.33.5 from 1.32.3

Database successfully upgraded to version 1.33.5.
Upgrading DB to 1.33.6 from 1.32.3

Database successfully upgraded to version 1.33.6.
Upgrading DB to 1.33.7 from 1.32.3

Database successfully upgraded to version 1.33.7.
Upgrading DB to 1.33.8 from 1.32.3

Database successfully upgraded to version 1.33.8.
Upgrading DB to 1.33.9 from 1.32.3

Database successfully upgraded to version 1.33.9.
Upgrading DB to 1.33.10 from 1.32.3

Database successfully upgraded to version 1.33.10.
Upgrading DB to 1.33.11 from 1.32.3

Database successfully upgraded to version 1.33.11.
Upgrading DB to 1.33.12 from 1.32.3
ERROR 1932 (42S02) at line 15: Table 'zm.Logs' doesn't exist in engine
Output:
Command 'mysql -hlocalhost -uzmuser -p"zmpass" zm < /usr/share/zoneminder/db/zm_update-1.33.12.sql' exited with status: 1

Freshening configuration in database
Migratings passwords, if any...
Loading config from DB 230 entries
Saving config to DB 230 entries
* Starting Apache httpd web server apache2
*
Starting ZoneMinder:
Jan 19 09:56:35 c6570ff7876c zmpkg[847]: INF [Sanity checking States table...]
DBD::mysql::st execute failed: Table 'zm.Logs' doesn't exist in engine at /usr/share/perl5/ZoneMinder/Logger.pm line 600.
Jan 19 09:56:35 c6570ff7876c zmpkg[847]: ERR [Can't execute log entry 'INSERT INTO Logs ( TimeKey, Component, ServerId, Pid, Level, Code, Message, File, Line ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, NULL )': Table 'zm.Logs' doesn't exist in engine]
Jan 19 09:56:35 c6570ff7876c zmpkg[847]: INF [Command: start]
Jan 19 09:56:35 c6570ff7876c zmpkg[847]: FAT [Version mismatch, system is version 1.34.0, database is 1.32.3, please run zmupdate.pl to update.]
ZoneMinder failed to start

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

*** Killing all processes...
Jan 19 09:56:35 c6570ff7876c syslog-ng[16]: syslog-ng shutting down; version='3.13.2'

You seem to not have a Logs table. That's pretty weird.

cutnpaste the following into mysql to recreate it.

CREATE TABLE `Logs` (
`Id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`TimeKey` decimal(16,6) NOT NULL,
`Component` varchar(32) NOT NULL,
`ServerId` int(10) unsigned,
`Pid` int(10) DEFAULT NULL,
`Level` tinyint(3) NOT NULL,
`Code` char(3) NOT NULL,
`Message` text NOT NULL,
`File` varchar(255) DEFAULT NULL,
`Line` smallint(5) unsigned DEFAULT NULL,
PRIMARY KEY (`Id`),
KEY `TimeKey` (`TimeKey`)
) ENGINE=InnoDB;

CREATE INDEX `Logs_TimeKey_idx` ON `Logs` (`TimeKey`);
CREATE INDEX `Logs_Level_idx` ON `Logs` (`Level`);

Thanks. Not sure if that would have fixed it as I just did a whole reinstall. Maybe should have waited.


Thanks again.

Since I hit this issues as well it seams to be a MySQL / ram? crashing issue.
-------------------------------------------------------------------------------------------------------------------------------------------------------
Database successfully upgraded to version 1.33.11.
Upgrading DB to 1.33.12 from 1.32.3
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2013 (HY000) at line 15: Lost connection to MySQL server during query
Output:
Command 'mysql -hlocalhost -uzmuser -p"zmpass" zm < /usr/share/zoneminder/db/zm_update-1.33.12.sql' exited with status: 1
---------------------------------------------------------------------------------------------------------------------------------------------------


What I did to fix it.

Rename the old table then recreate structure then rerun zmupdate.pl

mysql

RENAME TABLE Logs TO Logs_OLD


CREATE TABLE `Logs` (
`Id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`TimeKey` decimal(16,6) NOT NULL,
`Component` varchar(32) NOT NULL,
`ServerId` int(10) unsigned,
`Pid` int(10) DEFAULT NULL,
`Level` tinyint(3) NOT NULL,
`Code` char(3) NOT NULL,
`Message` text NOT NULL,
`File` varchar(255) DEFAULT NULL,
`Line` smallint(5) unsigned DEFAULT NULL,
PRIMARY KEY (`Id`),
KEY `TimeKey` (`TimeKey`)
) ENGINE=InnoDB;

CREATE INDEX `Logs_TimeKey_idx` ON `Logs` (`TimeKey`);
CREATE INDEX `Logs_Level_idx` ON `Logs` (`Level`);

quit;

then run
zmupdate.pl