-
Posts
219 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by CoZ
-
So then, yes, add the 'retain / default' entry to the Snapshots as well.
-
Anyone else have an issue with recordings not being deleted as set up by the config file? For instance, I have record: enabled: True events: retain: default: 2 snapshots: enabled: True But, I've still got 7+ days of recordings. Looking at this again, maybe it's just the snapshots / thumbnails that aren't being automatically deleted? Do I have to add a 'retain: default: 2' under the snapshots entry as well?
-
The only thing I get while in game is "High server load - there maybe some hiccups" message on the lower left. I actually never see any hiccups though and my server is never "maxxed out" either.
-
Sound like my experience with anyone involved in the Frigate project - they arent' friendly nor do they ever want to help. I feel your pain.
-
@ONI: Backup your /appdata/enshrouded directory (copy it somehwere else) Take screenshots of your current containers variables (if you aren't going to remember what you had them set up as) Remove the Enshrouded Container Remove the Enshrouded Container template (if it exsists? not sure if there would be one if you manually created or, imported XML) Pull down new Enshrouded container from Community Apps store. Enter in the variables / paths from your previous Enshrouded container. Move back the /appdata/enshrouded directory, overwritting the folder if already present in /appdata @Nodiaque FYI for those of us who imported your XML and/or installed the old version of your container before you added the backup function, pulling down the newest container from C.A. doesn't add those variables for the backup capability. One has to add them manually or, remove the current container and pull down the new container but, backing up everything like above. Just in case someone comes on here asking.
-
Done.
-
I'm launching it as I do every other container. Right clicking + Start Container. These are the entire logs when it first starts up: s6-rc: info: service s6rc-fdholder: starting s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service s6rc-fdholder successfully started s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service trt-model-prepare: starting s6-rc: info: service log-prepare: starting s6-rc: info: service log-prepare successfully started s6-rc: info: service nginx-log: starting s6-rc: info: service go2rtc-log: starting s6-rc: info: service frigate-log: starting s6-rc: info: service nginx-log successfully started s6-rc: info: service go2rtc-log successfully started s6-rc: info: service go2rtc: starting s6-rc: info: service frigate-log successfully started s6-rc: info: service go2rtc successfully started s6-rc: info: service go2rtc-healthcheck: starting s6-rc: info: service go2rtc-healthcheck successfully started Generating the following TRT Models: yolov4-416,yolov4-tiny-416 Downloading yolo weights 2024-02-01 10:30:12.079536551 [INFO] Preparing new go2rtc config... 2024-02-01 10:30:13.159361526 [INFO] Starting go2rtc... 2024-02-01 10:30:13.279687971 10:30:13.279 INF go2rtc version 1.8.4 linux/amd64 2024-02-01 10:30:13.280390371 10:30:13.280 INF [api] listen addr=:1984 2024-02-01 10:30:13.280428249 10:30:13.280 INF [rtsp] listen addr=:8554 2024-02-01 10:30:13.280808608 10:30:13.280 INF [webrtc] listen addr=:8555 Creating yolov4-tiny-416.cfg and yolov4-tiny-416.weights Creating yolov4-416.cfg and yolov4-416.weights Done. 2024-02-01 10:30:21.744747617 [INFO] Starting go2rtc healthcheck service... Generating yolov4-416.trt. This may take a few minutes. Traceback (most recent call last): File "/usr/local/src/tensorrt_demos/yolo/onnx_to_tensorrt.py", line 214, in <module> main() File "/usr/local/src/tensorrt_demos/yolo/onnx_to_tensorrt.py", line 202, in main engine = build_engine( File "/usr/local/src/tensorrt_demos/yolo/onnx_to_tensorrt.py", line 112, in build_engine with trt.Builder(TRT_LOGGER) as builder, builder.create_network(*EXPLICIT_BATCH) as network, trt.OnnxParser(network, TRT_LOGGER) as parser: TypeError: pybind11::init(): factory function returned nullptr [02/01/2024-10:30:38] [TRT] [W] Unable to determine GPU memory usage [02/01/2024-10:30:38] [TRT] [W] Unable to determine GPU memory usage [02/01/2024-10:30:38] [TRT] [W] CUDA initialization failure with error: 35. Please check your CUDA installation: http://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html Loading the ONNX file... Generating yolov4-tiny-416.trt. This may take a few minutes. Traceback (most recent call last): File "/usr/local/src/tensorrt_demos/yolo/onnx_to_tensorrt.py", line 214, in <module> main() File "/usr/local/src/tensorrt_demos/yolo/onnx_to_tensorrt.py", line 202, in main engine = build_engine( File "/usr/local/src/tensorrt_demos/yolo/onnx_to_tensorrt.py", line 112, in build_engine with trt.Builder(TRT_LOGGER) as builder, builder.create_network(*EXPLICIT_BATCH) as network, trt.OnnxParser(network, TRT_LOGGER) as parser: TypeError: pybind11::init(): factory function returned nullptr [02/01/2024-10:30:41] [TRT] [W] Unable to determine GPU memory usage [02/01/2024-10:30:41] [TRT] [W] Unable to determine GPU memory usage [02/01/2024-10:30:41] [TRT] [W] CUDA initialization failure with error: 35. Please check your CUDA installation: http://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html Loading the ONNX file... Available tensorrt models: ls: cannot access '*.trt': No such file or directory s6-rc: warning: unable to start service trt-model-prepare: command exited 2 I had removed the original Frigate container and template and pulled down a "fresh" copy for v13 and installed the NVIDIA Branch when it asked me in Community Apps which branch I wanted to install. So I did not upgrade from 12-13, I started with a new pull down of the container. I wanted to be safe that there would be no issues left over.
-
So I have a CUDA capable GPU - I checked. I also have the newest NVIDIA drivers. As of ver13 attempting to run the container results in this error: [01/31/2024-16:13:22] [TRT] [W] CUDA initialization failure with error: 35. Please check your CUDA installation: http://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html So, after following that link it's talking about installing the CUDA libraries, etc. Before I break something else, is this actually needed?
-
A new patch for the game was pushed out today. I'm assuming a restart of the docker container will pull down the new patch and apply it automatically?
-
Yup. Then there is something wrong on your side. Could be NAT translation like @Nodiaque said. I had that same issue until a firmware update for my router was pushed out. Can you try this website https://portchecker.co/ See if anything gets a hit there? I've got dual Intel® Xeon® CPU E5-2630L v2 with 32GB RAM on each CPU. Yes, I can actually watch my utility/electric bill go up and down every time the CPUs are acccessed. lol
-
I've left my server up and running now for about 2 days without rebooting/restarting. So far, I haven't really seen any memory leak or high CPU usage at all. RAM usage still hovering around 35-37% which is kind of normal for my system and the CPUs really never get over 25%.
-
Open Steam. Go to view at the top. Then look for Game Servers on the drop down box. Click on Favorites on the new window that pops up and look for the + sign on the bottom right of the screen. This will allow you to manually enter in your WAN or LAN server's IP address. This way you can see if it "resolves". If it doesn't show up here, then there is something configured incorrectly.
-
Chiming in on this; I've been running ich777's containers on "bridge" network for a while now with no issues. Have I been doing it wrong for years and I just don't know any better? I only have two containers on host; Plex and Home Assistant. Every single other container is bridge.
-
You know your own External IP address? If so, then enter your server into the Steam Server browser manually and try to connect to it that way instead of watiing for the in-game-server-browser to populate. This way you know if it's working or not instead of wasting time waiting for it to auto populate.
-
Thank you for explaining it better than I did. Sorry I couldn't elaborate more. I was in the middle of finally getting Fiber internet installed.
-
@Nodiaque It's a minor thing and maybe now that it's in C.A. it won't show anymore? Right after creating the my-enshrouded.xml file and then importing off of github and then adding the container from the templates. On that screen that follows it's right at the very top. I should have taken a screenshot but I was so excited about finally getting it up and running that I just continued forward figuring that was a leftover remnant from a Palword game server docker template that must have been used to build this one.
-
Imported the XML and just saw a minor typo at the top after you import the XML: This Docker will download and install SteamCMD. It will also install Palworld and run it.
-
From what I've read, the dedicated server stuff hasn't been optimized as yet by the DEVs
-
This still isn't listed in C.A.?? I had a work trip, figured I'd come back and install it, and it's still not listed? Yes, I know I can do the XML file thing but, I feel bad that it's not listed still after all this time you've put in.
-
@Nodiaquestill no results searching for "Enshrouded" in the CA Apps plug-in. That was really cool of @ich777to lend a hand !
-
There seems to be quite a few of them on Docker hub. However, I wouldn't even know which one would be "best" and not sure the level of trust would be the same as an ich777 docker container lol
-
Damn. That is disappointing - I came on here to ask for the same; Enshrouded Server. I do understand though, you've done a lot. Hopefully someone else makes one as rock solid as your Valheim server has been for me and, many others.
-
This helped me a great deal when setting up my notifcations https://community.home-assistant.io/t/frigate-mobile-app-notifications/311091
-
Ok, I took your advice and dropped it down to 4ps. I didn't see any noticeable difference either. Thank you for that suggestion.
-
Sorry. Absolutely nothing you just said made any sense to me. I'm waiting for the next version of Frigate, like you mentioned, that will have the NVIDIA detection stuff "built in". I can only guess that's what you meant by hwaccel card? I gave up on the TesnoRT stuff once I read your comment about that. I've offered cold-hard-Paypal funds to many people on many Frigate forums to just code my YML for me since I've been working on this for almost a year now and simply can't figure it out. No one has taken me up on my offer. So, I just keep plugging away at this in an act of frustration. Thanks anyway. I will continue to just lurk here and read and not post anything because I don't have the basic knowledge to even understand your reply. lol