Frequent agent alert issue - [genmsga.c:8438]: Forwarding message/action response to OVO message . (OpC30-36)led due to server failure

Hi, anyone experience the below agent alert issue with 2 gw and 2 dps setup ? 

All of sudden started getting multiple false agent alert's even though the agent is running fine, up on investigation found the below error in System.txt 

opcmsga (30699/140123769714496): [genmsga.c:8438]: Forwarding message/action response to OVO message
. (OpC30-36)led due to server failure : (bbc-73) An exception occured which has prevented the receipt of an HTTP response from the peer application.

OBM Version: 2022.05

OBM Agent Version 12.20

  • Suggested Answer

    0  

    Hello,

    You can try:

    OPC_RPC_ONLY to TRUE
    Set the OPC_RPC_ONLY variable to TRUE by running the following command:
    ovconfchg -ns eaagt -set OPC_RPC_ONLY TRUE

    docs.microfocus.com/.../12.24
    DISABLE_EXPECT_100 bbc.http
    The Expect HTTP request header implies expectations to be fulfilled by server for client to continue forward the request. In scenarios, where client plans to send large content in message body, it initially sends request to server with expectation of interim "100 continue" response from the server. This header is useful in environments where there are potential of large request size in the payloads, wherein server can choose to reject request based on the size mentioned in the content-length header. 100 continue status code implies that server intends to receive the request body before acting upon the same and sending the final response.

    Setting DISABLE_EXPECT_100 to TRUE helps in avoiding network round trip time caused with 100-continue responses.

    It's good to set this value to TRUE in the management server as well as agent.

    For management server:
    ovconfchg -ns bbc.http -set DISABLE_EXPECT_100 TRUE

    ovconfchg -ovrg server -ns bbc.http -set DISABLE_EXPECT_100 TRUE

    Thanks.

  • Verified Answer

    +1 in reply to   

    Dear 

    Thanks for the quick update, 

    As i verified, EXPECT_100 is already set to DISABLE on both client and Mgmt server, 

    DISABLE_EXPECT_100=true

    Also as I checked RPC in client side which is as below: 

    OPC_MONA_CONF_RPC_ONLY=TRUE
    OPC_RPC_ONLY=TRUE

    From Mgmt server side its as below: 

    OPC_MONA_CONF_RPC_ONLY=FALSE
    OPC_RPC_ONLY=TRUE

  • Verified Answer

    +1 in reply to 

    As you have mentioned its seems to be issue with the Packets only, because we could see the buffering alert volume is less during the non-business hours and high volume of alerts in the business hours. So suspect some thing related to network.

    [bbc.cb]
    LOCAL_CONTROL_ONLY=true
    LOCAL_INFO_ONLY=true
    REQUEST_TIMEOUT=1
    RESTRICT_REG=true
    SSL_REQUIRED=true

    [bbc.fx]
    FX_MAX_RETRIES=3

    [bbc.http]
    LOCAL_INFO_ONLY=false
    LOG_SERVER_ACCESS=false
    MAX_CONNECTIONS=0
    RESPONSE_TIMEOUT=100000
    SERVER_PORT=0

    [bbc.http.ext.opcmsga]
    AUTO_CONNECTION_CLOSE_INTERVAL=60

    [bbc.snf]
    MAX_FILE_BUFFER_SIZE=0

    OPC_BUFLIMIT_SEVERITY=major
    OPC_BUFLIMIT_SIZE=10000
    OPC_HBP_INTERVAL_ON_AGENT=300
    OPC_INSTALLATION_TIME=Mon Apr 29 08:51:24 +03 2024
    OPC_INSTALLED_VERSION=12.24.008
    OPC_INT_MSG_FLT=TRUE
    OPC_IP_ADDRESS=******************
    OPC_LE_CMD_WAIT_TIME=500
    OPC_MONA_CONF_RPC_ONLY=TRUE
    OPC_NODENAME=*************
    OPC_NODE_CHARSET=utf8
    OPC_PUB_DIR_NOT_WW=true
    OPC_RPC_ONLY=TRUE

    ======================================================

    Below is the System.txt error which is logged exactly upon agent moves to buffer state: 

    0: INF: Wed May 1 11:55:07 2024: opcmsga (1440323/140067547158336): Exception:: Server config info XML file is empty [ file will be ignored ] or not present itself.
    0: INF: Wed May 1 11:55:07 2024: opcmsga (1440323/140067547158336): Server config info xml file is empty or not present, skipping deployment integrity check
    0: WRN: Wed May 1 11:59:03 2024: ovbbccb (1440127/139904966231808): (bbc-90) The incoming HTTPS client connection from host 172.24.12.183 failed due to the SSL error:
    1: ERR: Wed May 1 11:59:03 2024: ovbbccb (1440127/139904966231808): (xpl-333) recv() on '[DPS:IP]:21195' failed.
    2: ERR: Wed May 1 11:59:03 2024: ovbbccb (1440127/139904966231808): (RTL-104) Connection reset by peer
    0: WRN: Wed May 1 11:59:03 2024: ovbbccb (1440127/139904970442496): (bbc-90) The incoming HTTPS client connection from host 172.24.12.183 failed due to the SSL error:
    1: ERR: Wed May 1 11:59:03 2024: ovbbccb (1440127/139904970442496): (xpl-333) recv() on '[DPS:IP]:23106' failed.
    2: ERR: Wed May 1 11:59:03 2024: ovbbccb (1440127/139904970442496): (RTL-104) Connection reset by peer

    =======================================================================

  • 0   in reply to 

    Hello,

    Thanks for letting me know.  The RTL-104 is your usual "104 Connection reset by peer" error.  If it works most of the time, then yes, it may be a networking issue of some sort.  I really don't know and cannot comment any further...

    Best of luck.