Splunk Search

When setting up a distribution search, why am I getting the following error when adding search or index peers?

enmanu
New Member

I encountered the following error while trying to save:

"The time difference / clock skew between this system and the intended peer at uri=https://:8089 was too big. Please bring system clocks into agreement. search_head_time=1537513347.801773 peer_time=1537517825.000000 skew_seconds=-4477.198227 addpeer_skew_limit=600 Skew limit from limits.conf, [search] stanza."

Can someone help please?

Tags (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Make sure all of your Splunk instances are on servers that run NTP. Splunk can't search properly if the system clocks are more than 10 minutes apart and yours are off by over an hour.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Make sure all of your Splunk instances are on servers that run NTP. Splunk can't search properly if the system clocks are more than 10 minutes apart and yours are off by over an hour.

---
If this reply helps you, Karma would be appreciated.
0 Karma

enmanu
New Member

Thank you Rich. I installed ntp on the vm and that fixed the error

0 Karma

richgalloway
SplunkTrust
SplunkTrust

@enmanu If your problem is resolved, please accept the answer to help future readers.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...

Announcing the Migration of the Splunk Add-on for Microsoft Azure Inputs to ...

Announcing the Migration of the Splunk Add-on for Microsoft Azure Inputs to Officially Supported Splunk ...

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI! Discover how Splunk’s agentic AI ...