Network node manager upgrade

We are in the process of purchasing an upgrade to NNMi. We are currently running version 9.23. The part number for the upgrade is TA064AAE . I need to know if that will upgrade us to version 10. Please note I cannot contact HP support directly because our service contract (SAID) has expired. I have called support twice and sales support at 877-686-9637 twice with no answer to my question.  I contacted HP Chat twice also and still have no answer. The person on chat just suggested I try the forum. I just need to know if this will upgrade us to version 10.  

To integrate LMS 2.6 with NNM you will need to install either the adapter or utility.
If they are to be on same server, you can download and install Adapter.v1-7.sol.nnm.tar (assuming solaris) to CW box.
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-nnm
(also download readme for directions).
Readme does mentions:
Adapter(Version 1.7) for integrating Cisco Applications and Cisco Devices into HP Network Node Manager 6.4 , 7.0 , 7.01 and 7.5 versions
If you are installing NNM on separate server, you can install the Integration Utility (IU) on the remote server where HP NNM is installed which you may download from this link:
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-utility

Similar Messages

  • Upgrade from 10.3.2 to 10.3.3 - node manager?

    Hi,
    I have a very quick question I guess - do I need to upgrade the node manager when running the upgrade from 10.3.2 to 10.3.3?
    The upgrade guide E13754-02 says that I need to do it with the existing pre-10.0 node manager but doesn't say it is mandatory otherwise.
    Can you please clarify.
    Thank you
    Anatoliy

    See the following document on upgrading (http://download.oracle.com/docs/cd/E14571_01/web.1111/e13754.pdf).
    Particulary see the section on Upgrading the NodeManager (4.2):
    You must upgrade each instance of Node Manager that you want to run in the
    WebLogic Server 10.3.3 environment. Specifically, you must upgrade Node Manager
    on every machine in the domain.

  • 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

  • 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?

  • 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,

  • What is Node Manager ?

    Hi
    I have been reading documents on Oracle Fusion Middleware 11g. At lot of places 'Node Manager' is mentioned across these documents.
    Please can someone explain here what is Node Manager and what it is its role in OFMW 11g ?
    Cheers
    Mayur

    Hi Mayur,
    For more details please refer to: http://weblogic-wonders.com/weblogic/2010/06/18/weblogic-initials/
    <b><font color=maroon> What is NodeManager?</font></b>
    A Node Manager process is not associated with a specific WebLogic domain but with a machine. Node Manager process to control server instances in any WebLogic Server domain until the server instances reside on the same machine as the Node Manager process.
    Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. Although Node Manager is optional, it is recommended if your WebLogic Server environment hosts applications with high availability requirements.
    A Node Manager process is not associated with a specific WebLogic domain but with a machine. You can use the same Node Manager process to control server instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the Node Manager process.
    <b><font color=maroon>Why We Need Nodemanagers?</font></b>
    1). It can Start, Shut Down, and Restart an Administration Server which has assigned a Machine.
    2). It can Start, Shut Down, and Restart an Managed Server which has assigned a Machine.
    3). It can Restart Administration and Managed Servers. (Crash Recovery of Servers is an Interesting feature)
    4). It can be used to Monitor Servers and View Log Data
    <b><font color=maroon>Types of NodeManagers?</font></b>
    *1). Java Based Nodemanager:* This can be used in Windiows as well as UNIX based Operating systems. Java Based Node Manager is not supported on Open VMS, OS/390, AS400, UnixWare, or Tru64 UNIX.
    *2). Script Based Nodemanager:* This nodemanager can be used in UNIX based operating systems. The advantage of the script-based Node Manager is that it can remotely manage servers over a network that has been configured to use SSH.
    For More Information on NodeManager please refer to:
    http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/nodemgr.html
    And
    http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
    Thanks
    Jay SenSharma

  • WLST - Failing to run nmConnect() command / node manager becomes unreachabl

    Hello guys,
    I'm facing some issues to setup some configurations of one application that I've deployed on weblogic 10.3.3.0.
    One of the needed steps in order to configure this applications is open the WLST in offline mode an run 2 commands:
    */bea/mytrack/wlserver_10.3/common/bin/wlst.sh*
    Then I try to connect in the nodemanager:
    * wls:/offline> nmConnect('admin30800','weblogic_password',port='30801',domainName='track30800')*
    The following error returns:
    Connecting to Node Manager ...
    <Jul 13, 2011 2:23:45 PM CDT> <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.>
    <Jul 13, 2011 2:23:45 PM CDT> <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.>
    <Jul 13, 2011 2:23:45 PM CDT> <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.>
    <Jul 13, 2011 2:23:45 PM CDT> <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.>
    <Jul 13, 2011 2:23:45 PM CDT> <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.>
    <Jul 13, 2011 2:23:45 PM CDT> <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.>
    <Jul 13, 2011 2:23:45 PM CDT> <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.>
    <Jul 13, 2011 2:23:45 PM CDT> <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.>
    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. : Access to domain 'track30800' for user 'admin30800' denied
    I did some research and found this thread here: http://kr.forums.oracle.com/forums/thread.jspa?threadID=788163
    that solves the initial problem, however after I performed the nmConnect and a storeUserConfig() command, I exit() from the WLST and restart the node manager with success, the node manager becomes unreachable.
    I used the WL adm console and access -> appdomain -> environments -> machines -> monitoring -> node manager status to check the unreachable status.
    Thanks in advance,
    Davinod

    Nice it worked!!
    However when I try to start the servers controlled by this node manager I got this error:
    -sh-3.2$ <Jul 14, 2011 8:43:42 AM> <WARNING> <Exception while starting server 'track30800-01'>
    java.io.FileNotFoundException: /u01/track30800/user_projects/domains/track30800/servers/track30800-01/data/nodemanager/boot.properties (Permission denied)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
    at weblogic.nodemanager.server.ServerManager.saveBootIdentity(ServerManager.java:495)
    at weblogic.nodemanager.server.ServerManager.saveStartupConfig(ServerManager.java:438)
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:301)
    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)
    Jul 14, 2011 8:43:42 AM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'track30800-01'
    java.io.FileNotFoundException: /u01/track30800/user_projects/domains/track30800/servers/track30800-01/data/nodemanager/boot.properties (Permission denied)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
    at weblogic.nodemanager.server.ServerManager.saveBootIdentity(ServerManager.java:495)
    at weblogic.nodemanager.server.ServerManager.saveStartupConfig(ServerManager.java:438)
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:301)
    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)
    <Jul 14, 2011 8:43:42 AM CDT> <Error> <NodeManager> <BEA-300048> <Unable to start the server track30800-01 : Exception while starting server 'track30800-01'>
    Edited: Should I change the chmod for 777 for this file in order to check that all users have write permission?
    -rw-r--r-- 1 root iluser 193 Jun 24 11:05 boot.properties
    Did I miss a step?
    Thanks,
    Davinod
    Edited by: davinod on Jul 14, 2011 6:58 AM

  • Node manager

    i have two managed servers MS_Dev1 and MS_Dev2 in MS windows 7 system. when starting the admin MS_Dev2 reaches to running mode as i configured node-manager for both server. But MS_Dev1 went to shutdown state, not able to start from Admin console. It went to Failed " FAILED_NOT_RESTARTABLE ". checked the log it says invalid password.
    i have re typed the pwd in Settings for MS_Dev1 -> Server Start -> username and password, again the same " FAILED_NOT_RESTARTABLE ". finally i went to C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\security and re typed the username and password in boot.properties file. Restarted the admin server but same " FAILED_NOT_RESTARTABLE " for MS_Dev1. Also i have tried to shutdown the MS_Dev1 in admin console, it throws below
    Message icon - Warning The server MS_Dev1 is in an incompatible state.
    Message icon - Warning 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.
    Note: Pwd for Admin, MS_Dev1 and 2 are same
    Looking the solution to fix this issue ASAP, Thnks a lot in Advance !
    refer the logs below,
    dev_domain.log
    ####<Mar 1, 2013 8:49:49 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362107989715> <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.>
    ####<Mar 1, 2013 8:49:49 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362107989715> <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.>
    ####<Mar 1, 2013 8:49:49 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362107989731> <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.>
    ####<Mar 1, 2013 8:49:49 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362107989731> <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.>
    AdminServer.log
    ####<Mar 1, 2013 9:04:36 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108876293> <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.>
    ####<Mar 1, 2013 9:04:36 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108876309> <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.>
    ####<Mar 1, 2013 9:04:36 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108876309> <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.>
    ####<Mar 1, 2013 9:05:04 AM IST> <Warning> <netuix> <Ram-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1362108904420> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=WLSServerControlTablePage.>
    ####<Mar 1, 2013 9:05:04 AM IST> <Warning> <Socket> <Ram-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108904872> <BEA-000449> <Closing socket as no data read from it on 192.168.56.1:58,895 during the configured idle timeout of 5 secs>
    ####<Mar 1, 2013 9:05:04 AM IST> <Warning> <Socket> <Ram-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108904872> <BEA-000449> <Closing socket as no data read from it on 192.168.56.1:58,894 during the configured idle timeout of 5 secs>
    MS_Dev1.log
    ####<Mar 1, 2013 9:02:09 AM IST> <Notice> <Log Management> <Ram-PC> <MS_Dev1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108729431> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    ####<Mar 1, 2013 9:02:09 AM IST> <Info> <Diagnostics> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108729462> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
    ####<Mar 1, 2013 9:02:09 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108729493> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
    ####<Mar 1, 2013 9:02:09 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108729493> <BEA-000133> <Waiting to synchronize with other running members of Dev_Cluster.>
    ####<Mar 1, 2013 9:02:11 AM IST> <Info> <Cluster> <Ram-PC> <MS_Dev1> <weblogic.cluster.MessageReceiver> <<WLS Kernel>> <> <> <1362108731677> <BEA-003107> <Lost 2 unicast message(s).>
    ####<Mar 1, 2013 9:02:25 AM IST> <Info> <Cluster> <Ram-PC> <MS_Dev1> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108745889> <BEA-000111> <Adding MS_Dev2 with ID -3996848074127341669S:192.168.56.1:[7004,7004,-1,-1,-1,-1,-1]:dev_domain:MS_Dev2 to cluster: Dev_Cluster view.>
    ####<Mar 1, 2013 9:02:25 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108745889> <BEA-000142> <Trying to download cluster JNDI tree from server MS_Dev2.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Info> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746139> <BEA-000128> <Updating -3996848074127341669S:192.168.56.1:[7004,7004,-1,-1,-1,-1,-1]:dev_domain:MS_Dev2 in the cluster.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746357> <BEA-000164> <Synchronized cluster JNDI tree from server MS_Dev2.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <main> <<WLS Kernel>> <> <> <1362108746404> <BEA-000365> <Server state changed to ADMIN>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <main> <<WLS Kernel>> <> <> <1362108746419> <BEA-000365> <Server state changed to RESUMING>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746451> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746778> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746841> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746841> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\MIDDLE~1\JDK160~1\jre\lib\security\cacerts.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746903> <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.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746903> <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.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <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.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <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.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <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.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <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.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <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.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746934> <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.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746950> <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.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Info> <WebLogicServer> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746950> <BEA-000307> <Exportable key maximum lifespan set to 500 uses.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Info> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746950> <BEA-002610> <Dynamic Listener Service initialized.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746950> <BEA-002613> <Channel "Default" is now listening on 192.168.56.1:7003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746965> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.56.1:7503 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746965> <BEA-000332> <Started WebLogic Managed Server "MS_Dev1" for domain "dev_domain" running in Development Mode>
    ####<Mar 1, 2013 9:02:27 AM IST> <Info> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108747028> <BEA-002635> <The server "AdminServer" connected to this server.>
    ####<Mar 1, 2013 9:02:27 AM IST> <Info> <JMX> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108747090> <BEA-149511> <Established JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://14.96.37.127:7001/jndi/weblogic.management.mbeanservers.domainruntime.>
    ####<Mar 1, 2013 9:02:27 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <main> <<WLS Kernel>> <> <> <1362108747979> <BEA-000365> <Server state changed to RUNNING>
    ####<Mar 1, 2013 9:02:27 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <main> <<WLS Kernel>> <> <> <1362108747995> <BEA-000360> <Server started in RUNNING mode>
    ####<Mar 1, 2013 9:02:27 AM IST> <Info> <J2EE> <Ram-PC> <MS_Dev1> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108747995> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
    ####<Mar 1, 2013 9:02:29 AM IST> <Info> <Cluster> <Ram-PC> <MS_Dev1> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108749524> <BEA-000128> <Updating -3996848074127341669S:192.168.56.1:[7004,7004,-1,-1,-1,-1,-1]:dev_domain:MS_Dev2 in the cluster.>
    ####<Mar 1, 2013 9:03:26 AM IST> <Info> <Health> <Ram-PC> <MS_Dev1> <weblogic.GCMonitor> <<anonymous>> <> <> <1362108806365> <BEA-310002> <80% of the total memory in the server is free>
    ####<Mar 1, 2013 9:03:32 AM IST> <Info> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108812808> <BEA-002634> <The server "AdminServer" disconnected from this server.>

    Kishore,
    checked the boot.properties file, it not having .txt and find the nodemanager.log as given below,
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Boot identity properties saved to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\data\nodemanager\boot.properties">
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Startup configuration properties saved to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\data\nodemanager\startup.properties">
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out00006">
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Server error log also redirected to server log>
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Starting WebLogic server with command line: C:\Oracle\Middleware\user_projects\domains\dev_domain\bin\startWebLogic.cmd >
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Working directory is 'C:\Oracle\Middleware\user_projects\domains\dev_domain'>
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out00007">
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Server error log also redirected to server log>
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out'>
    <Mar 1, 2013 8:21:21 AM> <INFO> <dev_domain> <MS_Dev1> <Server failed during startup so will not be restarted>
    <Mar 1, 2013 8:21:21 AM> <WARNING> <Exception while starting server 'MS_Dev1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
         at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
         at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
         at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
         at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
         at weblogic.nodemanager.server.Handler.run(Handler.java:71)
         at java.lang.Thread.run(Thread.java:662)
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Boot identity properties saved to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\data\nodemanager\boot.properties">
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Startup configuration properties saved to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\data\nodemanager\startup.properties">
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out00008">
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Server error log also redirected to server log>
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Starting WebLogic server with command line: C:\Oracle\Middleware\user_projects\domains\dev_domain\bin\startWebLogic.cmd >
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Working directory is 'C:\Oracle\Middleware\user_projects\domains\dev_domain'>
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out00009">
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Server error log also redirected to server log>
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out'>
    <Mar 1, 2013 8:24:59 AM> <INFO> <dev_domain> <MS_Dev1> <Server failed during startup so will not be restarted>
    <Mar 1, 2013 8:24:59 AM> <WARNING> <Exception while starting server 'MS_Dev1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
         at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
         at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
         at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
         at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
         at weblogic.nodemanager.server.Handler.run(Handler.java:71)
         at java.lang.Thread.run(Thread.java:662)

  • Weblogic 10.3.6 update node manager error.

    After installing 10.3.5 I did the installation on WebLogic 10.3.6 upgrade. (wls1036_upgrade_generic.jar). Domain installation does not work if I did, and then I saw when I ran the node manager.
    Error
    C:\oracle\Middleware\wlserver_10.3\server\bin>set CLASSPATH=.;C:\oracle\MIDDLE~1
    \patch_wls1036\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\ora
    cle\MIDDLE~1\patch_ocp371\profiles\default\sys_manifest_classpath\weblogic_patch
    .jar;C:\oracle\MIDDLE~1\patch_jdev1112\profiles\default\sys_manifest_classpath\w
    eblogic_patch.jar;C:\PROGRA~1\Java\JDK17~1.0_0\lib\tools.jar;C:\oracle\MIDDLE~1\
    WLSERV~1.3\server\lib\weblogic_sp.jar;C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\w
    eblogic.jar;C:\oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.6.0
    .jar;C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\oracle\MIDDLE~1
    \modules\ORGAPA~1.1/lib/ant-all.jar;C:\oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/
    ant-contrib.jar;
    C:\oracle\Middleware\wlserver_10.3\server\bin>if not "" == "" set CLASSPATH=;.;C
    :\oracle\MIDDLE~1\patch_wls1036\profiles\default\sys_manifest_classpath\weblogic
    patch.jar;C:\oracle\MIDDLE~1\patchocp371\profiles\default\sys_manifest_classpa
    th\weblogic_patch.jar;C:\oracle\MIDDLE~1\patch_jdev1112\profiles\default\sys_man
    ifest_classpath\weblogic_patch.jar;C:\PROGRA~1\Java\JDK17~1.0_0\lib\tools.jar;C:
    \oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\oracle\MIDDLE~1\WLSERV
    ~1.3\server\lib\weblogic.jar;C:\oracle\MIDDLE~1\modules\features\weblogic.server
    .modules_10.3.6.0.jar;C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C
    :\oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\oracle\MIDDLE~1\modules\
    NETSFA~1.0_1/lib/ant-contrib.jar;
    C:\oracle\Middleware\wlserver_10.3\server\bin>if not "" == "" set CLASSPATH=.;C:
    \oracle\MIDDLE~1\patch_wls1036\profiles\default\sys_manifest_classpath\weblogic_
    patch.jar;C:\oracle\MIDDLE~1\patch_ocp371\profiles\default\sys_manifest_classpat
    h\weblogic_patch.jar;C:\oracle\MIDDLE~1\patch_jdev1112\profiles\default\sys_mani
    fest_classpath\weblogic_patch.jar;C:\PROGRA~1\Java\JDK17~1.0_0\lib\tools.jar;C:\
    oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\oracle\MIDDLE~1\WLSERV~
    1.3\server\lib\weblogic.jar;C:\oracle\MIDDLE~1\modules\features\weblogic.server.
    modules_10.3.6.0.jar;C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:
    \oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\oracle\MIDDLE~1\modules\N
    ETSFA~1.0_1/lib/ant-contrib.jar;;
    C:\oracle\Middleware\wlserver_10.3\server\bin>cd C:\oracle\MIDDLE~1\WLSERV~1.3\c
    ommon\NODEMA~1
    C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1>if not "" == "" if not "" == "" go
    to runNMWithListenAddressAndPort
    C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1>if not "" == "" goto runNMWithList
    enAddress
    C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1>if not "" == "" goto runNMWithList
    enPort
    C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1>"C:\PROGRA~1\Java\JDK17~1.0_0\bin\
    java.exe" -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning -Dcoher
    ence.home=C:\oracle\MIDDLE~1\COHERE~1.7 -Dbea.home=C:\oracle\MIDDLE~1 -Xverify:
    none "-Djava.security.policy=C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.p
    olicy" "-Dweblogic.nodemanager.javaHome=C:\PROGRA~1\Java\JDK17~1.0_0" weblogic.N
    odeManager -v
    <Jan 4, 2012 4:22:31 PM> <INFO> <Loading domains file: C:\oracle\MIDDLE~1\WLSERV
    ~1.3\common\NODEMA~1\nodemanager.domains>
    Jan 04, 2012 4:22:31 PM weblogic.nodemanager.server.NMServerConfig initDomainsMa
    p
    INFO: Loading domains file: C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1\nodema
    nager.domains
    <Jan 4, 2012 4:22:36 PM> <INFO> <Loading identity key store: FileName=C:/oracle/
    MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
    Jan 04, 2012 4:22:36 PM weblogic.nodemanager.server.SSLConfig loadKeyStoreConfig
    INFO: Loading identity key store: FileName=C:/oracle/MIDDLE~1/WLSERV~1.3/server\
    lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true
    <Jan 4, 2012 4:22:36 PM> <SEVERE> <Fatal error in node manager server>
    weblogic.nodemanager.common.ConfigException: Unknown key store identity alias or
    not a key entry alias: DemoIdentity
    at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.ja
    va:177)
    at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:102)
    at weblogic.nodemanager.server.NMServer.init(NMServer.java:186)
    at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:148)
    at weblogic.nodemanager.server.NMServer.main(NMServer.java:380)
    at weblogic.NodeManager.main(NodeManager.java:31)
    Jan 04, 2012 4:22:36 PM weblogic.nodemanager.server.NMServer main
    SEVERE: Fatal error in node manager server
    weblogic.nodemanager.common.ConfigException: Unknown key store identity alias or
    not a key entry alias: DemoIdentity
    at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.ja
    va:177)
    at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:102)
    at weblogic.nodemanager.server.NMServer.init(NMServer.java:186)
    at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:148)
    at weblogic.nodemanager.server.NMServer.main(NMServer.java:380)
    at weblogic.NodeManager.main(NodeManager.java:31)
    C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1>goto finish
    C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1>ENDLOCAL
    Correction would be how.

    Hi,
    You should check admin server's logs found under ${DOMAIN_HOME}/servers/AdminServer/logs.
    Regards,
    Mohab

  • Node manager not starting

    I have just installed a second CRS 5.0(2) server which I intend to add to the cluster, but I'm having a problem in that the Node Manager Service hangs on startup. The error I get is:
    Event ID:7022
    The CRS Node Manager Service Hung on starting.
    I can see from the Windows services that the service remains in a 'starting state'.
    I wanted to attach the MIVR logs to this post but I'm finding that there is no MIVR folder in c:/Program Files/wfavvid/log. Has the install completed successfully? I had no errors when installing the package.
    I've checked the binding order of the NIC cards and they are correct. I have also run the 'postinstall.exe' but still the same problem.
    On another note, how can you tell if the license provided (uploaded by someone else) includes HA software?
    Thanks

    Try checking out the MCVD logs and the application and system logs for any error with NIC or network connectivity.
    As for the second question the key you are looking for in the Lic is the entry.
    INCREMENT CRS_EXP_PRE_WARM_STBY cisco 5.0
    In case its already uploaded in CRS the Control Center >Display Licenses will show HA enabled.

  • Weblogic 9.2 Node Manager Starts, Managed Servers Do Not

    Hello,
    We just upgraded from 8.1.6 to 9.2.3 and I got the Node Manager and the admin console to start up.
    However, anytime I try to start a managed server, I get a failed error. I tried to create a new server and start it, and I get the same error. When I go to the server.out file, this is what I see in the file.
    See below.
    Any advice / help would be greatly appreciated. Thanks in advance!!!
    <Apr 20, 2011 2:34:17 PM> <Info> <NodeManager> <Starting WebLogic server with command line: D:\bea\jdk150_12\jre\bin\java -Dweblogic.Name=da_01 -Djava.security.policy=D:\bea\WEBLOG~2\server\lib\weblogic.policy -Dweblogic.management.server=http://10.32.12.77:7001 -Djava.library.path=D:\bea\WEBLOG~2\server\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\bea\WEBLOG~2\server\native\win\32;D:\bea\WEBLOG~2\server\bin;D:\bea\jdk150_12\jre\bin;D:\bea\jdk150_12\bin;D:\bea\WEBLOG~2\server\native\win\32\oci920_8;D:\Program Files\Documentum\Shared;D:\Documentum\product\5.3\bin;D:\Documentum\fulltext\fast40;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;D:\Documentum\product\5.3\fusion;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\ -Djava.class.path=.;D:\bea\patch_weblogic923\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\bea\jdk150_12\lib\tools.jar;D:\bea\WEBLOG~2\server\lib\weblogic_sp.jar;D:\bea\WEBLOG~2\server\lib\weblogic.jar;D:\bea\WEBLOG~2\server\lib\webservices.jar; -Dweblogic.system.BootIdentityFile=D:\bea_domains\cheniere_dctm\servers\da_01\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false weblogic.Server >
    <Apr 20, 2011 2:34:17 PM> <Info> <NodeManager> <Working directory is "D:\bea_domains\cheniere_dctm">
    <Apr 20, 2011 2:34:17 PM> <Info> <NodeManager> <Server output log file is "D:\bea_domains\cheniere_dctm\servers\da_01\logs\da_01.out">
    Usage: java [-options] class [args...]
    (to execute a class)
    or java [-options] -jar jarfile [args...]
    (to execute a jar file)
    where options include:
    -client     to select the "client" VM
    -server     to select the "server" VM
    -hotspot     is a synonym for the "client" VM [deprecated]
    The default VM is client.
    -cp <class search path of directories and zip/jar files>
    -classpath <class search path of directories and zip/jar files>
    A ; separated list of directories, JAR archives,
    and ZIP archives to search for class files.
    -D<name>=<value>
    set a system property
    -verbose[:class|gc|jni]
    enable verbose output
    -version print product version and exit
    -version:<value>
    require the specified version to run
    -showversion print product version and continue
    -jre-restrict-search | -jre-no-restrict-search
    include/exclude user private JREs in the version search
    -? -help print this help message
    -X print help on non-standard options
    -ea[:<packagename>...|:<classname>]
    -enableassertions[:<packagename>...|:<classname>]
    enable assertions
    -da[:<packagename>...|:<classname>]
    -disableassertions[:<packagename>...|:<classname>]
    disable assertions
    -esa | -enablesystemassertions
    enable system assertions
    -dsa | -disablesystemassertions
    disable system assertions
    -agentlib:<libname>[=<options>]
    load native agent library <libname>, e.g. -agentlib:hprof
    see also, -agentlib:jdwp=help and -agentlib:hprof=help
    -agentpath:<pathname>[=<options>]
    load native agent library by full pathname
    -javaagent:<jarpath>[=<options>]
    load Java programming language agent, see java.lang.instrument
    <Apr 20, 2011 2:34:18 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>

    Hi,
    Your JAVA_OPTIONS contains -Djava.library.path which has values with SPACES which is causing the issue.
    Example:
    -Djava.library.path=D:\bea\WEBLOG~2\server\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\bea\WEBLOG~2\server\native\win\32;D:\bea\WEBLOG~2\server\bin;D:\bea\jdk150_12\jre\bin;D:\bea\jdk150_12\bin;D:\bea\WEBLOG~2\server\native\win\32\oci920_8;D:\Program Files\Documentum\Shared;D:\Documentum\product\5.3\bin;D:\Documentum\fulltext\fast40;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;D:\Documentum\product\5.3\fusion;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\There are some paths included in the java.library.path which contains SPACES like C:\Program Files\Microsoft SQL Server\90\Tools\binn\
    It means there is a Space between words like 'C:\Program Files'
    Please add the complete java.library.path inside a Double quote so that the Spaces will not cause any issue...
    Example : with the below run you will get the same exception as you mentioned
    java   -Djava.library.path=C:\Program Files\Microsoft SQL Server\90\Tools\binn\    HelloWorldCorrect way as following:
    java   -Djava.library.path="C:\Program Files\Microsoft SQL Server\90\Tools\binn\"    HelloWorldQuotation mark added in the path which has spaces.
    Regards,
    Ravish Mody
    http://middlewaremagic.com/weblogic
    Come, Join Us and Experience The Magic…

  • What is the procedure of Call Manager upgrade from version CUCM 7.1 (MCS Server) to version CUCM 10.2 (on UCS server)

    Hi
    What is the procedure of Call Manager upgrade from version CUCM 7.1 (MCS Server)  to version CUCM 10.2 (on UCS server) , please let me know the steps to what would be the backup procedures and upgrades.
    Regards
    Gaurav

    I'd suggest reading this guide to make sure you have prepared your environment to support 10.x first. The link below also contains the upgrade path to 10.0(1).
    One of the ways you can do this is:
    1/ Apply refresh upgrade cop file on all servers in cluster.
    2/ Upgrade the cluster to 8.6(2). Take a backup of the cluster.
    3/ Build a cluster of 8.6(2) servers on VMs, and assign them the same hostnames and IP address as the hardware cluster. (You may need to keep these on a separate network until switching off the hardware machines)
    4/ Restore the backup taken from the hardware cluster on to the VM cluster.
    5/ Upgrade VM cluster to 10.0(1).
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100_chapter_010.html#CUCM_RF_UA60AFAB_00

  • Solution Manager upgrade issue on Linux

    Hi Alll,
    Need your inputs/thoughts on this issue.
    We are planning for Solution Manager upgrade from 3.1 to 4.0 and for this the setup and plan is as below:
    The production data of the solution manager has been copied as a VMX FILE(VM Player) file on to a test server and we have plans to upgrade that and check and then upgrade on the production system.
    The test machine has got a different IP address and hostname. From the test machine when I start the sap instance its affecting the Production machine and dueto which the production will not work until I stop the SAP Instance on the test machine.
    It cannot be a IP conflict or hostname conflict as we have them differently on the test machine. But still there is an issue. The IT dept says the issue is with the starting up of the instance and we dont know where to see what exactly is the problem.
    I am new to upgradation stuffs, this is my 1st assignment and I am not sure from where to start!!
    Can anyone of you tell me where to check for the details?
    SOLMAN is installed on a unix machine with oracle 9.2 and we are planning to upgrade it to SOLMAN 7.0
    any suggestions on where to look out for the possible issue?

    Hi,
    I did this a lot and know the side effects a little.
    My recipe:
    1. Start the copy without network and manage it from the VMWare Console. Change the IP address and make sure all references to the hostname (DNS and /etc/hosts) point to the new one. I hope you're working consistently with hostnames and no IP addresses.
    2. Configure the firewall (iptables) on the copied system to block all requests from and to the original production server. If there is any communication with other SAP servers (like monitoring agents, SLD, or others) block this too!
    3. Re-enable the network in VMWare.
    Alternatively: Can't you simply put this in a VLAN or a real seperated network with just the server and a management workstation?
    Hope that helps..
    Nikolaus

  • Cisco Unified CCX Node Manager service terminated unexpectedly

    "Windows must now restart because the Cisco Unified CCX Node Manager service terminated unexpectedly."
    After I installed my CCX os and software. The os reminded me like above. I guessed I need to upgrade the patch of my OS. And I also installed McAfee ver 8.5i at my OS. But that doesn't work. I noticed that the status of cisco unified ccx node manager was starting.

    On a new install, this can occur if you start patching the OS before you get UCCX installed.  This is especially a problem in an HA environment.  Some of the patches set values to things they should not be if they are applied before the software is installed. 
    When installing UCCX on a new system, you should build the OS on the box (DO NOT PATCH at this time), Install the UCCX software and integrate with CCM, get your second server (if you are doing HA) on line with OS and UCCX and integrated.  Once all the above are done, then you can start installing OS patches and UCCX patches.
    You should NEVER start installing things like AV software before you have the system completely up and working.  If you do, and they cause issues, you cannot tell if it's a system issue, or something caused by your a/v software. 

  • 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

