Are you a member of the Splunk Community?
- Find Answers
- :
- Apps & Add-ons
- :
- All Apps and Add-ons
- :
- DB Connect 3.1.4 Error "unable_to_load_checkpoint"...
- 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
Version: DB Connect 3.1.4
Issue: DB Connections and DB Inputs created via GUI works fine with no issues.
When new connections and inputs are added via CLI, the checkpoint for new inputs are not created and results in error.
ERROR c.s.d.s.dbinput.task.DbInputCheckpointRepository - action=unable_to_load_checkpoint
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Can you please let us know, how you configured via CLI ? If you modified db_inputs.conf directly then it will not create checkpoint file automatically. When you create new input via GUI, it will create initial checkpoint file with value you provided during setup.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Can you please let us know, how you configured via CLI ? If you modified db_inputs.conf directly then it will not create checkpoint file automatically. When you create new input via GUI, it will create initial checkpoint file with value you provided during setup.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Modified db_inputs.conf directly.
And yes, that is exactly my question. Why is the checkpoint created when configured via GUI and why not when edited via CLI ?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When you create DB Input via GUI, it will hit DB Connect REST API (These are not publicly documented) which will create checkpoint file, however that is not the case when you modify config file directly.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is it possible to define the data input in the back-end including the checkpoint information?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can create checkpoint file manually but I'll not recommend it.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you saying that when creating new Data Inputs, I should define the configurations from the UI?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes use the GUI, there are REST APIs but those are not documented by Splunk so I'll not use those as well.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We did exactly that over the weekend (after finding out that the back-end config doesn't work) and the problem is the initial load from the DB, that in some cases took hours, and we need to do couple of hundreds of DBs soon.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That explains the issue. Thanks for the information.
Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform
Calling All Security Pros: Ready to Race Through Boston?
Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...
