Trustwave and Cybereason Merge to Form Global MDR Powerhouse for Unparalleled Cybersecurity Value. Learn More

Trustwave and Cybereason Merge to Form Global MDR Powerhouse for Unparalleled Cybersecurity Value. Learn More

Services
Managed Detection & Response

Eliminate active threats with 24/7 threat detection, investigation, and response.

Co-Managed SOC (SIEM)

Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.

Advisory & Diagnostics

Advance your cybersecurity program and get expert guidance where you need it most.

Penetration Testing

Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.

Database Security

Prevent unauthorized access and exceed compliance requirements.

Email Security

Stop email threats others miss and secure your organization against the #1 ransomware attack vector.

Digital Forensics & Incident Response

Prepare for the inevitable with 24/7 global breach response in-region and available on-site.

Firewall & Technology Management

Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.

Solutions
BY TOPIC
Microsoft Security
Unlock the full power of Microsoft Security
Offensive Security
Solutions to maximize your security ROI
Rapidly Secure New Environments
Security for rapid response situations
Securing the Cloud
Safely navigate and stay protected
Securing the IoT Landscape
Test, monitor and secure network objects
Why Trustwave
About Us
Awards and Accolades
Trustwave SpiderLabs Team
Trustwave Fusion Security Operations Platform
Trustwave Security Colony
Partners
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Trustwave PartnerOne Program
Join forces with Trustwave to protect against the most advance cybersecurity threats
Loading...
Loading...

HOWTO: Recovering from corrupt or failed DBLog file issues

Expand / Collapse


This article applies to:

  • Trustwave MailMarshal (SEG)

Problem:

  • New messages do not appear in Mail History
  • Database logging files (dblog) could not be transferred to Array Manager
  • MM Controller log entries like: Event - Database Logging Error: DBLog file <Server1.672ce4220000.dblog> could not be transferred to Array Manager after 30 attempts
  • MM Array Manager log entries like: Event - Failed to process log file 

Background:

MailMarshal Mail History is generated from the SQL database. 

Mail processing information is transferred from each processing server to the Array Manager for insertion to the database.

This transfer is in the form of "DBLog" files.

If the files are corrupt or cannot be transferred, Mail History will not include the related information.

Procedure:

To troubleshoot DBLog issues:

  1. Check the MMController text log on each processing server. You should see lines similar to Server1.672ce4090000.dblog (338 bytes) sent to manager
  2. If you see lines with Database Logging Error, this indicates a problem sending the files.
  3. Also check for the presence of a large number of files in the DBLog folder on the processing node, by default C:\Trustwave\Secure Email Gateway\Logging\DBLog.
    • Then check the MMArrayManager log file for Failed to process log file entries - this would indicate that the Controller can connect.
  4. If there are no errors in the MMArrayManager log, verify the connectivity between the processing node and Array Manager on the required ports.
  5. If there are errors in the Array Manager log (other than database connection failures), look for issues at the node.
    • The most likely issues are disk full condition, or a third party anti-malware product interfering with the file creation.
Before proceeding, identify and correct the issue that is causing file corruption. Check the Windows Event Logs and other debugging tools.

To resume logging:

Transfer of each file is attempted 30 times, so the presence of a large number of corrupt files can delay Mail History for a significant time.
  1. Move all .dblog files from the DbLog folder to a temporary location.
  2. Check that newly generated files are being processed quickly and Mail History updates have resumed.
  3. You can attempt to recover history by moving small numbers of files from the temporary location back to the DBLog folder. Copy the latest files first (files from after the time you corrected any issue.) Check that the files are actually processed before copying additional files.
  4. If the original issue was due to lost connectivity, you can also try copying files from the processing server BadLog subfolder back to the DBLog folder.
Any files that are actually corrupt cannot be recovered. Message History covered in these files will be lost.


    To contact Trustwave 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
    .