Logstash version (e.g. bin/logstash --version) - 7.10.2
Logstash installation source (e.g. built from source, with a package manager: DEB/RPM, expanded from tar or zip archive, docker) - installed with apt-get
How is Logstash being run (e.g. as a service/service manager: systemd, upstart, etc. Via command line, docker/kubernetes) - via command line
How was the Logstash Plugin installed - command line
JVM (e.g. java -version): 1.8.0_312
If the affected version of Logstash is 7.9 (or earlier), or if it is NOT using the bundled JDK or using the 'no-jdk' version in 7.10 (or higher), please provide the following information:
JVM version (java -version)
JVM installation source (e.g. from the Operating System's package manager, from source, etc).
Value of the JAVA_HOME environment variable if set.
OS version (uname -a if on a Unix-like system): Linux ip-10-210-30-158 5.11.0-1028-aws #31~20.04.1-Ubuntu SMP Fri Jan 14 14:37:50 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Description of the problem including expected versus actual behavior:
Logstash just stops consuming SQS messages on the configured queue. There are no errors in the logs, it consumes whatever is on the queue when it starts up and then messages just pile up on the queue after that until i restart logstash.
Steps to reproduce:
Please include a minimal but complete recreation of the problem,
including (e.g.) pipeline definition(s), settings, locale, etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.
This is my dead-simple input:
input {
sqs {
access_key_id => "xxxxxxxxxxxxx"
secret_access_key => "yyyyyyyyyyyyyy"
queue => "places"
region => "us-west-2"
}
}
Logstash information:
Please include the following information:
bin/logstash --version) - 7.10.2JVM (e.g.
java -version): 1.8.0_312If the affected version of Logstash is 7.9 (or earlier), or if it is NOT using the bundled JDK or using the 'no-jdk' version in 7.10 (or higher), please provide the following information:
java -version)JAVA_HOMEenvironment variable if set.OS version (
uname -aif on a Unix-like system): Linux ip-10-210-30-158 5.11.0-1028-aws #31~20.04.1-Ubuntu SMP Fri Jan 14 14:37:50 UTC 2022 x86_64 x86_64 x86_64 GNU/LinuxDescription of the problem including expected versus actual behavior: Logstash just stops consuming SQS messages on the configured queue. There are no errors in the logs, it consumes whatever is on the queue when it starts up and then messages just pile up on the queue after that until i restart logstash.
Steps to reproduce:
Please include a minimal but complete recreation of the problem, including (e.g.) pipeline definition(s), settings, locale, etc. The easier you make for us to reproduce it, the more likely that somebody will take the time to look at it.
This is my dead-simple input: input { sqs { access_key_id => "xxxxxxxxxxxxx" secret_access_key => "yyyyyyyyyyyyyy" queue => "places" region => "us-west-2" } }
Provide logs (if relevant):