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!

Splunk Observability Cloud | Customer Survey!

If you use Splunk Observability Cloud, we invite you to share your valuable insights with us through a brief ...

Happy CX Day, Splunk Community!

Happy CX Day, Splunk Community! CX stands for Customer Experience, and today, October 3rd, is CX Day — a ...

.conf23 | Get Your Cybersecurity Defense Analyst Certification in Vegas

We’re excited to announce a new Splunk certification exam being released at .conf23! If you’re going to Las ...