WebSphere Application Server & Liberty

 View Only
  • 1.  stop Node - SOAP request could not be authenticated

    Posted Wed March 09, 2022 07:41 AM
    Hi, can anyone help with this error please.

    On WAS 9.0.5.8 Trad. 
    Cell
       - Virtual Machine 1: Dmgr & Node Agent 1.
       - Virtual Machine 2: Node Agent 2.

    I have this problem on Virtual Machine 2 only. If I stop the Node Agent 2 there's a SOAP error (SOAP request could not be authenticated), and the node agent is not stopped. I can kill it, and do a syncnode, that works fine. No errors on start up.

    I've increased the log levels on the node agent and Dmgr, but nothing is obvious. Certs are in date. Nodes are in sync.
    Apart from this, the node agent seems to be working correctly; reporting to the Admin console, I can stop & start application servers.

    But I cannot see what's causing the SOAP authentication error?


    STOPPING node agent gets error
    ----------------------------------
    Pre Prod:devpnfvm002582:wasadmin:/usr/WebSphere1/AppServer/profiles/AppServer/bin>./stopNode.sh

    ADMU0116I: Tool information is being logged in file
               /usr/WebSphere1/AppServer/profiles/AppServer/logs/nodeagent/stopServer.log
    ADMU0128I: Starting tool with the AppServer profile
    ADMU3100I: Reading configuration for server: nodeagent
    ADMU0111E: Program exiting with error: javax.management.JMRuntimeException:
               SOAP request could not be authenticated.
    ADMU1211I: To obtain a full trace of the failure, use the -trace option.
    ADMU0211I: Error details may be seen in the file:
               /usr/WebSphere1/AppServer/profiles/AppServer/logs/nodeagent/stopServer.log

    Any advise and guidance would be appreciated.

    Many thanks,
    Mark.​

    ------------------------------
    Mark Shaw
    ------------------------------


  • 2.  RE: stop Node - SOAP request could not be authenticated

    IBM Champion
    Posted Wed March 09, 2022 09:39 AM
    Hello Mark,

    You need to edit soap.client.propos in the Virtual Machine 2.

    You need a USER with at least "Operation" role, usually "primary admin user" is used or user with "Administrator" role. You need the PASSWORD to this USER

    NOTE: Check if you have one user configured in Virtual machine 1.

    Virtual machine 1.
    ------------------
    Go to the WAS_HOME/profiles/DMGR_PROFILE/properties and check in the soap.client.props file

    com.ibm.SOAP.securityEnabled=true
    com.ibm.SOAP.loginUserid=VM1_USER
    com.ibm.SOAP.loginPassword=VM1_PASSWORD

    If you haven't nothing in DMGR_PROFILE check in WAS_HOME/profiles/NODE_PROFILE/properties the same properties.

    Virtual machine 2.
    ------------------
    If you have a VM1_USER and VM1_PASSWORD from Virtuak machine 1. copy the same in WAS_HOME/profiles/NODE_PROFILE/properties/soap.client.props. if not use the USER and PASSWORD with at least "Operation" role.


    When you have edit the file test restarting the node from admin console.


    Hope this helps. Tell us if you need more support.

    Regards

    ------------------------------
    Gabriel Aberasturi
    Versia tecnologias emergentes
    ------------------------------



  • 3.  RE: stop Node - SOAP request could not be authenticated

    Posted Wed March 09, 2022 11:51 AM
    Hi Gabriel,

    That worked great.   The solution was to add the following to the node agent soap.client.props, as they were missing.
    com.ibm.SOAP.loginUserid= aaaa
    com.ibm.SOAP.loginPassword= bbbb

    Now on the same node2 I face another issue.

    I'm having problems with about half of the application servers not starting on VM2/Node2. About half ~20 JVMs, start fine, and show running in the Admin console. 
    I've increased the log level. The ones that won't start, appear not to be joining the HA.


    [09/03/22 16:22:13:445 GMT] 00000046 MbuRmmAdapter I   DCSV1032I: DCS Stack DefaultCoreGroup at Member N02: Connected a defined member cell001\vm2\nodeagent.
    [09/03/22 16:22:13:504 GMT] 00000046 MbuRmmAdapter I   DCSV1032I: DCS Stack DefaultCoreGroup at Member N02: Connected a defined member cell001\cellManager\dmgr.
    [09/03/22 16:22:13:728 GMT] 00000046 MbuRmmAdapter I   DCSV1032I: DCS Stack DefaultCoreGroup at Member N02: Connected a defined member cell001\vm1\nodeagent.
    [09/03/22 16:22:23:869 GMT] 00000059 Peer          I   ODCF8531I: Added neighbor ip=10.123.45.67 udp=10311 tcp=10301 ID=zxcvbnm version=0;cellName=cell001;bridgedCells=[];structuredGateway=true;properties={inOdc=1, memberName=cell001\vm2\nodeagent, MEMBER_STARTUP_TIME=1646841637875, epoch=1646841639251, MEMBER_VERSION=4}, neighbor set size is now 1.
    [09/03/22 16:22:23:870 GMT] 00000059 Peer          I   ODCF8517I: The unstructured overlay is operational, with security: 10.123.45.67  udp_port=31327  tcp_port=31328.
    [09/03/22 16:22:27:103 GMT] 0000005c NGUtil$Server I   ASND0002I: Detected server nodeagent started on node vm2
    [09/03/22 16:23:11:547 GMT] 00000055 RLSHAGroupCal W   CWRLS0030W: Waiting for HAManager to activate recovery processing for local WebSphere server.
    For more information about how to troubleshoot startup, see https://www.ibm.com/support/knowledgecenter/en/SSAW57_9.0.0/com.ibm.websphere.nd.multiplatform.doc/ae/ttrb_server_startup.html


    I have read the suggested 'Troubleshooting server start caused by the CWRLS0030W message' however I do not see the the subsequent error 'DCSV8030I'.

    Thanks,
    Mark.​

    ------------------------------
    Mark Shaw
    ------------------------------



  • 4.  RE: stop Node - SOAP request could not be authenticated

    IBM Champion
    Posted Wed March 09, 2022 01:39 PM
    Hi Mark,

    I'm glad the problem is solved!

    To avoid mixing problems please open another thread.

    Thanks in advanced.

    Regards

    ------------------------------
    Gabriel Aberasturi
    Versia tecnologias emergentes
    ------------------------------



  • 5.  RE: stop Node - SOAP request could not be authenticated

    Posted Thu February 08, 2024 02:28 AM

    Hai Gabriel,

               

                 i try above solution but below issue Please help me. 

                    ODCF8531I: Added neighbor ip=10.3.77.53 udp=11008 tcp=11009 ID=67c172380b80791cbf804cc409a265b1ca0e1b55 version=0;cellName=icdCell01;bridgedCells=[];structuredGateway=false;properties={inOdc=1, epoch=1705644924277, MEMBER_STARTUP_TIME=1705644922496, memberName=icdCell01\icdNode01\icdSrv02, MEMBER_VERSION=4}, neighbor set size is now 3.
    [1/19/24 9:15:29:458 EAT] 00000041 MbuRmmAdapter I   DCSV1032I: DCS Stack DefaultCoreGroup at Member icdCell01\icdNode01\icdSrv01: Connected a defined member icdCell01\icdNode01\icdSrv02.
    [1/19/24 9:15:32:670 EAT] 000001d1 SystemOut     O 
    [1/19/24 9:15:35:493 EAT] 00000041 VSyncAlgo1    I   DCSV2004I: DCS Stack DefaultCoreGroup at Member icdCell01\icdNode01\icdSrv01: View synchronization completed successfully. The View Identifier is (124:0.icdCell01\icdCellManager01\dmgr). The internal details are None.
    [1/19/24 9:15:35:525 EAT] 00000040 CoordinatorIm I   HMGR0228I: The Coordinator is not an Active Coordinator for core group DefaultCoreGroup. The active coordinator set is [icdCell01\icdCellManager01\dmgr].
    [1/19/24 9:15:35:526 EAT] 00000040 CoordinatorIm I   HMGR0218I: A new core group view has been installed. The core group is DefaultCoreGroup. The view identifier is (125:0.icdCell01\icdCellManager01\dmgr). The number of members in the new view is 4.
    [1/19/24 9:15:35:527 EAT] 00000040 CoreGroupMemb I   DCSV8050I: DCS Stack DefaultCoreGroup at Member icdCell01\icdNode01\icdSrv01: New view installed, identifier (125:0.icdCell01\icdCellManager01\dmgr), view size is 4 (AV=4, CD=4, CN=4, DF=10)
    [1/19/24 9:15:35:534 EAT] 00000050 ViewReceiver  I   DCSV1033I: DCS Stack DefaultCoreGroup at Member icdCell01\icdNode01\icdSrv01: Confirmed all new view members in view identifier (125:0.icdCell01\icdCellManager01\dmgr). View channel type is View|Ptp.

    Thanks,

    Korlapati Mohan Krishna.                           



    ------------------------------
    korlapati mohan krishna
    ------------------------------