Running WebSphere V5 as a non root User
Balasubramanian Mangalaganesh
I am running into some issues running WebSphere as a non-root User.
I followed the instructions on the infocenter about runing the DM, NA
and App Servers as non-root Users
I attempted to start of the node agent as a non-root User
and this is what i receive
ADMU0116I: Tool information is being logged in file
/opt/WebSphere/AppServer/logs/nodeagent/startServer.log
ADMU3100I: Reading configuration for server: nodeagent
ADMU0111E: Program exiting with error:
com.ibm.ws.process.exception.InvalidGroupException: PROC0002E:
Group: [wasgroup] does not appear to be valid on this system.
Process could not be created.
ADMU0211I: Error details may be seen in the file:
/opt/WebSphere/AppServer/logs/nodeagent/startServer.log
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
The message seems to suggest that wasgroup is not valid while it is
indeed valid
i see this group in the /etc/group file in my machine. (Solaris 5.8)
My DM also refuses to start as a non-root User with the same messa
The StartServer.log contains this message
[6/2/04 16:11:27:337 SGT] 34a1fc AdminTool A ADMU0111E: Program
exiting with
error: com.ibm.ws.process.exception.InvalidGroupException: PROC0002E:
Group: [wasgr
oup] does not appear to be valid on this system. Process could not be
created.
at
com.ibm.ws.process.UnixProcessImpl.create(UnixProcessImpl.java:113)
at com.ibm.ws.process.ProcessFactory.create(Unknown Source)
at
com.ibm.ws.management.launcher.ProcessLauncher.launch(ProcessLauncher.ja
va:66)
at
com.ibm.ws.management.launcher.LaunchCommand.launchProcess(LaunchCommand
.java:167)
at
com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.ja
va:213)
at
com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:173)
at
com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:
93)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
Apprecaite any suggestions.
Manglu
lall
Apparently, this exception occurs in WAS 4.0.x if all processes are not
run under the same non-root id...
http://www-1.ibm.com/support/docview.wss?uid=swg21050891
For info on running as non-root on WAS5, see:
http://www-1.ibm.com/support/docview.wss?uid=swg21166015
Thx
Balasubramanian Mangalaganesh wrote:
> *Hi,
> ...java:167)
> at
> com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.ja
> va:213)
> at
> com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:173)
> at
> com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:
> 93)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
>
>
>
>
> Apprecaite any suggestions.
> Manglu *
--
lall
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message248207.html
Venkatesh Babu Sira
Did you change under appserver/process definitation/process execution
change umask to 002 & enter the user & gruop name save & restart.
It's working for me.
-Venkat Sira
Balasubramanian Mangalaganesh <man...@NOSPAM-eutama.com> wrote in message news:<40BE44A7...@NOSPAM-eutama.com>...
Balasubramanian Mangalaganesh
I did manage to get it to work in my Development Environment but it
throws up the error in my Prod environment.
The only difference is Development does not have Security enaqbled whiel
the PROD has.
But the problem here stems something from the OS rather than WebSphere.
I did read through the docs before attempting to run it as a non-root user.
To compound this further one of my PROD machines work while the other
does not.
Anyway thanks for your assistance.
Manglu