All Apps and Add-ons
Highlighted

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

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?

Highlighted

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

Champion
0 Karma
Highlighted

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

Path Finder

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

0 Karma
Highlighted

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

Explorer

Same issue here at the moment.

0 Karma
Highlighted

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

Explorer

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

0 Karma
Speak Up for Splunk Careers!

We want to better understand the impact Splunk experience and expertise has has on individuals' careers, and help highlight the growing demand for Splunk skills.