I have a very similar issue running 9.1_02 (build b04-fcs) on CentOS 4.6. I have two servers with one domain, two clusters and 4 instances. I created a new user and assigned it to the asadmin group. I did pretty much the same thing as Jean then. Took down the node agents on both servers. Stopped and started the admin server and restarted the node agents on both servers. After that there was only one instance that would restart and the other three instances would would not start.
On the command line I would get the following
[glassfish_at_wb1co ~]$ start_instance.sh wb2co-ent_srv
Starting instance wb2co-ent_srv
Failed file login for appadmin.
CLI137 Command start-instance failed.
The logs would show:
[#|2009-02-05T08:19:40.454-0700|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application server startup complete.|#]
[#|2009-02-05T08:19:40.463-0700|INFO|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=20;_ThreadName=RMI TCP Connection(8)-10.187.225.118;appadmin;|SEC5046: Audit: Authentication refused for [appadmin].|#]
[#|2009-02-05T08:19:45.432-0700|INFO|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=20;_ThreadName=RMI TCP Connection(8)-10.187.225.118;appadmin;|SEC5046: Audit: Authentication refused for [appadmin].|#]
[#|2009-02-05T08:19:50.692-0700|INFO|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=21;_ThreadName=RMI TCP Connection(11)-10.187.225.118;appadmin;|SEC5046: Audit: Authentication refused for [appadmin].|#]
[#|2009-02-05T08:20:00.717-0700|INFO|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=16;_ThreadName=RMI TCP Connection(13)-10.187.225.118;appadmin;|SEC5046: Audit: Authentication refused for [appadmin].|#]
[#|2009-02-05T08:20:01.249-0700|INFO|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=22;_ThreadName=RMI TCP Connection(15)-10.187.225.118;appadmin;|SEC5046: Audit: Authentication refused for [appadmin].|#]
I eventually found that the admin-keyfile for the three instances would not update and I had to manually add the key I found in the one server that was working to the other three. Once I did that there was no issues.
Has anyone seen that before?
Cheers,
[Message sent by forum member 'no_life' (no_life)]
http://forums.java.net/jive/thread.jspa?messageID=330417