How to resolve this error: HTTP 401 -- call not properly authenticated dbconnect?

Path Finder

Hello hello,

We have the Splunk db connect app working in our environment, but suddenly stops working

And I can see this log:

2022-11-21 23:22:39.050 -0500 [dw-203047 - PUT /api/inputs/server_average_latency] ERROR c.s.d.m.repository.DefaultConfigurationRepository - action=failed_to_get_the_conf reason=HTTP 401 -- call not properly authenticated com.splunk.HttpException: HTTP 401 -- call not properly authenticated at com.splunk.HttpException.create( at com.splunk.DBXService.sendImpl( at com.splunk.DBXService.send( at com.splunk.HttpService.get( at com.splunk.Entity.refresh( at com.splunk.Entity.refresh( at com.splunk.Resource.validate( at com.splunk.Entity.validate( at com.splunk.Entity.getContent( at com.splunk.Entity.size( at java.util.HashMap.putMapEntries( at java.util.HashMap.<init>( at com.splunk.dbx.model.repository.JsonMapperEntityResolver.apply( at com.splunk.dbx.model.repository.JsonMapperEntityResolver.apply( at com.splunk.dbx.model.repository.DefaultConfigurationRepository.get( at com.splunk.dbx.server.dbinput.task.DbInputTaskLoader.load( at com.splunk.dbx.server.api.service.conf.impl.InputServiceImpl.update( at com.splunk.dbx.server.api.service.conf.impl.InputServiceImpl.update( at com.splunk.dbx.server.api.resource.InputResource.updateInput( at sun.reflect.GeneratedMethodAccessor482.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke( CONTINUES


I am not going to add the whole log because is huge.


We have a cluster and our dbconnect is install at the search heads and all the inputs are configured at the Heavy Forwarder.


Is you have any idea what I can check to see what is the issue, please let me know.


The environment is over linux.


Thanks in advance.

Best Regards.

Labels (1)
Tags (1)
0 Karma

Path Finder

This was something odd.

After a lot of troubleshooting I decided to restart the Splunk service of the Heavy Forwarder, where the dbconnect was configured.


And after that I started receiving the logs and the issue not there anymore.

Get Updates on the Splunk Community!

Build Scalable Security While Moving to Cloud - Guide From Clayton Homes

 Clayton Homes faced the increased challenge of strengthening their security posture as they went through ...

Mission Control | Explore the latest release of Splunk Mission Control (2.3)

We’re happy to announce the release of Mission Control 2.3 which includes several new and exciting features ...

Cloud Platform | Migrating your Splunk Cloud deployment to Python 3.7

Python 2.7, the last release of Python 2, reached End of Life back on January 1, 2020. As part of our larger ...