Connection Refused when starting node manager on Linux

Hi,
I'm using Weblogic 6.1 SP 2 on Redhat Linux 7.1 with Sun JDK 1.3.1. When I'm running
the Node Manager on one machine and try to connect to it from another machine (Admin
Server) I'm getting the following message:
<May 28, 2002 6:35:59 PM IDT> <Error> <NodeManager> <Could not start server 'EnvelopeManagedBackup'
via Node Manager - reason: '[SecureCommandInvoker: Could not create a socket to the
NodeManager running on host 'jarjar:5555' to execute command 'online null', reason:
Connection refused: connect. Ensure that the NodeManager on host 'jarjar' is configured
to listen on port '5555' and that it is actively listening]'>
The Node Manager is listening on the server's listen address (jarjar) and on the
correct port (5555). When running netstat -a | grep 5555 on the server I get the
following (jarjar is the computer name):
tcp 0 0 jarjar:5555 *:* LISTEN
The admin server is registered in the nodemanager.hosts file.
Can anyone help me on this?

....I happened to get "execute command 'online null'" because of a missing
"Listen Address" and/or "Listen Port" entry in the "Remote Start" tab of the
Administration Server.
Node Manager passes on such values when starting up a managed server - if
either is blank, the managed server can not identify the Admin Server to
register to...
Paola R.

Similar Messages

Need help: error when starting node manager

When attempting to start node manager i recieve the following error:
<Sep 30, 2004 1:30:47 PM EDT> <Error> <NodeManager> <Node manager could not find the required library, libNodeManager.so, in path - /usr/j2se/jre/lib/i386/client:/usr/j2se/jre/lib/i386:/usr/j2se/jre/../lib/i386:/export/home/bea/weblogic81/server/lib/solaris:/export/home/bea/weblogic81/server/lib/solaris/oci920_8:/usr/lib>
i have copied the file, libnodemanager.so to every directory in the path above, spelling and case are correct, permissions set to rwxrwxrwx but still get error.
wl 8.1 sp2 solaris 9.1.
please help if you can.
thanks.
vb

Hi Chaitanya,
Does the nodemanager.domains file exists in
/home/xyz/Oracle/Middleware/Oracle_Home/oracle_common/common/nodemanager?
Does it contain a reference to your domain?
For example:
tetra=/u01/app/oracle/domains/tetra
Regards Peter
http://theheat.dk

OBIEE 11g (11.1.1.5.0) - Issue with starting Node Manager

Hi,
Have anyone faced an issue with starting Node Manager in OBIEE 11g (11.1.1.5.0)? OS is 64 bit Linux, WebLogic is 10.3.5. I used the software-install method and followed by running config.sh. Everything completed successfully. I updated the catalog and rpd location in the FMW control screen.
To get it activated I bounced services and when I try to start Node Manager it gives below error --
<Aug 30, 2011 2:02:42 PM CDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Aug 30, 2011 2:02:42 PM> <SEVERE> <Fatal error in node manager server>
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
Aug 30, 2011 2:02:42 PM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
+ set +x
I see the same issue reported in ML OBIEE 11g - Node manager fails to start upon upgrade [ID 1329442.1] and WebLogic Server: Node Manager Startup is Failing with java.io.IOException: Unsupported cypher suite [ID 1329260.1] I tried to modify commEnv.sh. But it didnt help me.
Please let me know if anyone have faced similar issue and what exactly did you do to resolve it.
Cherrish Vaidiyan
Edited by: Cherrish on Aug 30, 2011 3:14 PM

Hi,
There are Two types of Cipher suites --- Certicom Cipher Suite and SunJSSE Equivalent Cipher Suite. And with Weblogic 10.3.5, you are using Sun JSSE Cipher Suite, and by default Node Manager uses the Certicom Cipher Suite.
In the nodemanager.properties, Add CipherSuite=SSL_RSA_EXPORT_WITH_RC4_40_MD5, save and restart Node Manager.
Reference Metalink Note: WebLogic Server 10.3.x: Getting "Unsupported Cipher" Exceptions When Starting Node Manager [ID 1307325.1]
Cherrish Vaidiyan

Start node manager using WLST

I am trying to start node manager using WLST with following command
wls:/offline> nmConnect('weblogic','weblogic123','localhost','5556','FirstDomain','C:\Oracle\Middleware\user_projects\domains\FirstDomain','plain')but getting below exception
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 618, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : Connection refused: connect. Could not connect to NodeManager. Check
that it is running at localhost:5,556.
Use dumpStack() to view the full stacktrace
wls:/offline>
I am using weblogic 11g.
Can anybody let me know how to fix this issue.

