Problem to connect node manager

Hi,
When i am trying to connect node manager using below command i am getting error
wls:/offline> nmConnect('system','weblogic','localhost',5557,'punedomain')
Connecting to Node Manager ...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1447, in nmConnect
WLSTException: "Error occured while performing nmConnect : Cannot connect to the Node Manager.Access to domain 'punedomain' for user 'system' denied Use dumpStack() to view the full stacktrace"
wls:/offline> dumpStack()
This Exception occured at Sun Oct 24 12:48:16 GMT 2010
weblogic.nodemanager.NMException: Access to domain 'punedomain' for user 'system' denied
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:249)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:213)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:160)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:41)
at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
        at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
        at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
        at org.python.core.PyMethod.__call__(PyMethod.java:96)
        at org.python.core.PyObject.__call__(PyObject.java:248)
        at org.python.core.PyObject.invoke(PyObject.java:2016)
        at org.python.pycode._pyx4.nmConnect$89(<iostream>:1434)
        at org.python.pycode._pyx4.call_function(ILorg.python.core.PyFrame;)Lorg.python.core.PyObject;(<iostream>:???)
        at org.python.core.PyTableCode.call(PyTableCode.java:208)
        at org.python.core.PyTableCode.call(PyTableCode.java:404)
        at org.python.core.PyFunction.__call__(PyFunction.java:184)
        at org.python.core.PyObject.__call__(PyObject.java:248)
        at org.python.pycode._pyx97.f$0(<console>:1)
        at org.python.pycode._pyx97.call_function(ILorg.python.core.PyFrame;)Lorg.python.core.PyObject;(<console>:???)
        at org.python.core.PyTableCode.call(PyTableCode.java:208)
        at org.python.core.PyCode.call(PyCode.java:14)
        at org.python.core.Py.runCode(Py.java:1135)
        at org.python.core.Py.exec(Py.java:1157)
        at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:148)
        at org.python.util.InteractiveInterpreter.runcode(InteractiveInterpreter.java:89)
        at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:70)
        at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:44)
        at weblogic.management.scripting.WLST.main(WLST.java:142)
I am giving same credentila which i used to create during my domain creation.I am using weblogic 9.2 version.Do i need to provide some other password.When i investigate i found that this command taking password from nm_password file but this password is in encrypted form.
Please help on this problem.
Thanks
Sahil

Hi,
When i use nmconnect command with more parameters i got some strange error
ls:/offline> nmConnect('system','weblogic','localhost',5557,'punedomain','C:\9.2\bea\user_projects\domains\punedomain','plain')
Connecting to Node Manager ...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1447, in nmConnect
WLSTException: 'Error occured while performing nmConnect : Cannot connect to the Node Manager.Unexpected response from server: \x15\x00\x02\x00\x02\x02F Use dumpStack() to view the full stacktrace'
wls:/offline> dumpStack()
This Exception occured at Sun Oct 24 13:11:27 GMT 2010
java.io.IOException: Unexpected response from server: § ☻ ☻☻F
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:253)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:199)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:160)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:41)
at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
        at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
        at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
        at org.python.core.PyMethod.__call__(PyMethod.java:96)
        at org.python.core.PyObject.__call__(PyObject.java:248)
        at org.python.core.PyObject.invoke(PyObject.java:2016)
        at org.python.pycode._pyx4.nmConnect$89(<iostream>:1434)
        at org.python.pycode._pyx4.call_function(ILorg.python.core.PyFrame;)Lorg.python.core.PyObject;(<iostream>:???)
        at org.python.core.PyTableCode.call(PyTableCode.java:208)
        at org.python.core.PyTableCode.call(PyTableCode.java:404)
        at org.python.core.PyFunction.__call__(PyFunction.java:184)
        at org.python.core.PyObject.__call__(PyObject.java:248)
        at org.python.pycode._pyx116.f$0(<console>:1)
        at org.python.pycode._pyx116.call_function(ILorg.python.core.PyFrame;)Lorg.python.core.PyObject;(<console>:???)
        at org.python.core.PyTableCode.call(PyTableCode.java:208)
        at org.python.core.PyCode.call(PyCode.java:14)
        at org.python.core.Py.runCode(Py.java:1135)
        at org.python.core.Py.exec(Py.java:1157)
        at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:148)
        at org.python.util.InteractiveInterpreter.runcode(InteractiveInterpreter.java:89)
        at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:70)
        at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:44)
        at weblogic.management.scripting.WLST.main(WLST.java:142)

