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!

Splunk Search APIを使えば調査過程が残せます

   このゲストブログは、JCOM株式会社の情報セキュリティ本部・専任部長である渡辺慎太郎氏によって執筆されました。 Note: This article is published in both Japanese ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...