You can use something like this:
beahome = '/home/oracle/soasuite';
pathseparator = '/';
adminusername = 'weblogic';
adminpassword = 'magic11g';
domainname = 'base_domain';
domainlocation = beahome + pathseparator + 'user_projects' + pathseparator + 'domains' + pathseparator + domainname;
nodemanagerhomelocation = beahome + pathseparator + 'wlserver_10.3' + pathseparator + 'common' + pathseparator + 'nodemanager';
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');More information can be found here: http://middlewaremagic.com/weblogic/?p=6040
in particular the "Starting the SOA environment" section

Unable to start Node Manager

Hello everyone,
I've installed WLS 10.3.3 on windows. *2 Managed servers (jitu-pc, jitu-pc1) & 1 admin server on same machine*.
Below are the SSL configurations for both:
Host Name Verification = None
Machine>Node Manager: Type=PLAIN
When I try to start the node manager ($BEA_HOME\server\bin\startNodeManager.cmd" I get below error:
<Oct 15, 2010 4:11:33 AM> <INFO> <Secure socket listener started on port 5556>
Oct 15, 2010 4:11:33 AM weblogic.nodemanager.server.SSLListener run
*INFO: Secure socket listener started on port 5556*
<Oct 15, 2010 4:12:04 AM GMT+05:30> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer 01HW165700.entcorp.ttsl.com - 172.17.43.84 during SSL handshake.>
<Oct 15, 2010 4:12:04 AM GMT+05:30> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer 01HW165700.entcorp.ttsl.com - 172.17.43.84 during SSL handshake.>
<Oct 15, 2010 4:12:04 AM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer 01HW165700 - 172.17.43.84 during SSL handshake.>
javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer 01HW165700 - 172.17.43.84 during SSL handshake.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
at com.certicom.tls.record.ReadHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Can anybody tell me what am I missing ?

Thanks Jay,
That worked.
Also, I've one more doubt.
I browsed to the $WEBLOGIC_HOME/common/nodemanager directory.
From there I executed $WEBLOGIC_HOME/server/bin startNodeManager.cmd.
But before starting there is no "nodemanager.properties" file.
After I started node manager, it started with default properties, and wrote the same to "nodemanager.properties" file in the same directory I started the node manager from.
Then I aborted the node manager, edited the property file for SecureListener and then restarted. Then everything went up and fine.
My question is that is there any default "nodemanager.properties" ?

Starting Node Manager

We have a configuration where weblogic installed as
          /weblogic/bea/wlserevr6.1
          The applications are installed as
          /usr1/config/<app>
          To start the node manager I copied the certificates into /usr1/config
          directory and specified the path on the command line for nodce manager.
          When I try to start node manager from the /usr/config directory I get an
          access control exception.
          However I am able to start node manager from the directory where weblogic is
          installed.
          Any ideas?


I cut and paste the description of the note. There is a statement with the cause that states
"This issue happens only when the display name of a NIC configured for migration in nodemanager is null"
and it is a little ambigious. It implies there is a workaround of setting the display name, but doesn't discuss how to apply this workaround; the display name it refers to generated by a code call to the NetworkInterface.getDisplayName() method from the JDK.
I assume that the display name here is the parameter called Interface within the nodemanger.properties, but there is nothing within the note that confirms this, nor if setting this to the NICE name will fix this issue. here is a full list of the nodemanger.propertes file -> http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
I'd download and try the patch in your place; it's a WLS patch (as nodemanager is part of WLS) so shouldn't affect SOA Suite. Failing that, open a SR.

Passing arguments to Managed Server ServerStart when using Node Manager

Below is the procedure to pass arguments to Managed Server serverstart tab when using Node Manager to start and stop the Managed Server instance
For passing the JVM arguments we will have to use "-server" which is hotspot and then pass the arguments
for eg: "-server -Xms2048m -Xmx2048m -verbosegc"
For adding jar's to the classpath you will have to add weblogic.jar and weblogic_sp.jar from WL_HOME/server/lib directory as well along with the custom jar (In some cases we can ignore weblogic_sp.jar, just adding weblogic.jar will do).
for eg: "\home\user\debug.jar;\home\user\bea\wlserver_10.3\server\lib\weblogic.jar;\home\user\bea\wlserver_10.3\server\lib\weblogic_sp.jar;"
- - Tarun

Hi,
To me, if you don't wanna use the NodeManager, you won't be able to start your managed servers with WLST.
I guess the only ways are :
* through the console / WLST using the NodeManager
* using the startManagedWebLogic.[cmd/sh]
Regards

10g on enterprise linux AS 3 - connection refused when attempting to ...

I recently installed 10g on RedHat Linux Enterprise AS 3. The installation appeared to go seamlessly and immediately afterwards I was able to access SQL PLUs via
http://localhost.localdomain:5560/isqlplus and login as system and perform queries. Shortly thereafter, this stopped working. When attempting to relaunch the browser and direct to this address, I receive the error: The connection was refused when attempting to contact localhost.localdomain:5560. The same error is received for other urls , e.g. ..ulrasearch, em etc.
I checked some of the prior postings that discuss checking configuration files for Apache, etc. I don't seem to have an Apache directory created anywhere although it is referenced in some of the log files.
Rebooting the machine makes no difference.
I am new to 10g and running Oracle on linux so any help is appreciated.

Alison is right,
For the another processes you need to type :
ULTRASEARCH
$$ORACLE_HOME/bin/searchctl start [stop]
ENTERPRISE MANAGER DATABSE CONTROL
$$ORACLE_HOME/bin/emctl start dbconsole [stop]
ORACLE MANAGEMENT AGENT
$$ORACLE_HOME/bin/emctl start agent [stop]

Native IO Disabled when using node manager to start managed server

Hi,
I am able to start my node manager and the managed server from the Admin Console. OS is AIX, WebLogic 9.2 MP3. The managed server starts OK, but Native IO is disabled even though it is enabled in the Admin Console for that manager server:
####<Jul 28, 2009 8:25:00 AM CDT> <Info> <Socket> <pstps09.statefarm.com> <PIA2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1248787500274> <BEA-000447> <Native IO Disabled. Using Java IO.>
I set NativeVersionEnabled to False in nodemanager.properties as specified in the BEA documentation, but can get Native IO to work. The log file clearly indicates that the JDK version is 32-bit:
java.fullversion = J2RE 1.5.0 IBM J9 2.3 AIX ppc-32 j9vmap3223-20071007 (JIT enabled)
Any ideas how to fix this or is this working as designed for AIX platforms?
Thanks!
-Mary Manchukian

The following document asks to set NativeVersionEnabled to False:
http://edocs.bea.com/wls/docs61/adminguide/remotestart.html#1043956:
The Node Manager is available for use only on Windows and UNIX platforms. Native libraries are available for running the Node Manager on Windows, Solaris, HP-UX, AIX and Red Hat Linux operating systems. For UNIX operating systems other than Solaris and HP UX, you will need to use the following argument on the java command line when starting the Node Manager:
-Dweblogic.nodemanager.nativeVersionEnabled=false
If we do not set NativeVersionEnabled to False, the managed server doesn't start at all and fails with the error:
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:296)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:511)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:115)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:810)
All I want is to be able to start the managed server from the Admin Console > Remote Start tab.
Thanks,
-Mary