Similar Messages

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?

Problem starting managed server using Node Manager/WL 7

I have just configured Node Manager for the first time to start a managed server,
following the documentation 'Managing Server Availability with Node Manager'. However
when I attempt to start the managed server from the Administration Console I always
get the following exception:
<Jul 10, 2002 1:59:29 PM EDT> <Info> <[email protected]:5555> <Starting
Server webdevDomain::apps ...>
<Jul 10, 2002 1:59:29 PM EDT> <Info> <[email protected]:5555> <BaseProcessControl:
saving process id of Weblogic Managed server 'apps', pid: 15094>
Starting WebLogic Server...
Connecting to http://198.242.140.49:17043...
<Jul 10, 2002 1:59:32 PM EDT> <Critical> <WebLogicServer> <000364> <Server failed
during initialization. Exception:weblogic.management.configuration.ConfigurationException:
Exception encountered connecting to http://198.242.140.49:17043/wl_management_internal2/Bootstrap
- with nested exception:
[java.io.StreamCorruptedException: InputStream does not contain a serialized object]
java.io.StreamCorruptedException: InputStream does not contain a serialized object
     at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:844)
     at java.io.ObjectInputStream.<init>(ObjectInputStream.java:163)
     at weblogic.management.ManagedServerAdmin.bootstrapLocalServer(ManagedServerAdmin.java:212)
     at weblogic.management.ManagedServerAdmin.initialize(ManagedServerAdmin.java:122)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:665)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
     at weblogic.Server.main(Server.java:31)
But I am able to start the managed server using the startApps.sh script with no problems.
I am running WL 7 on Solaris 2.8. All processes are running on the same host.
Any help is appreciated!
John

Re-installing WL Server 7.0.0.1 resolved this problem.
- John

Auto restart node manager connection

