Installation

LMStackMgr - resetting slave warnings for master slave list

kevintelford
Path Finder

I was looking at my splunkd.log file and noticed that this line was being written to the log file once per second. What is the cause of this? I assume it's not normal behavior. Also every few seconds I see a message about "LMSlaveInfo - Detected that masterTimeFromSlave < lastRolloverTime, meaning that the master has already rolled over. Ignoring slave persisted usage." Splunk4Life!

gekoner
Communicator

This error gets logged in a distributed environment when the license.slave server tries to contact his license.master and the license info has already rolled over. Or on the license.master if the time on the license.master server is set behind the license.slave, as it should manage the roll over time for itself and the slave(s).

See http://docs.splunk.com/Documentation/Splunk/latest/Admin/Groups,stacks,pools,andotherterminology

Typical issues are timezone issues [license.slave(s) not being on the same time as license.master] or communication or the clocks not being set correctly.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...