Path problem when use node manager to start Managed Server

Hi, I have met a problem:
My managed server's root directory is /usr/local/bea/cluster1/usr_projects/mydomain
My Node Manager 's default directory is /usr/local/bea/cluster1/weblogic700/common/nodemanager
I have some config file located under managed server's root directory and log
file is also should be generated in managed server's root directory.
But when I try to use node manager to startup/shutdown the Managed Server, I found
weblogic can not find the config file if I don't move the config file from Managed
server's root directory to node manager server's default directory. and also log
file was created under node manager's default directory.
It seems that managed server's default directory has been changed to node manager's
default directory.
What shall I do if I want Managed Server's default directory to be kept?

Hi Lumin,
If the weblogic version is 8.1, there is a RootDirectory field in Remote
Start tab which should resolve your problem. Just enter the absolute
directory pathname on the machine where you are starting your managed server
and the current working directory of the managed server will be this
RootDirectory. Before 8.1, the RootDirectory was used for finding the config
file for weblogic but it was never used to change the working directory of
the managed server created by the node manager.
cheers,
gaurav.
"lumin" <[email protected]> wrote in message
news:3eb7a4ae$[email protected]..
>
Hi, I have met a problem:
My managed server's root directory is/usr/local/bea/cluster1/usr_projects/mydomain
My Node Manager 's default directory is/usr/local/bea/cluster1/weblogic700/common/nodemanager
>
I have some config file located under managed server's root directory andlog
file is also should be generated in managed server's root directory.
But when I try to use node manager to startup/shutdown the Managed Server,I found
weblogic can not find the config file if I don't move the config file fromManaged
server's root directory to node manager server's default directory. andalso log
file was created under node manager's default directory.
It seems that managed server's default directory has been changed to nodemanager's
default directory.
What shall I do if I want Managed Server's default directory to be kept?

