Skip to content
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 error message #1611

Open
openbrian opened this issue Nov 10, 2023 · 3 comments
Open

Upload failure error message #1611

openbrian opened this issue Nov 10, 2023 · 3 comments

Comments

@openbrian
Copy link

Describe the bug

I've had uploads work. And now one is failing. I see "Error i" in red. When I mouse over this I get the request uuid.

Expected Behavior

I want to see the error message!

If you don't have the error handy, tell or direct the user to where to see the error message.

Steps to Reproduce the Problem

  1. Hard to say, I don't know why the upload is failing.

Specifications

  • GeoNode client version: 4.2.0 dev
  • Browser: Firefox
  • Installation type (vanilla, geonode-project): docker-compose
  • Additional details:

I've already called /api/v2/upload-size-limits to see the limits were set to 5MB. I used the admin interface to raise that to 50MB. My upload file is about 11MB. I've also restarted the django service in the docker-compose.

Online documentation at https://docs.geonode.org/en/master/usage/managing_datasets/uploading_datasets.html does not say where to find the error message.

I've check /var/log/geonode.log in the django service. But there are no error messages here. I've also checked celery and rabbit logs.

Where's the error message?

@openbrian
Copy link
Author

docker compose logs celery didn't have the error message, but docker compose exec celery cat /var/log/celery.log did. That error message is not coming out via /executionrequest.

@openbrian
Copy link
Author

docker compose logs celery didn't have the error message, but docker compose exec celery cat /var/log/celery.log did. That error message is not coming out via /executionrequest.

So many pieces in GeoNode. Can you get that message to the appropriate project? Thanks.

@ffischer1984
Copy link

I would recommend to use the "DEFAULT_MAX_UPLOAD_SIZE" Environment Variable by the .env file.
I'm unsure if the value persists after a restart when you set it through the Django admin panel.
Uploadsizes near 1gb or above are not recommended.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants