-
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
Upload failure: saved_layer is None #4241
Comments
I see similar errors on GeoServer, like:
Before that I read:
RabbitMQ says:
...and...
|
I see the standard Geonode black bar on top, like I has been kicked out, with no possibility to login directly (CSRF error), so I have to refresh the page. https://screenshots.firefox.com/3GFdEpB6m6yAtxaF/nindocker02.nina.no
|
It looks like the Rabbit MQ error is not critical and can be ignored (it happens even in successful tests) and even the "file not found" message seems not relevant. A bit hard to debug with all these non-relevant errors :-) It is not a network issue either. It seems to be linked with the data volumes, because using the same configuration with a different set of volumes fixes it; maybe some incompatibilities between 2.8 and current master. |
I can confirm this error happens also on fresh and working docker setups. I just tried to upload an archive:
|
Workaround: I created a fresh instance and moved the data with the aid of some tools I developed. |
It seems hard to me to understand what could be the issue because GeoNode is not able to display its error properly. See: #4321 |
I get those errors, too. I used SPC with |
@gannebamm any chance to test again with these changes? |
@afabiani My error was related to SSL misconfiguration. The message:
was just a culminating message, which was not related to the original failure. |
@gannebamm yeps, that PR aims to avoid hiding those errors and trying to push up the original cause to the interface (as much as possible) |
Running SPCGeonode, GeoNode commit 287708d (Jan 15 2019).
I also see some errors on GeoServer:
The text was updated successfully, but these errors were encountered: