-
Notifications
You must be signed in to change notification settings - Fork 1
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
Exceptions during setup.sh execution #69
Comments
Celery logging errors "real time" During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): [2024-12-16 22:11:51,216: WARNING/ForkPoolWorker-4] /opt/invenio/.venv/lib/python3.12/site-packages/invenio_rdm_records/services/tasks.py:63: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC). |
Ivan, I built image My When I run the following with the default compose file in separate terminal windows:
I don't see any exceptions in setup.sh execution. This is with a clean install and no pre-existing db, web or worker containers. I need to create an admin account and can then upload files to s3. The last few lines of the setup.sh output (where they start to differ from yours) are:
|
Looking at your output, it seems that the errors are triggered when trying to create OpenSearch indexes. Is this on a fresh install? You can remove the OpenSearch indexes with |
It was bad indices Martin, thanks. |
Still seeing validation errors using "latest" pull on clean install. S3 issue still? In my docker-compose I have
This appears twice, once for environment:and then again in worker: section In my invenio.cfg I have (unchanged from git pull)
AND
My bucket rdm12 in exists in eu-central-1 and has the CORS headers set. What works?
What fails? Questions
|
@ivanbishop The s3 settings in the Docker Compose are duplicated because |
|
I tested uploading with the |
In summary, I think that something is not working with passing ENV variables into the InvenioRDM instance. Check the |
Ah! Fool me... can u pls share your obfuscated .env file Martin. I totally blanked on config versus .env Thanks for your patience |
The S3 part looks like this: INVENIO_S3_ENDPOINT_URL=https://fly.storage.tigris.dev |
I updated the readme to include the S3 configuration: https://github.com/front-matter/invenio-rdm-starter. Did the same with the InvenioRDM Starter documentation (still updating): https://starter.front-matter.io/ |
@ivanbishop were you able to solve this? |
Hello Martin, haven't got round to testing. Mea Culpa. I will this weekend. Thanks. |
Using this image:
web:
image: ghcr.io/front-matter/invenio-rdm-starter:v12.0.10.1
pull_policy: if_not_present
Exceptions running
docker exec -it invenio-rdm-starter-worker-1 setup.sh
dec16th-setup.txt
The text was updated successfully, but these errors were encountered: