-
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
Unable to upload layers anymore #4232
Comments
duplicate of #4233 ? |
No, different commits sadly, and setting |
Cannot update metadata either. |
@frafra can you maybe send instructions on how to setup the environment e try to reproduce this? |
Not easy to reproduce at the moment, but I will try to explain what is happening. We have 2 almost identical setups, one for testing, one for production.
The certificate is valid: https://www.ssllabs.com/ssltest/analyze.html?d=geodata.nina.no&latest |
Thanks @afabiani for the reply. The documentation says:
I am not used a self-signed nor a non-trusted certificate, so it seems strange to me that I have to manually add it to a custom keystore. The error comes from Django, so I do not understand why GeoServer truststore should be related. |
|
@giohappy yes, I still get that error and adding the certificate to the keystore (see #4245) didn't solve the issue. But I still don't understand why a |
Even if the browsers are able to connect to the website, it looks like the OS certificates are not enough. |
SSL issue is now resolved, but it would be nice to have a mechanism similar to #4245 to import the certificate chain. |
Still have the same old error: "DoesNotExist: AccessToken matching query does not exist." |
@frafra the issue here is not depending on the AccessToken. That is just a warning. The real cause is an issue with the layer upload, causing some sort of error/exception and next to the impossibility to unpickle the StackTrace stored into the UploadSession object. I remember facing a similar issue some time ago and tried to fix it like this https://github.com/GeoNode/geonode/blob/master/geonode/layers/views.py#L245 Question is, are you using GeoNode master branch code? Or 2.8.x one? If the latter, maybe it is just matter of backporting the fix, otherwise that means that the issue was not solved on master too. You might envisage to put some log lines on the view (see the reference above) and see what GeoServer Importer is returning. |
@afabiani Thank you for the reply. As I said in the first comment, I am running a quite recent version of GeoNode from master:
As |
Running SPCGeonode, GeoNode commit 287708d (Jan 15 2019). I am unable to upload layers. Data comes from a 2.8 instance. I tried to generate and run migrations to see it that could be the issue, but it is not (and the makemigrations warning is shown every time). GeoNode and GeoServer can talk each other and the configuration seems just fine.
It worked fine, now I have the same issue on two different servers. The only thing that happens is that the containers get restarted from time to time.
The first relevant error is the following one (I am logged in as administrator):
Then there is a database error and an additional error trying to manage the previous one.
Full logs below:
The text was updated successfully, but these errors were encountered: