Ad Widget

**Markku** · 10-06-2024, 18:18

Configuration syncer seems to crash, and if I interpret the output (container?) correctly, you don't have CacheSize specified, which means to use the default of 32 MB. Have you tried setting it to something like 128 MB for a start and see if that makes a difference? If your configuration does not fit to the cache (I don't know if that would emit a clear error message or just cause a crash).

Markku

**M-Schmitt** · 11-06-2024, 08:36

Good Day,
i did set the cache size to 128MB and double of that, it did sadly change nothing.
Yes you are correct this is a Docker Container running on Ubuntu 24.04 LTS.

I did set the other Cache configurations higher as their default Value was, just to look if it would make any difference, but it didn't.

I put my Configuration file here too:

File Start:
__________________________________________________ _________________________________
# This is a configuration file for Zabbix server daemon
# To get more information about Zabbix, visit http://www.zabbix.com

############ GENERAL PARAMETERS #################

### Option: ListenPort
# Listen port for trapper.
#
# Mandatory: no
# Range: 1024-32767
# Default:
# ListenPort=10051

### Option: SourceIP
# Source IP address for outgoing connections.
#
# Mandatory: no
# Default:
# SourceIP=

### Option: LogType
# Specifies where log messages are written to:
# system - syslog
# file - file specified with LogFile parameter
# console - standard output
#
# Mandatory: no
# Default:
# LogType=file
LogType=console

### Option: LogFile
# Log file name for LogType 'file' parameter.
#
# Mandatory: yes, if LogType is set to file, otherwise no
# Default:
# LogFile=

### Option: LogFileSize
# Maximum size of log file in MB.
# 0 - disable automatic log rotation.
#
# Mandatory: no
# Range: 0-1024
# Default:
# LogFileSize=1

### Option: DebugLevel
# Specifies debug level:
# 0 - basic information about starting and stopping of Zabbix processes
# 1 - critical information
# 2 - error information
# 3 - warnings
# 4 - for debugging (produces lots of information)
# 5 - extended debugging (produces even more information)
#
# Mandatory: no
# Range: 0-5
# Default:
# DebugLevel=3

### Option: PidFile
# Name of PID file.
#
# Mandatory: no
# Default:
# PidFile=/tmp/zabbix_server.pid

### Option: SocketDir
# IPC socket directory.
# Directory to store IPC sockets used by internal Zabbix services.
#
# Mandatory: no
# Default:
# SocketDir=/tmp

### Option: DBHost
# Database host name.
# If set to localhost, socket is used for MySQL.
# If set to empty string, socket is used for PostgreSQL.
# If set to empty string, the Net Service Name connection method is used to connect to Oracle database; also see
# the TNS_ADMIN environment variable to specify the directory where the tnsnames.ora file is located.
#
# Mandatory: no
# Default:
# DBHost=localhost
DBHost=mysql-server

### Option: DBName
# Database name.
# If the Net Service Name connection method is used to connect to Oracle database, specify the service name from
# the tnsnames.ora file or set to empty string; also see the TWO_TASK environment variable if DBName is set to
# empty string.
#
# Mandatory: yes
# Default:
# DBName=

DBName=zabbix

### Option: DBSchema
# Schema name. Used for PostgreSQL.
#
# Mandatory: no
# Default:
# DBSchema=

### Option: DBUser
# Database user.
#
# Mandatory: no
# Default:
# DBUser=

DBUser=zabbix

### Option: DBPassword
# Database password.
# Comment this line if no password is used.
#
# Mandatory: no
# Default:
# DBPassword=
DBPassword=zabbix

### Option: DBSocket
# Path to MySQL socket.
#
# Mandatory: no
# Default:
# DBSocket=

### Option: DBPort
# Database port when not using local socket.
# If the Net Service Name connection method is used to connect to Oracle database, the port number from the
# tnsnames.ora file will be used. The port number set here will be ignored.
#
# Mandatory: no
# Range: 1024-65535
# Default:
# DBPort=
DBPort=3306

### Option: AllowUnsupportedDBVersions
# Allow server to work with unsupported database versions.
# 0 - do not allow
# 1 - allow
#
# Mandatory: no
# Default:
# AllowUnsupportedDBVersions=0

### Option: HistoryStorageURL
# History storage HTTP[S] URL.
#
# Mandatory: no
# Default:
# HistoryStorageURL=

### Option: HistoryStorageTypes
# Comma separated list of value types to be sent to the history storage.
#
# Mandatory: no
# Default:
# HistoryStorageTypes=uint,dbl,str,log,text

### Option: HistoryStorageDateIndex
# Enable preprocessing of history values in history storage to store values in different indices based on date.
# 0 - disable
# 1 - enable
#
# Mandatory: no
# Default:
# HistoryStorageDateIndex=0

### Option: ExportDir
# Directory for real time export of events, history and trends in newline delimited JSON format.
# If set, enables real time export.
#
# Mandatory: no
# Default:
# ExportDir=

### Option: ExportFileSize
# Maximum size per export file in bytes.
# Only used for rotation if ExportDir is set.
#
# Mandatory: no
# Range: 1M-1G
# Default:
# ExportFileSize=1G

### Option: ExportType
# List of comma delimited types of real time export - allows to control export entities by their
# type (events, history, trends) individually.
# Valid only if ExportDir is set.
#
# Mandatory: no
# Default:
# ExportType=events,history,trends

############ ADVANCED PARAMETERS ################

### Option: StartPollers
# Number of pre-forked instances of pollers.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartPollers=5

### Option: StartIPMIPollers
# Number of pre-forked instances of IPMI pollers.
# The IPMI manager process is automatically started when at least one IPMI poller is started.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartIPMIPollers=0

### Option: StartPreprocessors
# Number of pre-forked instances of preprocessing workers.
# The preprocessing manager process is automatically started when preprocessor worker is started.
#
# Mandatory: no
# Range: 1-1000
# Default:
# StartPreprocessors=3

### Option: StartPollersUnreachable
# Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java).
# At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers
# are started.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartPollersUnreachable=1

### Option: StartHistoryPollers
# Number of pre-forked instances of history pollers.
# Only required for calculated and internal checks.
# A database connection is required for each history poller instance.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartHistoryPollers=5

### Option: StartTrappers
# Number of pre-forked instances of trappers.
# Trappers accept incoming connections from Zabbix sender, active agents and active proxies.
# At least one trapper process must be running to display server availability and view queue
# in the frontend.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartTrappers=5

### Option: StartPingers
# Number of pre-forked instances of ICMP pingers.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartPingers=1

### Option: StartDiscoverers
# Number of pre-forked instances of discoverers.
#
# Mandatory: no
# Range: 0-250
# Default:
# StartDiscoverers=1

### Option: StartHTTPPollers
# Number of pre-forked instances of HTTP pollers.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartHTTPPollers=1

### Option: StartTimers
# Number of pre-forked instances of timers.
# Timers process maintenance periods.
# Only the first timer process handles host maintenance updates. Problem suppression updates are shared
# between all timers.
#
# Mandatory: no
# Range: 1-1000
# Default:
# StartTimers=1

### Option: StartEscalators
# Number of pre-forked instances of escalators.
#
# Mandatory: no
# Range: 1-100
# Default:
# StartEscalators=1

### Option: StartAlerters
# Number of pre-forked instances of alerters.
# Alerters send the notifications created by action operations.
#
# Mandatory: no
# Range: 1-100
# Default:
# StartAlerters=3

### Option: JavaGateway
# IP address (or hostname) of Zabbix Java gateway.
# Only required if Java pollers are started.
#
# Mandatory: no
# Default:
# JavaGateway=
JavaGateway=zabbix-java-gateway

### Option: JavaGatewayPort
# Port that Zabbix Java gateway listens on.
#
# Mandatory: no
# Range: 1024-32767
# Default:
# JavaGatewayPort=10052

### Option: StartJavaPollers
# Number of pre-forked instances of Java pollers.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartJavaPollers=0
StartJavaPollers=5

### Option: StartVMwareCollectors
# Number of pre-forked vmware collector instances.
#
# Mandatory: no
# Range: 0-250
# Default:
# StartVMwareCollectors=0

### Option: VMwareFrequency
# How often Zabbix will connect to VMware service to obtain a new data.
#
# Mandatory: no
# Range: 10-86400
# Default:
# VMwareFrequency=60

### Option: VMwarePerfFrequency
# How often Zabbix will connect to VMware service to obtain performance data.
#
# Mandatory: no
# Range: 10-86400
# Default:
# VMwarePerfFrequency=60

### Option: VMwareCacheSize
# Size of VMware cache, in bytes.
# Shared memory size for storing VMware data.
# Only used if VMware collectors are started.
#
# Mandatory: no
# Range: 256K-2G
# Default:
# VMwareCacheSize=8M

### Option: VMwareTimeout
# Specifies how many seconds vmware collector waits for response from VMware service.
#
# Mandatory: no
# Range: 1-300
# Default:
# VMwareTimeout=10

### Option: SNMPTrapperFile
# Temporary file used for passing data from SNMP trap daemon to the server.
# Must be the same as in zabbix_trap_receiver.pl or SNMPTT configuration file.
#
# Mandatory: no
# Default:
# SNMPTrapperFile=/tmp/zabbix_traps.tmp
SNMPTrapperFile=/var/lib/zabbix/snmptraps/snmptraps.log

### Option: StartSNMPTrapper
# If 1, SNMP trapper process is started.
#
# Mandatory: no
# Range: 0-1
# Default:
# StartSNMPTrapper=0
StartSNMPTrapper=1

### Option: ListenIP
# List of comma delimited IP addresses that the trapper should listen on.
# Trapper will listen on all network interfaces if this parameter is missing.
#
# Mandatory: no
# Default:
# ListenIP=0.0.0.0

### Option: HousekeepingFrequency
# How often Zabbix will perform housekeeping procedure (in hours).
# Housekeeping is removing outdated information from the database.
# To prevent Housekeeper from being overloaded, no more than 4 times HousekeepingFrequency
# hours of outdated information are deleted in one housekeeping cycle, for each item.
# To lower load on server startup housekeeping is postponed for 30 minutes after server start.
# With HousekeepingFrequency=0 the housekeeper can be only executed using the runtime control option.
# In this case the period of outdated information deleted in one housekeeping cycle is 4 times the
# period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.
#
# Mandatory: no
# Range: 0-24
# Default:
# HousekeepingFrequency=1

### Option: MaxHousekeeperDelete
# The table "housekeeper" contains "tasks" for housekeeping procedure in the format:
# [housekeeperid], [tablename], [field], [value].
# No more than 'MaxHousekeeperDelete' rows (corresponding to [tablename], [field], [value])
# will be deleted per one task in one housekeeping cycle.
# If set to 0 then no limit is used at all. In this case you must know what you are doing!
#
# Mandatory: no
# Range: 0-1000000
# Default:
# MaxHousekeeperDelete=5000

### Option: CacheSize
# Size of configuration cache, in bytes.
# Shared memory size for storing host, item and trigger data.
#
# Mandatory: no
# Range: 128K-64G
# Default:
# CacheSize=128MB
CacheSize=128M

