AM 6.x install fails with emb.creatingfamsuffix.failure error when installing on a Unix or Linux system
The purpose of this article is to provide assistance if the AM install fails with an "emb.creatingfamsuffix.failure" error when installing on a Unix® or Linux® system with an embedded DS configuration store. You will also see a 'Connect Error' followed by "Error loading OpenAM suffix 1" when this happens.
The installation fails when attempting to create the AM suffix after the embedded configuration store is installed.
You can see this failure in the browser if you are configuring AM via the browser:Installing OpenAM configuration store in /am/conf/opends...Success. Creating OpenAM suffix You have provided options for scheduling this operation as a task but options provided for connecting to the server's tasks backend resulted in the following error: 'Connect Error' Error loading OpenAM suffix 1 emb.creatingfamsuffix.failure, refer to install.log under /am/conf for more information.
The install.log (located in the /path/to/am directory) also shows the same error, with additional details:Installing OpenAM configuration store in /am/conf/opends...Success. Creating OpenAM suffix You have provided options for scheduling this operation as a task but options provided for connecting to the server's tasks backend resulted in the following error: 'Connect Error' Error loading OpenAM suffix 1 AMSetupServlet.processRequest: error com.sun.identity.setup.ConfiguratorException: emb.creatingfamsuffix.failure at com.sun.identity.setup.EmbeddedOpenDS.setup(EmbeddedOpenDS.java:266) at com.sun.identity.setup.AMSetupServlet.setupEmbeddedDS(AMSetupServlet.java:964) at com.sun.identity.setup.AMSetupServlet.setupSMDatastore(AMSetupServlet.java:1020) at com.sun.identity.setup.AMSetupServlet.configure(AMSetupServlet.java:1092) at com.sun.identity.setup.AMSetupServlet.processRequest(AMSetupServlet.java:692) at com.sun.identity.config.DefaultSummary.createDefaultConfig(DefaultSummary.java:131) ...
Installed AM on Unix or Linux.
The hostname for AM is not resolvable. You can check this as follows:
- Find your hostname using the following command: $ hostname
- Check if the hostname returned in step 1 is resolvable using the following command: $ ping [hostname]If it is not resolvable, you will see the following response instead of the ping results: ping: cannot resolve am.example.com: Unknown host
If your hostname is resolvable, it could be because you have previously installed an external version of DS on the same server as the one you are now attempting to install AM. The external DS installation created a $HOME/.opendj/tools.properties file with its own configuration, which is overriding the connection details (hostname, port etc) for the embedded configuration data store.
The solution depends on the cause identified:
- If your AM hostname is not resolvable: this issue can be resolved by ensuring you use a Fully Qualified Domain Name (FQDN) for AM. This hostname must be resolvable, meaning either a DNS entry or an entry in the /etc/hosts file must exist. See Preparing a Fully Qualified Domain Name for further information.
- If a $HOME/.opendj/tools.properties file exists: this issue can be resolved by removing the $HOME/.opendj/tools.properties file prior to re-installing AM.
Related Issue Tracker IDs