Search results

I used to use Zabbix and Linux auto-discoveries scripts I had made long time ago. But I have to test direct integration pointed by @Taomyn !

Hello. I think that Turnkey linux addressed that with container templates proposed in Proxmox no ?

I am not a mac user. Maybe this can help (after rebooting on MacOS) : https://osxdaily.com/2015/02/03/set-or-disable-sleep-due-to-mac-system-inactivity-from-the-command-line-in-os-x/

OK. Can you send the syslog before/during crash ? You can use something like : journalctl --since "2025-02-19 20:22" --until --since "2025-02-19 20:46"

Hello. Do you use HA ?

What settings are not accessible ? I tested and it seems that only device pass-through is disabled.

Chipset on the MB, port, cable or disk...

I can not tell you more.

So it is pretty sure to be a hardware problem.

Sorry, I don't use Ansible for VMs, thus I can't provide example. Maybe you should post to Ansible forum, as @aabraham suggested ?

You are welcome.

Please read here to understand : https://unix.stackexchange.com/questions/237817/delete-file-while-it-is-in-use

I don't know. Personally I would restart and do a full test.

Simple stupid and cheap solution : backup (within proxmox virtual environment) your VM on an other sever storage (NFS export for example). When you will need to restore the backup, it will be local and will take less time. Good solution : as @Johannes S said : reverse proxy (application level...

Hello Look at : https://docs.ansible.com/ansible/latest/collections/community/general/proxmox_module.html ==> You can specify storage.

You can try a low level disk test and a RAM test.

Check your gateway IP : .1 or .254 ? Is the interface in the bridge (conf applied ?) : brctl show

Hello. The problem can be anywhere on the chain : processor, RAM bus, RAM, PCI or SATA or whatever bus, RAM of the disk, disk chip or firmware, disk itself. We cannot tell. But it is often a disk or RAM problem (if the RAM is not ECC). Just to check, is your disk direct attached, it is not a...

Hello. It seems that your antivirus is scanning the whole backup files. Thus it takes long time. Thus the old backup file cannot be deleted by the backup rotation and the system. Thus your storage is full. And when you unmount or if you stop and start kesl, the space is cleared. Solution : use...

My advices for disk performance : - use local disk storage - read this if you want extra speed be be carefull with data loss with writeback : https://pve.proxmox.com/wiki/Performance_Tweaks