Hi,
when we try to restart all server with auto restart scripts way.following error come:-
[oracle@acldlu01oam bin]$ cd /home/oracle/scripts/AutoRestart/
[oracle@acldlu01oam AutoRestart]$ ls
AdminServer.py config    ServerStatus.py startManualNode.sh startupOAM.sh
bin             security ServerStop.py    startScripts.sh
[oracle@acldlu01oam AutoRestart]$ ./startScripts.sh status
CLASSPATH=/u01/oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_cla                                                                                        sspath/weblogic_patch.jar:/u01/oracle/Middleware/patch_ocp371/profiles/default/s                                                                                        ys_manifest_classpath/weblogic_patch.jar:/u01/oracle/jdk1.7.0_67/lib/tools.jar:/                                                                                        u01/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/u01/oracle/Middl                                                                                        eware/wlserver_10.3/server/lib/weblogic.jar:/u01/oracle/Middleware/modules/featu                                                                                        res/weblogic.server.modules_10.3.6.0.jar:/u01/oracle/Middleware/wlserver_10.3/se                                                                                        rver/lib/webservices.jar:/u01/oracle/Middleware/modules/org.apache.ant_1.7.1/lib                                                                                        /ant-all.jar:/u01/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/                                                                                        ant-contrib.jar::/u01/oracle/Middleware/utils/config/10.3/config-launch.jar::/u0                                                                                        1/oracle/Middleware/wlserver_10.3/common/derby/lib/derbynet.jar:/u01/oracle/Midd                                                                                        leware/wlserver_10.3/common/derby/lib/derbyclient.jar:/u01/oracle/Middleware/wls                                                                                        erver_10.3/common/derby/lib/derbytools.jar::
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to Node Manager ...
<Feb 24, 2015 11:16:12 PM CST> <Info> <Security> <BEA-090905> <Disabling CryptoJ                                                                                         JCE Provider self-integrity check for better startup performance. To enable thi                                                                                        s check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Feb 24, 2015 11:16:12 PM CST> <Info> <Security> <BEA-090906> <Changing the defa                                                                                        ult Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disabl                                                                                        e this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 E                                                                                        ntrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Ent                                                                                        rust\, Inc.,C=US". The loading of the trusted certificate list raised a certific                                                                                        ate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1                                                                                        .2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. -                                                                                         For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US                                                                                        ". The loading of the trusted certificate list raised a certificate parsing exce                                                                                        ption PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.                                                                                        1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=thawte Primary Root CA - G2,OU=(c) 2007 thawte\, Inc. -                                                                                         For authorized use only,O=thawte\, Inc.,C=US". The loading of the trusted certi                                                                                        ficate list raised a certificate parsing exception PKIX: Unsupported OID in the                                                                                         AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=Buypass Class 3 Root CA,O=Buypass AS-983163327,C=NO". T                                                                                        he loading of the trusted certificate list raised a certificate parsing exceptio                                                                                        n PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11                                                                                        .>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=Buypass Class 2 Root CA,O=Buypass AS-983163327,C=NO". T                                                                                        he loading of the trusted certificate list raised a certificate parsing exceptio                                                                                        n PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11                                                                                        .>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,                                                                                        O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certifica                                                                                        te list raised a certificate parsing exception PKIX: Unsupported OID in the Algo                                                                                        rithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,                                                                                        O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certifica                                                                                        te list raised a certificate parsing exception PKIX: Unsupported OID in the Algo                                                                                        rithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=VeriSign Class 3 Public Primary Certification Authority                                                                                         - G4,OU=(c) 2007 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Ne                                                                                        twork,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raise                                                                                        d a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifi                                                                                        er object: 1.2.840.10045.4.3.3.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". Th                                                                                        e loading of the trusted certificate list raised a certificate parsing exception                                                                                         PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.                                                                                        >
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO                                                                                        .\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate                                                                                         parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.8                                                                                        40.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=AffirmTrust Commercial,O=AffirmTrust,C=US". The loading                                                                                         of the trusted certificate list raised a certificate parsing exception PKIX: Un                                                                                        supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c)                                                                                         2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriS                                                                                        ign\, Inc.,C=US". The loading of the trusted certificate list raised a certifica                                                                                        te parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.                                                                                        2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=AffirmTrust Premium ECC,O=AffirmTrust,C=US". The loadin                                                                                        g of the trusted certificate list raised a certificate parsing exception PKIX: U                                                                                        nsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loadin                                                                                        g of the trusted certificate list raised a certificate parsing exception PKIX: U                                                                                        nsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 20                                                                                        08 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of                                                                                         the trusted certificate list raised a certificate parsing exception PKIX: Unsup                                                                                        ported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=GeoTrust Primary Certification Authority - G2,OU=(c) 20                                                                                        07 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of                                                                                         the trusted certificate list raised a certificate parsing exception PKIX: Unsup                                                                                        ported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr                                                                                        usted CA certificate "CN=AffirmTrust Premium,O=AffirmTrust,C=US". The loading of                                                                                         the trusted certificate list raised a certificate parsing exception PKIX: Unsup                                                                                        ported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.12.>
This Exception occurred at Tue Feb 24 23:16:12 CST 2015.
weblogic.nodemanager.NMConnectException: Connection refused. Could not connect t                                                                                        o NodeManager. Check that it is running at localhost:5556.
Problem invoking WLST - Traceback (innermost last):
File "/home/oracle/scripts/AutoRestart/ServerStatus.py", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node                                                                                         Manager. : Connection refused. Could not connect to NodeManager. Check that it                                                                                         is running at localhost:5556.
Use dumpStack() to view the full stacktrace
could you please help.
Thanks,
Hiresh

