. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 1 Error and warning messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IPv6-enabled daemon on a system without IPv6 support fail: 8 Listener failed with error: socket() for [[(null)]:10051] failed with error 97: Address family not supported by protocol. 3.3.3 For version 1.8.5 • or later on a system with kernel 2.6.26 or older will fail:socket() for [[-]:10050] failed with error 22: Invalid argument 3.3.4 For version 1.8.6 • Zabbix daemons now refuse to start up if configuration

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1849 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . code will be ”0”; otherwise, the component will exit with non-zero exit code and a corresponding error message. Warnings (e.g., in case of a deprecated parameter) will not affect successful exit code icmpping • icmppingloss • icmppingsec This parameter can be used to specify whether redirected responses should be treated as target host up or target host down. See simple checks for more details. Logging

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1658 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . became unsupported: • {ITEM.STATE.ERROR} - for item-based internal notifications; • {LLDRULE.STATE.ERROR} - for LLD-rule based internal notifications; • {TRIGGER.STATE.ERROR} - for trigger-based internal are NaNs then ’avg’, ’max’, ’min’, and ’sum’ return a ”no data (at least one value is required)” error, while ’count’ returns 0. Previously, if NaN was the first value in a dataset then: • ’avg’, ’max’

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1669 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . provides mutexes for locking in OpenSSL. If a mutex lock or unlock fails then an error message is printed to the standard error stream (STDERR) and Agent 2 exits with return code 2 or 3, respectively. 4 Proxy configuring them. Debugging Java gateway In case there are any problems with Java gateway or an error message that you see about an item in the frontend is not descriptive enough, you might wish to take

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1790 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ConfigFrequency. Attention: If both ProxyConfigFrequency and ConfigFrequency are used, the proxy will log an error and terminate. Also, the default value of CacheUpdateFrequency on the server has been lowered from anymore (user role setting can be found under Permissions tab). When trying to do so, you will face an error stating: ”Cannot add user: field ”roleid” is mandatory”. TimescaleDB 2.11 support Support for TimescaleDB

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909 13 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . variable overrides a scenario-level variable or the variables of the previous step. 9 5.1.4 Improved error logging Previously, when server or proxy performed web monitoring and there was a failure, it only only mentioned scenario and step names, for example: web scenario step "scenario:step" error: error doing curl_easy_perform: Couldn't resolve host name With templated web monitoring the need to know which

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . icons in listings Previously, green status icons were displayed in the last Error column of the item and trigger listings, for error-free entries, which could be misunderstood as if, on the contrary, the background. 5.10.15 Changes regarding multibyte string support Zabbix frontend now displays fatal error if mbstring PHP functions are not enabled. There are no string wrapper functions anymore; they have

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1542 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the Microsoft Teams webhook, hardcoded teams_endpoint check has been removed to prevent URL syntax error. PostgreSQL plugin • PostgreSQL plugin for Zabbix agent 2 now supports custom queries; • Unix socket parameters; it returns ’100.0’ with pfree. Previously in this case the item would return a not supported error with message ”Cannot be calculated because swap file size is 0.”. Frontend • If Zabbix web interface

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1719 14 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . has been introduced in the new version on the basis of an individual item. If previously any item error resulted in the item becoming unsupported, now it is possible to use a new preprocessing rule called value (in this case the item becomes supported and the value can be used in triggers) • set another error message 10 This preprocessing step can be used only once and it makes sense to have it as the first

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1805 14 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . log(4, JSON.stringify(object)) console.warn(object) Zabbix.log(3, JSON.stringify(object)) console.error(object) Zabbix.log(2, JSON.stringify(object)) XML object New JavaScript object XML has been added parameters; it returns ’100.0’ with pfree. Previously in this case the item would return a not supported error with message ”Cannot be calculated because swap file size is 0.”. Frontend • If Zabbix web interface