### Option: CacheUpdateFrequency
# How often Zabbix will perform update of configuration cache, in seconds.
#
# Mandatory: no
# Range: 1-3600
# Default:
# CacheUpdateFrequency=60

### Option: StartDBSyncers
# Number of pre-forked instances of DB Syncers.
#
# Mandatory: no
# Range: 1-100
# Default:
# StartDBSyncers=4

### Option: HistoryCacheSize
# Size of history cache, in bytes.
# Shared memory size for storing history data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# HistoryCacheSize=128MB
HistoryCacheSize=128M

### Option: HistoryIndexCacheSize
# Size of history index cache, in bytes.
# Shared please increase CacheSizememory size for indexing history cache.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# HistoryIndexCacheSize=128MB
HistoryIndexCacheSize=128M

### Option: TrendCacheSize
# Size of trend write cache, in bytes.
# Shared memory size for storing trends data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# TrendCacheSize=128MB
TrendCacheSize=128M

### Option: TrendFunctionCacheSize
# Size of trend function cache, in bytes.
# Shared memory size for caching calculated trend function data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# TrendFunctionCacheSize=128MB
TrendFunctionCacheSize=128M

### Option: ValueCacheSize
# Size of history value cache, in bytes.
# Shared memory size for caching item history data requests.
# Setting to 0 disables value cache.
#
# Mandatory: no
# Range: 0,128K-64G
# Default:
# ValueCacheSize=128MB
ValueCacheSize=128M

### Option: Timeout
# Specifies how long we wait for agent, SNMP device or external check (in seconds).
#
# Mandatory: no
# Range: 1-30
# Default:
# Timeout=3

### Option: TrapperTimeout
# Specifies how many seconds trapper may spend processing new data.
#
# Mandatory: no
# Range: 1-300
# Default:
# TrapperTimeout=300

### Option: UnreachablePeriod
# After how many seconds of unreachability treat a host as unavailable.
#
# Mandatory: no
# Range: 1-3600
# Default:
# UnreachablePeriod=45

### Option: UnavailableDelay
# How often host is checked for availability during the unavailability period, in seconds.
#
# Mandatory: no
# Range: 1-3600
# Default:
# UnavailableDelay=60

### Option: UnreachableDelay
# How often host is checked for availability during the unreachability period, in seconds.
#
# Mandatory: no
# Range: 1-3600
# Default:
# UnreachableDelay=15

### Option: AlertScriptsPath
# Full path to location of custom alert scripts.
# Default depends on compilation options.
# To see the default path run command "zabbix_server --help".
#
# Mandatory: no
# Default:
# AlertScriptsPath=${datadir}/zabbix/alertscripts
AlertScriptsPath=/usr/lib/zabbix/alertscripts

### Option: ExternalScripts
# Full path to location of external scripts.
# Default depends on compilation options.
# To see the default path run command "zabbix_server --help".
#
# Mandatory: no
# Default:
# ExternalScripts=${datadir}/zabbix/externalscripts
ExternalScripts=/usr/lib/zabbix/externalscripts

### Option: FpingLocation
# Location of fping.
# Make sure that fping binary has root ownership and SUID flag set.
#
# Mandatory: no
# Default:
# FpingLocation=/usr/sbin/fping
FpingLocation=/usr/bin/fping

### Option: Fping6Location
# Location of fping6.
# Make sure that fping6 binary has root ownership and SUID flag set.
# Make empty if your fping utility is capable to process IPv6 addresses.
#
# Mandatory: no
# Default:
# Fping6Location=/usr/sbin/fping6

### Option: SSHKeyLocation
# Location of public and private keys for SSH checks and actions.
#
# Mandatory: no
# Default:
# SSHKeyLocation=
SSHKeyLocation=/var/lib/zabbix/ssh_keys

### Option: LogSlowQueries
# How long a database query may take before being logged (in milliseconds).
# Only works if DebugLevel set to 3, 4 or 5.
# 0 - don't log slow queries.
#
# Mandatory: no
# Range: 1-3600000
# Default:
# LogSlowQueries=0

### Option: TmpDir
# Temporary directory.
#
# Mandatory: no
# Default:
# TmpDir=/tmp

### Option: StartProxyPollers
# Number of pre-forked instances of pollers for passive proxies.
#
# Mandatory: no
# Range: 0-250
# Default:
# StartProxyPollers=1

### Option: ProxyConfigFrequency
# How often Zabbix Server sends configuration data to a Zabbix Proxy in seconds.
# This parameter is used only for proxies in the passive mode.
#
# Mandatory: no
# Range: 1-3600*24*7
# Default:
# ProxyConfigFrequency=3600

### Option: ProxyDataFrequency
# How often Zabbix Server requests history data from a Zabbix Proxy in seconds.
# This parameter is used only for proxies in the passive mode.
#
# Mandatory: no
# Range: 1-3600
# Default:
# ProxyDataFrequency=1

### Option: StartLLDProcessors
# Number of pre-forked instances of low level discovery processors.
#
# Mandatory: no
# Range: 1-100
# Default:
# StartLLDProcessors=2

### Option: AllowRoot
# Allow the server to run as 'root'. If disabled and the server is started by 'root', the server
# will try to switch to the user specified by the User configuration option instead.
# Has no effect if started under a regular user.
# 0 - do not allow
# 1 - allow
#
# Mandatory: no
# Default:
# AllowRoot=0

### Option: User
# Drop privileges to a specific, existing user on the system.
# Only has effect if run as 'root' and AllowRoot is disabled.
#
# Mandatory: no
# Default:
# User=zabbix
User=zabbix

### Option: Include
# You may include individual files or all files in a directory in the configuration file.
# Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.
#
# Mandatory: no
# Default:
# Include=

