Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Professional Edition
-
None
-
None
Description
Hello,
i tried to update but some db issues occured during update
[2020/06/12 14:31:18 +0200] discovery.php(946): ====== Schema update 428 -> 429 ============== |
[2020/06/12 14:31:18 +0200] discovery.php(946): Query: CREATE TABLE `autodiscovery` ( `autodiscovery_id` INT NOT NULL AUTO_INCREMENT , `poller_id` INT NOT NULL , `device_id` INT NULL DEFAULT NULL , `remote_hostname` VARCHAR(253) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL , `remote_ip` VARCHAR(128) CHARACTER SET latin1 COLLATE latin1_general_ci NULL DEFAULT NULL , `remote_device_id` INT NULL DEFAULT NULL , `protocol` VARCHAR(11) CHARACTER SET latin1 COLLATE latin1_general_ci NOT NULL , `added` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP , `last_checked` TIMESTAMP on update CURRENT_TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP , `last_reason` ENUM('ok','no_xdp','no_fqdn','no_dns','no_ip_permit','no_ping','no_snmp','no_db','duplicated','unknown') CHARACTER SET latin1 COLLATE latin1_general_ci NULL DEFAULT NULL , PRIMARY KEY (`autodiscovery_id`)) ENGINE = InnoDB CHARSET=utf8 COLLATE utf8_general_ci; |
[2020/06/12 14:31:18 +0200] discovery.php(946): Error: (1293) Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause |
[2020/06/12 14:31:18 +0200] discovery.php(946): Query: ALTER TABLE `autodiscovery` ADD INDEX `remote_hostname_ip` (`poller_id`, `remote_hostname`, `remote_ip`); |
[2020/06/12 14:31:18 +0200] discovery.php(946): Error: (1146) Table 'observium.autodiscovery' doesn't exist |
Attachments
Activity
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Review [ 10101 ] | New: Closed [ 6 ] |
| Status | Original: Pending Response [ 10000 ] | New: In Review [ 10101 ] |
| Status | Original: In Review [ 10101 ] | New: Pending Response [ 10000 ] |
Update with latest revision.
But now minimum supported versions is mysql 5.6.5 or mariadb 10.0.
| Status | Original: Pending Response [ 10000 ] | New: In Review [ 10101 ] |
Hello, yes this is a CentOS with 5.5.65-MariaDB
I will move to something newer
| Status | Original: In Review [ 10101 ] | New: Pending Response [ 10000 ] |
Hrm, there is no errors in SQL.. dear god, how old your MySQL (that error was fixed in mysql 5.6.5 in 2012 year)?
Please show versions as:
./discovery.php -VV
|
| Comment |
[ Please make and attach additional information about the device: * full snmp dump from device: {noformat} snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk {noformat} _If device not support SNMP version 2c, replace -v2c with -v1._ * If you have problems with discovery or poller processes, please do and attach these debugs: {noformat} ./discovery.php -d -h <device> ./poller.php -d -h <device> {noformat} * additionally attach device and/or vendor specific MIB files {color:#505F79}_Note, this comment is added automatically._{color} ] |
Issue can be closed