All Apps and Add-ons

After upgrading Splunk DB Connect, why am I getting error "invalid literal for float()" when I create a db input?

dbrancaglion
Explorer

I can see the results without problem in the query page, but if I create a db input, Splunk shows me the following error in /opt/splunk/var/log/splunk/dbx2.log :

[ERROR] [modular_input_event_writer.py], line 102: action=converting_incoming_data_in_csv_to_event_stream_failed input_mode=batch dbinput="mi_input://rec_limit_exporter" error="invalid literal for float(): 1471289753,172"

This error happened after I upgraded my Splunk DB Connect. Can I roll this back?

I tried to reinstall all Splunk DB Connect 2, but with no success.

Someone have a similar problem?

dlisicre
Explorer

As indicated in mhornste thread, changing output_timestamp_format = dd-MM-yyyy HH:mm:ss to Epoch managed to solve this issue for me.
Kind regards,
David Lisin

0 Karma

dlisicre
Explorer

Same issue here at the moment.

0 Karma

mhornste
Path Finder

I have the same problem. I'm not using SSL and enable_query_wrapping = 0/ 1 don't work (both of them).

0 Karma

jcoates_splunk
Splunk Employee
Splunk Employee
0 Karma
Get Updates on the Splunk Community!

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...