# Include=/usr/local/etc/zabbix_server.general.conf
# Include=/usr/local/etc/zabbix_server.conf.d/
# Include=/usr/local/etc/zabbix_server.conf.d/*.conf

### Option: SSLCertLocation
# Location of SSL client certificates.
# This parameter is used only in web monitoring.
# Default depends on compilation options.
# To see the default path run command "zabbix_server --help".
#
# Mandatory: no
# Default:
# SSLCertLocation=${datadir}/zabbix/ssl/certs
SSLCertLocation=/var/lib/zabbix/ssl/certs/

### Option: SSLKeyLocation
# Location of private keys for SSL client certificates.
# This parameter is used only in web monitoring.
# Default depends on compilation options.
# To see the default path run command "zabbix_server --help".
#
# Mandatory: no
# Default:
# SSLKeyLocation=${datadir}/zabbix/ssl/keys
SSLKeyLocation=/var/lib/zabbix/ssl/keys/

### Option: SSLCALocation
# Override the location of certificate authority (CA) files for SSL server certificate verification.
# If not set, system-wide directory will be used.
# This parameter is used in web monitoring, SMTP authentication, HTTP agent items and for communication with Vault.
#
# Mandatory: no
# Default:
# SSLCALocation=
SSLCALocation=/var/lib/zabbix/ssl/ssl_ca/

### Option: StatsAllowedIP
# List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances.
# Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests
# will be accepted.
# If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally
# and '::/0' will allow any IPv4 or IPv6 address.
# '0.0.0.0/0' can be used to allow any IPv4 address.
# Example: StatsAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com
#
# Mandatory: no
# Default:
# StatsAllowedIP=

####### LOADABLE MODULES #######

### Option: LoadModulePath
# Full path to location of server modules.
# Default depends on compilation options.
# To see the default path run command "zabbix_server --help".
#
# Mandatory: no
# Default:
# LoadModulePath=${libdir}/modules
LoadModulePath=/var/lib/zabbix/modules/

### Option: LoadModule
# Module to load at server startup. Modules are used to extend functionality of the server.
# Formats:
# LoadModule=<module.so>
# LoadModule=<path/module.so>
# LoadModule=</abs_path/module.so>
# Either the module must be located in directory specified by LoadModulePath or the path must precede the module name.
# If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.
# It is allowed to include multiple LoadModule parameters.
#
# Mandatory: no
# Default:
# LoadModule=

####### TLS-RELATED PARAMETERS #######

### Option: TLSCAFile
# Full pathname of a file containing the top-level CA(s) certificates for
# peer certificate verification.
#
# Mandatory: no
# Default:
# TLSCAFile=

### Option: TLSCRLFile
# Full pathname of a file containing revoked certificates.
#
# Mandatory: no
# Default:
# TLSCRLFile=

### Option: TLSCertFile
# Full pathname of a file containing the server certificate or certificate chain.
#
# Mandatory: no
# Default:
# TLSCertFile=

### Option: TLSKeyFile
# Full pathname of a file containing the server private key.
#
# Mandatory: no
# Default:
# TLSKeyFile=

####### For advanced users - TLS ciphersuite selection criteria #######

### Option: TLSCipherCert13
# Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3.
# Override the default ciphersuite selection criteria for certificate-based encryption.
#
# Mandatory: no
# Default:
# TLSCipherCert13=

### Option: TLSCipherCert
# GnuTLS priority string or OpenSSL (TLS 1.2) cipher string.
# Override the default ciphersuite selection criteria for certificate-based encryption.
# Example for GnuTLS:
# NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509
# Example for OpenSSL:
# EECDH+aRSA+AES128:RSA+aRSA+AES128
#
# Mandatory: no
# Default:
# TLSCipherCert=

### Option: TLSCipherPSK13
# Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3.
# Override the default ciphersuite selection criteria for PSK-based encryption.
# Example:
# TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA25 6
#
# Mandatory: no
# Default:
# TLSCipherPSK13=

### Option: TLSCipherPSK
# GnuTLS priority string or OpenSSL (TLS 1.2) cipher string.
# Override the default ciphersuite selection criteria for PSK-based encryption.
# Example for GnuTLS:
# NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL
# Example for OpenSSL:
# kECDHEPSK+AES128:kPSK+AES128
#
# Mandatory: no
# Default:
# TLSCipherPSK=

### Option: TLSCipherAll13
# Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3.
# Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.
# Example:
# TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA25 6:TLS_AES_128_GCM_SHA256
#
# Mandatory: no
# Default:
# TLSCipherAll13=

### Option: TLSCipherAll
# GnuTLS priority string or OpenSSL (TLS 1.2) cipher string.
# Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.
# Example for GnuTLS:
# NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509
# Example for OpenSSL:
# EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128 :kPSK+AES128
#
# Mandatory: no
# Default:
# TLSCipherAll=

### Option: DBTLSConnect
# Setting this option enforces to use TLS connection to database.
# required - connect using TLS
# verify_ca - connect using TLS and verify certificate
# verify_full - connect using TLS, verify certificate and verify that database identity specified by DBHost
# matches its certificate
# On MySQL starting from 5.7.11 and PostgreSQL following values are supported: "required", "verify_ca" and
# "verify_full".
# On MariaDB starting from version 10.2.6 "required" and "verify_full" values are supported.
# Default is not to set any option and behavior depends on database configuration
#
# Mandatory: no
# Default:
# DBTLSConnect=

### Option: DBTLSCAFile
# Full pathname of a file containing the top-level CA(s) certificates for database certificate verification.
# Supported only for MySQL and PostgreSQL
#
# Mandatory: no
# (yes, if DBTLSConnect set to one of: verify_ca, verify_full)
# Default:
# DBTLSCAFile=

