This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject

NetWitness Community

  • Home
  • Products
    • NetWitness Platform
      • Advisories
      • Documentation
        • Platform Documentation
        • Known Issues
        • Security Fixes
        • Hardware Documentation
        • Threat Content
        • Unified Data Model
        • Videos
      • Downloads
      • Integrations
      • Knowledge Base
    • NetWitness Cloud SIEM
      • Advisories
      • Documentation
      • Knowledge Base
    • NetWitness Detect AI
      • Advisories
      • Documentation
      • Knowledge Base
    • NetWitness Investigator
    • NetWitness Orchestrator
      • Advisories
      • Documentation
      • Knowledge Base
      • Legacy NetWitness Orchestrator
        • Advisories
        • Documentation
  • Community
    • Blog
    • Discussions
    • Events
    • Idea Exchange
  • Support
    • Case Portal
      • Create New Case
      • View My Cases
      • View My Team's Cases
    • Community Support
      • Getting Started
      • News & Announcements
      • Community Support Forum
      • Community Support Articles
    • Product Life Cycle
    • Support Information
    • General Security Advisories
  • Training
    • Blog
    • Certification Program
    • Course Catalog
      • Netwitness XDR
      • EC-Council Training
    • New Product Readiness
    • On-Demand Subscriptions
    • Student Resources
    • Upcoming Events
    • Role-Based Training
  • Technology Partners
  • Trust Center
Sign InRegister Now
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
NetWitness Discussions
  • NetWitness Community
  • Discussions
  • Re: Problems with Windows event collection from Aggregators
  • Options
    • Subscribe to RSS Feed
    • Mark Topic as New
    • Mark Topic as Read
    • Float this Topic for Current User
    • Bookmark
    • Subscribe
    • Mute
    • Printer Friendly Page

Problems with Windows event collection from Aggregators

ShishirKumar1
ShishirKumar1 Beginner
Beginner
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2019-03-01 09:23 AM

Hi All,

 

I am currently trying to integrate windows aggregators in our environment. The problem that I am facing is related to the rolling of a channel for the windows logs. I have the following error in the logs:

Log for channel Security may have rolled over. Previous/Current record number: xxxx/xxxx. 

 

As per the RSA link, I have increased the maximum log storage size to 2 GB from 20 MB on the windows aggregator and also tried to change the polling duration.  However, this is still not fixing the issue.

 

I have been trying with different Poll interval / Poll duration and maximum events. Still, I keep getting the same rollover error. Is there a way to derive an optimum setting for polling interval/ poll duration and maximum events ? Thanks for the assistance in advance.

 

Current settings:

Poll duration: 50 seconds
Poll interval: 60 seconds
Maximum events: 200000 

  • Community Thread
  • Discussion
  • Forum Thread
  • NetWitness
  • netwitness-logs
  • NW
  • NWP
  • RSA NetWitness
  • RSA NetWitness Platform
  • windows event collection
  • windows legacy collector
0 Likes
Reply
  • All forum topics
  • Previous Topic
  • Next Topic
8 REPLIES 8

SravanKoneti1
SravanKoneti1 Beginner
Beginner
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2019-03-08 04:48 AM

Hi Shishir,

 

option1:

In windows side, You can try increasing max log size before overriding old events

 

option2:

In Netwitness side, Set Max collcetion on collector side and disable debug.

 

both option details are available in 000029686 - Windows legacy log collection warni... | RSA Link 

0 Likes
Reply

ShishirKumar1
ShishirKumar1 Beginner
Beginner
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2019-03-11 05:14 AM

Hi Sravan,

 

Thanks for the response. I have used the same link you suggested and increased the maximum log size as well as tried to even set poll interval as -1 and maximum number of logs as 0 (which means unlimited) however it still comes back with this error.

 

I am not sure what else needs to be done for this error to not appear. Any suggestions ?

0 Likes
Reply

SravanKoneti1
SravanKoneti1 Beginner
Beginner
In response to ShishirKumar1
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2019-03-12 10:31 AM

Hi Shishir,

 

Please run below command in Log Collector to see if any pending messages for collection.

rabbitmqctl list_queues -p logcollection consumers name messages

 

Looking at error, Security channel logs are rolling over. Do you think any busy security event id can be excluded in Windows side?

0 Likes
Reply

EricPartington
Employee EricPartington
Employee
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2019-03-13 09:51 AM

not to avoid the problem but could using the Endpoint windows agent help solve your logging problems and get logs out of the system without worrying about polling intervals and batches?

depending on your version of NW that might be a quicker solution

0 Likes
Reply

ShishirKumar1
ShishirKumar1 Beginner
Beginner
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2019-03-18 07:28 AM

Hi Eric,

 

We are on 10.6.5.1 and so the Endpoint windows agent cannot be use I suppose.

 

Sravan Koneti‌ - The queue shows zero 

 

1 rabbitmq.log 0
1 shovel.checkpoint 0
1 shovel.cmdscript 0
1 shovel.file 0
1 shovel.odbc 0
1 shovel.syslog 0
1 shovel.windows 0

 

But I am still getting the following errors:

[WindowsCollection] [warning]  [processing] [WorkUnit] [processing] Log for channel Security may have rolled over. Previous/Current record number: 34190835/125837258.

 

I am only collecting forwarded events and the current configuration is:

Polling Interval : 180 secs
Polling Duration: 120 seconds
Maximum event per poll: 200000

 

Any further suggestions to resolve this please?

0 Likes
Reply

david_waugh
david_waugh Beginner
Beginner
In response to ShishirKumar1
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2019-03-18 12:32 PM

Hi I would try lowering your polling interval even more, to say even 10 seconds or lower.

You want to get as many events as you can, so polling more frequently should help.

0 Likes
Reply

ShishirKumar1
ShishirKumar1 Beginner
Beginner
In response to david_waugh
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2019-03-19 03:31 AM

Hi David,

 

Okay I will try that.

 

But I had a question about the polling duration and polling interval, should the polling duration always be lesser than polling interval.

 

For example, if I try polling interval of 10 s, what would you suggest the polling duration to be ? 

0 Likes
Reply

david_waugh
david_waugh Beginner
Beginner
In response to ShishirKumar1
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2019-03-21 09:49 AM

Hi my understanding is:

Polling Interval - How often it will attempt to collect events

Polling Duration: - The maximum it can take to collect the events.

 

I think I am correct that if a polling interval hasnt finished then it wont start a new one.

 

eg

If you poll every 10 seconds and have a duration of 60 seconds, then the next poll will be at the minimum of (polling interval, polling duration)

0 Likes
Reply
Powered by Khoros
  • Blog
  • Events
  • Discussions
  • Idea Exchange
  • Knowledge Base
  • Case Portal
  • Community Support
  • Product Life Cycle
  • Support Information
  • About the Community
  • Terms & Conditions
  • Privacy Statement
  • Acceptable Use Policy
  • Employee Login
© 2022 RSA Security LLC or its affiliates. All rights reserved.