New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect to Medusa - Log shows everything is running as usual #11645
Comments
I've seem to have the same problem.
Did your problem resolve itself or did you have to do something else? |
This problem has just kicked in for me, I had a networking issue last night, so I thought it was that. I've fixed that issue and now re-spun a fresh docker container of medusa AND I've rebooted the ubuntu server host AND I've rebooted the proxmox host which was running the ubuntu VM Nope and nope, still the same issue. I'm also connected to a CIFS server? |
I have attempted to roll back to an earlier docker image but from what I can tell, this didn't work either. |
+1 |
It seems to be a bug in cifs, |
I am a bit confused because my docker configuration data, for medusa is located on my local filesystem? |
Well Regardless of my skills and assumptions! You're correct and my confusion is irrelevant! It totally fixed the problem so I really appreciate it. Not a medusa fault, odd for it to 'fall over' due to SMB / CIFS issues just for the data folders but she seems ok. Really appreciate it, thank you. |
@jaxjexjox i have done the same fix than you |
I have no idea but I have thanked and asked the person on reddit, for their advice for this next month. |
My copy of pyMedusa suddenly showing "unable to connect to Medusa". Not sure what happened as it has been running fine prior to this. This pyMedusa was a docker installed.
The docker is on a different machine than all the media. Volume for the media is linked as writable CIFS.
I think this issue was caused by a "storage check" function on the script where it could not get the available storage due to the media volume being a network drive although this is my guess from the log, I'm no dev.
a few lines after that then I saw these:
So it can see the folder and contents within the folder.
Can someone help?
The text was updated successfully, but these errors were encountered: