Installation either completes with errors or warnings, or hangs: WAS ND

Installation either completes with errors or warnings, or hangs

Errors while installing the product

If the WebSphere Application Server installation program indicates that errors were encountered while installing the product:

Browse all of the log files in install_dir/logs/ for clues. Pay particular attention to the main installation log file, log.txt.

Check the command prompt from which the installation panel was launched for error messages.

Look up any error or warning messages in the message reference table by selecting the "Reference" view in the information center navigation and expanding the "Messages" heading.

Ensure that you have installed the latest fixes and fix packs.
For instructions, see Installing interim fixes, cumulative fixes, and fix packs.

Review Troubleshooting the installation.

Note: When you select the "migration installation" option the installation may take a long time to complete - several hours, depending on the number of applications on the older version - and appear to hang, even though it is running correctly.

Error message MSGS0601I occurs during installation of WebSphere Application Server
The series of messages that follow can occur in the SystemOut.log file when you install WebSphere Application Server on all platforms except Windows platforms. These messages indicate that WebSphere Embedded Messaging has not been installed

[date time CDT] 60cf2faf JMSRegistrati A MSGS0601I: WebSphere Embedded Messaging has not been installed [date time CDT] 60cf2faf JMSEmbeddedPr A MSGS0050I: Starting the Queue Manager [date time CDT] 60cf2faf JMSEmbeddedPr E MSGS0058E: Unable to start the JMS Server as WebSphere Embedded Messaging has not been installed [date time CDT] 60cf2faf JMSService E MSGS0001E: Starting the JMS Server failed with exception: java.lang.Exception: MSGS0058E: Unable to start the JMS Server as WebSphere Embedded Messaging has not been installed

The following associated messages are added to the mq_install.log file:

wmsetup: date time Checking if user "root" is in group "mqm" wmsetup: date time wmsetup: date time ERROR: Group "mqm" exists, id "root" is defined to the group but does not wmsetup: date time have the group in its current set of effective groups. wmsetup: date time Current group membership is : wmsetup: date time uid=0(root) gid=0(system) groups=2(bin) wmsetup: date time You may need to login. wmsetup: date time wmsetup: date time ... RC 4 from Check_root wmsetup: date time ERROR: User "root" not in group "mqm" wmsetup: date time Check_root mqbrkrs wmsetup: date time Checking for group "mqbrkrs" ... wmsetup: date time lsgroup returned "mqbrkrs id=203 admin=false users=root adms=root registry=files " RC=0 wmsetup: date time Checking if user "root" is in group "mqbrkrs" wmsetup: date time wmsetup: date time ERROR: Group "mqbrkrs" exists, id "root" is defined to the group but does not wmsetup: date time have the group in its current set of effective groups. wmsetup: date time Current group membership is : wmsetup: date time uid=0(root) gid=0(system) groups=2(bin) wmsetup: date time You may need to login. wmsetup: date time wmsetup: date time ... RC 4 from Check_root wmsetup: date time ERROR: User "root" not in group "mqbrkrs"
To prevent this problem, use the local machine to run WebSphere Application Server commands (for example, install, addnode, and startnode). If logon remotely, use ssh instead of telnet.

To correct this problem, reinstall the embedded messaging feature. Issue the install command from the local machine, or use ssh instead of telnet

If you do not see a problem that resembles yours, or if the information provided does not solve your problem, see Obtaining help from IBM.

Troubleshooting by task: What are you trying to do?
Troubleshooting by component: What is not working?
Troubleshooting the installation

Troubleshooting installation problems