Update to v3.15 issue

32 views
Skip to first unread message

Sergi Lendínez

unread,
Mar 3, 2022, 11:46:23 AM3/3/22
to nemo
Hello,

We have recently updated nemo from v3.13.2 to v3.15. To do so, we installed Python3.7 as required. (We are running nemo on a CentOS7 server.) The nemo install completed successfully, as well as the "django-admin collectstatic" and "django-admin migrate" commands.

Now, the new section of the landing page shows that nemo was updated to 3.15. However, the bottom bar of the landing page still shows v3.13.2, and it seems that the new features are not implemented: The Lab manager role is not showing up; the qualified checkbox is still unchecked by default; there is no Staff availability option on Detail administration; etc.

One thing I noticed is that new user permissions options have appeared on the Detailed Administration -> Users. These are the options related to closure, closure time, etc. which I think become available with v3.15.0.

Any ideas what could be going on?

Thank you,
Sergi


mathieu...@gmail.com

unread,
Mar 3, 2022, 12:18:56 PM3/3/22
to nemo, sergi...@gmail.com
Hello Sergi,
It's probably a mix up between python3.7 and whatever previous version you had.

I would double check that the pip command you used to update is the one in 3.7, check the django-admin command, and the gunicorn/systemd service command you are using to run NEMO.
"which django-admin" for example should show you a path inside python3.7 directory

My guess would be that you updated everything correctly with 3.7, but that you are running using gunicorn which points to the previous python environment, where 3.13.2 was installed.

Good luck!

Sergi Lendínez

unread,
Mar 3, 2022, 12:41:37 PM3/3/22
to nemo, mathieu...@gmail.com, Sergi Lendínez
Hi Mathieu,

That was indeed the issue. I just reinstalled gunicorn using the pip3 install command that now points to the python3.7 directory and that solved it.

Thanks, as always, for your useful help!

Sergi
Reply all
Reply to author
Forward
0 new messages