Hi Radu,
I write python scripts for getting server status and scripys is:
nmConnect(username='weblogic',password='welcome1',domainName='oam_domain')
#,host='acldlu01oam.corp.vha.com')
#nmConnect('weblogic','welcome1','acldlu01oam.corp.vha.com','5556','oam_domain','/u01/oracle/Middleware/user_projects/domains/oam_domain','ssl')
print "NodeManager connected.."
print " Admin Server is : "
nmServerStatus(serverName='AdminServer')
print " OAM Server is : "
nmServerStatus('oam_server1')
print "End of script"
but output we get:-
[oracle@acldlu01oam AutoRestart]$ ./startScripts.sh status
CLASSPATH=/u01/oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/oracle/jdk1.7.0_67/lib/tools.jar:/u01/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/u01/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/u01/oracle/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/u01/oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/u01/oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/u01/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/u01/oracle/Middleware/utils/config/10.3/config-launch.jar::/u01/oracle/Middleware/wlserver_10.3/common/derby/lib/derbynet.jar:/u01/oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/u01/oracle/Middleware/wlserver_10.3/common/derby/lib/derbytools.jar::
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to Node Manager ...
<Feb 25, 2015 4:37:57 AM CST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Feb 25, 2015 4:37:57 AM CST> <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>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G2,OU=(c) 2007 thawte\, Inc. - For authorized use only,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Buypass Class 3 Root CA,O=Buypass AS-983163327,C=NO". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Buypass Class 2 Root CA,O=Buypass AS-983163327,C=NO". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Class 3 Public Primary Certification Authority - G4,OU=(c) 2007 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Commercial,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Premium ECC,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G2,OU=(c) 2007 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Premium,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.12.>
This Exception occurred at Wed Feb 25 04:37:57 CST 2015.
weblogic.nodemanager.NMConnectException: Connection refused. Could not connect to NodeManager. Check that it is running at localhost:5556.
Problem invoking WLST - Traceback (innermost last):
File "/home/oracle/scripts/AutoRestart/ServerStatus.py", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Connection refused. Could not connect to NodeManager. Check that it is running at localhost:5556.
Use dumpStack() to view the full stacktrace
Thanks,
Hiresh

Error occured while performing nmConnect : Cannot connect to Node Manager.

Hi There,
I am trying to connect to my node manager via WLST, however when I try to do so I get the following exception:
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Read channel closed
I have searched Google for the reason behind this exception, but I couldnt find anything that explains why I am getting it.
Could someone help me out? All I want to do is connect to the node manager and then kill one of the nodes.
I should point out that the AdminServer and the node are the same machine.

The nodemanager will not accept SSL connections, I checked the config on WL itself.
I can confirm that it is also in nodemanager.domains
I have restarted the service and also bounced the box, but this hasnt helped. I get the following when running this command:
<27-May-2013 14:08:43 o'clock CEST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<27-May-2013 14:08:43 o'clock CEST> <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>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Should it be going through all of this if I am trying to connect with plain text?

Node Manager unable to start managed Server. SSL Handshake problem

