splunk sdk : com.splunk.HttpException: HTTP 401 -- call not properly authenticated
See original GitHub issueI am trying to search the string from splunk , i was getting 401 error. StringBuilder searchString = new StringBuilder();
searchString.append("search").append(" XXX");
Service service = Service.connect(splunkArgs); Job job = service.getJobs().create(searchString.toString());
Issue Analytics
- State:
- Created 10 years ago
- Comments:26 (9 by maintainers)
Top Results From Across the Web
Why am I getting "Status 401 call not properly aut...
Hello I am using Splunk java sdk 1.4.0.0 when I execute this query : String QUERY = "search \"ab_exper\" index=my_apache | rex.
Read more >Splunk throwing HTTP 401 not authorized error when ...
After looking into the code for a few minutes, I think this is an issue in the NiFi processor. The first time the...
Read more >Solved: Cron scheduling strategy with GetSplunk fails on s. ...
HttpException: HTTP 401 -- call not properly authenticated at com.splunk.HttpException.create(HttpException.java:84) ~[na:na] at com.splunk.
Read more >Connect to Splunk with Python - hackerrolls
This post will cover the following: Connecting to Splunk with the Python SDK, executing a search and receiving the results Connecting to ...
Read more >Failed opening seach.log - splunk-enterprise
HttpException: HTTP 401 -- call not properly authenticated at com.splunk.HttpException.create(HttpException.java:84) at com.splunk.DBXService.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
HTTP 401 – {“messages”:[{“type”:“WARN”,“text”:“call not properly authenticated”}]}
We are seeing this error intermittently. From what I can tell, it happens after the request is submitted to the server. I even suspect the query itself is being executed. I suspect this because our Splunk team is reporting more concurrent sessions for our user than is possible for us.
Is it possible the error messes is incorrect? I ask this because we get this once in a while from a process that is running and submits the request in the same way every time.
I was getting the same error. I have fixed this problem by upgrading splunk-sdk-java library from 1.3.2 to 1.6.5 (latest one). Now it’s working fine.