Jupiler

I've tried your suggestion @yayitazale but the new tensorRT model generation isn't very clear to me... I'm running into the following error when running the frigate:0.13.0-beta1-tensorrt docker I don't see any reference to having to build the new models myself in the new doc: https://deploy-preview-6262--frigate-docs.netlify.app/configuration/object_detectors/#generate-models D̶o̶ ̶w̶e̶ ̶s̶t̶i̶l̶l̶ ̶n̶e̶e̶d̶ ̶t̶o̶ ̶u̶s̶e̶ ̶t̶h̶e̶ ̶"̶t̶e̶n̶s̶o̶r̶r̶t̶-̶m̶o̶d̶e̶l̶s̶"̶ ̶d̶o̶c̶k̶e̶r̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶ ̶p̶r̶o̶c̶e̶s̶s̶ ̶o̶u̶t̶l̶i̶n̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶p̶r̶e̶v̶i̶o̶u̶s̶ ̶d̶o̶c̶ ̶f̶o̶r̶ ̶v̶1̶2̶ ̶ (like here) ̶t̶o̶ ̶g̶e̶n̶e̶r̶a̶t̶e̶ ̶t̶h̶e̶ ̶m̶o̶d̶e̶l̶s̶ ̶o̶r̶ ̶i̶s̶ ̶t̶h̶e̶ ̶n̶e̶w̶ ̶B̶e̶t̶a̶ ̶1̶3̶ ̶t̶a̶k̶i̶n̶g̶ ̶c̶a̶r̶e̶ ̶o̶f̶ ̶i̶t̶ ̶a̶l̶l̶ ̶w̶i̶t̶h̶i̶n̶ ̶t̶h̶e̶ ̶n̶e̶w̶ ̶c̶o̶n̶t̶a̶i̶n̶e̶r̶?̶ EDIT: nevermind, found the issue, I had to re-add --runtime=nvidia to the extra parameter of the docker container

Updated to 6.10.3, running an intel CPU (Q9400), appdata is set up as "Prefer: Cache" (should I set it up as cache only?). If we're talking about ServerFiles path it's `/mnt/user/appdata/vrising`. Still seeing the same errors after update: tail: cannot open '/serverdata/serverfiles/logs/VRisingServer.log' for reading: No such file or directory tail: no files remaining tail: invalid PID: ‘’ /opt/scripts/start-watchdog.sh: line 6: kill: `': not a pid or valid job spec tail: cannot open '/serverdata/serverfiles/logs/VRisingServer.log' for reading: No such file or directory tail: no files remaining tail: invalid PID: ‘’ /opt/scripts/start-watchdog.sh: line 6: kill: `': not a pid or valid job spec Session terminated, killing shell...kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

