u/jaysun_n

I have a VM for all my *arr applications but this weekend the VM which hosts all the docker images has suddenly started shutting down without any errors being logged in Proxmox and I am unsure why or where to check for the issue. It happens reliably, about 5 minutes after starting the VM. There are no tasks in the Proxmox log indicating it was told to shut down not any errors. This VM has been working for several months without any changes. I tried restoring an old backup of the VM but its still having the same issue, so I dont think its happening from the VM side but Im not 100% sure. I tried watching dmesg when the issue happened but all I saw was below

[   15.930629] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[   15.930634] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
^[[A[   99.909565] workqueue: pm_runtime_work hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
[  110.418099] workqueue: output_poll_execute hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
[  192.145611] workqueue: pm_runtime_work hogged CPU for >10000us 8 times, consider switching to WQ_UNBOUND
[  202.621305] workqueue: output_poll_execute hogged CPU for >10000us 8 times, consider switching to WQ_UNBOUND
[  375.328624] workqueue: pm_runtime_work hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND
[  385.422856] workqueue: output_poll_execute hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND
[  742.686663] workqueue: pm_runtime_work hogged CPU for >10000us 32 times, consider switching to WQ_UNBOUND
[  753.052906] workqueue: output_poll_execute hogged CPU for >10000us 32 times, consider switching to WQ_UNBOUND

Any help finding why VMs shut down would be appreciated, whether its within a VM or on the host. I am on Proxmox 9.1.5 and the VM is Ubuntu 24.04.4 LTS (GNU/Linux 6.8.0-110-generic x86_64).

I am working on a modpack and there are a few that add wrenches (and other similar tools) to interact with their respective modded blocks. Now, if these were just basic crafting materials or blocks, it’s quite trivial to replace all instances of one with instances of another using kubejs. Is there a way to perform a similar function with tools and items using kubejs or another mod? So instead of a wrench for mod A, another for B, another for C, I can have one combined wrench that interacts with mod A, B and C? If not, is there a better way to handle this problem?