Closed DammersH closed 1 year ago
First of all, did you turn the debug mode on by using DEBUG=1
? Afterwards there should be additional log output which helps with debugging the issue.
From a first look your setup seems fine. Since you mounted the mediafiles folder via a bind mount, the photos should be in the local mediafiles
folder. Can you check its contents and make sure that all the images are indeed there?
I'm not sure about the gunicorn error, but it shouldn't have anything to do with loading the images since they should be served directly by nginx instead of gunicorn.
Okay, interesseting the folder for the mediafiles was empty. Not that I did this on puropose, since I can only access it via shell. I will try readding the pictures and look what happens.
Where shall I look for the log files? Docker log or tandoor itself? Tandorr recognizes the debug mode, but I don't see any relevant logs when adding pictures.
'Current' logfile looks like this: `Gunicorn Media: False Sqlite: False Debug: True
SERVER_PROTOCOL:HTTP/1.0 REMOTE_ADDR:172.29.8.4 SERVER_PORT:8080
HTTP_HOST:mooncake:9999
HTTP_CONNECTION:close
HTTP_USER_AGENT:Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0
HTTP_ACCEPT:text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,/;q=0.8
HTTP_ACCEPT_LANGUAGE:de,en-US;q=0.7,en;q=0.3
HTTP_ACCEPT_ENCODING:gzip, deflate
HTTP_REFERER:http://
wsgi.errors:<gunicorn.http.wsgi.WSGIErrorsWrapper object at 0x7fe54e847100> wsgi.version:(1, 0) wsgi.multithread:True wsgi.multiprocess:True wsgi.run_once:False wsgi.file_wrapper: wsgi.input_terminated:True wsgi.input:<gunicorn.http.body.Body object at 0x7fe54e6a2da0> wsgi.url_scheme:http `
The logs should be visible in the docker container The output you sent is not the logfile but just some debug parameters.
The log files don't throw any error.
It seems that shutting down the NAS during the night somehow purges the media folder. Because the media files survive a container reboot but didn't survived the NAS shutdown.
Must be somehow a QNAP behavior...
I will try a different approach for storing the pictures and will come back with more information
It seems that solved it:
Instead of using a bind mount I went for volume and switched everything
from ./mediafiles
to mediafiles
and created a corresponding volume.
Thanks for the help @gloriousDan and the hint where to look for the media files.
Issue
Hello folks,
I'm a little bit lost here, were I made a wrong turn.
What i did tried after reading the FAQ was adding one of these entries to the .env
- MEDIA_URL=https://<myserver.name>9999/media/
- MEDIA_URL=https://<myserver.name>9999/media/recipes
- MEDIA_URL=https://<myserver.ipadress>9999/media/
- MEDIA_URL=https://<myserver.ipadress>9999/media/recipes
Out of fear I reuploaded all the pictures just to be sure, that I didn't deleted them
Tandoor Version
1.5.2
OS Version
QNAP QTS 5.0.1
Setup
Docker / Docker-Compose
Reverse Proxy
No reverse proxy
Other
No response
Environment file
Docker-Compose file
Relevant logs