Zabbix server not runing

[FildaSmile]

Hello,

i wanted upgrade my zabbix 4.4 to 5.0 so i stoppad the service with "/etc/init.d/zabbix-server stop" but afterwards my planns changed and i realized that i will stay with 4.4 so i decided to turn zabbix on but now i cant recieve data and zabbix front end telling that zabbix server not running:

zabbix@zabbix-virtual-machine:~$ service zabbix-server status
● zabbix-server.service - LSB: Start zabbix-server daemon
Loaded: loaded (/etc/init.d/zabbix-server; generated)
Active: active (exited) since Fri 2020-05-22 14:20:42 CEST; 11s ago
Docs: man:systemd-sysv-generator(8)
Process: 1892 ExecStop=/etc/init.d/zabbix-server stop (code=exited, status=0/SUCCESS)
Process: 1893 ExecStart=/etc/init.d/zabbix-server start (code=exited, status=0/SUCCESS)

mag 22 14:20:42 zabbix-virtual-machine systemd[1]: Starting LSB: Start zabbix-server daemon...
mag 22 14:20:42 zabbix-virtual-machine systemd[1]: Started LSB: Start zabbix-server daemon.

I tried "/etc/init.d/zabbix-server start" and also "service zabbix-server start" but nothing changed, i still dont recieve any data, can you please help how solve this issue ? i have no idea what happen.

Filip

[aib]

Did you check zabbix server .LOG file for any errors?
It is typically in /var/log/zabbix/zabbix_server.log

[FildaSmile]

yes here is last few rows:

2669:20200522:112716.950 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exit$
2679:20200522:112716.950 syncing history data in progress...
2679:20200522:112716.953 syncing history data... 100.000000%
2679:20200522:112716.953 syncing history data done
2669:20200522:112716.997 syncing trend data...
2669:20200522:112717.251 syncing trend data done
2669:20200522:112717.253 Zabbix Server stopped. Zabbix 4.4.6 (revision 8cc702429d).

[aib]

well, do you mind to check some lines before? That last lines showing the final steps of shutting down Zabbix Server.
In previous lines I hope to see the error message explaining WHY zabbix server is shutting down

[FildaSmile]

There are more lines, before i tried fix issues with fping because it didnt work.

2699:20200522:112156.044 Error of query maxQueryMetrics: 'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted..
2695:20200522:112256.888 Error of query maxQueryMetrics: 'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted..
2678:20200522:112301.659 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.write[{$URL},{HOST.HOST},ESXi_1_boot,latency]" became not supported: Performance counter data$
2676:20200522:112302.660 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.write[{$URL},{HOST.HOST},Local_Datastore_ESXi1,latency]" became not supported: Performance co$
2679:20200522:112303.661 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.write[{$URL},{HOST.HOST},Prod_Datastore_2200v3,latency]" became not supported: Performance co$
2677:20200522:112304.661 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.write[{$URL},{HOST.HOST},Test_Datastore_2200v3,latency]" became not supported: Performance co$
2678:20200522:112305.663 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.read[{$URL},{HOST.HOST},Backup_Datastore_2200v3_veeam,l atency]" became not supported: Perform$
2679:20200522:112306.664 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.read[{$URL},{HOST.HOST},ESXi_2_boot,latency]" became not supported: Performance counter data $
2677:20200522:112307.665 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.read[{$URL},{HOST.HOST},Local_Datastore_ESXi2,latency]" became not supported: Performance cou$
2678:20200522:112308.666 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.read[{$URL},{HOST.HOST},Prod_Datastore_2200v3,latency]" became not supported: Performance cou$
2678:20200522:112308.666 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.read[{$URL},Kamery_Datastore_2200v3,latency]" became not supported: Performance counter data is $
2676:20200522:112309.667 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.read[{$URL},{HOST.HOST},Test_Datastore_2200v3,latency]" became not supported: Performance cou$
2679:20200522:112310.668 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.write[{$URL},Kamery_Datastore_2200v3,latency]" became not supported: Performance counter data is$
2679:20200522:112314.672 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.read[{$URL},Backup_Datastore_2200v3_veeam,latency]" became not supported: Performance counter da$
2676:20200522:112315.673 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.read[{$URL},{HOST.HOST},Kamery_Datastore_2200v3,latency]" became not supported: Performance c$
2676:20200522:112315.673 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.read[{$URL},ESXi_1_boot,latency]" became not supported: Performance counter data is not availabl$
2677:20200522:112316.674 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.read[{$URL},ESXi_2_boot,latency]" became not supported: Performance counter data is not availabl$
2679:20200522:112319.677 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.read[{$URL},Local_Datastore_ESXi1,latency]" became not supported: Performance counter data is no$
2679:20200522:112319.677 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.write[{$URL},{HOST.HOST},Kamery_Datastore_2200v3,latency]" became not supported: Performance $
2679:20200522:112319.677 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.write[{$URL},{HOST.HOST},Backup_Datastore_2200v3_veeam,l atency]" became not supported: Perfor$
2679:20200522:112319.677 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.read[{$URL},Local_Datastore_ESXi2,latency]" became not supported: Performance counter data is no$
2678:20200522:112320.678 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.write[{$URL},{HOST.HOST},ESXi_2_boot,latency]" became not supported: Performance counter data$
2678:20200522:112320.678 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.read[{$URL},Prod_Datastore_2200v3,latency]" became not supported: Performance counter data is no$
2677:20200522:112321.678 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.read[{$URL},Test_Datastore_2200v3,latency]" became not supported: Performance counter data is no$

