Recent content by innostus

I got the mainboard replaced by the manufacturer. That solved the issue.

It happened again. This time clearly nothing in the logs on Proxmox. So I contacted the manufacturer, again. Now we wait.....

I ran memtest several times. It passed. I also tried to stress the server with stress-ng. No problem at all. During normal operation, the load on the server is low. I do not expect that load is an issue. Any ideas on how to proceed?

I already have network console access. The server seems to be just power off. First I thought it was a mainboard issue. I had help from the mainboard manufacturer, but no success. No clues. Can be mainboard, cpu, psu, memory or OS. The only log line that appears in the IPMI event log is...

Thanks for your respons. I'll start a memtest on the server.

But why does the logrotate result in a shutdown of pveproxy and spiceproxy? And why is that not happening every day at that same time?

Ones in a while, my PVE server shuts itself down. But not a clean shutdown. VM's are not shutdown before the servers stops. What I can find in the logs: Mar 07 00:00:52 pveserver pvefw-logger[28347]: received terminate request (signal) Mar 07 00:00:52 pveserver systemd[1]: Reloaded PVE...

So, basically, Proxmox PVE does not support NFS v4 in it's 'pure' form with just port 2049? Is there a workaround? This seems to be the same problem as https://forum.proxmox.com/threads/problem-adding-nfs4-storage.120774/#post-524652

I cannot add a NFS4 storage via Datacenter->Storage->Add->NFS. I always get "create storage failed: storage 'nfsshare' is not online (500)". I also tried adding the NFS4 storage manually to /etc/pve/storage.cfg: nfs: nfsshare export /nfsonceph path /mnt/pve/nfsshare...