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!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...