# Error makes logstash to crash **URL:** \ **Category:** Logstash\ **Created:** [July 8, 2016, 8:10pm UTC](https://discuss.elastic.co/t/error-makes-logstash-to-crash/55094 "2016-07-08T20:10:18Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Adrian\_Gallego](https://avatars.discourse-cdn.com/v4/letter/a/f17d59/32.png) [@Adrian\_Gallego](https://discuss.elastic.co/u/Adrian_Gallego)\ **Post date:** [July 8, 2016, 8:10pm UTC](https://discuss.elastic.co/t/error-makes-logstash-to-crash/55094/1 "2016-07-08T20:10:19Z")
Hi, Currently I'm using logstash with sns output plugin to send alerts to Amazon SNS service. I have found that logstash is crashing with the following error Seahorse::Client::NetworkingError: execution expired call at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/aws-sdk-core-2.1.36/lib/seahorse/client/plugins/raise\_response\_errors.rb:15 call at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/aws-sdk-core-2.1.36/lib/aws-sdk-core/plugins/param\_converter.rb:20 call at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/aws-sdk-core-2.1.36/lib/seahorse/client/plugins/response\_target.rb:21 send\_request at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/aws-sdk-core-2.1.36/lib/seahorse/client/request.rb:70 publish at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/aws-sdk-core-2.1.36/lib/seahorse/client/base.rb:207 send\_sns\_message at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-output-sns-3.0.4/lib/logstash/outputs/sns.rb:101 register at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-output-sns-3.0.4/lib/logstash/outputs/sns.rb:64 call at org/jruby/RubyProc.java:281 encode at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-codec-plain-2.0.4/lib/logstash/codecs/plain.rb:43 receive at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-output-sns-3.0.4/lib/logstash/outputs/sns.rb:79 multi\_receive at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/outputs/base.rb:83 each at org/jruby/RubyArray.java:1613 multi\_receive at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/outputs/base.rb:83 worker\_multi\_receive at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/output\_delegator.rb:130 multi\_receive at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/output\_delegator.rb:114 output\_batch at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:301 each at org/jruby/RubyHash.java:1342 output\_batch at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:301 worker\_loop at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:232 start\_workers at /appl/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:201 Any help is appreciated thanks in advance ---
**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:** [July 10, 2016, 6:15am UTC](https://discuss.elastic.co/t/error-makes-logstash-to-crash/55094/2 "2016-07-10T06:15:46Z")
Providing the config would he a helpful thing to do 🙂 ---
**Author:** ![Adrian\_Gallego](https://avatars.discourse-cdn.com/v4/letter/a/f17d59/32.png) [@Adrian\_Gallego](https://discuss.elastic.co/u/Adrian_Gallego)\ **Post date:** [July 10, 2016, 8:05pm UTC](https://discuss.elastic.co/t/error-makes-logstash-to-crash/55094/3 "2016-07-10T20:05:44Z")
Hi Mark, Thanks for your time. I must tell you that I found the reason of the error. As the exception suggest the problem its related to network config. In my case, it was an intermittent error accessing the Amazon SNS servers. Regards ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:48am UTC](https://discuss.elastic.co/t/error-makes-logstash-to-crash/55094/4 "2017-07-06T04:48:44Z")