Forums

I set all VirtualEnv and MySql databases and the front pages are working fine. however, when I try to access to the backend which is admin pages, I get

Something went wrong :-(

page. here is the server log

2020-07-11 13:41:19 *** backtrace of 13 ***#012loghomecrew loghomecrew.pythonanywhere.com uWSGI worker 1(uwsgi_backtrace+0x2c) [0x46529c]#012loghomecrew loghomecrew.pythonanywhere.com uWSGI worker 1(uwsgi_segfault+0x21) [0x465661]#012/lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7f09942964b0]#012/usr/lib/libpython3.7m.so.1.0(+0xe7bbf) [0x7f0990d7dbbf]#012/usr/lib/libpython3.7m.so.1.0(+0x13c441) [0x7f0990dd2441]#012/usr/lib/libpython3.7m.so.1.0(+0xf8283) [0x7f0990d8e283]#012/usr/lib/libpython3.7m.so.1.0(_PyObject_FastCallKeywords+0x104) [0x7f0990d30024]#012/usr/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x32aa) [0x7f0990d02d2a]#012/usr/lib/libpython3.7m.so.1.0(+0x688c0) [0x7f0990cfe8c0]#012/usr/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x7060) [0x7f0990d06ae0]#012/usr/lib/libpython3.7m.so.1.0(+0x688c0) [0x7f0990cfe8c0]#012/usr/lib/libpython3.7m.so.1.0(_PyFunction_FastCallDict+0x2be) [0x7f0990d2f8ae]#012/usr/lib/libpython3.7m.so.1.0(_PyObject_Call_Prepend+0xcd) [0x7f0990d30a2

there is no error message on the error log.

database settings are this

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': env('NAME'),
        'USER': env('USER'),
        'PASSWORD': env('PASSWORD'),
        'HOST': env('HOST'),
        'PORT': '',
    },
}

Are you using Django >= 3.0 with Python 3.7? If so, I think it might be happening because of a bug in Python 3.7.0, which is the point release of 3.7 that your account is configured to use. We can change it to 3.7.5, which does not have that bug, by changing your account's system image to our latest one. But one word of warning first -- because of the changes to the point releases of Python, any virtualenvs you have might break -- and if you're not using virtualenvs, the pre-installed Python modules will be upgraded so that might break any code you have that relies on the old installed versions.

If you're happy for us to switch you over despite that, then let us know.

The alternative would be to use Python 3.6, which also does not have that bug, or to use an older version of Django.

yes, I don't mine and I can easily fix the virtualenv problem(I guess).

change python version to the latest.

OK, no problem -- that's done now. Any new consoles you start will have the new system image; any scheduled/always-on tasks and websites will pick it up the next time they're (re)started.