Hi Sourav,
This happens when shovel gets fill for amqp and rabbitmq didnt able to clean the queue.
Open a case with support at the earliest, because amqp is responsible for keeping the logs.
If this error will exist be too long then there would be loss of logs so much.
Check with rsa support. Thanks.
Regards,
Deepanshu Sood.
From:"Sourav1984" <emc-community-network@emc.com>
Date:Tue, 2 Jun, 2015 at 13:16
Subject:[RSA Security Analytics] - Stopped receiving logs from Log Collector
ECN
Stopped receiving logs from Log Collector
created by Sourav1984 in RSA Security Analytics - View the full discussion
Hi,
I am observing logs are not reaching to SA from Decoders.
Below are the errors discovered from Log collector.
An error occurred publishing a statistic for plugin aa2e7a0e-e506-4982-981e-c95f84047f3b/logcollector_processinfo-string-uptime. Error: An error occurred publishing an AMQP Message. Exchange name: carlos.sms.collectd; error: An error occurred creating an AMQP Channel. Configuration: {#012 "urn": "carlos.sms.collectd",#012 "connection":#012 {#012 "vhost": "\/rsa\/system"#012 }#012}#012; error: a socket error occurred; message size: 321
Also getting error while adding decoders under Log Collector>Services>Local Colletors>Destination.
HttpOps: GET : SSL connection error: Broken pipe
Can anyone suggest what this signifies & the way of troubleshooting need to carry.
Thanks & regards,
Sourav.
Reply to this message by replying to this email, or go to the message on ECN Start a new discussion in RSA Security Analytics by email or at ECN Following RSA Security Analytics in these streams: Inbox
