International-Data-Spaces-Association / IDS-testbed

Apache License 2.0
24 stars 32 forks source link

Omejdn is not working in tesbed #139

Closed parwinderau closed 3 months ago

parwinderau commented 4 months ago

Dear Team,

I am trying to use IDS testbed to validate dataspace. However, I am countering the issues specific to the omejdn as given below. omejdn | 2024/04/22 13:03:31 [emerg] 1#1: unexpected "(" in /etc/nginx/conf.d/default.conf:14 omejdn | nginx: [emerg] unexpected "(" in /etc/nginx/conf.d/default.conf:14

I tried different versions, but they are still not working. This is an issue of parsing Ngnix.conf into the omejdn while creating the container. Due to this the connectorA could not get register with the broker as DAPS remains unreachable. Please help and let me know if you need any further rinformation

===================More logs are given below======================================= azureuser@IDSConnector:~/IDS-testbed$ docker-compose up Starting broker-core ... done Starting omejdn-ui ... done Starting omejdn-server ... done Starting postgresb-container ... done Starting postgresa-container ... done Recreating omejdn ... done Starting broker-fuseki ... done Starting broker-reverseproxy ... done Starting connectora ... done Starting connectorb ... done Attaching to broker-core, omejdn-server, omejdn-ui, postgresa-container, broker-fuseki, postgresb-container, broker-reverseproxy, omejdn, connectora, connectorb broker-core | Starting Spring boot app broker-core | ARGS=-Djava.security.egd=file:/dev/./urandom -Dsparql.url=http://broker-fuseki:3030/connectorData -Delasticsearch.hostname=broker-elasticsearch -Ddaps.validateIncoming=true -Dinfomodel.validateWithShacl=true -Dcomponent.uri=https://localhost/ -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005 broker-core | Listening for transport dt_socket at address: 5005 broker-reverseproxy | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration broker-reverseproxy | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/ broker-reverseproxy | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh broker-reverseproxy | 10-listen-on-ipv6-by-default.sh: info: IPv6 listen already enabled broker-reverseproxy | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh broker-reverseproxy | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh broker-reverseproxy | /docker-entrypoint.sh: Configuration complete; ready for start up omejdn-server | Starting Omejdn version 1.7.0 omejdn-server | ========================================= omejdn | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration omejdn | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/ omejdn | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh omejdn | 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf omejdn | 10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf omejdn | /docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh omejdn | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh omejdn | 20-envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/default.conf.template to /etc/nginx/conf.d/default.conf omejdn | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh omejdn | /docker-entrypoint.sh: Configuration complete; ready for start up omejdn | 2024/04/22 13:03:31 [emerg] 1#1: unexpected "(" in /etc/nginx/conf.d/default.conf:14 omejdn | nginx: [emerg] unexpected "(" in /etc/nginx/conf.d/default.conf:14 omejdn-ui | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration omejdn-ui | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/ postgresa-container | postgresa-container | PostgreSQL Database directory appears to contain a database; Skipping initialization postgresa-container |

jfernandezsqs commented 3 months ago

Dear @parwinderau, Configuring Nginx in Azure involves modifying specific configuration files and creating symbolic links for proper operation. Please take a look at the Nginx configuration in Azure.

However, looking at issue #141 it looks like you have already fixed the Nginx/DAPS issue. Could you please check that the DAPS is launched by making a request to https://localhost:443? In addition, if you share the complete deployment logs it can help to detect if there is any error in the deployment of any of the IDS-testbed components.

Finally, please share in this issue the changes you have made to the docker-compose IDS-testbed file to launch it in Azure and get DAPS working in conjunction with nginx redirection, so that it can help the community behind these components.

jfernandezsqs commented 3 months ago

I close this issue because it was due to the value of some variables, which are modified in pull request 143.