be4con

Thanks for the reply, sorry for the delay I've been away. I don't recall doing anything with SMB. The settings look standard and all my mounts are local drives.

Hi I seem to be getting this error and a reboot does not clear it. My server appears to functioning normally so I don't know whether it's anything I need to be concerned about. Can anyone advise? Thanks in advance tower-diagnostics-20231027-2232.zip

Thanks - I think I'm going to have to try rolling back. Unfortunately, I have also done the 6.12.2 upgrade so I can't just rollback within Unraid. I'll also do as you suggested and try with a small library. Thanks.

Any suggestions please? This is driving me nuts

Getting nowhere with MyMedia support they are ignoring my ticket requests. Can anyone help at all?

Thanks Oh, it's definitely misbehaving. I've got another support chat running about that container, although the support thread for the docker is pretty much dead. I've been having problems with it constantly stopping and refusing to autostart. So, I can't really check whether stopping that resolves anything because more often than not it's in the stopped state. I went through the process of uninstalling that container, deleting the image and the container's appdata folder and performing a fresh install but the issue with it continually stopping just returned as soon as I reinstalled it, and it's not really behaving normally since I reinstalled it either (it won't index the files on the server). I raised a ticket with the MMfA devs and they have failed to respond to that too. Getting a bit frustrating to be honest.

tower-diagnostics-20230704-1808.zip

Yeah I rebooted both after the install of the swapfile plugin and after uninstall of it, so the warnings were new at each stage. Just run FCP again and got a new error: Fresh diags attached tower-diagnostics-20230704-1808.zip

Both errors disappeared when I uninstalled the swap file plugin, but the Out of Memory error recurred. Any suggestions on what I do?

I've added the swapfile plugin and started it with 8MB file. The error has gone for the moment but as soon as I did this I got 2 new errors reported, not sure if correlation or causation:

Still having issues. I upgraded my RAM to 16Gb, and I also limited the memory use to 4Gb per docker as advised. I have yet to institute a swap file, but before I do that I thought we should explore further why this might be happening. I'm not running anything especially RAM heavy - I only have 2 active dockers, Delugevpn and MyMedia for Alexa - and there should be plenty of available RAM for what I am trying to achieve without adding a swap file surely? Any further advice before I explore swap files?

Thanks, yes it runs when I start it manually but then it randomly stops again after a variable period of time - usually after an hour or two. I am on 6.12, yes. Do you think it's worth rolling back?

I've tried everything now, including a full uninstall and deleting the image and my appdata folder, but when I reinstalled the docker I have the same issue. Can anyone help?

From what I had read, I thought 4Gb should be plenty, but I've managed to find an upgrade kit for my ancient server, so I'll boost the memory to the 16G max and see if that resolves everything. Thanks.

Last few days the docker keeps stopping, and despite autostart being set it doesn't start on a reboot. I've forced an update, and also updated unraid, but the issue remains. Any suggestions? Thanks

Thanks, I have only 4G RAM. Is it reasonable to limit it to 1G max per Docker? 2G??

Thanks, it happens periodically, maybe once per month on average. How do I go about limiting the RAM for VMs and/or docker containers? Do you think this could be the reason that the MyMedia docker keeps stopping, or should I look for specific help with that docker community?

Hi all I've been suffering occasional Out of Memory Errors for a while and haven't been able to get to the bottom of them myself. Can anyone help me resolve them? I haven't noted any issues with this until recently, then the last few days my MyMedia for Alexa Docker keeps stopping and won't auto-restart so I'm wondering if that is related. My diagnostics are attached. TIA tower-diagnostics-20230619-1126.zip

It's far more likely that I don't understand how this container works, and whilst my IT knowledge is intermediate my understanding of networking (and dockers/linux) is pretty rudimentary so forgive me if I have totally got this wrong. I don't know if any of this is relevant, but I'll include it just in case. My setup is that I have PIA installed on my router. However traffic to my unraid server is routed outside the VPN tunnel as I only needed deluge to be included. My understanding was that this container polled PIA for a forwarded port and then fed that back to the settings/config of the deluge client so that the correct static port was listed. However, I thought that (as with the standard deluge client) I still needed to take that port and forward it on my router, so that is what I have been trying to do. When I do that if I go to portchecker.co to test my port using the external IP address in deluge, and the port provided by the container then the port shows as open. If I don't port forward on my router it appears to show as closed. Similarly, when I port forward on my router then I show as connectable on the private tracker but when I don't I show (after variable delay I must admit) as not-connectable. You are correct I did use the magnet link on ipleak, though I hadn't considered that it wasn't in the same tunnel. I'm not sure I follow why that makes a difference though as the torrent that is used as a reference for the port probe is within the VPN tunnel and the browser site just reports the results. I guess I don't need to understand it though - if you do, and tell me that the information can't be relied upon I'm happy to accept that.

Just bumping this as I am still confused by this an hoping someone can help. If I don't port forward on my router then the port shows as closed and I am not connectable on the tracker. What am I doing wrong if port forwarding on my router isn't needed?

Suddenly started working again without me doing anytrhing but I'll try this next time, thanks

That's interesting, because unless I manually forward the port on my router it shows as closed. What do you mean by 'correctly using'? The container works fine, the log shows connected to PIA and gives a port which it maintains. As far as I can tell the VPN function is working OK - how else would I check it?

Does anyone know of a way I can propagate port changes in the docker back to my router so I don't have to do it manually to maintain port forwarding with PIA? I'm running an ASUS AC86U with Merlin firmware. TIA

I'm getting server disconnected (code 1006). Was working fine a couple of days ago, but now I can't seem to access the webUI. I had a look through the github docs and couldn't find anything that helps. Tried restarting the container but same result. Any suggestions?

Ah, the Host path is me messing with different options to see if anything worked - thought I'd changed it back before I took the screenshot. Apparently not. For the config fille - what's all the gubbins about changing the path mean then? I thought I had just followed the instructions in the file itself. OK, having changed that it is now finding files! Thanks for working through that with me. The log is showing a new issue though: It still seems to be scanning and finding new files but that last line is just repeating ad infinitum.