2677:20200522:112321.678 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.write[{$URL},{HOST.HOST},Local_Datastore_ESXi2,latency]" became not supported: Performance co$
2676:20200522:112322.679 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.write[{$URL},{HOST.HOST},Prod_Datastore_2200v3,latency]" became not supported: Performance co$
2677:20200522:112323.681 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.write[{$URL},{HOST.HOST},Test_Datastore_2200v3,latency]" became not supported: Performance co$
2677:20200522:112323.681 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.network.in[{$URL},{HOST.HOST},bps]" became not supported: Performance counter data is not available.
2678:20200522:112324.682 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.network.out[{$URL},{HOST.HOST},bps]" became not supported: Performance counter data is not available.
2678:20200522:112337.692 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.read[{$URL},{HOST.HOST},Kamery_Datastore_2200v3,latency]" became not supported: Performance c$
2676:20200522:112339.696 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.write[{$URL},Backup_Datastore_2200v3_veeam,latency]" became not supported: Performance counter d$
2676:20200522:112339.697 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.write[{$URL},ESXi_1_boot,latency]" became not supported: Performance counter data is not availab$
2677:20200522:112340.697 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.write[{$URL},{HOST.HOST},Kamery_Datastore_2200v3,latency]" became not supported: Performance $
2677:20200522:112340.697 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.write[{$URL},ESXi_2_boot,latency]" became not supported: Performance counter data is not availab$
2678:20200522:112342.702 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.write[{$URL},Local_Datastore_ESXi1,latency]" became not supported: Performance counter data is n$
2677:20200522:112343.703 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.write[{$URL},Local_Datastore_ESXi2,latency]" became not supported: Performance counter data is n$
2677:20200522:112345.709 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.read[{$URL},{HOST.HOST},Backup_Datastore_2200v3_veeam,l atency]" became not supported: Perform$
2677:20200522:112345.710 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.write[{$URL},Prod_Datastore_2200v3,latency]" became not supported: Performance counter data is n$
2679:20200522:112346.710 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.read[{$URL},{HOST.HOST},ESXi_1_boot,latency]" became not supported: Performance counter data $
2679:20200522:112346.710 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.write[{$URL},Test_Datastore_2200v3,latency]" became not supported: Performance counter data is n$
2679:20200522:112346.710 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.read[{$URL},{HOST.HOST},Local_Datastore_ESXi1,latency]" became not supported: Performance cou$
2678:20200522:112347.711 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.read[{$URL},{HOST.HOST},Prod_Datastore_2200v3,latency]" became not supported: Performance cou$
2676:20200522:112348.712 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.read[{$URL},{HOST.HOST},Test_Datastore_2200v3,latency]" became not supported: Performance cou$
2744:20200522:112349.222 fping failed: /usr/sbin/fping -C3 -i0 2>&1 </tmp/zabbix_server_2744.pinger;
2744:20200522:112350.225 fping failed: /usr/sbin/fping -C3 -i0 2>&1 </tmp/zabbix_server_2744.pinger;
2717:20200522:112356.931 Error of query maxQueryMetrics: 'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted..
2679:20200522:112357.723 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.network.in[{$URL},{HOST.HOST},bps]" became not supported: Performance counter data is not available.
2678:20200522:112358.725 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.network.out[{$URL},{HOST.HOST},bps]" became not supported: Performance counter data is not available.
2679:20200522:112359.726 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.write[{$URL},{HOST.HOST},Backup_Datastore_2200v3_veeam,l atency]" became not supported: Perfor$
2678:20200522:112408.738 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.read[{$URL},Kamery_Datastore_2200v3,latency]" became supported
2679:20200522:112410.739 item "434cc13c-1c93-47f8-b384-4cec69dab64a:vmware.datastore.write[{$URL},Kamery_Datastore_2200v3,latency]" became supported
2677:20200522:112416.745 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.read[{$URL},{HOST.HOST},Kamery_Datastore_2200v3,latency]" became supported
2679:20200522:112418.746 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.write[{$URL},{HOST.HOST},Kamery_Datastore_2200v3,latency]" became supported
2679:20200522:112444.790 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.read[{$URL},{HOST.HOST},Backup_Datastore_2200v3_veeam,l atency]" became supported
2732:20200522:112445.643 Zabbix agent item "wmi.getall[root\cimv2,"select * from win32_perfformatteddata_perfdisk_physicaldisk"]" on host "HUA004 - Backup" failed: first network err$
2676:20200522:112445.799 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.read[{$URL},{HOST.HOST},ESXi_1_boot,latency]" became supported
2679:20200522:112446.803 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.read[{$URL},{HOST.HOST},Local_Datastore_ESXi1,latency]" became supported
2676:20200522:112447.805 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.read[{$URL},{HOST.HOST},Prod_Datastore_2200v3,latency]" became supported
2679:20200522:112448.807 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.read[{$URL},{HOST.HOST},Test_Datastore_2200v3,latency]" became supported
2706:20200522:112456.658 Error of query maxQueryMetrics: 'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted..
2677:20200522:112459.819 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.write[{$URL},{HOST.HOST},Backup_Datastore_2200v3_veeam,l atency]" became supported
2734:20200522:112500.053 resuming Zabbix agent checks on host "HUA004 - Backup": connection restored
2676:20200522:112501.821 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.write[{$URL},{HOST.HOST},ESXi_1_boot,latency]" became supported
2676:20200522:112501.821 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.write[{$URL},{HOST.HOST},Local_Datastore_ESXi1,latency]" became supported
2678:20200522:112502.822 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.write[{$URL},{HOST.HOST},Prod_Datastore_2200v3,latency]" became supported
2679:20200522:112503.823 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.write[{$URL},{HOST.HOST},Test_Datastore_2200v3,latency]" became supported
2677:20200522:112504.824 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.read[{$URL},{HOST.HOST},Backup_Datastore_2200v3_veeam,l atency]" became supported
2678:20200522:112505.826 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.read[{$URL},{HOST.HOST},ESXi_2_boot,latency]" became supported
2677:20200522:112506.827 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.read[{$URL},{HOST.HOST},Local_Datastore_ESXi2,latency]" became supported
2676:20200522:112508.829 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.read[{$URL},{HOST.HOST},Prod_Datastore_2200v3,latency]" became supported
2679:20200522:112509.830 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.read[{$URL},{HOST.HOST},Test_Datastore_2200v3,latency]" became supported
2678:20200522:112519.838 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.write[{$URL},{HOST.HOST},Backup_Datastore_2200v3_veeam,l atency]" became supported
2677:20200522:112521.841 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.write[{$URL},{HOST.HOST},ESXi_2_boot,latency]" became supported
2677:20200522:112521.842 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.write[{$URL},{HOST.HOST},Local_Datastore_ESXi2,latency]" became supported
2678:20200522:112522.843 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.write[{$URL},{HOST.HOST},Prod_Datastore_2200v3,latency]" became supported
2679:20200522:112523.843 item "e048a530-0e3c-11e7-bf8a-f09838adf23d:vmware.hv.datastore.write[{$URL},{HOST.HOST},Test_Datastore_2200v3,latency]" became supported
2704:20200522:112556.634 Error of query maxQueryMetrics: 'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted..
2676:20200522:112637.933 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.read[{$URL},{HOST.HOST},Kamery_Datastore_2200v3,latency]" became supported
2678:20200522:112640.935 item "9f8a14fe-0e4e-11e7-8874-f09838b1df29:vmware.hv.datastore.write[{$URL},{HOST.HOST},Kamery_Datastore_2200v3,latency]" became supported
2716:20200522:112656.679 Error of query maxQueryMetrics: 'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted..
2669:20200522:112716.950 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
2679:20200522:112716.950 syncing history data in progress...
2679:20200522:112716.953 syncing history data... 100.000000%
2679:20200522:112716.953 syncing history data done
2669:20200522:112716.997 syncing trend data...
2669:20200522:112717.251 syncing trend data done
2669:20200522:112717.253 Zabbix Server stopped. Zabbix 4.4.6 (revision 8cc702429d).

