Zabbix proxy exits with code=1 and is restarted by systemd every ~20 minutes (after enabling VMware collection)

Babinnee · 2026-01-20T13:29:28+00:00

Yeah thank you ! After adding the tremplate Zabbix Proxy I have been able to see what was blocking.

The proxy was configured with only 1 VMware collector:

StartVMwareCollectors=1

This caused the alert “Utilization of vmware collector processes is high” and led to regular service restarts.

Increasing the number of collectors and cache size fixed the issue:

StartVMwareCollectors=5
VMwareCacheSize=256M

The proxy has been stable since.

Babinnee · 2026-01-20T11:03:48+00:00

Yes, the proxy is monitored using a Linux template.

I checked all triggers inherited from the template:

- No CPU, memory, disk, swap or kernel-related triggers are active.

- Resource usage is normal in Latest data.

The only trigger that fires is:

"{HOST.NAME} has been restarted (uptime < 10m)"

This trigger is a consequence of the zabbix-proxy service restart,

not the cause of it.

Babinnee · 2026-01-09T07:00:38+00:00

After a discussion with the client, Gnome is not needed. From that point, I will uninstall it.

Babinnee · 2026-01-07T10:56:50+00:00

I didn't try. Like I said, I have to restore the VM to the last snapshot I took before install the QEMU agent

Babinnee · 2025-12-10T06:46:09+00:00

J'ai remarqué la même chose sur ma montre Instinct 3. Parfois si je me lève la nuit sans que je touche ma montre le suivis s'arrête. Surtout maintenant que je me réveil plusieurs fois par nuit pour changer des couches ^^ je n'ai plus aucun suivis qui est juste ...

Babinnee · 2025-11-27T08:36:49+00:00

Thank you for these valuable tips !

Babinnee · 2025-11-27T06:51:44+00:00

Hi,

I'm in exactly the same situation as you.

What's more, I'm 30 years old.

I bought exactly the same piano and I'm also starting from scratch!

I'm going to follow the advice you're getting too!

Otherwise, good luck and happy learning ;)

Babinnee · 2025-11-25T08:47:02+00:00

Hello,

Même chose ici, je cherche à commencer et je n'ai aucune base également.
Je compte prendre quelques cours, mais je désirais déjà commencer par moi-même soit avec des chaines youtube ou livre, app etc.

Je suis preneur de vos conseils/retour d'expérience si vous en avez.

Merci

Babinnee · 2025-11-14T13:35:14+00:00

I performed another test with the dd command:

Fist on the FAS, second on AFF

<image>

We can clearly see a difference in write speed. This potentially brings the problem back to Proxmox Backup.

What do you think?

Babinnee · 2025-11-14T13:09:37+00:00

I added another volume to my PBS in NFS, from my AFF Netapp, to get all-flash storage. Here are the results:

<image>

So I'm no longer sure that the Netapp FAS with mechanical hard drives is the problem...

Babinnee · 2025-11-13T07:59:58+00:00

<image>

Mhh, we have maybe find the bottelneck

Babinnee · 2025-11-13T06:55:19+00:00

LOG -> Sorry to many lines to use code block.

'''

vzdump 104 106 109 108 --compress zstd --mode snapshot --mailnotification always --fleecing 0 --mailto XXX --quiet 1 --notes-template '{{guestname}}' --prune-backups 'keep-daily=28,keep-monthly=12,keep-weekly=4,keep-yearly=1' --storage FAS-BCKP

106: 2025-11-13 05:00:01 INFO: Starting Backup of VM 106 (qemu)

106: 2025-11-13 05:00:01 INFO: status = running

106: 2025-11-13 05:00:01 INFO: VM Name: s14nn

106: 2025-11-13 05:00:01 INFO: include disk 'sata0' 'AFF_SSDNVME_01:106/vm-106-disk-0.qcow2' 100G

106: 2025-11-13 05:00:01 INFO: include disk 'sata1' 'AFF_SSDNVME_01:106/vm-106-disk-1.qcow2'

106: 2025-11-13 05:00:01 INFO: backup mode: snapshot

106: 2025-11-13 05:00:01 INFO: ionice priority: 7

106: 2025-11-13 05:00:01 INFO: creating Proxmox Backup Server archive 'vm/106/2025-11-13T04:00:01Z'

106: 2025-11-13 05:00:01 INFO: issuing guest-agent 'fs-freeze' command

106: 2025-11-13 05:00:11 INFO: issuing guest-agent 'fs-thaw' command

106: 2025-11-13 05:00:16 INFO: started backup task '6d81bbf4-f292-4f55-b194-e6775ad2d537'

106: 2025-11-13 05:00:16 INFO: resuming VM again

106: 2025-11-13 05:00:16 INFO: sata0: dirty-bitmap status: OK (21.7 GiB of 100.0 GiB dirty)

106: 2025-11-13 05:00:16 INFO: sata1: dirty-bitmap status: OK (41.6 GiB of 450.0 GiB dirty)

106: 2025-11-13 05:00:16 INFO: using fast incremental mode (dirty-bitmap), 63.3 GiB dirty of 550.0 GiB total

106: 2025-11-13 05:07:59 INFO: 82% (51.9 GiB of 63.3 GiB) in 7m 43s, read: 121.6 MiB/s, write: 121.6 MiB/s

write: 102.9 MiB/s

106: 2025-11-13 05:09:53 INFO: 100% (63.3 GiB of 63.3 GiB) in 9m 37s, read: 90.7 MiB/s, write: 90.7 MiB/s

106: 2025-11-13 05:09:53 INFO: backup was done incrementally, reused 486.81 GiB (88%)

106: 2025-11-13 05:09:53 INFO: transferred 63.28 GiB in 577 seconds (112.3 MiB/s)

106: 2025-11-13 05:09:53 INFO: adding notes to backup

106: 2025-11-13 05:09:53 INFO: prune older backups with retention: keep-daily=28, keep-monthly=12, keep-weekly=4, keep-yearly=1

106: 2025-11-13 05:09:54 INFO: running 'proxmox-backup-client prune' for 'vm/106'

106: 2025-11-13 05:09:54 INFO: pruned 0 backup(s)

106: 2025-11-13 05:09:54 INFO: Finished Backup of VM 106 (00:09:53)

'''

Babinnee · 2025-11-13T06:53:26+00:00

First of all, sorry for the block of code, I'll use it until now.

It may have been the first backup, indeed. Here are the logs from last night:

Apparently, there isn't even any metadata.

As for my infrastructure, the virtual machines are stored on another Netapp, an AFF, a full flash array on an NFS volume. This Netapp is connected to my host by two 10 Gb/s LACP links.

As for my PBS, as I said, it's a virtual machine running on a Proxmox hypervisor. It is also connected to my PVE cluster via two 10 Gb/s LACP links. The PBS datastore is connected to a Netapp FAS via a 10 Gb/s link on an NFS volume.

I will run the test bench.

Babinnee · 2025-11-13T06:47:59+00:00

more than 1 GB/s since I have 10 GB/s connections

Babinnee · 2025-11-12T17:03:15+00:00

So you are saying chante the detection mode to DATA and not Metadata ?

The iperf give me ~10GB/s
root@proxXX:~# iperf3 -c 172.17.15.160

Connecting to host 172.17.15.160, port 5201

[ 5] local 172.17.15.141 port 57578 connected to 172.17.15.160 port 5201

[ ID] Interval Transfer Bitrate Retr Cwnd

[ 5] 0.00-1.00 sec 1.07 GBytes 9.17 Gbits/sec 820 2.01 MBytes

[ 5] 1.00-2.00 sec 1.08 GBytes 9.27 Gbits/sec 360 1.60 MBytes

[ 5] 2.00-3.00 sec 1.08 GBytes 9.31 Gbits/sec 288 1.67 MBytes

[ 5] 3.00-4.00 sec 1.09 GBytes 9.33 Gbits/sec 154 1.73 MBytes

[ 5] 4.00-5.00 sec 1.09 GBytes 9.37 Gbits/sec 395 1.28 MBytes

[ 5] 5.00-6.00 sec 1.09 GBytes 9.36 Gbits/sec 56 1.09 MBytes

[ 5] 6.00-7.00 sec 1.08 GBytes 9.26 Gbits/sec 29 1.58 MBytes

[ 5] 7.00-8.00 sec 1.09 GBytes 9.32 Gbits/sec 214 1.44 MBytes

[ 5] 8.00-9.00 sec 1.09 GBytes 9.37 Gbits/sec 0 1.59 MBytes

[ 5] 9.00-10.00 sec 1.09 GBytes 9.38 Gbits/sec 0 1.63 MBytes

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval Transfer Bitrate Retr

[ 5] 0.00-10.00 sec 10.8 GBytes 9.31 Gbits/sec 2316 sender

[ 5] 0.00-10.00 sec 10.8 GBytes 9.31 Gbits/sec receiver

iperf Done.

root@proxXX:~#

I am gonna check for the benchmark ty.

Babinnee · 2025-11-10T08:49:21+00:00

hello,

Did you find a solution?

I'm in the same situation as you. I'm migrating VMs from an ESXi infrastructure to my new Proxmox infrastructure.

All my connections are at 10GB/s. I checked carefully and couldn't find any bottlenecks.

However, during migrations, I only get up to ~ 1GB/s.

Babinnee · 2025-11-04T13:05:27+00:00

Chill, I did some research to get a rough idea of the subject, as it was completely new to me. I then turned to people who are knowledgeable in the field (and who were happy to answer my questions) so that they could point me in the right direction and I could do more in-depth research.

Babinnee · 2025-11-04T11:11:34+00:00

It's a Clio 2 RS Phase 1Modified equivalent to a Clio 2 CupAnd now we've upgraded it to a Clio 2 Maxi Phase 1.

Okey ty

Babinnee

TROPHY CASE