Continuation of ticket #10871 I updated the /etc/hosts file but the opendj server is still looking for localhost domain name. I know it finds the FQDN dynamically but where is it looking? (Is there another location other than /etc/hosts?) Here is my /etc/hosts file: 127.0.0.1 localhost 127.0.1.1 gts0001.kubecost-gluu-test.com gts0001 3.230.225.77 kubecost-gluu-test.com I confirmed with AWS Support this is the correct config on their end and to contact developer support. What am I missing? ************************************************************************************* ``` root@gts0001:~# service opendj status ● opendj.service - OpenDJ Directory Service Loaded: loaded (/etc/systemd/system/opendj.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2022-10-17 13:26:55 UTC; 33min ago Process: 62 ExecStart=/opt/opendj/bin/start-ds (code=exited, status=0/SUCCESS) Main PID: 361 (code=exited, status=143) Oct 17 13:23:30 gts0001.kubecost-gluu-test.com start-ds[362]: [17/Oct/2022:13:23:30 +0000] category=BACKEND severity=NOTICE msgID=513 msg=The database backend userRoot containing 0 entries has started Oct 17 13:23:30 gts0001.kubecost-gluu-test.com start-ds[362]: [17/Oct/2022:13:23:30 +0000] category=EXTENSIONS severity=NOTICE msgID=221 msg=DIGEST-MD5 SASL mechanism using a server fully qualified domain name of: localhost Oct 17 13:23:30 gts0001.kubecost-gluu-test.com start-ds[362]: [17/Oct/2022:13:23:30 +0000] category=CORE severity=NOTICE msgID=135 msg=The Directory Server has started successfully Oct 17 13:23:30 gts0001.kubecost-gluu-test.com start-ds[362]: [17/Oct/2022:13:23:30 +0000] category=CORE severity=NOTICE msgID=139 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryS> Oct 17 13:23:30 gts0001.kubecost-gluu-test.com start-ds[362]: [17/Oct/2022:13:23:30 +0000] category=PROTOCOL severity=NOTICE msgID=276 msg=Started listening for new connections on LDAPS Connection Handler 0.0.0.0 port 1636 Oct 17 13:23:30 gts0001.kubecost-gluu-test.com start-ds[362]: [17/Oct/2022:13:23:30 +0000] category=PROTOCOL severity=NOTICE msgID=276 msg=Started listening for new connections on LDAP Connection Handler 0.0.0.0 port 1389 Oct 17 13:23:30 gts0001.kubecost-gluu-test.com start-ds[362]: [17/Oct/2022:13:23:30 +0000] category=PROTOCOL severity=NOTICE msgID=276 msg=Started listening for new connections on Administration Connector 0.0.0.0 port 4444 Oct 17 13:23:31 gts0001.kubecost-gluu-test.com systemd[1]: Started OpenDJ Directory Service. Oct 17 13:26:55 gts0001.kubecost-gluu-test.com systemd[1]: opendj.service: Main process exited, code=exited, status=143/n/a Oct 17 13:26:55 gts0001.kubecost-gluu-test.com systemd[1]: opendj.service: Failed with result 'exit-code'. ```