Data upload via web UI fails - Logs

[marriz]

Dear openBIS community,

I am using an openBIS v20.10.5 docker container. I tried data upload via web UI (as shown here: https://openbis.ch/index.php/docs/user-documentation/data-upload/data-upload-via-web-ui/). The upload fails consistently, even with adjustments to dss_etc/service.properties. Logs in dss_logs are informative, while as_logs logs show only a “Cache clearance execution” entry. The only logs are in datastore_server/log-registrations/succeeded/ (not failed).

cat '2023-01-10_10-56-52-315_JythonIngestionService_2023-01-10_10-56-52-314_Service Conversations-T6::1673348212308-451712491 (ch.systemsx.cisd.openbis.generic.shared.IDataStoreService)_fileserialized.log'
2023-01-10 10:56:52 Start registration
2023-01-10 10:56:52 Prepared registration of 0 data sets:

2023-01-10 10:56:52 Preparation ready
2023-01-10 10:56:52 In pre-commit state; no data needed to be moved.
2023-01-10 10:56:52 About to register metadata with AS: registrationId(34)
2023-01-10 10:56:52 Will try to register data in openbis.
2023-01-10 10:56:52 No entities have been created or updated
2023-01-10 10:56:52 Data has been registered with the openBIS Application Server.
2023-01-10 10:56:52 Storage processors have committed.
2023-01-10 10:56:52 Data has been moved to the final store.

How can I further navigate this “upload failed” behaviour?

Thank you and best regards,
Mariam
Scientific IT, Fraunhofer IFAM

[marriz]

I would document my work on this issue for future use. My advice, when using docker.

• Make sure that you have a Role in openBIS for the etlserver user (core UI: Administration → Authorization → Roles → Assign Role) Choose as a role ‘INSTANCE_ETL_SERVER’ and select as a person ‘etlserver’ (Installation and Administrators Guide of the openBIS Data Store Server - openBIS Documentation Rel. 20.10 - Confluence)
• Make sure that, when you create the container, you write the absolute domain name: -e SERVER_HOST_PORT=openbis.university.de:443 --hostname=openbis.
• Unfortunately, it is better to create a new container (even with a new bind-mount directory). You might need to move the postgres_data dir from the older volume.

Best regards,
Mariam