[#ZBX-18950] Items cannot be updated due to "Timeout" field validation problem

hey @zux, thanks, this is very helpful! You pointed me into the right direction. I am running Zabbix 5.2.4 on MySQL 8.0. Did a table schema dump (mysqldump --no-data zabbix items):

CREATE TABLE `items` (
  `itemid` bigint unsigned NOT NULL,
  `type` int NOT NULL DEFAULT '0',
  `snmp_oid` varchar(512) COLLATE utf8_bin NOT NULL,
  `hostid` bigint unsigned NOT NULL,
  `name` varchar(255) COLLATE utf8_bin NOT NULL,
  `key_` varchar(2048) COLLATE utf8_bin NOT NULL DEFAULT '',
  `delay` varchar(1024) COLLATE utf8_bin NOT NULL,
  `history` varchar(255) COLLATE utf8_bin NOT NULL,
  `trends` varchar(255) COLLATE utf8_bin NOT NULL,
  `status` int NOT NULL DEFAULT '0',
  `value_type` int NOT NULL DEFAULT '0',
  `trapper_hosts` varchar(255) COLLATE utf8_bin NOT NULL,
  `units` varchar(255) COLLATE utf8_bin NOT NULL,
  `formula` varchar(255) COLLATE utf8_bin NOT NULL,
  `logtimefmt` varchar(64) COLLATE utf8_bin NOT NULL,
  `templateid` bigint unsigned DEFAULT NULL,
  `valuemapid` bigint unsigned DEFAULT NULL,
  `params` text COLLATE utf8_bin NOT NULL,
  `ipmi_sensor` varchar(128) COLLATE utf8_bin NOT NULL,
  `authtype` int NOT NULL DEFAULT '0',
  `username` varchar(64) COLLATE utf8_bin NOT NULL,
  `password` varchar(64) COLLATE utf8_bin NOT NULL,
  `publickey` varchar(64) COLLATE utf8_bin NOT NULL,
  `privatekey` varchar(64) COLLATE utf8_bin NOT NULL,
  `flags` int NOT NULL DEFAULT '0',
  `interfaceid` bigint unsigned DEFAULT NULL,
  `description` text COLLATE utf8_bin NOT NULL,
  `inventory_link` int NOT NULL DEFAULT '0',
  `lifetime` varchar(255) COLLATE utf8_bin NOT NULL,
  `evaltype` int NOT NULL DEFAULT '0',
  `jmx_endpoint` varchar(255) COLLATE utf8_bin NOT NULL,
  `master_itemid` bigint unsigned DEFAULT NULL,
  `timeout` varchar(255) COLLATE utf8_bin NOT NULL,
  `url` varchar(2048) COLLATE utf8_bin NOT NULL,
  `query_fields` varchar(2048) COLLATE utf8_bin NOT NULL,
  `posts` text COLLATE utf8_bin NOT NULL,
  `status_codes` varchar(255) COLLATE utf8_bin NOT NULL,
  `follow_redirects` int NOT NULL DEFAULT '1',
  `post_type` int NOT NULL DEFAULT '0',
  `http_proxy` varchar(255) COLLATE utf8_bin NOT NULL,
  `headers` text COLLATE utf8_bin NOT NULL,
  `retrieve_mode` int NOT NULL DEFAULT '0',
  `request_method` int NOT NULL DEFAULT '0',
  `output_format` int NOT NULL DEFAULT '0',
  `ssl_cert_file` varchar(255) COLLATE utf8_bin NOT NULL,
  `ssl_key_file` varchar(255) COLLATE utf8_bin NOT NULL,
  `ssl_key_password` varchar(64) COLLATE utf8_bin NOT NULL,
  `verify_peer` int NOT NULL DEFAULT '0',
  `verify_host` int NOT NULL DEFAULT '0',
  `allow_traps` int NOT NULL DEFAULT '0',
  `discover` int NOT NULL DEFAULT '0',
  PRIMARY KEY (`itemid`),
  KEY `items_3` (`status`),
  KEY `items_4` (`templateid`),
  KEY `items_5` (`valuemapid`),
  KEY `items_6` (`interfaceid`),
  KEY `items_7` (`master_itemid`),
  KEY `items_1` (`hostid`,`key_`(1021)),
  CONSTRAINT `c_items_1` FOREIGN KEY (`hostid`) REFERENCES `hosts` (`hostid`) ON DELETE CASCADE ON UPDATE RESTRICT,
  CONSTRAINT `c_items_2` FOREIGN KEY (`templateid`) REFERENCES `items` (`itemid`) ON DELETE CASCADE ON UPDATE RESTRICT,
  CONSTRAINT `c_items_3` FOREIGN KEY (`valuemapid`) REFERENCES `valuemaps` (`valuemapid`) ON DELETE RESTRICT ON UPDATE RESTRICT,
  CONSTRAINT `c_items_4` FOREIGN KEY (`interfaceid`) REFERENCES `interface` (`interfaceid`) ON DELETE RESTRICT ON UPDATE RESTRICT,
  CONSTRAINT `c_items_5` FOREIGN KEY (`master_itemid`) REFERENCES `items` (`itemid`) ON DELETE CASCADE ON UPDATE RESTRICT
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;

then compared it to /usr/share/doc/zabbix-server-mysql/create.sql.gz on Debian Buster, and here we go:

        `timeout`                varchar(255)    DEFAULT '3s'              NOT NULL,

Somehow, I was missing the DEFAULT '3s'. How could this have happened? Did not find any upgrade notes about manual db schema migrations for Zabbix 4.x -> 5.0 or any 5.x -> 5.2 upgrades.

ALTER TABLE items MODIFY `timeout` varchar(255) COLLATE utf8_bin NOT NULL DEFAULT '3s';

But the problem still occurs, as existing items still have empty timeout values. Only if I replace those, item editing (and cloning) works again. But I only did this for a single item (from a template that is applied to 15 hosts):

UPDATE items SET timeout = '3s' WHERE timeout != '3s' AND name = 'Certbot WARNING lines';
-- Query OK, 15 rows affected

SELECT itemid, type, name, timeout FROM items WHERE timeout != '3s';
-- 1951 rows in set

Isn't it too risky to change all those items' timeout values to '3s'? Could this be done for all items, no matter which type they are?

[ZBX-18950] Items cannot be updated due to "Timeout" field validation problem Created: 2021 Jan 31 Updated: 2021 Feb 19 Resolved: 2021 Feb 19
Status:	Closed
Project:	ZABBIX BUGS AND ISSUES
Component/s:	Frontend (F)
Affects Version/s:	5.0.8, 5.2.4
Fix Version/s:	None

[ZBX-18950] Items cannot be updated due to "Timeout" field validation problem Created: 2021 Jan 31 Updated: 2021 Feb 19 Resolved: 2021 Feb 19