Recent content by Dudeplayz

Hi there, If I have time, I will also test the sytemd_mount version. If it works, it would be nice. I will state my current workaround: job-end) ... at now + 1min -f /home/disk.sh ... The disk.sh script is the same as I posted back then. It starts a timer and unmounts the disk...

Thank you Fabian. I removed corosync and everything is still working, but now without the log spam. I have also discussed it a little bit more in the github issue. King regards, Dario

The QDevice is an RPi. QDevice and QNet are installed on it. I simply stopped the corosync service, nothing else. The setup worked before migration (I think, haven't looked at the Syslog before that much). Maybe caused by a qdevice update or similar.

Ok it has something to do with the qdevice. I stopped the corosync service on the qdevice and the log spam disappeared. Here is the corosync.conf of the device. Maybe there is a misconfiguration.

Ok here is the next weird info: I have now restarted both nodes. Independent from each other. And syslog spam still occurs while the other server is down while rebooting. So it shouldn't be a problem in packet loss between these servers when one is down. Or I am wrong?

How do I have to run tcpdump? I simply started it, but at first glance, there was nothing noticeable.

Yes before I restarted the service on both nodes. The debug log I only tested and one. Here is the log of the second one after the restart with debugging on.no, the qdevice is not operating at the knet layer at all.. did you restart corosync on both nodes?

They hang on the same switch in the same IP-Net. So it shouldn't pass through the router. Still it is confusing, why this first appeared after pve upgrade. Before everything was normal. Maybe it's a problem with the separate QDevice?

Here is the log after restarting corosync with debug information. It is now also always logging corosync[3787721]: [KNET ] rx: Unable to decrypt/auth packet.

Ok pve2 came up with some special after last reboot (29.9. 15:47):

Only this appears from time to time:

For the journalctl -b -u corosync command a huge log file with 750MB size is created. Only containing the nsscrypto message. This is real spam.