container docker-ldap-1 is unhealthy

[omarlabidi]

Hi ! I'm trying out GeOrchestra for the first time. I've set up the Docker composition, but I'm encountering an issue. I'm getting this error message: "dependency failed to start: container docker-ldap-1 is unhealthy". Any ideas on how to fix this?

Thanks!

checking the log (docker logs docker-ldap-1) I get this:

[INFO] No CUSTOM_SCRIPTS_DIRECTORY env variable set
run-parts: executing /docker-entrypoint.d/00-init
Info: Container already configured, therefore ignoring SLAPD_xxx environment variables and preseed files
run-parts: executing /docker-entrypoint.d/01-populate
LDAP already initialized !
run-parts: executing /docker-entrypoint.d/02-indexes
LDAP indexed
66110b86 @(#)

Debian OpenLDAP Maintainers [pkg-openldap-devel@lists.alioth.debian.org](mailto:pkg-openldap-devel@lists.alioth.debian.org)
66110b86 User Schema load failed for attribute "pwdAttribute". Error code 17: attribute type undefined
66110b86 config error processing olcOverlay={0}ppolicy,olcDatabase={1}mdb,cn=config: User Schema load failed for attribute "pwdAttribute". Error code 17: attribute type undefined
66110b86 slapd stopped.
66110b86 connections_destroy: nothing to destroy.

[pmauduit]

The docker ldap healthcheck is defined here: https://github.com/georchestra/georchestra/blob/master/ldap/Dockerfile#L35-L36

The only reason I see for it to fail is that somehow something gets corrupted in your setup, maybe you had an issue at bootstrap of the LDAP volumes (https://github.com/georchestra/docker/blob/master/docker-compose.yml#L77-L79) ; especially with the error message above:

66110b86 User Schema load failed for attribute "pwdAttribute". Error code 17: attribute type undefined

If you don't have anything sensitive in your LDAP tree yet, maybe it could be worth trying to remove the volumes and starting from scratch.

[omarlabidi]

Thank you pmauduit for your assistance. I uninstalled and reinstalled Docker. With the new setup, this time I encountered an issue with the container docker-console-1.

dependency failed to start: container docker-console-1 is unhealthy

below the log

2024-04-07 16:29:29.144:INFO:oejs.Server:main: Started @87285ms
2024-04-07 16:29:37 Dsn [WARN] *** Couldn't find a suitable DSN, Sentry operations will do nothing! See documentation: https://docs.sentry.io/clients/java/ ***
2024-04-07 16:29:38 DefaultSentryClientFactory [WARN] No 'stacktrace.app.packages' was configured, this option is highly recommended as it affects stacktrace grouping and display on Sentry. See documentation: https://docs.sentry.io/clients/java/config/#in-application-stack-frames

[pmauduit]

There should be something else before "Server:main: Started" which could explain why the console does not start, the "WARN" log line provided is something which can be ignored (about sentry logging configuration which is bundled into the webapp but unused / unconfigured by default).

[omarlabidi]

here is the entire log,

dependency failed to start: container docker-console-1 is unhealthy
PS C:\Docker\_GeoOrchestra\docker> docker logs docker-console-1
[INFO] No CUSTOM_SCRIPTS_DIRECTORY env variable set
2024-04-07 16:28:08.703:INFO::main: Logging initialized @6843ms to org.eclipse.jetty.util.log.StdErrLog
2024-04-07 16:28:14.430:INFO:oejs.Server:main: jetty-9.4.54.v20240208; built: 2024-02-08T19:42:39.027Z; git: cef3fbd6d736a21e7d541a5db490381d95a2047d; jvm 11.0.22+7
2024-04-07 16:28:14.677:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:///var/lib/jetty/webapps/] at interval 1
2024-04-07 16:28:16.942:INFO:oejj.ConnectorServer:main: JMX URL: service:jmx:rmi://0.0.0.0:1099/jndi/rmi://0.0.0.0:1099/jmxrmi
2024-04-07 16:28:34.994:INFO:oeja.AnnotationConfiguration:main: Scanning elapsed time=12124ms
2024-04-07 16:28:35.029:WARN:oejsh.AllowSymLinkAliasChecker:main: AllowSymLinkAliasChecker is deprecated
2024-04-07 16:28:39.357:INFO:oejshC.console:main: No Spring WebApplicationInitializer types detected on classpath
2024-04-07 16:28:41.594:INFO:oejs.session:main: DefaultSessionIdManager workerName=node0
2024-04-07 16:28:41.618:INFO:oejs.session:main: No SessionScavenger set, using defaults
2024-04-07 16:28:41.623:INFO:oejs.session:main: node0 Scavenging every 660000ms
2024-04-07 16:28:41.955:INFO:oejshC.console:main: Initializing Spring root WebApplicationContext
2024-04-07 16:28:54.245:INFO:oejshC.console:main: org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok)
2024-04-07 16:28:54.621:INFO:oejshC.console:main: Initializing Spring FrameworkServlet 'console'
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.springframework.cglib.core.ReflectUtils$1 (file:/var/lib/jetty/webapps/console/WEB-INF/lib/spring-core-4.3.22.RELEASE.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of org.springframework.cglib.core.ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
--------------------------------> DB OK <------------------------------------
2024-04-07 16:29:28.848:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@1b1cfb87{console,/console,[file:///var/lib/jetty/webapps/console/, jar:file:///var/lib/jetty/webapps/console/WEB-INF/lib/springfox-swagger-ui-2.9.2.jar!/META-INF/resources],AVAILABLE}{/var/lib/jetty/webapps/console}
2024-04-07 16:29:29.141:INFO:oejs.AbstractConnector:main: Started ServerConnector@273e7444{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
2024-04-07 16:29:29.144:INFO:oejs.Server:main: Started @87285ms
2024-04-07 16:29:37 Dsn [WARN] *** Couldn't find a suitable DSN, Sentry operations will do nothing! See documentation: https://docs.sentry.io/clients/java/ ***
2024-04-07 16:29:38 DefaultSentryClientFactory [WARN] No 'stacktrace.app.packages' was configured, this option is highly recommended as it affects stacktrace grouping and display on Sentry. See documentation: https://docs.sentry.io/clients/java/config/#in-application-stack-frames

[pmauduit]

There are nothing in the provided logs which can explain an issue at bootstrap, apart from the fact your docker composition is launched under Windows, and I have no idea if someone already tried it in such context (maybe @pierrejego ?).

The healthcheck for the console is defined here: https://github.com/georchestra/docker/blob/master/docker-compose.yml#L180

Can you try to load the "create account page" by hand ("https://.../console/account/new") ? It is still possible that the create account feature has been broken recently, but I'd have expected it would have been detected.

[fvanderbiest]

Hi @omarlabidi Are you running the master branch or the 23.0 one ?

[omarlabidi]

@pmauduit with the "https://.../console/account/new" i have the message under maintainance

[omarlabidi]

@fvanderbiest i'm running the branch 23.0. i also have tried the 22.0 and it seemed to be wonrking.

[jeanmi151]

hey,

did you wait enough time ? First run of the docker composition can take some time to start. Also to try geOrchestra you don't need to create a new account, you can use the default one specified in the README section 4

[omarlabidi]

@jeanmi151 yes i did.

[fvanderbiest]

@edevosc2c any idea here ? thx

[omarlabidi]

Hy Emilien and thank you.

Yes my folder is “C:\Docker\GeOrchestra\docker”’

Regards.

Omar

[edevosc2c]

Ha you are using Windows?

We have not validated that this docker composition works on Windows. You should use WSL for Linux support, maybe it will work better: https://learn.microsoft.com/en-us/windows/wsl/install

[omarlabidi]

Yes. Windows 10.

[edevosc2c]

Please try in a Linux environment. In a VM or with WSL (https://learn.microsoft.com/en-us/windows/wsl/install).