Monitoring Splunk

WARN LMTracker - skipping directive -> Any idea?

lpolo
Motivator

Any idea about this event in splunkd.log?

02-17-2014 17:36:12.384 +0000 WARN  LMTracker - skipping directive, reason='found invalid directive cmd='D_set_active_group' args=[Enterprise,,] argsize=3'

Thanks,
Lp

Tags (1)

jreuter_splunk
Splunk Employee
Splunk Employee

Are you connecting a <= 5.x license slave to a >= 6.x master? It would appear that this message is to be expected in this scenario due to a differing argument count/differing capabilities. This can be safely ignored, or the logging level of the LMTracker category can be set above WARN to avoid logging the condition.

BenjaminWyatt
Communicator

Bump. Has anybody ever figured this out?

0 Karma

mikesaia
Path Finder

Having the same error here. Did you find any info on this?

Get Updates on the Splunk Community!

Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...

The Transformative Power of AI and ML in Enhancing Observability   In the realm of IT operations, the ...

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...