DB Connect 3.1.4 Error "unable_to_load_checkpoint" when configured via CLI

[rajanala]

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

[harsmarvania57 · Accepted solution]

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.

[rajanala]

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 ?

[harsmarvania57]

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.

[danielbb]

@harsmarvania57 

Is it possible to define the data input in the back-end including the checkpoint information?

[harsmarvania57]

You can create checkpoint file manually but I'll not recommend it.

[danielbb]

@harsmarvania57

Are you saying that when creating new Data Inputs, I should define the configurations from the UI?

[harsmarvania57]

Yes use the GUI, there are REST APIs but those are not documented by Splunk so I'll not use those as well.

[danielbb]

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.

[rajanala]

That explains the issue. Thanks for the information.