I am getting the following Error:
weblogic.nodemanager.NodeManagerException: [Could not execute command start for server wecarebeadev via the Node Manager - reason: [CommandInvoker: Failed to send command: 'online to server 'wecarebeadev' to NodeManager at host: 'localhost:5555' with exception Write Channel Closed, possible SSL handshaking or trust failure. Please ensure that the NodeManager is active on the target machine].]
I have Weblogic Server 7.0 SP1 with Admin and Managed Server running on the same physical machine as Windows Services.
SSL port has been setup properly for Managed Server. Host Name Verification Ignored is checked for MS.

Hi Ajay,
This happens when the SSL communication between the admin and the node
manager fails. The SSL configuration of the admin server or the node
manager is the problem.
cheers,
gaurav.
On 30 Jun 2003 12:19:49 -0700, Ajay Kulkarni <[email protected]> wrote:
I am getting the following Error:
weblogic.nodemanager.NodeManagerException: [Could not execute command
start for server wecarebeadev via the Node Manager - reason:
[CommandInvoker: Failed to send command: 'online to server 'wecarebeadev'
to NodeManager at host: 'localhost:5555' with exception Write Channel
Closed, possible SSL handshaking or trust failure. Please ensure that the
NodeManager is active on the target machine].]
I have Weblogic Server 7.0 SP1 with Admin and Managed Server running on
the same physical machine as Windows Services.
SSL port has been setup properly for Managed Server. Host Name
Verification Ignored is checked for MS.
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Grid installtion failing with error Cannot connect to Node Manager. : Conf

I am trying to install Grid, however its failing with following error
I installed Weblogic server 10.3.4 and 11g R2 database
==============================================================
Code of Exception: Error occured while performing nmConnect : Cannot connect to Node Manager. : Configuration error while reading domain directory
Use dumpStack() to view the full stacktrace
Thu Mar 03 21:49:03 IST 2011
<traceback object at 1>
Connecting to Node Manager ...
This Exception occurred at Thu Mar 03 21:49:03 IST 2011.
Thu Mar 03 21:49:03 IST 2011
SEVERE: Exception: during stop of admin server
Thu Mar 03 21:49:03 IST 2011
Name of Exception: main.WLSTException
Thu Mar 03 21:49:03 IST 2011
Code of Exception: Error occured while performing nmConnect : Cannot connect to Node Manager. : Configuration error while reading domain directory
Use dumpStack() to view the full stacktrace
Thu Mar 03 21:49:03 IST 2011
<traceback object at 2>
Connecting to Node Manager ...
This Exception occurred at Thu Mar 03 21:49:03 IST 2011.
Thu Mar 03 21:49:03 IST 2011
Node Manager is not running
Mar 3, 2011 9:49:03 PM oracle.sysman.omsca.util.CoreOMSConfigAssistantUtil execCommand
INFO: error messages of the command :
weblogic.nodemanager.NMException: Configuration error while reading domain directory
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:301)
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:314)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:249)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:200)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:206)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:53)
at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:179)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:173)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx2.nmConnect$3(<iostream>:118)
at org.python.pycode._pyx2.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.pycode._pyx41.stopManagedServer$6(/u02/oracle/Oracle/Middleware/oms11g/sysman/omsca/scripts/wls/start_server.py:142)
at org.python.pycode._pyx41.call_function(/u02/oracle/Oracle/Middleware/oms11g/sysman/omsca/scripts/wls/start_server.py)
at org.python.core.PyTableCode.call(Unknown Source)

I am still getting error, even after installing Weblogic server 10.3.2
ar 4, 2011 10:44:42 AM oracle.sysman.omsca.util.CoreOMSConfigAssistantUtil execCommand
INFO: error messages of the command :
weblogic.nodemanager.NMConnectException: Connection refused. Could not connect to NodeManager. Check that it is running at node1.slksoft.com:7,403.
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:525)
at weblogic.nodemanager.client.SSLClient.createSocket(SSLClient.java:38)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:227)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:199)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:205)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:52)
at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
and also i am getting below error.
oracle@node1 grid]$ export ORACLE_SID=prod
[oracle@node1 grid]$ emctl status agent
EM Configuration issue. /u01/oracle/product/11.2.0/db_1/node1.soft.com_prod not found.
[oracle@node1 grid]$

Admin console cannot connect to Node Manager

I've just installed WLS 10.3.2, configured a domain (TEST), a machine (PHILO), a server (TEST1), and a node manager running on PHILO. I logged onto PHILO, ran "startNodeManager.sh", no problems, it says it's listening on 5556, like I configured. However, when I attempt to start the server TEST2 (associated with machine PHILO and in the domain TEST) from the admin gui I get the following error:
For server TEST1, the Node Manager associated with machine PHILO is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
If I log onto the local server where the admin node is running, I can telnet to PHILO 5556, so why can't the node manager be reached?