Maybe you are looking for

  • Help please can only print grey

    i am using a canon bjc80 which when i test print it prints all colours and black but when i print from pages or even word every thing is printed in grey i cannot find what i am doing wrong any help please thanks in advance

  • I can copy a URL, but cannot paste it in the body of an e-mail. Also doen't hypelink it. I do not have this problem using Internet Explorer..

    When I copy a URL and go to paste it in an e-mail, it won't paste. Some other box opens. I can paste the URL in the subject line, but doesn't hyperlink it. (blue) When using Internet Explorer, I don't have this problem. I'm new to FF with a new compu

  • Why not introduce a "but" condition?

    Hi, why not introduce a "but" condition into the Java language? Here's an example: if(earth.isUnderAttack()){ ���go to 10 }but if(earth.getAttack().getAttacker().equals("alien") && earth.getStatus().equals("nice place")){ ���go to 20 }else{ ���go to

  • Application Launch Failures

    Hello Everyone, When I try to launch certain applications, I get this error message: The application "(insert application name here)" could not be launched because of a shared library error: "<application><application><CarbonLib>" So far, I can't get

  • Nokia suite - restoring of contacts without phone

    I used to own a nokia N70 and still have backup files on my pc. Does anyone know a way of getting to the info on Nokia suite without having to connect a nokia phone. I have some phone numbers that i really need to get to. Perhaps a silly question but