10 months ago
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/ab9f0328-1668-4d99-9670-1aeed788fbc2/vol_rgqe02hjsgsw83ij
Accademic-Issue-Tracking-System
Starting Container
Accademic-Issue-Tracking-System
Operations to perform:
Accademic-Issue-Tracking-System
Apply all migrations: admin, auth, contenttypes, logbook, sessions
Accademic-Issue-Tracking-System
Running migrations:
Accademic-Issue-Tracking-System
No migrations to apply.
Accademic-Issue-Tracking-System
Stopping Container
Accademic-Issue-Tracking-System
[2025-05-16 08:55:51 +0000] [1] [INFO] Handling signal: term
Accademic-Issue-Tracking-System
[2025-05-16 08:55:51 +0000] [2] [INFO] Worker exiting (pid: 2)
Accademic-Issue-Tracking-System
[2025-05-16 08:55:52 +0000] [1] [INFO] Shutting down: Master
Accademic-Issue-Tracking-System
Stopping Container
Accademic-Issue-Tracking-System
Starting Container
Accademic-Issue-Tracking-System
Operations to perform:
Accademic-Issue-Tracking-System
Apply all migrations: admin, auth, contenttypes, logbook, sessions
Accademic-Issue-Tracking-System
Running migrations:
Accademic-Issue-Tracking-System
No migrations to apply.
Accademic-Issue-Tracking-System
Starting Container
Accademic-Issue-Tracking-System
Operations to perform:
Accademic-Issue-Tracking-System
Apply all migrations: admin, auth, contenttypes, logbook, sessions
Accademic-Issue-Tracking-System
Running migrations:
Accademic-Issue-Tracking-System
No migrations to apply.
Accademic-Issue-Tracking-System
Stopping Container
Accademic-Issue-Tracking-System
Starting Container
Accademic-Issue-Tracking-System
[2025-05-16 09:16:08 +0000] [1] [INFO] Starting gunicorn 23.0.0
Accademic-Issue-Tracking-System
[2025-05-16 09:16:08 +0000] [1] [INFO] Listening at: http://0.0.0.0:8000 (1)
Accademic-Issue-Tracking-System
[2025-05-16 09:16:08 +0000] [1] [INFO] Using worker: sync
Accademic-Issue-Tracking-System
[2025-05-16 09:16:08 +0000] [2] [INFO] Booting worker with pid: 2
Accademic-Issue-Tracking-System
Stopping Container
Accademic-Issue-Tracking-System
ERROR: Login error: {'non_field_errors': [ErrorDetail(string='Invalid credentials or inactive account.', code='invalid')]}
Accademic-Issue-Tracking-System
Internal Server Error: /login/
Accademic-Issue-Tracking-System
Stopping Container
1 Replies
10 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 10 months ago
10 months ago
Try adding a start-up cmd like gunicorn accademic.wsgi:application --bind 0.0.0.0:$PORT
If you’re running migrations in an entry-script, end that script with exec "$@" so the container hands over to Gunicorn and doesn’t just exit. Then redeploy.
Btw, sometimes we just waste too much time trying to fix something just for the sake of it, so whenever you're stuck with sth for too long, rethink if that method, service, architecture or stack is the right one. Things are evolving so freaking fast these days that a matter of hours will make you ditch sth you spent countless hours on to sth often better, faster, cheaper and nicer lol