# Jquery error meaning

**URL:** <https://discuss.elastic.co/t/jquery-error-meaning/97109>\
**Category:** Logstash\
**Created:** [August 15, 2017, 1:59pm UTC](https://discuss.elastic.co/t/jquery-error-meaning/97109 "2017-08-15T13:59:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GambitK](https://avatars.discourse-cdn.com/v4/letter/g/47e85d/32.png) [@GambitK](https://discuss.elastic.co/u/GambitK)\
**Post date:** [August 15, 2017, 1:59pm UTC](https://discuss.elastic.co/t/jquery-error-meaning/97109/1 "2017-08-15T13:59:21Z")

</div>

I'm moving a logstash config from one server to another and jquery is throwing an error that I don't know what it means:

```
[2017-08-15T09:57:12,980][INFO][logstash.pipeline] Starting pipeline {"id"=>"main", "pipeline.workers"=>5, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>5, "pipeline.max_inflight"=>625}
[2017-08-15T09:57:13,209][INFO][logstash.pipeline] Pipeline main started
[2017-08-15T09:57:13,273][INFO][logstash.agent] Successfully started Logstash API endpoint {:port=>9600}
[2017-08-15T09:58:00,559][WARN][logstash.inputs.jdbc] Failed test_connection.
{ 271316 rufus-scheduler intercepted an error:
  271316 job:
  271316 Rufus::Scheduler::CronJob "*/2 * * * *" {}
  271316 error:
  271316 271316
  271316 NoMethodError
  271316 undefined method `close_jdbc_connection' for #<Sequel::JDBC::Database:0x2516acc>
  271316 /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-jdbc-4.2.0/lib/logstash/plugin_mixins/jdbc.rb:174:in `open_jdbc_connection'
  271316 /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-jdbc-4.2.0/lib/logstash/plugin_mixins/jdbc.rb:217:in `execute_statement'
  271316 /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-jdbc-4.2.0/lib/logstash/inputs/jdbc.rb:272:in `execute_query'
  271316 /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-jdbc-4.2.0/lib/logstash/inputs/jdbc.rb:250:in `run'
  271316 org/jruby/RubyProc.java:281:in `call'
  271316 /opt/logstash/vendor/bundle/jruby/1.9/gems/rufus-scheduler-3.0.9/lib/rufus/scheduler/jobs.rb:234:in `do_call'
  271316 /opt/logstash/vendor/bundle/jruby/1.9/gems/rufus-scheduler-3.0.9/lib/rufus/scheduler/jobs.rb:258:in `do_trigger'
  271316 /opt/logstash/vendor/bundle/jruby/1.9/gems/rufus-scheduler-3.0.9/lib/rufus/scheduler/jobs.rb:300:in `start_work_thread'
  271316 org/jruby/RubyProc.java:281:in `call'
  271316 /opt/logstash/vendor/bundle/jruby/1.9/gems/rufus-scheduler-3.0.9/lib/rufus/scheduler/jobs.rb:299:in `start_work_thread'
  271316 org/jruby/RubyKernel.java:1479:in `loop'
  271316 /opt/logstash/vendor/bundle/jruby/1.9/gems/rufus-scheduler-3.0.9/lib/rufus/scheduler/jobs.rb:289:in `start_work_thread'
  271316 tz:
  271316 ENV['TZ']:
  271316 Time.now: 2017-08-15 09:58:00 -0400
  271316 scheduler:
  271316 object_id: 199242
  271316 opts:
  271316 {:max_work_threads=>1}
  271316 frequency: 0.3
  271316 scheduler_lock: #<Rufus::Scheduler::NullLock:0x703d4056>
  271316 trigger_lock: #<Rufus::Scheduler::NullLock:0x2d13231b>
  271316 uptime: 47.349 (47s348)
  271316 down?: false
  271316 threads: 2
  271316 thread: #<Thread:0x5710235c>
  271316 thread_key: rufus_scheduler_199242
  271316 work_threads: 1
  271316 active: 1
  271316 vacant: 0
  271316 max_work_threads: 1
  271316 mutexes: {}
  271316 jobs: 1
  271316 at_jobs: 0
  271316 in_jobs: 0
  271316 every_jobs: 0
  271316 interval_jobs: 0
  271316 cron_jobs: 1
  271316 running_jobs: 1
  271316 work_queue: 0
} 271316 .

```

How can I find out what's the problem? This configuration is working when I'm connecting to my Test database but when I change it to another DB it gives me this error.

---

<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:** [September 12, 2017, 2:00pm UTC](https://discuss.elastic.co/t/jquery-error-meaning/97109/2 "2017-09-12T14:00:00Z")

</div>

Closed on September 12, 2017, 2:00pm UTC

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