rcm024

root@Tower:~# lxc-start -F AMPStandalone lxc-start: AMPStandalone: ../src/lxc/conf.c: lxc_rootfs_init: 392 No space left on device - Failed to pin rootfs lxc-start: AMPStandalone: ../src/lxc/start.c: __lxc_start: 2086 Failed to handle rootfs pinning for container "AMPStandalone" lxc-start: AMPStandalone: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start lxc-start: AMPStandalone: ../src/lxc/tools/lxc_start.c: lxc_start_main: 312 Additional information can be obtained by setting the --logfile and --logpriority options attached tower-diagnostics-20250121-1749.zip

I'm also having a similar issue: root@Tower:~# lxc-start AMPStandalone lxc-start: AMPStandalone: ../src/lxc/lxccontainer.c: wait_on_daemonized_start: 837 Received container state "ABORTING" instead of "RUNNING" lxc-start: AMPStandalone: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start lxc-start: AMPStandalone: ../src/lxc/tools/lxc_start.c: lxc_start_main: 310 To get more details, run the container in foreground mode lxc-start: AMPStandalone: ../src/lxc/tools/lxc_start.c: lxc_start_main: 312 Additional information can be obtained by setting the --logfile and --logpriority options This is a Debian LXC that is only running AMP (Aplication Management Panel) for my game servers. I went to update my Factorio server as it just got an update and it gave me an error saying no space left on device even though there is plenty of space. I decided to try restarting the LXC to see if that would fix it, but when attempting to start it back up, it will not start. I additionally tried copying the container which worked and the container will start, but it doesn't grab any ip addresses at all let alone the same ones the original container used. Can you help me either fix the original container or get the new one to grab the addresses it needs? Thanks

great, now how do I add this? It doesn't appear to be part of nerd tools either EDIT: nevermind, I found un-get (by ich777) to install it

hey @ich777, any chance of a server docker image for Mount and Blade II: Bannerlord?

My only suggestion unfortunately is to try removing the mapped drives in windows and remapping them

Are you able to access your mapped network drives through windows file explorer? I only have this error pop up when my connection to the mapped drives fails. have you gotten it to run before and this just popped up or are you setting up for the first time? Edit: Just scrolled up further and saw you're just setting it up. My first part still stands though.

I'm seeing strange CPU spikes with the Tdarr server idling on my system. I want to keep it up so that new stuff automatically gets transcoded as added, but this weird idling behavior makes me want to turn it off. The server is causing a CPU spike consistently (up to 50% on every logical core) every 30 seconds. Using htop I have deduced that it is some shfs operation. Any idea what this might be or how to mitigate it? The Tdarr logs don't show anything about it. just the standard hourly check. Attaching screenshots for reference: 1 of CPU graph with Tdarr server stopped, 1 of CPU graph with Tdarr server started, and one of htop filtered to shfs at time of a spike Anyone seen this before and/or know how to mitigate it or should I just shut it off when not actively in use?

Not that I'm aware of. Sonarr/Radarr and Plex don't have any issues with them. Just Tdarr. Is there a way for me to double check easily?

So I've been running Tdarr/node for a few months now to transcode my library and it has worked great for the most part. I have run into a few issues with files that either fail health check or fail to transcode and can't figure out why. The files play fine using Plex and MPV but then throw errors for Tdarr. Would love some help or insight on how to fix my setup/plugins so these stop happening. I have 3 mp4-mkv transcodes so far that have failed with the following at the end of the info log: One of them below: The Hobbit (Transcode: Error/Cancelled) I also have 9 mkv files that have failed health checks before even getting to the transcoder and at the end they all say: Specific example with full info log: Komi Can't Communicate S01E11 (Health check: Error/Cancelled) Any help with this is appreciated. Thanks

Ok, so doing some additional testing, the logs I was getting before (with "VPN not configured!") only happen if I have more than one .ovpn file in the directory (even though only one of the files was named vpn.ovpn) so I have made sure to only keep one .ovpn file there. I presume the above error then is just with communicating with the VPN server? Maybe? Edit: yup, messing with different .ovpn files from my provider has done the trick. It's working again

These are the only files: And with the update that unraid had me apply to the template this morning I'm getting new logs:

Have now tried this with no success. I did decide to leave the container running for a few min and got some additional Log output: Seems to be missing vpn.conf? But it never had it before and worked fine. Any ideas? If not I'll submit to the github, but wanted to see if there might be something dumb I'm missing first. Thanks

So I've been using your OpenVPN container for a while, and have run into an issue. My power went out yesterday and my ups failed. Parity check came back clean, but my VPN container refuses to run properly. All that shows up in the log is: I haven't made any changes and have rebuilt the container and this is all I get. I've also tried multiple VPN server files to see if that was the issue and get the same thing.

This does appear to be the case. Just got a warning about it and checked and sure enough: This is the same template URL that replaced it last time. I'll be ignoring warning this time lol

Hey @ich777 I immediately deleted them once I noticed (and forgot to screenshot first), but somehow my templates for your OpenVPN-client container were replaced by some russian one. Not sure if this is something known or combatable, but thought you aught to be informed. If it happens again, I will make sure to take screenshots for you to see.