Hello, running into some issues when running the V Rising version of the container, I left all the parameters as default, didn't change any configuration, and on first boot, here is the log it produces, it keeps looping after a certain point ---Ensuring UID: 99 matches user--- ---Ensuring GID: 100 matches user--- ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Taking ownership of data...--- ---Starting...--- ---Update SteamCMD--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1654574676 -- type 'quit' to exit -- Loading Steam API...OK Connecting anonymously to Steam Public...OK Waiting for client config...OK /serverdata/steamcmd/steamcmd.sh: line 39: 32 Killed $DEBUGGER "$STEAMEXE" "$@" Waiting for user info...---Update Server--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' Looks like steam didn't shutdown cleanly, scheduling immediate update check [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1654574676 -- type 'quit' to exit -- Loading Steam API...OK "@sSteamCmdForcePlatformType" = "windows" �[0m Connecting anonymously to Steam Public...OK Waiting for client config...OK /serverdata/steamcmd/steamcmd.sh: line 39: 54 Killed $DEBUGGER "$STEAMEXE" "$@" Waiting for user info...---BepInEx for V Rising disabled!--- ---Checking if WINE workdirectory is present--- ---WINE workdirectory found--- ---Checking if WINE is properly installed--- ---WINE properly set up--- ---Checking for old display lock files--- ---Server ready--- ---Start Server--- tail: cannot open '/serverdata/serverfiles/logs/VRisingServer.log' for reading: No such file or directory tail: no files remaining tail: invalid PID: ‘’ /opt/scripts/start-watchdog.sh: line 6: kill: `': not a pid or valid job spec ---Ensuring UID: 99 matches user--- usermod: no changes ---Ensuring GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Taking ownership of data...--- ---Starting...--- ---Update SteamCMD--- ---Starting...--- ---Update SteamCMD--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' Looks like steam didn't shutdown cleanly, scheduling immediate update check [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1654574676 -- type 'quit' to exit -- Loading Steam API...OK Connecting anonymously to Steam Public...OK Waiting for client config...OK /serverdata/steamcmd/steamcmd.sh: line 39: 20 Killed $DEBUGGER "$STEAMEXE" "$@" Waiting for user info...---Update Server--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' Looks like steam didn't shutdown cleanly, scheduling immediate update check [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1654574676 -- type 'quit' to exit -- Loading Steam API...OK "@sSteamCmdForcePlatformType" = "windows" �[0m Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' Looks like steam didn't shutdown cleanly, scheduling immediate update check [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1654574676 -- type 'quit' to exit -- Loading Steam API...OK "@sSteamCmdForcePlatformType" = "windows" �[0m Connecting anonymously to Steam Public...OK Waiting for client config...OK /serverdata/steamcmd/steamcmd.sh: line 39: 40 Killed $DEBUGGER "$STEAMEXE" "$@" Waiting for user info...---BepInEx for V Rising disabled!--- ---Checking if WINE workdirectory is present--- ---WINE workdirectory found--- ---Checking if WINE is properly installed--- ---WINE properly set up--- ---Checking for old display lock files--- ---Server ready--- ---Start Server--- tail: cannot open '/serverdata/serverfiles/logs/VRisingServer.log' for reading: No such file or directory tail: no files remaining tail: invalid PID: ‘’ /opt/scripts/start-watchdog.sh: line 6: kill: `': not a pid or valid job spec ---Ensuring UID: 99 matches user--- usermod: no changes ---Ensuring GID: 100 matches user--- ---Ensuring UID: 99 matches user--- usermod: no changes ---Ensuring GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Taking ownership of data...--- ---Starting...--- ---Update SteamCMD--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' Looks like steam didn't shutdown cleanly, scheduling immediate update check [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1654574676 -- type 'quit' to exit -- Loading Steam API...OK Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' Looks like steam didn't shutdown cleanly, scheduling immediate update check [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1654574676 -- type 'quit' to exit -- Loading Steam API...OK Connecting anonymously to Steam Public...OK Waiting for client config...OK /serverdata/steamcmd/steamcmd.sh: line 39: 20 Killed $DEBUGGER "$STEAMEXE" "$@" Waiting for user info...---Update Server--- Maybe more specifically tied to this? Any help/insight appreciated! I have a Valheim version of the same container running flawlessly for months.

Apologies if this has been asked before, I looked but couldn't find an answer Regarding the Valheim (of course) dedicated server. I there a way to see the server logs themselves? I know how to access the docker logs (which might just be the exact server logs I'm talking about...), which works fine. But what I'm looking for is to be able to see which users connected to the server and at what time? Not sure if that can be surfaced in the docker logs or if that's even possible? Saw this image that outlined something similar, do I need to enable a different level of logging somewhere?

Quick update, when I use the cache drive, and then use the mover, speeds are a bit better. What I still don't understand is why every time I write something to the array, the disk shows the equal in read speeds? (with no other activity than writing to the array) Is there some verification mechanism that reads the data as it's writing it? I can't tell if this is expected behavior or not

Ah yes, that's my bad, I rewrote the command for clarity's sake and got the destination share wrong. I'm actually copying the data to TVShows (which has no cache), corrected version: rsync -zvh --progress /mnt/disks/Download/file1.zip /mnt/user/TVShows/file1.zip

Fairly new to unraid and I might be missing something obvious but when I transfer from an unassigned disk the to array I get the exact same write/read activity on the destination disk of the array? That and the speeds are very slow (10~20 MB/s) I mount the HDD using "Unassigned Device" and run the following command from the console: rsync -zvh --progress /mnt/disks/Download/file1.zip /mnt/user/Backup/file1.zip and I get around 10~20 mbps but weirdly the GUI Main page shows the exact same read and write speeds for the destination disk? (cache is not enabled for that share) Speed fluctuates but is always the exact same read and write on the same disk (see screenshot). Same when I try the "cp" command. Not sure if that is expected behavior or an indication as to why I'm getting very slow transfer speeds? borgcube-diagnostics-20200307-1638.zip