### Option: DBTLSCertFile
# Full pathname of file containing Zabbix server certificate for authenticating to database.
# Supported only for MySQL and PostgreSQL
#
# Mandatory: no
# Default:
# DBTLSCertFile=

### Option: DBTLSKeyFile
# Full pathname of file containing the private key for authenticating to database.
# Supported only for MySQL and PostgreSQL
#
# Mandatory: no
# Default:
# DBTLSKeyFile=

### Option: DBTLSCipher
# The list of encryption ciphers that Zabbix server permits for TLS protocols up through TLSv1.2
# Supported only for MySQL
#
# Mandatory no
# Default:
# DBTLSCipher=

### Option: DBTLSCipher13
# The list of encryption ciphersuites that Zabbix server permits for TLSv1.3 protocol
# Supported only for MySQL, starting from version 8.0.16
#
# Mandatory no
# Default:
# DBTLSCipher13=

### Option: VaultToken
# Vault authentication token that should have been generated exclusively for Zabbix server with read only permission
# to paths specified in Vault macros and read only permission to path specified in optional VaultDBPath
# configuration parameter.
# It is an error if VaultToken and VAULT_TOKEN environment variable are defined at the same time.
#
# Mandatory: no
# Default:
# VaultToken=

### Option: VaultURL
# Vault server HTTP[S] URL. System-wide CA certificates directory will be used if SSLCALocation is not specified.
#
# Mandatory: no
# Default:
# VaultURL=https://127.0.0.1:8200

### Option: VaultDBPath
# Vault path from where credentials for database will be retrieved by keys 'password' and 'username'.
# Example: secret/zabbix/database
# This option can only be used if DBUser and DBPassword are not specified.
#
# Mandatory: no
# Default:
# VaultDBPath=

### Option: StartReportWriters
# Number of pre-forked report writer instances.
#
# Mandatory: no
# Range: 0-100
# Default:
# StartReportWriters=0

### Option: WebServiceURL
# URL to Zabbix web service, used to perform web related tasks.
# Example: http://localhost:10053/report
#
# Mandatory: no
# Default:
# WebServiceURL=
WebServiceURL=http://zabbix-web-service:10053/report

### Option: ServiceManagerSyncFrequency
# How often Zabbix will synchronize configuration of a service manager (in seconds).
#
# Mandatory: no
# Range: 1-3600
# Default:
# ServiceManagerSyncFrequency=60

### Option: ProblemHousekeepingFrequency
# How often Zabbix will delete problems for deleted triggers (in seconds).
#
# Mandatory: no
# Range: 1-3600
# Default:
# ProblemHousekeepingFrequency=60

## Option: StartODBCPollers
# Number of pre-forked ODBC poller instances.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartODBCPollers=1

####### For advanced users - TCP-related fine-tuning parameters #######

## Option: ListenBacklog
# The maximum number of pending connections in the queue. This parameter is passed to
# listen() function as argument 'backlog' (see "man listen").
#
# Mandatory: no
# Range: 0 - INT_MAX (depends on system, too large values may be silently truncated to implementation-specified maximum)
# Default: SOMAXCONN (hard-coded constant, depends on system)
# ListenBacklog=

####### High availability cluster parameters #######

## Option: HANodeName
# The high availability cluster node name.
# When empty, server is working in standalone mode; a node with empty name is registered with address for the frontend to connect to.
#
# Mandatory: no
# Default:
# HANodeName=

## Option: NodeAddress
# IP or hostname with optional port to specify how frontend should connect to the server.
# Format: <address>[:<port>]
#
# If IP or hostname is not set, then ListenIP value will be used. In case ListenIP is not set, localhost will be used.
# If port is not set, then ListenPort value will be used. In case ListenPort is not set, 10051 will be used.
# This option can be overridden by address specified in frontend configuration.
#
# Mandatory: no
# Default:
# NodeAddress=localhost:10051
__________________________________________________ __________________________________________________ ____
File End

Best regards Michael

**M-Schmitt** · 11-06-2024, 08:38

F.y.i. i did write 128MB, but i didn't work so i changed it to 128M, to see if something happens.
And my Server got the following stats:
VCPU: 4
RAM: 8GB
DISK LOKAL: 160 GB

**tim.mooney** · 11-06-2024, 08:41

Originally posted by M-Schmitt

after succesfully upgrading zabbix from 5.0 to 6.0, the server is crashing.

In short on the upgrade:
- Was a hellish task
- Had to delete/create/etc. a lot on Tables/Columns/etc...

I posit that your problems with Zabbix crashing now are all because you did not have a successful upgrade. If you were manually modifying tables, columns, etc. as part of the upgrade, you likely have a database schema that doesn't match what Zabbix is expecting.

You should compare your existing database schema to what would have been created if you had fresh-installed Zabbix 6.0.x instead and see where there may be differences. It's highly likely those differences are causing problems.

**M-Schmitt** · 11-06-2024, 09:20

Thank you very much for the prompt reply.
Could you possibly let me know where I can find such a schema?
Best regards and many thanks, Michael

**M-Schmitt** · 11-06-2024, 14:19

Good Day,

i compared my DB Schema with the Schema from the Version 6.0.x. Had to change a lot of keys which were wrong or not there.

After changing them all succesfully i now get this error messages.

The Error Messages tell me that there are Unkown, but when i look up the tables the Columns are there and in the comparison DB file.

I tried to delete it without any success.

And i have a problem understanding the last error message ('Bad operator (INTEGER): At line 73 in /var/lib/mibs/ietf/SNMPv2-PDU ').

Thank you in advance Michael

Bad operator (INTEGER): At line 73 in /var/lib/mibs/ietf/SNMPv2-PDU

