Typo in run as user field: unable to start Deployment Manager

Today I was changing the run as user for my IBM Connections WebSphere Deployment manager back to the dedicated user after installing CR3 and I made a typo but did not catch it until I started my server up. Or at least tried to start it up.

Failed to look up group xxxxx

Past SetupChildContext and execvp block. An error occurred. Return valuue is: [2] and sysErr is: [0]

Creation failure, spawn was unsuccessfull. Therefore deallocating process structure at: ……

ADMU0111E: Program exiting with error:

com.ibm.ws.process.exception.InvalidGroupException: PROC0002E:

Group: [xxxxxx] does not appear to be valid on this system.

Process could not be created.

ADMU1211I: To obtain a full trace of the failure, use the -trace option.

ADMU0211I: Error details may be seen in the file:

/opt/IBM/WAS7/profiles/Dmgr01/logs/dmgr/startServer.log

Normally you would change this on the IBM Solutions console, guess what, this message says you cannot start it. same goes for the wsadmin command available to change this.

There is another place to go and that is your server.xml

In your profile path for your deployment manager go to /config/cells/cellname/nodes/nodename/servers/dmgr/server.xml

You will find a section in the bottom <processDefinition>, your runas user will be listed.

Leave a Comment

Your email address will not be published. Required fields are marked *