eds
Members
-
Joined
-
Last visited
-
Yes. I was doing a back up to remote server using duplicati. The system froze and I could not log in. I've had this problem before, but I attributed it to a windows 11 vm. Perhaps both running was the culprit. Glad to know its not bad ram. Will see if I can configure duplicati better. Thanks for the feedback.
-
Hello everyone. Running unraid 7.2.3 and Fix common problems reports the following on my system: Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the Unraid forums. I think I have a bad ram stick (or sticks), but not sure. Per forum instructions I've since rebooted my server. Attached is anonymized diagnostics (prior to the reboot). Any advice would be appreciated. --ES tsunamidream-diagnostics-20260116-0829-anonymized.zip
-
Getting same message/error:
-
This is a frustrating problem I cannot quite pinpoint, but will try to explain. I updated from 7.1.2 to 7.1.4 a few days ago. I started having issues with Cloudflare tunnel docker. The tunnel kept degrading, then coming back, then degrading, then coming back, then degrading, then coming back, etc. I initially thought it was a network cable issue, then an issue with one of my dockers using the tunnel, until I finally zeroed in (after a day) on cloudflare tunnel docker. I then went about creating new tunnels, deleting old tunnels and adding and removing tokens, deleting the docker, installing a new docker –all to no avail. After looking at forums, it dawned on me that this might be a networking issue with 7.1.4. So I reverted back to 7.1.2. But I am still having some wonky issues. For example, docker containers have are updates, but when I try, no updates download. Plugins check for update and sometimes I get a broken link, sometimes not. I am at my wits end. Any help would be appreciated. Thanks.tsunamidream-diagnostics-20250626-1935.zip Quick note: my vms are rock solid. No networking issues with any of them.
-
Not sure if this is related to the above mentioned issue with the cloudflare tunnel, but within the last five days, I've been having issues with the cloudflare tunnel. Log looks something like this: I am not sure what to make of it. If I restart the tunnel it come up for a few seconds, then goes down again. I was able to get it to last for a few days before going back down again. Also, I recently upgraded to 7.1.4 as well. Any thoughts?
-
I would love to know this. Would make this docker so much more useful.
-
I got this app installed and working. One of the questions I have: how to improve plugins support? There are a couple I would like to try but not sure how to install. Are there any instructions available?
-
I am wondering if anyone is experiencing issues recording. I can tune in channels, but if I try to record, I get the error "it looks like something went wrong. please try again". This has been since updating to the most recent docker version about a week ago. I keep seeing two errors in the logs: downloadContainer: expected MediaContainer element, found html Invalid library metadata ID tv.plex.xmltv://episode/CNN%20News%20Central/1/288 passed. Any help would be appreciated.
-
👍👍👍
-
I went back to 4.8.1.
-
I reverted back to a previous working build so that I could wait the "few weeks". Will give a look at the github issue link above. Thanks.
-
Lychee appears to be broken with newest build. Target class [log-viewer] does not exist. How to fix?
-
Ok. So this was my error. I was streaming at a rate "passthrough". This means, while encoding appears to be happening (according to the log), it is not. No encoding is happening server side - the stream is literally just passing through. I discovered that you can have multiple streams of different bitrate, frame rate, resolution, etc (low, medium, high and passthrough if you will). It's here that encoding actually happens. Once you set the different rates and begin the stream, the hardware transcoder using the gpu is engaged. Great work on nvidia plugin and this docker OP!
-
Thanks for catching that missing variable. I added it -- still no go. GPU is not being used when encoding. nvidia-smi shows nothing running when a stream is being sent to owncast. Will play with it some more tomorrow and see if I can narrow down the issue. Thanks again!
-
Thanks for the quick response. Not sure what you want to see from the owncast config. The owncast log says: "Video transcoder started using nvidia nvenc with 1 stream variants." But I can see no evidence of that. Is there a command in the docker that can be run by ffmpeg to give data on the nvidia hardware that is using the nvenc codec (like the gpu id)? Below is what i see in the admin area which appears to be normal. And attached is the advanced view. I pretty much guessed by using the docker notes (and having done this for other dockers) where everything goes. Let me know your thoughts..