211:20240611:095148.335 Zabbix agent item "system.swap.size[,free]" on host "Zabbix server" failed: first network error, wait for 15 seconds

216:20240611:095203.422 Zabbix agent item "system.cpu.util[,system]" on host "Zabbix server" failed: another network error, wait for 15 seconds

216:20240611:095218.436 Zabbix agent item "system.swap.size[,total]" on host "Zabbix server" failed: another network error, wait for 15 seconds

216:20240611:095233.447 temporarily disabling Zabbix agent checks on host "Zabbix server": interface unavailable

193:20240611:102131.287 executing housekeeper

193:20240611:102132.963 housekeeper [deleted 0 hist/trends, 0 items/triggers, 22932 events, 0 problems, 0 sessions, 0 alarms, 0 audit, 116 autoreg_host, 0 records in 1.666842 sec, idle for 1 hour(s)]

192:20240611:103525.146 [Z3005] query failed: [1054] Unknown column 'i.username' in 'field list' [select i.itemid,i.name,i.key_,i.type,i.value_type,i.delay ,i.history,i.trends,i.status,i.trapper_hosts,i.uni ts,i.formula,i.logtimefmt,i.valuemapid,i.params,i. ipmi_sensor,i.snmp_oid,i.authtype,i.username,i.pas sword,i.publickey,i.privatekey,i.description,i.int erfaceid,i.jmx_endpoint,i.master_itemid,i.timeout, i.url,i.query_fields,i.posts,i.status_codes,i.foll ow_redirects,i.post_type,i.http_proxy,i.headers,i. retrieve_mode,i.request_method,i.output_format,i.s sl_cert_file,i.ssl_key_file,i.ssl_key_password,i.v erify_peer,i.verify_host,i.allow_traps,i.discover from items i,item_discovery id where i.itemid=id.itemid and id.parent_itemid=39807]

181:20240611:103537.961 [Z3005] query failed: [1054] Unknown column 'i.username' in 'field list' [select i.itemid,i.hostid,i.status,i.type,i.value_type,i.k ey_,i.snmp_oid,i.ipmi_sensor,i.delay,i.trapper_hos ts,i.logtimefmt,i.params,ir.state,i.authtype,i.use rname,i.password,i.publickey,i.privatekey,i.flags, i.interfaceid,ir.lastlogsize,ir.mtime,i.history,i. trends,i.inventory_link,i.valuemapid,i.units,ir.er ror,i.jmx_endpoint,i.master_itemid,i.timeout,i.url ,i.query_fields,i.posts,i.status_codes,i.follow_re directs,i.post_type,i.http_proxy,i.headers,i.retri eve_mode,i.request_method,i.output_format,i.ssl_ce rt_file,i.ssl_key_file,i.ssl_key_password,i.verify _peer,i.verify_host,i.allow_traps,i.templateid,nul l from items i join item_rtdata ir on i.itemid=ir.itemid inner join hosts h on i.hostid=h.hostid where (h.status=0 or h.status=1) and (i.flags=0 or i.flags=1 or i.flags=4)]

zabbix_server [181]: ERROR [file and function: <dbconfig.c,DCsync_configuration>, revision:680df72, line:6783] Something impossible has just happened.

181:20240611:103537.961 === Backtrace: ===

181:20240611:103537.961 9: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.127737 sec, syncing configuration](zbx_backtrace+0x58) [0x64068043a518]

181:20240611:103537.961 8: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.127737 sec, syncing configuration](DCsync_configuration+0x1162) [0x6406803e6192]

181:20240611:103537.961 7: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.127737 sec, syncing configuration](dbconfig_thread+0x362) [0x6406802cc492]

181:20240611:103537.961 6: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.127737 sec, syncing configuration](zbx_thread_start+0x24) [0x64068043cad4]

181:20240611:103537.961 5: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.127737 sec, syncing configuration](+0x7656e) [0x6406802bd56e]

181:20240611:103537.961 4: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.127737 sec, syncing configuration](MAIN_ZABBIX_ENTRY+0x6fb) [0x6406802be43b]

181:20240611:103537.961 3: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.127737 sec, syncing configuration](main+0x547) [0x6406802b5437]

181:20240611:103537.961 2: /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7a1734180d90]

181:20240611:103537.961 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7a1734180e40]

181:20240611:103537.961 0: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.127737 sec, syncing configuration](_start+0x25) [0x6406802bc785]

180:20240611:111337.728 [Z3005] query failed: [1054] Unknown column 'propagation_rule' in 'field list' [select serviceid,status,algorithm,name,weight,propagation _rule,propagation_value from services]

193:20240611:112133.063 executing housekeeper

193:20240611:112133.593 housekeeper [deleted 0 hist/trends, 0 items/triggers, 22925 events, 0 problems, 0 sessions, 0 alarms, 0 audit, 0 autoreg_host, 0 records in 0.521663 sec, idle for 1 hour(s)]

7:20240611:114636.497 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:1997,re ason:0]. Exiting ...

179:20240611:114637.100 HA manager has been paused

199:20240611:114637.101 syncing history data in progress...

199:20240611:114637.101 syncing history data done

179:20240611:114638.140 HA manager has been stopped

7:20240611:114638.213 syncing trend data...

7:20240611:114638.220 syncing trend data done

7:20240611:114638.224 Zabbix Server stopped. Zabbix 6.0.30 (revision 680df72).

** Preparing Zabbix server

** Preparing database

** Using MYSQL_USER variable from secret file

** Using MYSQL_PASSWORD variable from secret file

********************

* DB_SERVER_HOST: mysql-server

* DB_SERVER_PORT: 3306

* DB_SERVER_DBNAME: zabbix

********************

** Database 'zabbix' already exists. Please be careful with database COLLATE!

