Recent content by Michiel_1afa

Not anymore, coredump is not installed by default on proxmox, and although I installed it on several nodes today, as mentioned HA is disabled so it wont actually catch anything here. Who knows, We have tried every angle we could immagine over the past year...

More updates from over the weekend: 2 reboots/crashes on 2 clusters. 1. This could be a problem with the server firmware or microcode? This one also gives slightly more information Jun 27 11:41:22 pve30 kernel: pve-ha-lrm[113646]: segfault at 8 ip 00005aa1b48e80f9 sp 00007ffca69d7630 error 4...

That is my aim as well, and why I was asking if its feasible to debug that daemon in some form, the Abort seems to come out of nowhere but has quite heavy consequences. echo "blacklist hpwdt" > /etc/modprobe.d/blacklist-hp.conf and updateinitramfs.. However this was only applied on 1 cluster as...

mlag -> 2 bonds -> several vlans. corosync is configured to use a primary and backup, which are also split across both bonds. On the corosync part my last error was months ago. Had another incident yesterday and I do think I got slightly closer to finding what the heck is going on. different...

Hello, any new inputs on this? since the last message we have had one more 'crash' of pvestatd (process kept running, but no more updates)

https://bugzilla.proxmox.com/show_bug.cgi?id=7688

There is, but not in gui. as mentioned before it can be done from CLI.

Thought you might want that: "journalctl -k -b -1" attached. As far as I know yes, we are scrutinizing logs on the daily and im not aware of any errors or warnings on this part. - Did a scan for "unable to acquire lock" on the logs on all servers from saturday till today (5 days) and I have 0...

When using PMG cluster with oauth and "auto create users" every time a new/yet unknown user logs in to the web interface, it throws an error about the partner server not knowing that user, clicking OK makes the message go away and not come back but it is a bit confusing for users. Obviously...

I happens often on 1 cluster, less often on another (often is 2-3x per month, if we do not touch anything manually) Softdog, were on HP machines so the HP modules are already blacklisted per earlier 'solution' Nothing custom. I hope not, its only proxmox installed there, logs do not seem to...

3x this week already - last saturday, yesterday and this morning pve-ha-crm decides to die without cause, or at least without a usable message. "watchdog update failed - Broken pipe" The server is not doing anything special at that moment, no heavy load, no network issues, no issues on other...

I can safely say this is not related to intel microcode, I see this happening since a short while on one of our clusters as well, which is fully AMD nodes.

As far as I know, on windows this is a "domain policy" pushed by the Active Directory. The windows domain policies don't work on anything but windows. Technically you can change the policy (GPT editor) to change the NTP server to something other then the main AD. However in my experience this is...

Not sure if it is 'The' recommended way, but as I mentioned, we rely on a NTP source in our network so it is reachable for all machines. In your case if you do not have the means to set up a dedicated NTP source, using one of the PVE hosts, or your router/switch as a NTP source will work fine...

This is not an 'ntp' option, this is for the startup of the vm, windows likes to have the system date/time in the local time zone, while *nix OS likes to have the system date/time in UTC. This option translates the host time for the vms to the timezone or not depending on that option. Which...