IBM QRadar

IBM QRadar

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Autoupdate Log - remotenet.conf failed verification. Reverting to backup

    Posted Wed September 18, 2024 08:27 AM
    Edited by Ralph Belfiore Mon September 23, 2024 07:14 AM

    Hi community,

    So far the auto updates in the lab have worked wonderfully. Since the beginning of the week the updates in our lab end with an error regarding the remotenet.conf:
    /store/configservices/staging/globalconfig/remotenet.conf failed verification.  Reverting to backup.

    Here are some more details:

    In other QRadar environments the update of remotenet.conf seems to work without errors.
    Who else knows this or has an idea how to fix it? Maybe @IBM Support?

    Regards,

    Ralph



    ------------------------------
    Ralph Belfiore
    Managing Consultant | Senior SIEM Expert
    connecT SYSTEMHAUS AG
    Siegen
    ------------------------------



  • 2.  RE: Autoupdate Log - remotenet.conf failed verification. Reverting to backup

    Posted Thu September 26, 2024 10:23 AM

    Hi Ralph,

    What do the first few lines of the file look like compared to one which is working?

    Also have there been any changes made to the remotenet.conf?

    Thanks



    ------------------------------
    John Dawson
    Qradar Support Architect
    IBM
    ------------------------------



  • 3.  RE: Autoupdate Log - remotenet.conf failed verification. Reverting to backup

    Posted Thu September 26, 2024 12:07 PM

    Hi John,

    inbetween i can see this behavior in many deployments. Indeed there were in two cases changes in the remote network section related to the TrustedNetworks - Remote Network with individual entries. 

     This has always worked well so far and there have been no problems with updates to remotenet.conf..

    Regards,

    Ralph



    ------------------------------
    Ralph Belfiore
    Managing Consultant | Senior SIEM Expert
    connecT SYSTEMHAUS AG
    Siegen
    ------------------------------



  • 4.  RE: Autoupdate Log - remotenet.conf failed verification. Reverting to backup

    Posted Thu September 26, 2024 12:19 PM

    Hey Ralph,

    So are you seeing this on multiple deployments now?

    I would think there is something wrong in the /store/configservices/staging/globalconfig/remotenet.conf

    What do the first few lines of it look like?

    Thanks



    ------------------------------
    John Dawson
    Qradar Support Architect
    IBM
    ------------------------------



  • 5.  RE: Autoupdate Log - remotenet.conf failed verification. Reverting to backup

    Posted Fri September 27, 2024 04:49 AM

    Hi John,

    the first few lines look like this..

    Regards,

    Ralph



    ------------------------------
    Ralph Belfiore
    Managing Consultant | Senior SIEM Expert
    connecT SYSTEMHAUS AG
    Siegen
    ------------------------------



  • 6.  RE: Autoupdate Log - remotenet.conf failed verification. Reverting to backup

    Posted Fri September 27, 2024 12:00 PM

    Hey Ralph

    Looks like the /store/configservices/staging/globalconfig/remotenet.conf is corrupt

    Can you try the following

    Create backup folder on console: 

    # mkdir /store/ibmsupport

    # cp /store/configservices/staging/globalconfig/remotenet.conf /store/ibmsupport

    -Copy the file from templates folder:

    # cp /opt/qradar/conf/templates/remotenet.conf /store/configservices/staging/globalconfig/remotenet.conf

    Once copied then execute command below from CLI on console and check the issue:

    #/opt/qradar/bin/UpdateConfs.pl -d 4 -runall

    Thanks



    ------------------------------
    John Dawson
    Qradar Support Architect
    IBM
    ------------------------------



  • 7.  RE: Autoupdate Log - remotenet.conf failed verification. Reverting to backup

    Posted Mon September 30, 2024 04:08 AM

    Hi John,

    that's exactly how it works! Thanks to the workaround you described, i have already been able to solve this issue in two cases :)

    Regards,

    Ralph



    ------------------------------
    Ralph Belfiore
    Managing Consultant | Senior SIEM Expert
    connecT SYSTEMHAUS AG
    Siegen
    ------------------------------