# Logstash stuck at 'Fixnum is deprecated'

**URL:** <https://discuss.elastic.co/t/logstash-stuck-at-fixnum-is-deprecated/231164>\
**Category:** Logstash\
**Created:** [May 5, 2020, 1:36pm UTC](https://discuss.elastic.co/t/logstash-stuck-at-fixnum-is-deprecated/231164 "2020-05-05T13:36:11Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jaishree\_Pal](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@Jaishree\_Pal](https://discuss.elastic.co/u/Jaishree_Pal)\
**Post date:** [May 5, 2020, 1:36pm UTC](https://discuss.elastic.co/t/logstash-stuck-at-fixnum-is-deprecated/231164/1 "2020-05-05T13:36:11Z")

</div>

Hi all, I was trying to send data to elasticsearch using scheduler. I want it to run once a day and update new records. But it gets stuck everytime after these outputs.  
Please suggest any solution, thanks.

```auto
Sending Logstash logs to C:/logstash-7.6.1/logs which is now configured via log4j2.properties
[2020-05-05T18:46:10,371][WARN][logstash.config.source.multilocal] Ignoring the 'pipelines.yml' file because modules or command line options are specified
[2020-05-05T18:46:10,646][INFO][logstash.runner] Starting Logstash {"logstash.version"=>"7.6.1"}
[2020-05-05T18:46:18,642][INFO][org.reflections.Reflections] Reflections took 207 ms to scan 1 urls, producing 20 keys and 40 values
[2020-05-05T18:46:21,535][INFO][logstash.outputs.elasticsearch][main] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[http://<ip address>:9200/]}}
[2020-05-05T18:46:22,149][WARN][logstash.outputs.elasticsearch][main] Restored connection to ES instance {:url=>"http://<ip address>:9200/"}
[2020-05-05T18:46:22,297][INFO][logstash.outputs.elasticsearch][main] ES Output version determined {:es_version=>7}
[2020-05-05T18:46:22,335][WARN][logstash.outputs.elasticsearch][main] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document _type {:es_version=>7}
[2020-05-05T18:46:22,455][INFO][logstash.outputs.elasticsearch][main] New Elasticsearch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>["//<ip address>:9200"]}
[2020-05-05T18:46:22,634][INFO][logstash.outputs.elasticsearch][main] Using default mapping template
[2020-05-05T18:46:22,721][WARN][org.logstash.instrument.metrics.gauge.LazyDelegatingGauge][main] A gauge metric of an unknown type (org.jruby.specialized.RubyArrayOneObject) has been create for key: cluster_uuids. This may result in invalid serialization. It is recommended to log an issue to the responsible developer/development team.
[2020-05-05T18:46:22,739][INFO][logstash.javapipeline][main] Starting pipeline {:pipeline_id=>"main", "pipeline.workers"=>4, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>50, "pipeline.max_inflight"=>500, "pipeline.sources"=>["C:/logstash-7.6.1/log_server_db.conf"], :thread=>"#<Thread:0x4fd171c5 run>"}
[2020-05-05T18:46:22,808][INFO][logstash.outputs.elasticsearch][main] Attempting to install template {:manage_template=>{"index_patterns"=>"logstash-*", "version"=>60001, "settings"=>{"index.refresh_interval"=>"5s", "number_of_shards"=>1}, "mappings"=>{"dynamic_templates"=>[{"message_field"=>{"path_match"=>"message", "match_mapping_type"=>"string", "mapping"=>{"type"=>"text", "norms"=>false}}}, {"string_fields"=>{"match"=>"*", "match_mapping_type"=>"string", "mapping"=>{"type"=>"text", "norms"=>false, "fields"=>{"keyword"=>{"type"=>"keyword", "ignore_above"=>256}}}}}], "properties"=>{"@timestamp"=>{"type"=>"date"}, "@version"=>{"type"=>"keyword"}, "geoip"=>{"dynamic"=>true, "properties"=>{"ip"=>{"type"=>"ip"}, "location"=>{"type"=>"geo_point"}, "latitude"=>{"type"=>"half_float"}, "longitude"=>{"type"=>"half_float"}}}}}}}
[2020-05-05T18:46:25,628][INFO][logstash.javapipeline][main] Pipeline started {"pipeline.id"=>"main"}
[2020-05-05T18:46:25,764][INFO][logstash.agent] Pipelines running {:count=>1, :running_pipelines=>[:main], :non_running_pipelines=>[]}
[2020-05-05T18:46:27,199][INFO][logstash.agent] Successfully started Logstash API endpoint {:port=>9601}
C:/logstash-7.6.1/vendor/bundle/jruby/2.5.0/gems/rufus-scheduler-3.0.9/lib/rufus/scheduler/cronline.rb:77: warning: constant ::Fixnum is deprecated

```

I've already tried adding the timezone and using different versions of logstash but atill not getting rid of it.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 5, 2020, 9:38pm UTC](https://discuss.elastic.co/t/logstash-stuck-at-fixnum-is-deprecated/231164/2 "2020-05-05T21:38:57Z")

</div>

What do you mean by stuck? It looks like that shouldn't stop the processing of the data.

---

<div class="post-metadata">

**Author:** ![Jaishree\_Pal](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@Jaishree\_Pal](https://discuss.elastic.co/u/Jaishree_Pal)\
**Post date:** [May 6, 2020, 4:28am UTC](https://discuss.elastic.co/t/logstash-stuck-at-fixnum-is-deprecated/231164/3 "2020-05-06T04:28:52Z")

</div>

Means nothing is happening after that, importing of data remains pending.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 6, 2020, 7:07am UTC](https://discuss.elastic.co/t/logstash-stuck-at-fixnum-is-deprecated/231164/4 "2020-05-06T07:07:38Z")

</div>

OK, well what does your config look like?

---

<div class="post-metadata">

**Author:** ![Jaishree\_Pal](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@Jaishree\_Pal](https://discuss.elastic.co/u/Jaishree_Pal)\
**Post date:** [May 6, 2020, 7:14am UTC](https://discuss.elastic.co/t/logstash-stuck-at-fixnum-is-deprecated/231164/5 "2020-05-06T07:14:47Z")

</div>

This is how the config file looks like

```auto
input {
  jdbc {
    jdbc_driver_library => "C:\Users\jpal1\Downloads\mysql-connector-java-5.1.39.jar"
    jdbc_connection_string => "jdbc:mysql://localhost:3306/nsat_regression"
    jdbc_driver_class => "com.mysql.jdbc.Driver"
    jdbc_user => "root"
    jdbc_password => "root123"
    tracking_column => "id"
    use_column_value =>true
    statement => "SELECT * FROM tab4 WHERE id > :sql_last_value"
    schedule => "0 0 * * *"
    clean_run => true
  }
}

output {
  elasticsearch {
    hosts => ["<ip_address>:9200"]
    index => "log_server_db"
  }

  stdout
  {
    codec => json
  }
}

```

I'm using logstash 7.6.1, though the issue persists on 7.6.2 also.

---

<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:** [May 6, 2020, 8:38am UTC](https://discuss.elastic.co/t/logstash-stuck-at-fixnum-is-deprecated/231164/6 "2020-05-06T08:38:54Z")

</div>

@Jaishree_Pal - `schedule` is set to `0 0 * * *` which means the statement will run every day at 12:00AM. Logstash is probably not "stuck" - it is just waiting for the timing to execute the SQL statement.

---

<div class="post-metadata">

**Author:** ![Jaishree\_Pal](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@Jaishree\_Pal](https://discuss.elastic.co/u/Jaishree_Pal)\
**Post date:** [May 6, 2020, 8:04pm UTC](https://discuss.elastic.co/t/logstash-stuck-at-fixnum-is-deprecated/231164/7 "2020-05-06T20:04:04Z")

</div>

Thanks a lot @ropc ! You're right, it wasn't stuck, it was waiting for that time.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 3, 2020, 8:04pm UTC](https://discuss.elastic.co/t/logstash-stuck-at-fixnum-is-deprecated/231164/8 "2020-06-03T20:04:16Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