How to configure Node manager on Linux on ssl port

Hi,
I have installed SOA BPM 11.1.1.3 on linux with ssl enabled. I am trying to configure Node Manager but it's not working.
Here are the steps I did to configure.
1. Created a machine
2. Added managed servers to the machine i.e. soa,bam
3. Enroll domain using nmEnroll using
cd $BEA_HOME/user_projects/domains/<domain_name>/bin/
. setDomainEnv.sh
java weblogic.WLST
wls> connect(’weblogic’,'weblogic1’, ‘t3://mymachine.mydomain:7001’)
wls> nmEnroll(’$BEA_HOME/user_projects/domains/<domain_name>’, ‘$BEA_HOME/wlserver_<version>/common/nodemanager’)
here 7001 is the admin server non-ssl port but when I try 7002 ssl port it doesn't connect. But I need to enroll it on ssl port as I have ssl enabled.
4. reset the node manager user/password same as weblogic console
5. started the node manager using $WL_HOME\server\bin\startNodeManager.sh
But when I log back into console and try to start my manage server it gives the following error
SEVERE: java.io.FileNotFoundException: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/./config/jps-config.xml (No such file or directory)
<Aug 6, 2010 5:30:16 PM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.I did not add my Admin server to be part of the machine.
Any help if I am missing anything or doing anything wrong.
Thanks

Hi,
Do I need to add Admin Server also part of the Machine where I added bam,soa servers. I tried again following the steps but gets the below error again. Appreciate if someone can list the steps as the docs are a bit vague:
<Aug 6, 2010 6:14:01 PM> <INFO> <wcbpm_domain> <bam_server1> <Starting WebLogic server with command line: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/bin/startWebLogic.sh >
Aug 6, 2010 6:14:01 PM weblogic.nodemanager.server.ServerManager log
INFO: Starting WebLogic server with command line: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/bin/startWebLogic.sh
<Aug 6, 2010 6:14:01 PM> <INFO> <wcbpm_domain> <bam_server1> <Working directory is '/usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain'>
Aug 6, 2010 6:14:01 PM weblogic.nodemanager.server.ServerManager log
'/usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/servers/bam_server1/logs/bam_server1.out'
<Aug 6, 2010 6:14:02 PM> <INFO> <wcbpm_domain> <bam_server1> <Server failed during startup so will not be restarted>
Aug 6, 2010 6:14:02 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Aug 6, 2010 6:14:02 PM> <WARNING> <Exception while starting server 'bam_server1'>
java.io.IOException: Server failed to start up. See server output log for more details.
        at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
        at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
        at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
        at weblogic.nodemanager.server.Handler.run(Handler.java:70)
        at java.lang.Thread.run(Thread.java:619)
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
Unknown option or illegal argument: -XX:+UseParallelGC.
Please check for incorrect spelling or review documentation of startup options.
Could not create the Java virtual machine.
<Aug 6, 2010 6:14:02 PM> <FINEST> <NodeManager> <Waiting for the process to die: 590>
<Aug 6, 2010 6:14:02 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Aug 6, 2010 6:14:02 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>Don't know if I hve missed any steps in node manager configuration.
Thanks

Error Message when starting Object Manager on the Client

I�ve installed sgd 4 successfully and I can start applications - except
Array- and Objectmanager from my client.
Here I get the message
ErrTransportNotAvailable
ErrTransportNotAvailable
Standard error of script process:
Third tier output log:
Any ideas on this??
I have telnet installed and enabled, but can�t log in as root yet.

Hi Matthias
I can't immediately explain this but the error message says that a
connection to port 33521 on host 172.17.32.37 was refused. This usually
means that the 33521 service (whatever this is) is not currently
running.
I don't recognise this as a port number that should be connected to
during a launch, perhaps it would help if you posted the messages in
the server error logs that occur at the time the launch is made.
In case this is some kind of proxy service it might be worth checking
to see if anything is running on this port. i.e. use
netstat -an | grep 33521
there may be something listening on the loopback interface?
In general you should use 'ssh'. To get this working for the X11
protocol, which is the protocol required by the object manager. You
need to enable X11 forwarding in your /etc/ssh/ssh_config ( set
ForwardX11 yes), and in your /etc/ssh/sshd_config ( set X11Forwarding
yes ) on all machines connecting via ssh.
Note. I'm assuming you are using Linux with moderate security settings
because you are getting this problem -- if you are using something
different the actual files you need to change may vary.
Regards
Barrie
On 2005-02-17, Matthias Michl <[email protected]> wrote:
Hello,
how to set up SGD to launch xterm?
I can run the objectmanager within an x-session on the SGD Server itself.
But not within SGD.
I can connect to the server by ssh and telnet from my Windows client
perfectly.
I have switched the objectmanager to connect over telnet and I get the
message
ErrTransport not Available
connect (7, 172.17.32.37:33521):(111) Connection refused
Standard error of script process:
Third tier output log:
Kind Regards
Matthias
Mel O wrote:
It usually means that the object's connection method is not configured
correctly. So if you have telnet enabled but the object is configured
for SSH, you'll get this message.
Try launching a xterm. konsole on the SGD 4 server. You can do this via
SGD. Then as root
$ tarantella objectmanager
Now check that the Object and Array Manager objects have telnet selected
as the connection method.
Regards,
Matthias Michl wrote:
I�ve installed sgd 4 successfully and I can start applications - except
Array- and Objectmanager from my client.
Here I get the message
ErrTransportNotAvailable
ErrTransportNotAvailable
Standard error of script process:
Third tier output log:
Any ideas on this??
I have telnet installed and enabled, but can�t log in as root yet.

SUNW.iws - "Connection refused" when probing a uri in monitor_uri_list

Hi,
I use Sun Cluster 3.2 and would like to set Sun Webserver 7u2 as failover resource.
I configured Resource Group which contain Logical Hostname and Sun Webserver as data resource (using SUNW.iws). I set all nedded data and turn on the resource.
I've got the messages:
Feb 11 01:25:21 krasnal-A SC[SUNW.iws:5,Webserver-gr,Webserver-server,iws_svc_start]: Failed to connect to host ha-web and port 80: Connection refused.
Feb 11 01:25:36 krasnal-A last message repeated 7 times
Feb 11 01:25:37 krasnal-A SC[SUNW.iws:5,Webserver-gr,Webserver-server,iws_svc_start]: A resource restart attempt on resource Webserver-server in resource group Webserver-gr has been blocked because the number of restarts within the past Retry_interval (620 seconds) would exceed Retry_count (2)
Feb 11 01:25:37 krasnal-A SC[SUNW.iws:5,Webserver-gr,Webserver-server,iws_svc_start]: Failed to start iPlanet Web Server.
Feb 11 01:25:37 krasnal-A Cluster.RGM.rgmd: Method <iws_svc_start> failed on resource <Webserver-server> in resource group <Webserver-gr> [exit code <1>, time used: 7% of timeout <300 seconds>]
server has been shutdown
In this moment the second node on cluster start the resource and do the same. Monitor, failed, turn off. :-( . Resource are switched 3 times between nodes and at the end get offline status.
The most important is that connection refused for uri in monitor_uri_list and resource in cluster isn't start or triggering restart/failover.
It is look like the failover monitor try check resource on port 80 after service start and when notice that service (Webserver) not started - turn down the interface on this node and turn up on second node. Service (webserver) can;t start becouse the interface are down.
I've found some similar problems which are describes on sunsolve:
http://sunsolve.sun.com/search/document.do?assetkey=1-1-4900125-1
and
http://sunsolve.sun.com/search/document.do?assetkey=1-1-4967197-1
I'm beginner in cluster problems and maybe I did some big mistake, but ...some help me
Irek

Solved!
I read this post: http://forum.java.sun.com/thread.jspa?messageID=3966316
and now get things work.
If you installed NetBeans, you should notice that in your {tomcat_home}/conf/web.xml, NetBeans add these:
<filter>
    <filter-name>HTTPMonitorFilter</filter-name>
    <filter-class>org.netbeans.modules.web.monitor.server.MonitorFilter</filter-class>
    <init-param>
      <param-name>netbeans.monitor.ide</param-name>
      <param-value>127.0.0.1:8082</param-value>
    </init-param>
</filter>
<filter-mapping>
    <filter-name>HTTPMonitorFilter</filter-name>
    <url-pattern>/*</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>INCLUDE</dispatcher>
    <dispatcher>ERROR</dispatcher>
</filter-mapping>Now you should comment out these lines and then can get connected.

OSB: problem when starting a managed server in an OSB cluster

Hi,
I used the configuration wizard to setup a very simple domain, containing a cluster with a managed server. When I start the managed server from the console I get prompted for the boot user and password. I specify the values I defined during the installation (weblogic user and custom passwort). After some time the managed server exists with the following exception:
####<21.04.2010 19.25 Uhr CEST> <Critical> <WebLogicServer> <DEMUC10525> <ManagedServer1> <main> <<WLS Kernel>> <> <> <1271870735741> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
     at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
What is its problem and how do I fix it? I have not configured anything special in the domain - just the cluster, a single machine and the managed server and admin server targeted at this machine.
The admin server starts without these problems. I also tried copying the boot.properties from the admin server to the managed server without any success - the same problem.
Regards
Dimo
Edited by: dimo velev on 21.04.2010 11:24

Hi Anuj,
it turned out to be an OSB related problem - WLS forum would not have been able to help.
The startManagedWebLogic script should be run only within an environment which has been correctly setup using the domain setDomainEnv script. This seems to add some classpaths and stuff like this which, if missing, produces the exception - it actually has absolutely nothing to do with the user and password being wrong.
If you are using a node manager to start the managed servers then it should also be run within an evironment correctly setup with the domain's setDomainEnv script.
Best regards
Dimo

NPE while starting Node Manager in SOA 11.1.1.5

I have installed SOA Suite 11g (11.1.1.5) as per Oracle Quick Start Guide for SOA Suite 11.1.1.5.
I start the database and Weblogic admin server. When I try to start the node manager, I am getting following error:
1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer <init>
WARNING: Node manager configuration properties file 'C:\Oracle\MIDDLE~3\WLSERV~1
.3\common\NODEMA~1\nodemanager.properties' not found. Using default settings.
<1 Nov, 2011 9:23:28 AM> <INFO> <Saving node manager configuration properties to
'C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1\nodemanager.properties'>
1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer <init>
INFO: Saving node manager configuration properties to 'C:\Oracle\MIDDLE~3\WLSERV
~1.3\common\NODEMA~1\nodemanager.properties'
<1 Nov, 2011 9:23:28 AM> <SEVERE> <Fatal error in node manager server>
java.lang.NullPointerException
at java.util.Hashtable.containsKey(Hashtable.java:314)
at weblogic.nodemanager.server.NMServerConfig.initNetworkInfoList(NMServ
erConfig.java:491)
at weblogic.nodemanager.server.NMServerConfig.getNetworkInfoList(NMServe
rConfig.java:481)
at weblogic.nodemanager.server.NMServerConfig.getConfigProperties(NMServ
erConfig.java:545)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:154)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
at weblogic.NodeManager.main(NodeManager.java:31)
1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.lang.NullPointerException
at java.util.Hashtable.containsKey(Hashtable.java:314)
at weblogic.nodemanager.server.NMServerConfig.initNetworkInfoList(NMServ
erConfig.java:491)
at weblogic.nodemanager.server.NMServerConfig.getNetworkInfoList(NMServe
rConfig.java:481)
at weblogic.nodemanager.server.NMServerConfig.getConfigProperties(NMServ
erConfig.java:545)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:154)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
at weblogic.NodeManager.main(NodeManager.java:31)
C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1>goto finish
C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1>ENDLOCAL
C:\Oracle\Middleware\wlserver_10.3\server\bin>
I checked "C:\Oracle\Middleware\wlserver_10.3\common\nodemanager" directory. There is no nodemanager.properties file there. Do I need to create it manually?
Please advise.
Thanks,
Vivek

I cut and paste the description of the note. There is a statement with the cause that states
"This issue happens only when the display name of a NIC configured for migration in nodemanager is null"
and it is a little ambigious. It implies there is a workaround of setting the display name, but doesn't discuss how to apply this workaround; the display name it refers to generated by a code call to the NetworkInterface.getDisplayName() method from the JDK.
I assume that the display name here is the parameter called Interface within the nodemanger.properties, but there is nothing within the note that confirms this, nor if setting this to the NICE name will fix this issue. here is a full list of the nodemanger.propertes file -> http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
I'd download and try the patch in your place; it's a WLS patch (as nodemanager is part of WLS) so shouldn't affect SOA Suite. Failing that, open a SR.

Connection Refused when starting node manager on Linux

Similar Messages

Maybe you are looking for