** Table 'zabbix.dbversion' already exists.

** Preparing Zabbix server configuration file

** Updating '/etc/zabbix/zabbix_server.conf' parameter "ListenIP": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "ListenPort": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "ListenBacklog": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "SourceIP": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "LogType": 'console'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "LogFile": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "LogFileSize": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "PidFile": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "DebugLevel": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "DBHost": 'mysql-server'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "DBPort": '3306'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "DBSocket": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "DBName": 'zabbix'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "DBSchema": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "VaultDBPath": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "VaultURL": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "DBUser": 'zabbix'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "DBPassword": '****'. Enable DEBUG_MODE to view value ...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "AllowUnsupportedDBVersions": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartReportWriters": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "WebServiceURL": 'http://zabbix-web-service:10053/report'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "HistoryStorageURL": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "HistoryStorageTypes": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "HistoryStorageDateIndex": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StatsAllowedIP": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartPollers": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartIPMIPollers": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartPollersUnreachable": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartTrappers": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartPingers": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartDiscoverers": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartHistoryPollers": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartHTTPPollers": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartODBCPollers": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartPreprocessors": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartTimers": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartEscalators": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartAlerters": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartTimers": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartEscalators": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartLLDProcessors": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "JavaGateway": 'zabbix-java-gateway'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "JavaGatewayPort": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartJavaPollers": '5'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartVMwareCollectors": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "VMwareFrequency": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "VMwarePerfFrequency": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "VMwareCacheSize": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "VMwareTimeout": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "SNMPTrapperFile": '/var/lib/zabbix/snmptraps/snmptraps.log'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartSNMPTrapper": '1'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "HousekeepingFrequency": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "MaxHousekeeperDelete": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "ProblemHousekeepingFrequency": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "CacheSize": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "CacheUpdateFrequency": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartDBSyncers": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "HistoryCacheSize": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "HistoryIndexCacheSize": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TrendCacheSize": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TrendFunctionCacheSize": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "ValueCacheSize": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "Timeout": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TrapperTimeout": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "UnreachablePeriod": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "UnavailableDelay": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "UnreachableDelay": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "AlertScriptsPath": '/usr/lib/zabbix/alertscripts'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "ExternalScripts": '/usr/lib/zabbix/externalscripts'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "FpingLocation": '/usr/bin/fping'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "Fping6Location": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "SSHKeyLocation": '/var/lib/zabbix/ssh_keys'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "LogSlowQueries": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "StartProxyPollers": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "ProxyConfigFrequency": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "ProxyDataFrequency": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "SSLCertLocation": '/var/lib/zabbix/ssl/certs/'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "SSLKeyLocation": '/var/lib/zabbix/ssl/keys/'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "SSLCALocation": '/var/lib/zabbix/ssl/ssl_ca/'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "LoadModulePath": '/var/lib/zabbix/modules/'...updated

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCAFile": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCRLFile": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCertFile": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCipherAll": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCipherAll13": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCipherCert": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCipherCert13": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCipherPSK": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSCipherPSK13": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSKeyFile": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSPSKIdentity": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "TLSPSKFile": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "ServiceManagerSyncFrequency": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "HANodeName": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "NodeAddress": ''...removed

** Updating '/etc/zabbix/zabbix_server.conf' parameter "User": 'zabbix'...updated

Starting Zabbix Server. Zabbix 6.0.30 (revision 680df72).

Press Ctrl+C to exit.

7:20240611:114643.469 Starting Zabbix Server. Zabbix 6.0.30 (revision 680df72).

7:20240611:114643.469 ****** Enabled features ******

7:20240611:114643.469 SNMP monitoring: YES

7:20240611:114643.469 IPMI monitoring: YES

7:20240611:114643.469 Web monitoring: YES

7:20240611:114643.469 VMware monitoring: YES

7:20240611:114643.469 SMTP authentication: YES

7:20240611:114643.469 ODBC: YES

7:20240611:114643.469 SSH support: YES

7:20240611:114643.469 IPv6 support: YES

7:20240611:114643.469 TLS support: YES

7:20240611:114643.469 ******************************

7:20240611:114643.469 using configuration file: /etc/zabbix/zabbix_server.conf

7:20240611:114643.520 current database version (mandatory/optional): 06000000/06000044

7:20240611:114643.520 required mandatory version: 06000000

7:20240611:114643.541 database could be upgraded to use primary keys in history tables

179:20240611:114643.561 starting HA manager

179:20240611:114643.572 HA manager started in active mode

7:20240611:114643.573 server #0 started [main process]

180:20240611:114643.573 server #1 started [service manager #1]

181:20240611:114643.574 server #2 started [configuration syncer #1]

182:20240611:114643.696 server #3 started [alert manager #1]

183:20240611:114643.696 server #4 started [alerter #1]

184:20240611:114643.697 server #5 started [alerter #2]

185:20240611:114643.697 server #6 started [alerter #3]

186:20240611:114643.698 server #7 started [preprocessing manager #1]

187:20240611:114643.698 server #8 started [preprocessing worker #1]

188:20240611:114643.699 server #9 started [preprocessing worker #2]

189:20240611:114643.699 server #10 started [preprocessing worker #3]

190:20240611:114643.700 server #11 started [lld manager #1]

191:20240611:114643.701 server #12 started [lld worker #1]

192:20240611:114643.701 server #13 started [lld worker #2]

193:20240611:114643.702 server #14 started [housekeeper #1]

194:20240611:114643.703 server #15 started [timer #1]

195:20240611:114643.706 server #16 started [http poller #1]

196:20240611:114643.706 server #17 started [discoverer #1]

197:20240611:114643.733 server #18 started [history syncer #1]

