# Pipeline on error: recurrent problem

**URL:** <https://discuss.elastic.co/t/pipeline-on-error-recurrent-problem/149406>\
**Category:** Logstash\
**Created:** [September 21, 2018, 7:16am UTC](https://discuss.elastic.co/t/pipeline-on-error-recurrent-problem/149406 "2018-09-21T07:16:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michel99\_7](https://avatars.discourse-cdn.com/v4/letter/m/97f17d/32.png) [@Michel99\_7](https://discuss.elastic.co/u/Michel99_7)\
**Post date:** [September 21, 2018, 7:16am UTC](https://discuss.elastic.co/t/pipeline-on-error-recurrent-problem/149406/1 "2018-09-21T07:16:39Z")

</div>

Hi all,

We are having an error when a pipeline is starting, The log provides the following error.  
Any hint about how to make a diagnosis and to solve the problem (file corruption?)

- OS: Red Hat Enterprise Linux Server release 7.3
- Logstash version: 6.3.0
- ES version: 6.3.2  
==========

2018-09-21 06:37:30,170 Ruby-0-Thread-21@[cpdlc]\>worker0: /usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:383 ERROR An exception occurred processing Appender plain\_console java.lang.NullPointerException  
at org.logstash.ext.JrubyTimestampExtLibrary$RubyTimestamp.ruby\_to\_iso8601(JrubyTimestampExtLibrary.java:112)  
at org.logstash.ext.JrubyTimestampExtLibrary$RubyTimestamp.ruby\_inspect(JrubyTimestampExtLibrary.java:106)  
at org.logstash.ext.JrubyTimestampExtLibrary$RubyTimestamp$INVOKER$i$0$0$ruby\_inspect.call(JrubyTimestampExtLibrary$RubyTimestamp$INVOKER$i$0$0$ruby\_inspect.gen)  
at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:318)  
at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:131)  
at org.jruby.RubyBasicObject.rbInspect(RubyBasicObject.java:1142)  
at org.jruby.RubyObject.inspect(RubyObject.java:530)  
at org.jruby.RubyHash$4.visit(RubyHash.java:801)  
at org.jruby.RubyHash$4.visit(RubyHash.java:796)  
at org.jruby.RubyHash.visitLimited(RubyHash.java:662)  
at org.jruby.RubyHash.visitAll(RubyHash.java:647)  
at org.jruby.RubyHash.inspectHash(RubyHash.java:791)  
at org.jruby.RubyHash.inspect(RubyHash.java:815)  
at org.jruby.RubyHash$INVOKER$i$0$0$inspect.call(RubyHash$INVOKER$i$0$0$inspect.gen)  
at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:318)  
at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:131)  
at org.jruby.RubyBasicObject.rbInspect(RubyBasicObject.java:1142)  
at org.jruby.RubyObject.inspect(RubyObject.java:530)  
at org.jruby.RubyHash$4.visit(RubyHash.java:801)  
at org.jruby.RubyHash$4.visit(RubyHash.java:796)  
at org.jruby.RubyHash.visitLimited(RubyHash.java:662)  
at org.jruby.RubyHash.visitAll(RubyHash.java:647)  
at org.jruby.RubyHash.inspectHash(RubyHash.java:791)  
at org.jruby.RubyHash.inspect(RubyHash.java:815)  
at org.jruby.RubyHash.to\_s(RubyHash.java:882)  
at org.jruby.RubyHash$INVOKER$i$0$0$to\_s.call(RubyHash$INVOKER$i$0$0$to\_s.gen)  
at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:318)  
at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:131)  
at org.jruby.RubyObject.toString(RubyObject.java:339)  
at java.lang.String.valueOf(String.java:2994)  
at java.lang.StringBuilder.append(StringBuilder.java:131)  
at org.logstash.log.StructuredMessage.getFormattedMessage(StructuredMessage.java:60)  
at org.apache.logging.log4j.core.pattern.MessagePatternConverter.format(MessagePatternConverter.java:141)  
at org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:38)  
at org.apache.logging.log4j.core.layout.PatternLayout$PatternSerializer.toSerializable(PatternLayout.java:333)  
at...

---

<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:** [October 19, 2018, 7:16am UTC](https://discuss.elastic.co/t/pipeline-on-error-recurrent-problem/149406/2 "2018-10-19T07:16:52Z")

</div>

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