LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
View All Services
Solutions
BY INDUSTRY
BY REGULATION
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
We reduce cyber risk and fortify organizations
Awards and Accolades
Recognition by analysts and media outlets
LevelBlue SpiderLabs
Global researchers, ethical hackers, and responders
LevelBlue Security Operations Platforms
Unprecedented security visibility and control
Security Colony
Access to cybersecurity threat protection resources
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Register
Login
Resources
BLOGS
UPCOMING
MEDIA & ASSETS
NOTICES
HELP
Loading...
Loading...

LevelBlue Knowledge Base

Home » Knowledgebase » Legacy Products » Secure Web Gateway » Networking » INFO: Scanning Server fails to Commit / stuck in Committing...

INFO: Scanning Server fails to Commit / stuck in Committing Status

Expand / Collapse
Show/Hide Article Tools


  • Description
    A repetitive "Commiting..." issue occurs when a scanning server is being managed by more than one Policy Server.

  • Symptoms
    The symptoms are seen from the following window of the Policy Server management module under Settings -> Devices -> Scanner's IP -> Committing Status and Device configuration revision:
    1. The Committing Status will be set to "Commitiing..."
    2. The Scanning Server's "Device configuration revision" will change.
    3. The Scanning Server's Commiting Status will then start the commit process again (Step 1-3).
      These 3 steps will constantly happen in a loop.

    This loop shows that the scanner is being controlled by two (or more) separate Policy Servers.
    The "Device Configuration Revision" will match the configuration revision number of the first Policy Server and then the other Policy Server/s.


  • Cause
    The cause of this issue is that two or more Policy Servers have been configured to manage the affected scanning server/s.

  • Solution
    There are 2 optional solutions for this issue:

    Solution 1
    Remove the affected scanning servers from the configuration of one of the controlling Policy Servers, leaving only one Policy Server to manage the scanning server/s.

    Solution 2
    Switch off one of the Policy Servers, or disconnect from the LAN, and then re-configure outside of the environment.

  • Software Version
    8.3.x

    • This article applies to:
    NG 1000
    NG 5000
    NG 8000
    This article was previously published as:
    Finjan KB 1363

    To contact LevelBlue about this article or to request support:

    Rate this Article:
         

    Add Your Comments


    Comment submission is disabled for anonymous users.
    Please send feedback to Trustwave Technical Support or the Webmaster    .


    Execution: 0.062. 8 queries. Compression Disabled.
    Powered by InstantKB.NET