[FildaSmile]

this is log from zabbix_agentd.log.1

1048:20200522:153311.589 Starting Zabbix Agent [Zabbix server]. Zabbix 4.4.8 (revision 3d7663fd7c).
1048:20200522:153311.619 **** Enabled features ****
1048:20200522:153311.619 IPv6 support: YES
1048:20200522:153311.619 TLS support: YES
1048:20200522:153311.619 **************************
1048:20200522:153311.619 using configuration file: /etc/zabbix/zabbix_agentd.conf
1048:20200522:153311.627 agent #0 started [main process]
1072:20200522:153311.628 agent #3 started[listener #2]
1073:20200522:153311.630 agent #4 started[listener #3]
1069:20200522:153311.631 agent #1 started [collector]
1071:20200522:153311.631 agent #2 started[listener #1]
1074:20200522:153311.632 agent #5 started [active checks #1]
1074:20200522:153311.715 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]:$

It seems that there is problem in internal comunication ?

[FildaSmile]

I really dont understand this:

zabbix@zabbix-virtual-machine:/usr/bin$ systemctl status zabbix_server.service
Unit zabbix_server.service could not be found.

Seems like something was deleted or missing, how it is possible that service not be found ?

[Mike2K]

I really dont understand this:

zabbix@zabbix-virtual-machine:/usr/bin$ systemctl status zabbix_server.service
Unit zabbix_server.service could not be found.

