SQL Schema Update 509 -> 510 failing
I'm experiencing an issue with the SQL schema update process and would appreciate your guidance.
The schema update from version 509 to 510 is failing during the discovery process. Here's the output I'm seeing:
./discovery.php -h none -- .... 509 -> 510 # (db) (Column collations were changed from UTF-8 to Latin1 where it wasn't actually necessary)...........F. Done (6s, 1 errors). -- Done. -- Observium is up to date.
Has anyone encountered this issue before? Any insights or recommendations would be much appreciated.
Best Helge
What database server are you using?
The schema changes are just what I copy/paste into my own dev install, so shouldn’t really be able to fail 😅
Though now we have a lot of mariadb/mysql behaviour differences, it’s not great.
Adam.
Sent from my iPhone
On 11 Sep 2025, at 14:53, Wiethoff, Helge via observium observium@lists.observium.org wrote:
I'm experiencing an issue with the SQL schema update process and would appreciate your guidance.
The schema update from version 509 to 510 is failing during the discovery process. Here's the output I'm seeing:
./discovery.php -h none -- .... 509 -> 510 # (db) (Column collations were changed from UTF-8 to Latin1 where it wasn't actually necessary)...........F. Done (6s, 1 errors). -- Done. -- Observium is up to date.
Has anyone encountered this issue before? Any insights or recommendations would be much appreciated.
Best Helge _______________________________________________ observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
Oh I see.
That was just the comment in the file.
You can ignore!
Adam.
Sent from my iPhone
On 11 Sep 2025, at 17:50, Adam Armstrong adama@observium.org wrote:
What database server are you using?
The schema changes are just what I copy/paste into my own dev install, so shouldn’t really be able to fail 😅
Though now we have a lot of mariadb/mysql behaviour differences, it’s not great.
Adam.
Sent from my iPhone
On 11 Sep 2025, at 14:53, Wiethoff, Helge via observium observium@lists.observium.org wrote:
I'm experiencing an issue with the SQL schema update process and would appreciate your guidance.
The schema update from version 509 to 510 is failing during the discovery process. Here's the output I'm seeing:
./discovery.php -h none -- .... 509 -> 510 # (db) (Column collations were changed from UTF-8 to Latin1 where it wasn't actually necessary)...........F. Done (6s, 1 errors). -- Done. -- Observium is up to date.
Has anyone encountered this issue before? Any insights or recommendations would be much appreciated.
Best Helge _______________________________________________ observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
This error is not critical, but to understand what the reason, write additional information:
- versions ./discovery.php -VV
- last schema update error tail -n 10 /opt/observium/logs/update-errors.log
Wiethoff, Helge via observium wrote on 11.09.2025 11:20:
I'm experiencing an issue with the SQL schema update process and would appreciate your guidance.
The schema update from version 509 to 510 is failing during the discovery process. Here's the output I'm seeing:
./discovery.php -h none -- .... 509 -> 510 # (db) (Column collations were changed from UTF-8 to Latin1 where it wasn't actually necessary)...........F. Done (6s, 1 errors). -- Done. -- Observium is up to date.
Has anyone encountered this issue before? Any insights or recommendations would be much appreciated.
Best Helge _______________________________________________ observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
[2025/09/11 11:15:46 +0200] discovery.php(14942): ====== Schema update 502 -> 503 ============== [2025/09/11 11:15:46 +0200] discovery.php(14942): Query: CREATE TABLE IF NOT EXISTS `stp_vlan_map` (`device_id` INT UNSIGNED NOT NULL, `vlan_vlan` INT UNSIGNED NOT NULL, `stp_instance_id` INT UNSIGNED NOT NULL, PRIMARY KEY (`device_id`,`vlan_vlan`), KEY `stp_instance_id` (`stp_instance_id`)) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;-- STP schema enhancements: admin_enable flag, regional_root and alternate root info ALTER TABLE `stp_ports` ADD COLUMN `admin_enable` TINYINT(1) DEFAULT NULL AFTER `base_port`; [2025/09/11 11:15:46 +0200] discovery.php(14942): Error: (1064) You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'ALTER TABLE `stp_ports` ADD COLUMN `admin_enable` TINYINT(1) DEFAULT NULL AF...' at line 2 [2025/09/11 11:15:52 +0200] discovery.php(14942): ====== Schema update 509 -> 510 ============== [2025/09/11 11:15:52 +0200] discovery.php(14942): Query: ALTER TABLE `probe_metrics` CHANGE `metric_label` `metric_label` VARCHAR(255) CHARACTER SET latin1 COLLATE latin1_general_ci NOT NULL, CHANGE `metric_rrd` `metric_rrd` VARCHAR(255) CHARACTER SET latin1 COLLATE latin1_general_ci NOT NULL, CHANGE `metric_type` `metric_type` ENUM('GAUGE','COUNTER') CHARACTER SET latin1 COLLATE latin1_general_ci NOT NULL DEFAULT 'GAUGE', CHANGE `metric_uom` `metric_uom` VARCHAR(32) CHARACTER SET latin1 COLLATE latin1_general_ci NULL DEFAULT NULL; [2025/09/11 11:15:52 +0200] discovery.php(14942): Error: (1054) Unknown column 'metric_rrd' in 'probe_metrics'
It's pretty old server and i need to migrate it asap: o PHP 7.4.33 o MariaDB 10.5.26-MariaDB (extension: mysqli 7.4.33)
Am Donnerstag, dem 11.09.2025 um 16:11 +0200 schrieb Mike Stupalov: This error is not critical, but to understand what the reason, write additional information:
- versions ./discovery.php -VV
- last schema update error tail -n 10 /opt/observium/logs/update-errors.log
Wiethoff, Helge via observium wrote on 11.09.2025 11:20:
I'm experiencing an issue with the SQL schema update process and would appreciate your guidance.
The schema update from version 509 to 510 is failing during the discovery process. Here's the output I'm seeing:
./discovery.php -h none -- .... 509 -> 510 # (db) (Column collations were changed from UTF-8 to Latin1 where it wasn't actually necessary)...........F. Done (6s, 1 errors). -- Done. -- Observium is up to date.
Has anyone encountered this issue before? Any insights or recommendations would be much appreciated.
Best Helge _______________________________________________ observium mailing list -- observium@lists.observium.orgmailto:observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.orgmailto:observium-leave@lists.observium.org
participants (3)
-
Adam Armstrong -
Mike Stupalov -
Wiethoff, Helge