# Logstash Configuarion file issue

**URL:** https://discuss.elastic.co/t/logstash-configuarion-file-issue/218346
**Category:** Logstash
**Created:** [February 7, 2020, 12:23pm UTC](https://discuss.elastic.co/t/logstash-configuarion-file-issue/218346 "2020-02-07T12:23:40Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![ropc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ropc/32/47022_2.png) [@ropc](https://discuss.elastic.co/u/ropc)
#### Post date: [February 7, 2020, 2:38pm UTC](https://discuss.elastic.co/t/logstash-configuarion-file-issue/218346/4 "2020-02-07T14:38:03Z")

</div>

@Syed.Ubaid -

1. It seems that you are facing the same issue as what was reported in this [Discuss topic](https://discuss.elastic.co/t/logstash-error-no-implicit-conversion-of-integer-into-string/192901).

[The last run metadata file](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-jdbc.html#_state) will store the `sql_last_value` and It is updated accordingly after subsequent queries are run.

It seems that Logstash cannot parse the value stored in this file. It could be because you have been running Logstash with different SQL statements and the `sql_last_value` type keeps on changing?

1. What you could try:

- use the [clean\_run](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-jdbc.html#plugins-inputs-jdbc-clean_run) option to ignore the previous state. or,
- use `use_column_value` option along with the `tracking_column` option. or,
- delete the [last run metadata file](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-jdbc.html#plugins-inputs-jdbc-last_run_metadata_path) but I believe this would only be a temporary solution.

I hope that helps.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-configuarion-file-issue/218346)._