Seems like something was deleted or missing, how it is possible that service not be found ?

Perhaps you should try zabbix-server

[FildaSmile]

Thank you it way typo, unfortunately im not able to start zabbix server from friday i really dont want what happen i just did "/etc/init.d/zabbix-server start" and after that i cant start it again,

zabbix@zabbix-virtual-machine:/usr/bin$ systemctl status zabbix-server.service
● zabbix-server.service - LSB: Start zabbix-server daemon
Loaded: loaded (/etc/init.d/zabbix-server; generated)
Active: active (exited) since Mon 2020-05-25 15:38:13 CEST; 15h ago
Docs: man:systemd-sysv-generator(8)
Process: 1445 ExecStart=/etc/init.d/zabbix-server start (code=exited, status=0/SUCCESS)

How can i use debug level or some more deep troubleshooting ?

[FildaSmile]

I hceckeg the status of DB and there is also (code=exited, status=0/SUCCESS) does it mean that some problems could be also in the DB ?

root@zabbix-virtual-machine:~# sudo systemctl status mariadb
● mariadb.service - MariaDB 10.1.44 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2020-05-26 09:14:33 CEST; 5s ago
Docs: man:mysqld(8)

https://mariadb.com/kb/en/library/systemd/

Process: 5661 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 5658 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
Process: 5555 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && sys
Process: 5553 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 5552 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 5631 (mysqld)
Status: "Taking your SQL requests now..."
Tasks: 27 (limit: 4915)
CGroup: /system.slice/mariadb.service
└─5631 /usr/sbin/mysqld

mag 26 09:14:32 zabbix-virtual-machine systemd[1]: Starting MariaDB 10.1.44 database server...
mag 26 09:14:32 zabbix-virtual-machine mysqld[5631]: 2020-05-26 9:14:32 140618022112384 [Note] /usr/sbin/mysqld (mysqld 10.1.44-MariaDB-0ub
mag 26 09:14:33 zabbix-virtual-machine /etc/mysql/debian-start[5660]: Upgrading MySQL tables if necessary.
mag 26 09:14:33 zabbix-virtual-machine systemd[1]: Started MariaDB 10.1.44 database server.
mag 26 09:14:33 zabbix-virtual-machine /etc/mysql/debian-start[5664]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
mag 26 09:14:33 zabbix-virtual-machine /etc/mysql/debian-start[5664]: Looking for 'mysql' as: /usr/bin/mysql
mag 26 09:14:33 zabbix-virtual-machine /etc/mysql/debian-start[5664]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
mag 26 09:14:33 zabbix-virtual-machine /etc/mysql/debian-start[5664]: This installation of MySQL is already upgraded to 10.1.44-MariaDB, use
mag 26 09:14:33 zabbix-virtual-machine /etc/mysql/debian-start[5673]: Checking for insecure root accounts.

[FildaSmile]

hi a figured out how start server, i went to zabbix.com and do steps like when i want install fresh zabbix, i took command: "apt install zabbix-server-mysql zabbix-frontend-php zabbix-apache-conf zabbix-agent" i updated the packages but refuse to update zabbix_server.conf, after restart of VM where server is installed server is running and i collect data.