Replies: 2 comments 1 reply
-
@AstridTrj : Can you share your docker files - how have you started the services? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Verify if the file owner of your mapped out LDAP directories volumes:
- /data_warehouse/dcm4chee-arc/ldap:/var/lib/openldap/openldap-data
- /data_warehouse/dcm4chee-arc/slapd.d:/etc/openldap/slapd.d matches the user/group ID running slapd in the container, 1021/1021 by default, s.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
[+] Running 4/4$OpenLDAP: slapd 2.4.48 (May 7 2020 12:49:13) $
⠿ Network dcm4chee_default Created 0.1s
⠿ Container dcm4chee-db-1 Created 0.1s
⠿ Container dcm4chee-ldap-1 Created 0.1s
⠿ Container dcm4chee-arc-1 Created 0.1s
Attaching to dcm4chee-arc-1, dcm4chee-db-1, dcm4chee-ldap-1
dcm4chee-ldap-1 | 62ff007e @(#)
dcm4chee-ldap-1 | openldap
dcm4chee-ldap-1 | 62ff007e ldif_read_file: Permission denied for "/etc/openldap/slapd.d/cn=config.ldif"
dcm4chee-ldap-1 | 62ff007e slapd stopped.
dcm4chee-ldap-1 | 62ff007e connections_destroy: nothing to destroy.
dcm4chee-db-1 |
dcm4chee-db-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
dcm4chee-db-1 |
dcm4chee-db-1 | 2022-08-19 11:16:14.946 CST [1] LOG: starting PostgreSQL 12.2 (Debian 12.2-2.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
dcm4chee-db-1 | 2022-08-19 11:16:14.946 CST [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
dcm4chee-db-1 | 2022-08-19 11:16:14.946 CST [1] LOG: listening on IPv6 address "::", port 5432
dcm4chee-db-1 | 2022-08-19 11:16:14.947 CST [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
dcm4chee-db-1 | 2022-08-19 11:16:14.966 CST [28] LOG: database system was interrupted; last known up at 2022-08-18 16:20:41 CST
dcm4chee-ldap-1 exited with code 1
dcm4chee-db-1 | 2022-08-19 11:16:15.165 CST [28] LOG: database system was not properly shut down; automatic recovery in progress
dcm4chee-db-1 | 2022-08-19 11:16:15.167 CST [28] LOG: redo starts at 0/188FE98
dcm4chee-db-1 | 2022-08-19 11:16:15.167 CST [28] LOG: invalid record length at 0/188FF80: wanted 24, got 0
dcm4chee-db-1 | 2022-08-19 11:16:15.167 CST [28] LOG: redo done at 0/188FF48
dcm4chee-db-1 | 2022-08-19 11:16:15.178 CST [1] LOG: database system is ready to accept connections
dcm4chee-arc-1 | Waiting for ldap:389 ...
dcm4chee-arc-1 | nc: getaddrinfo for host "ldap" port 389: Name or service not known
dcm4chee-arc-1 | nc: getaddrinfo for host "ldap" port 389: Name or service not known
dcm4chee-arc-1 | nc: getaddrinfo for host "ldap" port 389: Name or service not known
dcm4chee-arc-1 | nc: getaddrinfo for host "ldap" port 389: Name or service not known
dcm4chee-arc-1 | nc: getaddrinfo for host "ldap" port 389: Name or service not known
dcm4chee-arc-1 | nc: getaddrinfo for host "ldap" port 389: Name or service not known
dcm4chee-arc-1 | nc: getaddrinfo for host "ldap" port 389: Name or service not known
Beta Was this translation helpful? Give feedback.
All reactions