Closed neutralboy closed 5 months ago
So I investigated further to see what could be going on and the backend container does not have show any log when the event happens
[2024-06-05 16:44:54 +0000] [1] [INFO] Starting gunicorn 22.0.0
[2024-06-05 16:44:54 +0000] [1] [INFO] Listening at: http://0.0.0.0:8000 (1)
[2024-06-05 16:44:54 +0000] [1] [INFO] Using worker: gthread
[2024-06-05 16:44:54 +0000] [7] [INFO] Booting worker with pid: 7
[2024-06-05 16:44:54 +0000] [8] [INFO] Booting worker with pid: 8
I also checked frappe.web.log
at /home/frappe/frappe-bench/sites/frontend/logs
It is empty
So turns out I had memory limits turned on for container which abruptly caused the container process to exit and restart immediately. This meant that it would result in the above errors.
Description of the issue
The docker compose
pwd.yaml
is broken. When the docker compose is run erpnext and frappe apps are successfully installed. This means that the frontend is also accessible on port 8080 as expected. Any action taken on it leads to an internal error. The frontend just logs that the upstream disconnected abruptly. However the DB logs as below:Context information (for bug reports)
I am running the pwd.yaml found in the main branch of this repo. I have made no changes and I ran the command with
I am on Ubuntu 22 with docker and compose plugin installed.
Steps to reproduce the issue
docker compose -f ./pwd.yaml
Observed result
Expected result
That I can login and make it work