I have a similar problem trying to start my Managed server. I get the following error:
Unexpected response from server: § ☻ ☻☻F
weblogic.management.scripting.ScriptException: Error occured while performing st
art : Server with name geo-apps failed to be started
at weblogic.management.scripting.ExceptionHandler.handleException(Except
ionHandler.java:48)
at weblogic.management.scripting.LifeCycleHandler.startServer(LifeCycleH
andler.java:501)
at weblogic.management.scripting.WLScriptContext.start(WLScriptContext.j
ava:477)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx16.start$80(<iostream>:1270)
at org.python.pycode._pyx16.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.pycode._pyx15.f$0(D:\product\Oracle\11.1.1\Middleware\user
projects\domains\basedomain\ServerStart.py:4)
at org.python.pycode._pyx15.call_function(D:\product\Oracle\11.1.1\Middl
eware\user_projects\domains\base_domain\ServerStart.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.util.PythonInterpreter.execfile(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at weblogic.WLST.main(WLST.java:29)
Problem invoking WLST - Traceback (innermost last):
File "D:\product\Oracle\11.1.1\Middleware\user_projects\domains\base_domain\Se
rverStart.py", line 4, in ?
File "<iostream>", line 1280, in start
File "<iostream>", line 1744, in raiseWLSTException
WLSTException: Error occured while performing start : Error starting the server
: Error occured while performing start : Server with name geo-apps failed to be
started
Use dumpStack() to view the full stacktrace

WLSTException: Cannot connect to Node Manager

Hello,
I am trying to connect to my nodemanager via the WLST rather than the service and get the following error. (I am using custom keystores instead of Demo)
wls:/offline> nmConnect('weblogic','1234',' xx.xx.xx ','5556','base_domain',':/Oracle/Middleware/user_projects/domains/base_domain','ssl')
Connecting to Node Manager ...
<Oct 17, 2012 4:52:38 PM PDT> <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>
<Oct 17, 2012 4:52:41 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certifica
te parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Oct 17, 2012 4:52:41 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. -For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Oct 17, 2012 4:52:41 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Oct 17, 2012 4:52:41 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Oct 17, 2012 4:52:41 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Oct 17, 2012 4:52:41 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Oct 17, 2012 4:52:41 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Oct 17, 2012 4:52:41 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Un
supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Oct 17, 2012 4:52:41 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupp
orted OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Oct 17, 2012 4:52:41 PM PDT> <Warning> <Security> <BEA-090542> <Certificate chain received from xx.xx.xx - yy.yy.yy.yy was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configurati
on to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS se
rver behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : [Security:090542]Certificate chain received from xx.xx.xx - yy.yy.yy.yy was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore= DemoTrust on the command line for this client.
Thanks..

Yes Node Manager is running fine. I was able to overcome the above error, by using the following parameters while running Weblogic.WLST:
"java -Dweblogic.security.TrustKeyStore=CustomTrust -Dweblogic.security.CustomTrustKeyStoreFileName=<name>.jks weblogic.WLST"
Thanks,

Trusted CA Certificate Ignored When Connecting To Node Manager

I have a question about Node Manager.
I have the following configuration:
OS: Linux (CentOS 5.4) 32bit
Oracle WebLogic Server 11gR1 (10.3.2)
Portal, Forms, Reports and Discoverer (11.1.1.2.0) - only Forms and Reports are installed and configured
All configured components start successfuly, but I receive the following security related messages when I connect to Node Manager.
java -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust weblogic.WLST
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> nmConnect('weblogic', <weblogic password>, 'icweb001', '5556', <domain name>)
Connecting to Node Manager ...
<Nov 25, 2009 3:35:35 PM EST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Nov 25, 2009 3:35:35 PM EST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Successfully Connected to Node Manager.
wls:/nm/DynaMed>I understand that the two BEA-090898 messages associated with the specified certificates are informational, but is there anything I can do to either,
1) correct the certificate so the messages are not generated, or
2) change my setup so that the messages are not displayed?
Thanks in advance for your help.

