Forums

DAMN ! worker 1 (pid: 205) died, killed by signal 7 :( trying respawn ...

Have a simple sign in page. Everytime trying to sgn in have next message in *.server.log

2018-05-22 02:13:48 DAMN ! worker 1 (pid: 199) died, killed by signal 7 :( trying respawn ...
2018-05-22 02:13:48 Respawned uWSGI worker 1 (new pid: 202)
2018-05-22 02:13:48 spawned 2 offload threads for uWSGI worker 1
2018-05-22 02:14:30 announcing my loyalty to the Emperor...
2018-05-22 02:14:32 DAMN ! worker 1 (pid: 202) died, killed by signal 7 :( trying respawn ...
2018-05-22 02:14:32 Respawned uWSGI worker 1 (new pid: 205)
2018-05-22 02:14:32 spawned 2 offload threads for uWSGI worker 1
2018-05-22 02:15:01 DAMN ! worker 1 (pid: 205) died, killed by signal 7 :( trying respawn ...
2018-05-22 02:15:01 Respawned uWSGI worker 1 (new pid: 208)
2018-05-22 02:15:01 spawned 2 offload threads for uWSGI worker 1

What does this message mean? Thank you for the help in advance.

That's one I haven't seen before. Signal 7 is usually for bad memory access and that's not usually a thing in Python. I would suggest trying to work out which view is causing the error and then see if you can isolate what is causing it in the view.

I am having the same issue. I am also getting a "Bus error" when running migrate or make makemigrations. I am trying to deploy a copy of an app that I am running in a different pythonanywhere instance, the only difference is that I am using MySQl in this instance and sqlite in the instance that works.
Any other suggestions at things to check?

thank you.

Update - I uninstalled a few packages and that cleared up the issue. I don't know which specific one caused the conflict as I had a lot of extra packages from my requirements.txt

Hhm. That's interesting. I'm not sure what a package would have to do to cause trouble like that just because it was installed.