It seems graylog2 is not honoring that "transport_email_use_ssl to false"
I edited the /etc/graylog2.conf and restarted graylog2 and i still get the same error. I added the -f argument to the startup script but its still giving me the same error. is there a way to query the options that the server is currently seing/using. -Miguel On Wednesday, April 23, 2014 1:28:43 PM UTC-4, lennart wrote: > > Seems like you have enabled SSL for the email transport but port 25 > doesn't sound like you actually want to use SSL. > > Set transport_email_use_ssl to false in your graylog2.conf > > On Wed, Apr 23, 2014 at 7:21 PM, Miguel Cruz <[email protected]<javascript:>> > wrote: > > Here is output from graylog2.log file: > > > > [root@awslxgrayuted01 log]# tailf graylog2.log > > > > at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:484) > > > > at > > > com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:863) > > > > > at > > > com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1188) > > > > > > at > > > com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1215) > > > > > > at > > > com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1199) > > > > > > at > > > com.sun.mail.util.SocketFetcher.configureSSLSocket(SocketFetcher.java:549) > > > > at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:354) > > > > at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:211) > > > > at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1927) > > > > ... 58 more > > > > 2014-04-23 13:16:07,468 ERROR: > > org.graylog2.rest.resources.streams.alerts.StreamAlertResource - Sending > > dummy alert failed: {} > > > > org.apache.commons.mail.EmailException: Sending the email to the > following > > server failed : localhost:25 > > > > at org.apache.commons.mail.Email.sendMimeMessage(Email.java:1410) > > > > at org.apache.commons.mail.Email.send(Email.java:1437) > > > > at org.graylog2.alerts.AlertSender.sendEmail(AlertSender.java:106) > > > > at org.graylog2.alerts.AlertSender.sendEmails(AlertSender.java:64) > > > > at > > > org.graylog2.rest.resources.streams.alerts.StreamAlertResource.sendDummyAlert(StreamAlertResource.java:355) > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > > > at > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > > > > > at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > > > > > at java.lang.reflect.Method.invoke(Method.java:597) > > > > at > > > org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) > > > > > > at > > > org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151) > > > > > > at > > > org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171) > > > > > > at > > > org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:152) > > > > > > at > > > org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104) > > > > > > at > > > org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:402) > > > > > > at > > > org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:349) > > > > > > at > > > org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:106) > > > > > > at > org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:259) > > > > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) > > > > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) > > > > at org.glassfish.jersey.internal.Errors.process(Errors.java:315) > > > > at org.glassfish.jersey.internal.Errors.process(Errors.java:297) > > > > at org.glassfish.jersey.internal.Errors.process(Errors.java:267) > > > > at > > > org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:318) > > > > > > at > org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:236) > > > > at > > > org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1010) > > > > > > at > > > org.graylog2.jersey.container.netty.NettyContainer.messageReceived(NettyContainer.java:275) > > > > > > at > > > org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > > > > > > at > > > org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > > > > > > at > > > org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > > > > > > at > > > org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:142) > > > > > > at > > > org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > > > > > > at > > > org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > > > > > > at > org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) > > > > at > > > org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:459) > > > > > > at > > > org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:536) > > > > > > at > > > org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) > > > > > > at > > > org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > > > > > > at > > > org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > > > > > > at > > > org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) > > > > > > at > org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) > > > > at > org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) > > > > at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) > > > > at > > > org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) > > > > > > at > > > org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) > > > > > > at > > > org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) > > > > > > at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) > > > > at > > > org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) > > > > > > at > > > org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) > > > > > > at > > > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > > > > > > at > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > > > > > > at java.lang.Thread.run(Thread.java:680) > > > > Caused by: javax.mail.MessagingException: Could not connect to SMTP > host: > > localhost, port: 25; > > > > nested exception is: > > > > javax.net.ssl.SSLException: Unrecognized SSL message, plaintext > connection? > > > > at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1961) > > > > at > com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:654) > > > > at javax.mail.Service.connect(Service.java:295) > > > > at javax.mail.Service.connect(Service.java:176) > > > > at javax.mail.Service.connect(Service.java:125) > > > > at javax.mail.Transport.send0(Transport.java:194) > > > > at javax.mail.Transport.send(Transport.java:124) > > > > at org.apache.commons.mail.Email.sendMimeMessage(Email.java:1400) > > > > ... 51 more > > > > Caused by: javax.net.ssl.SSLException: Unrecognized SSL message, > plaintext > > connection? > > > > at > > > com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:652) > > > > > > at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:484) > > > > at > > > com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:863) > > > > > at > > > com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1188) > > > > > > at > > > com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1215) > > > > > > at > > > com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1199) > > > > > > at > > > com.sun.mail.util.SocketFetcher.configureSSLSocket(SocketFetcher.java:549) > > > > at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:354) > > > > at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:211) > > > > at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1927) > > > > ... 58 more > > > > ^C > > > > [root@awslxgrayuted01 log]# netstat -tlpn > > > > Active Internet connections (only servers) > > > > Proto Recv-Q Send-Q Local Address Foreign Address > > State PID/Program name > > > > tcp 0 0 0.0.0.0:111 0.0.0.0:* > > LISTEN 808/rpcbind > > > > tcp 0 0 0.0.0.0:9200 0.0.0.0:* > > LISTEN 877/java > > > > tcp 0 0 0.0.0.0:9300 0.0.0.0:* > > LISTEN 877/java > > > > tcp 0 0 0.0.0.0:22 0.0.0.0:* > > LISTEN 850/sshd > > > > tcp 0 0 127.0.0.1:25 0.0.0.0:* > > LISTEN 964/master > > > > tcp 0 0 0.0.0.0:514 0.0.0.0:* > > LISTEN 30166/java > > > > tcp 0 0 0.0.0.0:12900 0.0.0.0:* > > LISTEN 30166/java > > > > tcp 0 0 0.0.0.0:9350 0.0.0.0:* > > LISTEN 30166/java > > > > > > You can see smtp listening on localhost (127.0.0.1) > > > > Thanks, > > -Miguel > > > > > > On Wednesday, April 23, 2014 11:06:31 AM UTC-4, Miguel Cruz wrote: > >> > >> Each host is configured to accept email on localhost 25, then that > message > >> gets forwarded to our mail relay which is the one that can actually > send > >> emails out of our VPC. From each graylog host (meaning the ES and > Mongodb > >> instances) i can send emails to my corp email from the command line so > I > >> know email is working properly. > >> > >> Attached is a screenshot of the error. > >> > >> -Miguel > >> > >> > >> On Wednesday, April 23, 2014 4:01:26 AM UTC-4, Kay Röpke wrote: > >>> > >>> The transport_email_web_interface_url is the URL to the web interface. > >>> This is used to build links that are being generated for the email. > >>> The recipient of the alert email should be able to reach that url, the > >>> graylog2 servers will never connect to the web interface. > >>> It is not a mail server address (this is why it's called _url at the > end) > >>> > >>> You need to configure the transport_email_hostname and > >>> transport_email_port to point to your mail server. So unless you have > a > >>> server running on localhost:25 the config is not correct. > >>> > >>> Best, > >>> Kay > >>> > >>> > >>> On Tuesday, April 22, 2014 5:52:20 PM UTC+2, Miguel Cruz wrote: > >>>> > >>>> This is my config on the graylog server: > >>>> > >>>> # Email transport > >>>> transport_email_enabled = true > >>>> transport_email_protocol = smtp > >>>> transport_email_hostname = localhost > >>>> transport_email_port = 25 > >>>> #transport_email_use_auth = true > >>>> #transport_email_use_tls = true > >>>> #transport_email_auth_username = [email protected] > >>>> #transport_email_auth_password = secret > >>>> transport_email_subject_prefix = [graylog2] > >>>> transport_email_from_email = [email protected] > >>>> transport_email_from_name = Graylog2 > >>>> transport_email_web_interface_url = http://10.162.0.21:3000 > >>>> > >>>> The graylog server and web interface are in separate hosts, does the > >>>> server attempts to contact the "transport_email_web_interface_url" ? > If so, > >>>> that is not open on our security group. > >>>> > >>>> -Miguel > >>>> > >>>> On Tuesday, April 22, 2014 10:09:33 AM UTC-4, Kay Röpke wrote: > >>>>> > >>>>> Hi! > >>>>> > >>>>> Yes, I would be very much surprised if it read the /etc/profiles env > >>>>> variable, as Java programs aren't likely to. > >>>>> Also, it is the server that sends the email, not the web interface, > but > >>>>> that changes nothing. > >>>>> > >>>>> The email alert system should use whatever mail server you have > >>>>> configured through the graylog2 server config file. I do not thing > it would > >>>>> pick any system-wide proxy at all, on any system. > >>>>> > >>>>> Please also check what the graylog2 server log says, the line below > is > >>>>> from the web interface. > >>>>> > >>>>> Best, > >>>>> -k > >>>>> > >>>>> On Tuesday, April 22, 2014 4:18:37 AM UTC+2, Miguel Cruz wrote: > >>>>>> > >>>>>> I'm trying to configure alerts and when i click on the "Send test > >>>>>> alert" I get an error: > >>>>>> Error! ×Unable to send dummy alert, check server log for details: > API > >>>>>> call failed GET > >>>>>> http://@ > 10.162.0.17:12900/streams/5355ca40e4b062bcf9b28836/alerts/sendDummyAlert > >>>>>> returned 500 Internal Server Error body: Sending the email to the > following > >>>>>> server failed : localhost:25 > >>>>>> > >>>>>> Just as a test I sent a email from the command line of the same > server > >>>>>> and it worked so i know postfix is working properly. > >>>>>> > >>>>>> I'm pretty sure graylog-web is not following the NO_PROXY env > variable > >>>>>> set in /etc/profiles. > >>>>>> > >>>>>> Where do i need to enter the no proxy line for the web interface to > >>>>>> follow it. > >>>>>> > >>>>>> > >>>>>> Cheers, > >>>>>> -Miguel > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "graylog2" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