The certificates at issue belong to the $JAVA_HOME keystore in weblogic
$JAVA_HOME/jre/lib/security/cacerts
ttelesecglobalrootclass3ca, Feb 10, 2009, trustedCertEntry,
ttelesecglobalrootclass2ca, Feb 10, 2009, trustedCertEntry,I was able to stop the warning messages from appearing when connecting to node manager, by removing these two certificates from the $JAVA_HOME/jre/lib/security/cacerts keystore.
cd $JAVA_HOME/jre/lib/security
cp -p cacerts cacerts.original
chmod 644 cacerts
keytool -delete -alias ttelesecglobalrootclass2ca -keystore cacerts
keytool -delete -alias ttelesecglobalrootclass3ca -keystore cacerts
chmod 444 cacerts cacerts.originalOnce the certs are removed from the keystore, the warning messages no longer appear when connecting to node manager.
Some additional information on these two certificates can be found at:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6803022Edited by: wblum on Feb 18, 2010 1:10 PM

Problem starting Admin Server using Node Manager

I have configured the Node Manager to run as a windows service. I want it to start the Admin Server when it is started. This is not working. The Node Manager starts without problem but does not appear to even attempt to start the Admin Server. No error message is written to the nodemanager.log. I have configured the following properties as described in the documentation:
StartScriptEnabled=true
StartScriptName=startWebLogic.cmd
Starting the Admin Server using wlst works. As does starting and stopping a Managed server using the Admin console. This leads me to conclude that the Node Manager configuration is ok.
WLS version is 9.2.
All suggestions as to what could be the issue here would be greatly appreciated.
Cheers!

Ok, I just wasted a whole day before I found the tricks.
First, you don't need to do that StartScriptEnabled stuff, unless you have important things to add there.
Ok, and now what I found:
- You must make sure you have installed the NodeManager as a service
- Next, make sure the admin server is assigned to the right machine. Since you can do the WLST trick, that should be fine. If not, tough luck, because the docs say you cannot re-assign an admin server.
- In nodemanager.properties (...\weblogic92\common\nodemanager) make sure CrashRecoveryEnabled is set to true
- In nodemanager.domains (same dir) make sure your domain is mentioned with its path
- For each of the servers to be auto-started, make sure that a startup.properties (in <your-domain-dir> \servers\<server-name> \data\nodemanager) contains Arguments=-Xnohup (for JRockit, for Sun JDK its -Xrs)
Make sure they are started through the nodemanager, et voila, they'll be restarted after a reboot.
Why this works? At reboot, the OS ask all processes to die, nicely. Those that don't, get killed forcibly. Without the -Xnohup/rs, the WebLogic servers respond to the nice request, and the nodemanager immediately tries to restart them. Unfortunately, the OS refuses to do that, and the server process is marked as failed, and won't be restarted after reboot. With the option given, the servers ignore mr nice guy, and get killed after the nodemanager has disappeared.
What can go wrong? A lot. I was playing with the nodemanager username and password, and that took some time to clean up. I probably have to redo the entire setup just to make sure I have a repeatable experience now...
Cheers,
Bert

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.

Server stop problem with node manager

Hi ,
I get this error often when I try to stop a managed server via the nodemanager
from the admin console or from the weblogic.Admin command. The server does not
stop and it goes into an unknown state and I have to do a force shutdown
[java] Error: [Could not execute command shutdown for server xxx via the N e Manager
- reason: [__COMMAND_EXCEPTION__Request: failed to execute command ' utdown' on
server 'xxx - reason: '[Unable to send shutdown request to server.> ].]
[java] Start server side stack trace: [java] weblogic.nodemanager.NodeManagerException:
[Could not execute comman shutdown for server xxx via the Node Manager - reason:
[__COMMAND_EXCEPTION__ quest: failed to execute command 'shutdown' on server 'xxx
- reason: '[Unable o send shutdown request to server.]'> ].] [java] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeMa
gerRuntime.java:472) [java] at weblogic.nodemanager.NodeManagerRuntime.shutdown(NodeManagerR
time.java:86) [java] at java.lang.reflect.Method.invoke(Native Method) [java]
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(D amicMBeanImpl.java:732)
[java] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicM anImpl.java:714)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl ava:1557)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl ava:1525)
[java] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Rem

