Error with net/smtp in Logstash (Docker)

Hi everyone,
im having some issue with docker and logstash. I have the following error:

2023-10-03 14:46:24 warning: thread "[main]-pipeline-manager" terminated with exception (report_on_exception is true):
2023-10-03 14:46:24 LoadError: no such file to load -- net/smtp
2023-10-03 14:46:24            require at org/jruby/RubyKernel.java:1057
2023-10-03 14:46:24      <module:Mail> at /usr/share/logstash/vendor/bundle/jruby/3.1.0/gems/mail-2.6.6/lib/mail.rb:9
2023-10-03 14:46:24             <main> at /usr/share/logstash/vendor/bundle/jruby/3.1.0/gems/mail-2.6.6/lib/mail.rb:3
2023-10-03 14:46:24            require at org/jruby/RubyKernel.java:1057
2023-10-03 14:46:24           register at /usr/share/logstash/vendor/bundle/jruby/3.1.0/gems/logstash-input-imap-3.2.0/lib/logstash/inputs/imap.rb:89
2023-10-03 14:46:24   register_plugins at /usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:237
2023-10-03 14:46:24               each at org/jruby/RubyArray.java:1987
2023-10-03 14:46:24   register_plugins at /usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:236
2023-10-03 14:46:24       start_inputs at /usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:395
2023-10-03 14:46:24      start_workers at /usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:320
2023-10-03 14:46:24                run at /usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:194
2023-10-03 14:46:24              start at /usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:146

It looks like i don't have the file net/smtp, i have checked from the files and i cant find it.
Im using logstash on docker with WSL2.

Thank you in advance :slight_smile:

This is a bug on version 8.10.X, it is being tracked here.

You should use rollback to version 8.9.

1 Like

Hi @leandrojmp, thank you for your help. Now im facing a different problem, i'm getting the following error:

2023-10-05 10:07:27 Oct 05, 2023 8:07:27 AM jnr.netdb.NativeProtocolsDB load
2023-10-05 10:07:27 WARNING: Failed to load native protocols db
2023-10-05 10:07:27 java.lang.RuntimeException: getprotobyname_r failed
2023-10-05 10:07:27     at jnr.netdb.NativeProtocolsDB$LinuxNativeProtocolsDB.getProtocolByName(NativeProtocolsDB.java:180)
2023-10-05 10:07:27     at jnr.netdb.NativeProtocolsDB.load(NativeProtocolsDB.java:80)
2023-10-05 10:07:27     at jnr.netdb.NativeProtocolsDB.access$000(NativeProtocolsDB.java:40)
2023-10-05 10:07:27     at jnr.netdb.NativeProtocolsDB$SingletonHolder.<clinit>(NativeProtocolsDB.java:47)
2023-10-05 10:07:27     at jnr.netdb.NativeProtocolsDB.getInstance(NativeProtocolsDB.java:43)
2023-10-05 10:07:27     at jnr.netdb.Protocol$ProtocolDBSingletonHolder.load(Protocol.java:107)
2023-10-05 10:07:27     at jnr.netdb.Protocol$ProtocolDBSingletonHolder.<clinit>(Protocol.java:103)
2023-10-05 10:07:27     at jnr.netdb.Protocol.getProtocolDB(Protocol.java:96)
2023-10-05 10:07:27     at jnr.netdb.Protocol.getProtocolByNumber(Protocol.java:59)
2023-10-05 10:07:27     at org.jruby.ext.socket.Addrinfo.<init>(Addrinfo.java:847)
2023-10-05 10:07:27     at org.jruby.ext.socket.SocketUtils$2.addrinfo(SocketUtils.java:256)
2023-10-05 10:07:27     at org.jruby.ext.socket.SocketUtils.buildAddrinfoList(SocketUtils.java:322)
2023-10-05 10:07:27     at org.jruby.ext.socket.SocketUtils.getaddrinfoList(SocketUtils.java:232)
2023-10-05 10:07:27     at org.jruby.ext.socket.Addrinfo.getaddrinfo(Addrinfo.java:322)
2023-10-05 10:07:27     at org.jruby.ext.socket.Addrinfo$INVOKER$s$0$0$getaddrinfo.call(Addrinfo$INVOKER$s$0$0$getaddrinfo.gen)
2023-10-05 10:07:27     at org.jruby.internal.runtime.methods.JavaMethod$JavaMethodN.call(JavaMethod.java:846)
2023-10-05 10:07:27     at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:329)
2023-10-05 10:07:27     at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:87)
2023-10-05 10:07:27     at org.jruby.ir.instructions.CallBase.interpret(CallBase.java:549)

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