Only one Elasticsearch jdbc input is executing
up vote
0
down vote
favorite
I have two jdbc inputs in my logstash.conf file. The file validates and starts fine and I can see the pipeline running.
The second query shows up in the log and processes fine, but the first jdbc input query never even tries to run (at least there are no references to it in the log).
I use an identical template for all of the jdbc settings, so I know that is correct. The only difference is the name of the statement_filepath, but both of those files execute fine in Toad and return data.
input {
jdbc {
jdbc_driver_library => "/iappl/confluent-4.1.1/share/java/kafka-connect-jdbc/ojdbc7.jar"
jdbc_driver_class => "Java::oracle.jdbc.driver.OracleDriver"
jdbc_connection_string => "..."
jdbc_user => "..."
jdbc_password => "..."
schedule => "*/30 * * * * * "
statement_filepath => "/iappl/log_conf/current/configs/scania/sql/V02_INBOUNDLOAD.sql"
type => "V02_INBOUND"
}
jdbc {
jdbc_driver_library => "/iappl/confluent-4.1.1/share/java/kafka-connect-jdbc/ojdbc7.jar"
jdbc_driver_class => "Java::oracle.jdbc.driver.OracleDriver"
jdbc_connection_string => "..."
jdbc_user => "..."
jdbc_password => "..."
schedule => "*/30 * * * * * "
statement_filepath => "/iappl/log_conf/current/configs/scania/sql/V02_OUTBOUNDLOAD.sql"
type => "V02_OUTBOUND"
}
}
In the log, the second query shows up on schedule, but the first one never does, and there is no mention of it failing in the log.
Ideas?
elasticsearch logstash asked 2 days ago
Frank Blau
13
add a comment |
up vote
0
down vote
favorite
I have two jdbc inputs in my logstash.conf file. The file validates and starts fine and I can see the pipeline running.
The second query shows up in the log and processes fine, but the first jdbc input query never even tries to run (at least there are no references to it in the log).
I use an identical template for all of the jdbc settings, so I know that is correct. The only difference is the name of the statement_filepath, but both of those files execute fine in Toad and return data.
input {
jdbc {
jdbc_driver_library => "/iappl/confluent-4.1.1/share/java/kafka-connect-jdbc/ojdbc7.jar"
jdbc_driver_class => "Java::oracle.jdbc.driver.OracleDriver"
jdbc_connection_string => "..."
jdbc_user => "..."
jdbc_password => "..."
schedule => "*/30 * * * * * "
statement_filepath => "/iappl/log_conf/current/configs/scania/sql/V02_INBOUNDLOAD.sql"
type => "V02_INBOUND"
}
jdbc {
jdbc_driver_library => "/iappl/confluent-4.1.1/share/java/kafka-connect-jdbc/ojdbc7.jar"
jdbc_driver_class => "Java::oracle.jdbc.driver.OracleDriver"
jdbc_connection_string => "..."
jdbc_user => "..."
jdbc_password => "..."
schedule => "*/30 * * * * * "
statement_filepath => "/iappl/log_conf/current/configs/scania/sql/V02_OUTBOUNDLOAD.sql"
type => "V02_OUTBOUND"
}
}
In the log, the second query shows up on schedule, but the first one never does, and there is no mention of it failing in the log.
Ideas?
elasticsearch logstash asked 2 days ago
Frank Blau
13
can you start logstash with--debugand see if anything weird pops up?
– Val
2 days ago
It's running as a service, so it's practically an act of god to get it to run otherwise... is there some way to get that debug done with the service without needing root access?
– Frank Blau
2 days ago
You could update the logging level of thejdbcinput via the API without restarting Logstash
– Val
2 days ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have two jdbc inputs in my logstash.conf file. The file validates and starts fine and I can see the pipeline running.
The second query shows up in the log and processes fine, but the first jdbc input query never even tries to run (at least there are no references to it in the log).
I use an identical template for all of the jdbc settings, so I know that is correct. The only difference is the name of the statement_filepath, but both of those files execute fine in Toad and return data.
input {
jdbc {
jdbc_driver_library => "/iappl/confluent-4.1.1/share/java/kafka-connect-jdbc/ojdbc7.jar"
jdbc_driver_class => "Java::oracle.jdbc.driver.OracleDriver"
jdbc_connection_string => "..."
jdbc_user => "..."
jdbc_password => "..."
schedule => "*/30 * * * * * "
statement_filepath => "/iappl/log_conf/current/configs/scania/sql/V02_INBOUNDLOAD.sql"
type => "V02_INBOUND"
}
jdbc {
jdbc_driver_library => "/iappl/confluent-4.1.1/share/java/kafka-connect-jdbc/ojdbc7.jar"
jdbc_driver_class => "Java::oracle.jdbc.driver.OracleDriver"
jdbc_connection_string => "..."
jdbc_user => "..."
jdbc_password => "..."
schedule => "*/30 * * * * * "
statement_filepath => "/iappl/log_conf/current/configs/scania/sql/V02_OUTBOUNDLOAD.sql"
type => "V02_OUTBOUND"
}
}
In the log, the second query shows up on schedule, but the first one never does, and there is no mention of it failing in the log.
Ideas?
elasticsearch logstash asked 2 days ago
Frank Blau
13
I have two jdbc inputs in my logstash.conf file. The file validates and starts fine and I can see the pipeline running.
The second query shows up in the log and processes fine, but the first jdbc input query never even tries to run (at least there are no references to it in the log).
I use an identical template for all of the jdbc settings, so I know that is correct. The only difference is the name of the statement_filepath, but both of those files execute fine in Toad and return data.
input {
jdbc {
jdbc_driver_library => "/iappl/confluent-4.1.1/share/java/kafka-connect-jdbc/ojdbc7.jar"
jdbc_driver_class => "Java::oracle.jdbc.driver.OracleDriver"
jdbc_connection_string => "..."
jdbc_user => "..."
jdbc_password => "..."
schedule => "*/30 * * * * * "
statement_filepath => "/iappl/log_conf/current/configs/scania/sql/V02_INBOUNDLOAD.sql"
type => "V02_INBOUND"
}
jdbc {
jdbc_driver_library => "/iappl/confluent-4.1.1/share/java/kafka-connect-jdbc/ojdbc7.jar"
jdbc_driver_class => "Java::oracle.jdbc.driver.OracleDriver"
jdbc_connection_string => "..."
jdbc_user => "..."
jdbc_password => "..."
schedule => "*/30 * * * * * "
statement_filepath => "/iappl/log_conf/current/configs/scania/sql/V02_OUTBOUNDLOAD.sql"
type => "V02_OUTBOUND"
}
}
In the log, the second query shows up on schedule, but the first one never does, and there is no mention of it failing in the log.
Ideas?
elasticsearch logstash elasticsearch logstash asked 2 days ago
Frank Blau
13
asked 2 days ago
Frank Blau
13
asked 2 days ago
Frank Blau
13
asked 2 days ago
Frank Blau
13
asked 2 days ago
Frank Blau
13
13
can you start logstash with--debugand see if anything weird pops up?
– Val
2 days ago
It's running as a service, so it's practically an act of god to get it to run otherwise... is there some way to get that debug done with the service without needing root access?
– Frank Blau
2 days ago
You could update the logging level of thejdbcinput via the API without restarting Logstash
– Val
2 days ago
add a comment |
can you start logstash with--debugand see if anything weird pops up?
– Val
2 days ago
It's running as a service, so it's practically an act of god to get it to run otherwise... is there some way to get that debug done with the service without needing root access?
– Frank Blau
2 days ago
You could update the logging level of thejdbcinput via the API without restarting Logstash
– Val
2 days ago
can you start logstash with
--debug and see if anything weird pops up?– Val
2 days ago
can you start logstash with
--debug and see if anything weird pops up?– Val
2 days ago
It's running as a service, so it's practically an act of god to get it to run otherwise... is there some way to get that debug done with the service without needing root access?
– Frank Blau
2 days ago
It's running as a service, so it's practically an act of god to get it to run otherwise... is there some way to get that debug done with the service without needing root access?
– Frank Blau
2 days ago
You could update the logging level of the
jdbc input via the API without restarting Logstash– Val
2 days ago
You could update the logging level of the
jdbc input via the API without restarting Logstash– Val
2 days ago
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53409875%2fonly-one-elasticsearch-jdbc-input-is-executing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
can you start logstash with
--debugand see if anything weird pops up?– Val
2 days ago
It's running as a service, so it's practically an act of god to get it to run otherwise... is there some way to get that debug done with the service without needing root access?
– Frank Blau
2 days ago
You could update the logging level of the
jdbcinput via the API without restarting Logstash– Val
2 days ago