Hi Anil,
A little more information might be helpful. Which version are you talking
about ? What is the server state when you issue the command ? Is the server
very busy. Are you able to get the server state from the nodemanager when
the server is running ? Are you able to communicate from admin server ->
nodemanager <-> managed server ?
cheers,
gaurav.
"Anil Jacob" <[email protected]> wrote in message
news:3fb16b7c$[email protected]..
>
Hi ,
I get this error often when I try to stop a managed server via thenodemanager
from the admin console or from the weblogic.Admin command. The server doesnot
stop and it goes into an unknown state and I have to do a force shutdown
[java] Error: [Could not execute command shutdown for server xxx via the N
e Manager> - reason: [__COMMAND_EXCEPTION__Request: failed to execute command 'utdown' on> server 'xxx - reason: '[Unable to send shutdown request to server.> .]
[java] Start server side stack trace: [java]weblogic.nodemanager.NodeManagerException:
[Could not execute comman shutdown for server xxx via the Node Manager -
reason:> [__COMMAND_EXCEPTION__ quest: failed to execute command 'shutdown' onserver 'xxx> - reason: '[Unable o send shutdown request to server.'> ].] [java] atweblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeMa
gerRuntime.java:472) [java] atweblogic.nodemanager.NodeManagerRuntime.shutdown(NodeManagerR
time.java:86) [java] at java.lang.reflect.Method.invoke(Native Method)[java]
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DamicMBeanImpl.java:732)
[java] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicManImpl.java:714)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImplava:1557)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImplava:1525)
[java] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Rem

Multiple Node Manager Instances and servers sharing the same domain home.

Hi,
We have a 8 man server weblogic cluster spread over 4 machines. Each machine runs 2 man servers each.
Each of the machine is configured to run node manager.
We use shared storage accessible to all 8 servers and all 8 man servers have the same domain_home.
Lets call it W:/domain
Now the problem we are facing is that node manager running on 1 machine is trying to access/control a managed server on a different machine after a machine restart.
eg.
ManServer1 Home : W:/domain/servers/server1 ====> runs on Machine 1
ManServer2Home : W:/domain/servers/server2 ====> runs on Machine 2
Problem is node manager on machine 1 is trying to restart man server 2. The path W:/domain/servers/server2 is accessible to Machine 1.
After a restart, what I assume is happening is that the nodemanager is checking all servers folder under Domain_Home/Servers and trying to restart servers instead of restarting only those which it should start. The config file has the server and machine assignment done correctly. Is there a way to make this configuration towork. Or do we need to create different domain_home's for different man servers like
Domain_Home for MS1: W:/domain/MS1 ( Server Home would be : W:/domain/MS1/servers/MS1)
Domain_Home for MS2: W:/domain/MS2 ( Server Home would be : W:/domain/MS2/servers/MS2)
Regards,
Atheek
Edited by: atheek1 on 03-May-2010 00:27

Thanks - We have tried putting 2 dad entries in file, but not sure how you connect. You only specify a port number, so how does it connect that to a db???

Unable to initialize Node Manager on Weblogic 11g (10.3.5) Linux env..

Hello,
I worked earlier on Weblogic 8.1 and after a long gap I am coming back to Weblogic Server.
And I tried to install & setup Weblogic Server 11g R1 (10.3.5). I successfully installed WL 11g on a Linux machine, configured the domain, and admin server without any problem. I created a managed server on the Console and tried to initialize the node manager to be able to start the managed server. I am getting the following error message repeatedly. And I did not select SSL connection, while setting up the environment.
Can someone help me resolve this issue?
<Sep 13, 2011 12:19:31 PM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.>
javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 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:71)
at java.lang.Thread.run(Thread.java:662)
Sep 13, 2011 12:19:31 PM weblogic.nodemanager.server.Handler run

Can you see what listen address you have given to Node Manager in console or in config.xml?
<machine xsi:type="unix-machineType">
<name>Servername</name>
<node-manager>
<name>Servername</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
Another way to start Managed server is to use startManaged.sh script.

Problem to connect node manager

Similar Messages

Maybe you are looking for