-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error module encodings not found with manual install ubuntu 22.04 when try to activate uwsgi #12078
Comments
Folks I have a similar issue with GeoNode UWSGI Service. Please see my geonode log here; *** Starting uWSGI 2.0.20-debian (64bit) on [Thu Mar 28 18:26:10 2024] *** The above exception was the direct cause of the following exception: Traceback (most recent call last): unable to load app 0 (mountpoint='') (callable not found or import error) |
Expected Behavior
I have installed Geoserver successfully and went through the steps to install and initialize geonode. I think that it went correctly, though I'm not completely sure. The next step is to install uwsgi and nginx and have them be able to properly serve Geonode on my domain.
Actual Behavior
I have Geoserver installed and working properly. I install Geonode and initialize apparently successfully. When I then install UWSGI and try to start it up, I receive an error related to python that it is not able to find the module 'encodings'. The searching I have done shows this error appears to be related to where django is looking for python in the virtual environment. I just don't know how to fix the problem successfully. I've tried multiple installations of this and at this point, am getting stopped at the same place each time.
Steps to Reproduce the Problem
Specifications
I don't know if this is the proper place to put this issue, but I haven't received responses on the mailing list or Gitter page, so this seems to be my last option. I've attempted this install 7 or 8 times now with no luck.
20240229_IB_AWS_GeoNode_Install_MattiaGiupponi_Instructions.txt
The text was updated successfully, but these errors were encountered: