Join the Conversation
- Find Answers
- :
- Using Splunk
- :
- Splunk Search
- :
- search peers sick
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi im having this issue :
The times on the system clocks for the machines running this search head and the intended search peer at uri=https://x.x.x.x:8089 differ from each other. You must make the times identical, so that time comparisons are valid across the deployment. skew_seconds=-247. The max tolerable skew may be configured in [search]:max_tolerable_skew in limits.conf on the search head. Last Connect Time:2019-06-29T01:03:17.000-04:00; Failed 1 out of 1 times.
What's the root issue of this?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This usually happens when your servers aren't connected to NTP server.
The server time of your search head and indexer starts to skew.
You can increase max_lorerable_skew in limits.conf OR manually run the below command on all your splunk servers.
sudo date -s "29 JUN 2019 08:55:00".
Adjust time/date according to your time.
The best option is still to connect to NTP server as with the time fix, eventually down the line your time will get skewed again and you will have to run the date command again manually.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This usually happens when your servers aren't connected to NTP server.
The server time of your search head and indexer starts to skew.
You can increase max_lorerable_skew in limits.conf OR manually run the below command on all your splunk servers.
sudo date -s "29 JUN 2019 08:55:00".
Adjust time/date according to your time.
The best option is still to connect to NTP server as with the time fix, eventually down the line your time will get skewed again and you will have to run the date command again manually.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, chin, this is Correct could you please change it to comment so I can approve it as the answer.
Also deleting and adding the peer again work sometimes.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@jadengoho ,
Are the search heads and indexers use same NTP servers? Worth to check the time on the hosts and make sure that they are ticking correctly
What goes around comes around. If it helps, hit it with Karma 🙂
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions
Splunk Community Badges!
[Puzzles] Solve, Learn, Repeat: Matching cron expressions
