Re: <BEA-002616> <Failed to
listen on channel

This has nothing to do with clustering. I also have a simple Administrative
Server that start & stops Applicatition Servers via the scripted
NodeManager:

ssh %H /apps02/BEA/weblogic91/common/bin/wlscontrol.sh -d %D -r %R -s %S %C

For this scripted nodeManager to work without intervention an ssh public key
exchange needs to be setup.

My problem was 

1. I installed & setup WLS aas root
2. I ran WLS as root
3. In my enviroment this is not permited so I stopped WLS & I did a chown -R
nobody:nobody
4. Then I got the errors spoke of here after restarting (related to the ssh line
above & incorrect authorization setup in general). Of course that the 
errors would probably be permissions & authorizations was clear because I
just ran the chown.
5. For me, the easy thing was to remove WLS & then reinstall everything as
nobody:nobody
6. I run WLS as nobody
7. Problem is gone.

I think you should double check authorizations & permissions for your
WebLogic setup.

In my short experience with Weblogic and my experience with WebSphere, UNIX, and
even Windows, a surprisingly high number of 'unexplainable' errors have their
roots in access control issues. There is a whole computer security