Summary
Error
When installing Application Lifecycle Management (ALM) 12 on Suse Linux Enterprise (SLES) 11 an error message is thrown at the final "Deployment" step which causes the installation to fail:
===
The installation failed
-----------------------
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file/..../ application/20qcbin.war/
WEB-INF/lib/slf4j-log4j12-1.7.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/..../application/20qcbin.war/
WEB-INF/lib/slf4j-log4j12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
Configuration failed
Failed to create/upgrade Site Admin Schema. By default, the output is saved in
<ALM repository path>\sa\DomsInfo
\MaintenanceData\out on your ALM server machine.:
java.net.UnknownHostException:
ALM's Installation log shows the following error:
java.net.UnknownHostException: <machine name>
at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:894)
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1286)
at java.net.InetAddress.getLocalHost(InetAddress.java:1462)
wrapped in java.net.UnknownHostException:
Cause
Fix
Modify /etc/hosts by adding a new line
" <your-machine-ip> <your-machine-name> localhost "
Rebooting the server might be required.
Note: It is important that ALM is uninstalled properly once the installation has failed. All available data from ALM Deployment and Installation folders should be removed prior starting the new installation.