Dashboards & Visualizations

how to fix: Failed write of Log Event: {"text":"The requested URL was not found on this server.","code":404}

steveIMS
Engager

I have Java program accessing HTTPS the HEC with Token; I have tracing on for the SSL Handshake; it goes thru handshake,

*** ClientHello, TLSv1.2
*** ServerHello, TLSv1.2

when actual event is written, then get:

Failed write of Log Event: {"text":"The requested URL was not found on this server.","code":404}

Reply: {"text":"The requested URL was not found on this server.","code":404}
ErrorCode: 404
Failed write of Log Event: {"text":"The requested URL was not found on this server.","code":404}
OkHttp ConnectionPool, called close()
OkHttp ConnectionPool, called closeInternal(true)
OkHttp ConnectionPool, SEND TLSv1.2 ALERT: warning, description = close_notify
CipherBox: Using cipher AES/GCM/NoPadding from provider from init IBMJCE version 1.8
AESGCM encrypt: key=
0000: dc 8f 84 2a b6 a6 30 8d 18 d7 6c d0 e8 85 82 51 ......0...l....Q

So the HEC acknowledges both the client and itself, then fails. Anybody know what this issue would be? Thanks, Steve.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...