199:20240611:114643.736 server #20 started [history syncer #3]

202:20240611:114643.740 server #23 started [java poller #1]

198:20240611:114643.740 server #19 started [history syncer #2]

200:20240611:114643.740 server #21 started [history syncer #4]

203:20240611:114643.741 server #24 started [java poller #2]

201:20240611:114643.741 server #22 started [escalator #1]

204:20240611:114643.742 server #25 started [java poller #3]

205:20240611:114643.749 server #26 started [java poller #4]

207:20240611:114643.750 server #28 started [snmp trapper #1]

206:20240611:114643.751 server #27 started [java poller #5]

208:20240611:114643.753 server #29 started [proxy poller #1]

209:20240611:114643.835 server #30 started [self-monitoring #1]

210:20240611:114643.835 server #31 started [task manager #1]

211:20240611:114643.844 server #32 started [poller #1]

212:20240611:114643.848 server #33 started [poller #2]

213:20240611:114643.850 server #34 started [poller #3]

214:20240611:114643.852 server #35 started [poller #4]

217:20240611:114643.856 server #38 started [trapper #1]

218:20240611:114643.858 server #39 started [trapper #2]

215:20240611:114643.858 server #36 started [poller #5]

216:20240611:114643.933 server #37 started [unreachable poller #1]

219:20240611:114643.937 server #40 started [trapper #3]

220:20240611:114643.939 server #41 started [trapper #4]

221:20240611:114643.939 server #42 started [trapper #5]

222:20240611:114643.942 server #43 started [icmp pinger #1]

224:20240611:114643.944 server #45 started [history poller #1]

223:20240611:114643.945 server #44 started [alert syncer #1]

225:20240611:114643.948 server #46 started [history poller #2]

226:20240611:114643.950 server #47 started [history poller #3]

227:20240611:114643.952 server #48 started [history poller #4]

228:20240611:114644.033 server #49 started [history poller #5]

230:20240611:114644.036 server #51 started [trigger housekeeper #1]

229:20240611:114644.040 server #50 started [availability manager #1]

231:20240611:114644.046 server #52 started [odbc poller #1]

Bad operator (INTEGER): At line 73 in /var/lib/mibs/ietf/SNMPv2-PDU

**tim.mooney** · 12-06-2024, 21:39

Originally posted by M-Schmitt

i compared my DB Schema with the Schema from the Version 6.0.x. Had to change a lot of keys which were wrong or not there.
After changing them all succesfully i now get this error messages.

192:20240611:103525.146 [Z3005] query failed: [1054] Unknown column 'i.username' in 'field list' [select i.itemid,i.name,i.key_,i.type,i.value_type,i.delay ,i.history,i.trends,i.status,i.trapper_hosts,i.uni ts,i.formula,i.logtimefmt,i.valuemapid,i.params,i. ipmi_sensor,i.snmp_oid,i.authtype,i.username,i.pas sword,i.publickey,i.privatekey,i.description,i.int erfaceid,i.jmx_endpoint,i.master_itemid,i.timeout, i.url,i.query_fields,i.posts,i.status_codes,i.foll ow_redirects,i.post_type,i.http_proxy,i.headers,i. retrieve_mode,i.request_method,i.output_format,i.s sl_cert_file,i.ssl_key_file,i.ssl_key_password,i.v erify_peer,i.verify_host,i.allow_traps,i.discover from items i,item_discovery id where i.itemid=id.itemid and id.parent_itemid=39807]

181:20240611:103537.961 [Z3005] query failed: [1054] Unknown column 'i.username' in 'field list' [select i.itemid,i.hostid,i.status,i.type,i.value_type,i.k ey_,i.snmp_oid,i.ipmi_sensor,i.delay,i.trapper_hos ts,i.logtimefmt,i.params,ir.state,i.authtype,i.use rname,i.password,i.publickey,i.privatekey,i.flags, i.interfaceid,ir.lastlogsize,ir.mtime,i.history,i. trends,i.inventory_link,i.valuemapid,i.units,ir.er ror,i.jmx_endpoint,i.master_itemid,i.timeout,i.url ,i.query_fields,i.posts,i.status_codes,i.follow_re directs,i.post_type,i.http_proxy,i.headers,i.retri eve_mode,i.request_method,i.output_format,i.ssl_ce rt_file,i.ssl_key_file,i.ssl_key_password,i.verify _peer,i.verify_host,i.allow_traps,i.templateid,nul l from items i join item_rtdata ir on i.itemid=ir.itemid inner join hosts h on i.hostid=h.hostid where (h.status=0 or h.status=1) and (i.flags=0 or i.flags=1 or i.flags=4)]

You're still missing things in your schema that should have been created by the automated upgrade process.

Since it appears that you're using MySQL or a MySQL-compatible database server, you might want to consider taking the database schema file for your version of Zabbix and creating a new database with a different name, maybe something like zabbix_correct, then import the schema into that second database so all the tables and objects are created. Once you have this second database with known good schema, you can use a tool like 'mysqldiff' to compare your existing database to the temporary database with the correct schema. That may help you find additional areas where your database doesn't match what it should be.

However, if columns, relations, or entire tables were missing and you manually created them, isn't it also possible that your data is now incorrect or incomplete? I would worry that even if you manage to "fix" your database so it has all the tables, columns, indexes, etc. that Zabbix expects, it might still be possible that the data in those tables is not correct or complete.

My advice would be to figure out why you had problems upgrading from 5.0, fix those problems and re-do the upgrade so that the automated database upgrade works correctly.

Ad Widget

After Upgrading from 5.0 to 6.0 crashing server

After Upgrading from 5.0 to 6.0 crashing server

Comment

Comment

Comment

Comment

Comment

Comment

Comment