That fixed the issue on another test I installed, but didn't resolve the issue with my initial install. I started changing them one by one via the File Manager but that was tiresome so I open the Web Terminal and ran: I looked at the File Manager for the Volume and spotted that some folders and the metadata.db were owned by root instead of Cloudron. I think this is perhaps somehow related to Volumes because I was just able to recreate it. The newly built image has been uploaded to the docker hub: lwabish/calibre-web - Docker Image | Docker Hub.Said in Cloudron say app is running, but there is an Internal Server Error: The faster solution is: fork linuxserver/docker-calibre-web, add pip uninstall scholarly -y to the dockerfile and cancel the support of google scholar. It is initially suspected that google scholar was requested when editing the metadata of the book, but the status code 403 was returned, and the logic of the relevant code was wrong when processing the request for retry, resulting in infinite retry, which further blocked the main thread of the web server. You can see many duplicate log blocks in the log file as follows. Accordingly, the location in the container is / app/calibre-web/calibre-web.log The problem is still found, and the cluster network problem is preliminarily eliminated.Īt this time, you need to look at the calibre Web Log: after some search and research, it is found that the log of the project will not be output to stdout, but the calibre-web.log file located in the project directory. Checkįirst, directly use kubectl port forward calibre-6c5c84fd4f-z2mgb 8083:12345 proxy to access calibre's pod in the cluster, bypass other network components in the cluster, such as traefik, and eliminate the problem of the cluster itself. Using Linux server in k8s cluster linuxserver/docker-calibre-web The image is deployed janeczku/calibre-web, after 211011 upgraded the latest image, it was found that the web page was frequently unresponsive: the browser tab continued to rotate, and the timeout would not be reported until a long time later, and all requests could not be completed normally since then.Īfter many attempts, it is found that the operation method of reproducing the problem in the front end is to edit books, obtain metadata and click save.
0 kommentar(er)
