Regular ZED messages in syslog?

n1nj4888

Member
Jan 13, 2019
159
14
23
41
Hi There,

I'm running latest pve and using ZFS replication between local-zfs on 2 nodes. Every time the replication runs it seems to output the following type of messages in syslog without any clear meaning what they are referring to or whether they are just unnecessary noise?

Code:
Feb 28 07:29:01 pve-host2 systemd[1]: Started Proxmox VE replication runner.
Feb 28 07:30:00 pve-host2 systemd[1]: Starting Proxmox VE replication runner...
Feb 28 07:30:02 pve-host2 zed[9491]: eid=6441 class=history_event pool_guid=0x69E5B29BD15B9EA3
Feb 28 07:30:02 pve-host2 zed[9493]: eid=6442 class=history_event pool_guid=0x69E5B29BD15B9EA3
Feb 28 07:30:02 pve-host2 zed[9555]: eid=6443 class=history_event pool_guid=0x69E5B29BD15B9EA3
Feb 28 07:30:02 pve-host2 zed[9563]: eid=6444 class=history_event pool_guid=0x69E5B29BD15B9EA3
Feb 28 07:30:03 pve-host2 zed[9635]: eid=6445 class=history_event pool_guid=0x69E5B29BD15B9EA3
Feb 28 07:30:03 pve-host2 zed[9637]: eid=6446 class=history_event pool_guid=0x69E5B29BD15B9EA3
Feb 28 07:30:04 pve-host2 zed[9775]: eid=6447 class=history_event pool_guid=0x69E5B29BD15B9EA3
Feb 28 07:30:04 pve-host2 zed[9777]: eid=6448 class=history_event pool_guid=0x69E5B29BD15B9EA3
Feb 28 07:30:04 pve-host2 zed[9780]: eid=6449 class=history_event pool_guid=0x69E5B29BD15B9EA3
Feb 28 07:30:05 pve-host2 systemd[1]: pvesr.service: Succeeded.
Feb 28 07:30:05 pve-host2 systemd[1]: Started Proxmox VE replication runner.
Feb 28 07:30:05 pve-host2 zed[9791]: eid=6450 class=history_event pool_guid=0x69E5B29BD15B9EA3
Feb 28 07:30:05 pve-host2 zed[9793]: eid=6451 class=history_event pool_guid=0x69E5B29BD15B9EA3
Feb 28 07:30:05 pve-host2 zed[9795]: eid=6452 class=history_event pool_guid=0x69E5B29BD15B9EA3

# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e)
pve-kernel-5.3: 6.1-5
pve-kernel-helper: 6.1-5
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.18-1-pve: 5.3.18-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.14-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-12
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-4
libpve-storage-perl: 6.1-4
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-19
pve-docs: 6.1-6
pve-edk2-firmware: 2.20191127-1
pve-firewall: 4.0-10
pve-firmware: 3.0-5
pve-ha-manager: 3.0-8
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-3
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-6
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

Thanks!
 

H4R0

Active Member
Apr 5, 2020
611
130
43
I had the same issue, here is a one liner in case anyone else needs it.

Code:
sed -i "s/zed_log_msg/if [ \"\${ZEVENT_SUBCLASS}\" = \"history_event\" ]; then exit 0; fi\nzed_log_msg/g" /etc/zfs/zed.d/all-syslog.sh
 

erreu

New Member
Jul 7, 2020
1
1
3
54
You can also uncomment this line:
#ZED_SYSLOG_SUBCLASS_EXCLUDE="statechange|config_*|history_event"
in /etc/zfs/zed.d/zed.rc to prevent those types of events from being logged
 
  • Like
Reactions: H4R0

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!