Search results

Thanks. Not seen any slowness on our Ceph pools when it happens. Very little/low usage on the last one. Sub 1/2MB/s.

Do we have anything further on this. Another watchdog reboot yesterday.

I assume you mean @Michiel_1afa? The host that this happened on for us had 1 VM running.

Logs don’t show any. Just to note, this issue occurs any time of the day. Our backups only run at very specific times. There is no correlation

20 mins before the last reboot and one prior to that.

Full logs as in the whole of the journal, or just specific to a process? The usually happens just out of the blue but has during an upgrade too. pveversion -v

Interesting. Wonder when those issues were introduced. The number of VMs and HA resources we have has not changed since these issues occurred. Our issues started mid-Nov.

Would be nice to get some Proxmox involvement as this is clearly an issue with this and other threads of the same problem.

We are solely Intel, so I don't think chipset is relevant.

Now you mention it, we saw that on our last upgrade. Nodes drying during apt-get dist-upgrade. Never seen that before. We just thought it was because they were busy.

No entries around the time of the reboot. Jan 20 04:04:06 hv-5-i corosync[1826]: [QUORUM] Sync members[7]: 1 2 3 4 5 6 7 Jan 20 04:04:06 hv-5-i corosync[1826]: [QUORUM] Sync joined[6]: 1 2 3 4 6 7 Jan 20 04:04:06 hv-5-i corosync[1826]: [TOTEM ] A new membership (1.759) was formed. Members...

Something we've seen in version 9 is an increase in watchdog reboots - in fact from none to many. Last few entries of the journal show: ``` Jan 22 04:39:09 hv-5-i watchdog-mux[1504]: client watchdog is about to expire Jan 22 04:39:09 hv-5-i systemd-journald[841]: Received client request to...

We installed this but the web server appears unresponsive. Processes are up, server rebooted but nothing. Port 8443 does show in use. ``` proxmox-d 540 www-data 14u IPv6 2946 0t0 TCP *:8443 (LISTEN) proxmox-d 540 www-data 15u...

I will check when we try again but the main question remains. Do the nodes that are exclusively running virtual machines need to see/access the internal ceph network. Should they only require, at a minimum, interface for internet/VM traffic to the world and cluster traffic (which is shared with...

Ceph installed OK but it was during the configuration. Near immediately after nodes starting rebooting. Yes we use HA. Public interface is 95.x.x.x Ceph Public/Cluster is 10.0.0.0/24 (we also set a backup ring on the public) Ceph Internal is 192.168.0.0/24 There was no saturation of any link...

We've been using a traditional SAN with iscsi for over 10 years, it has been ultra reliable. Now looking at ceph and have built a 3-server ceph cluster with Dell R740xds. The device has six interfaces, three to one switch, three to another. One port is public internet One port is public ceph...

Are people still suffering this? Upgraded to the latest and got the 6.8 kernel and saw very poor I/O wait as described. We are using iSCSI.

Any further comment here on the last post as to the processing logic and wasting of valuable DNSBL queries on "virus" messages which will be caught either way.

Is this fixed. Still adding a IPv6 CIDR range in the Who > IP Network filter does not appear to work. IPv4 does.

Unfortunately, it's not a rule that is putting the mail in to quarantine, hence the post. It is a mail attachment, being classed as a virus, when it is not. It's happened to various users but maintaining rulesets for each domain/user and from or to address becomes a mammouth task and could...