We have been getting an "[Errno 90] Message too long" for the last few weeks that gets the UDPStreamer in udp.py stuck in a loop.
I noticed the except statement just waits and tries again in an endless loop trying to send the same log. I dropped a break in there instead (left the log line so I could see when it happens) and we are able to continue sending logs (probably on a new source port) and we do not have to kill processes or reboot (./encore.sh stop does not work, just hangs) and this appears to fix the endless loop that stops sending logs requiring manual intervention.
We do have a case open with Cisco on what is sending these longer that 1500 MTU sized logs (maybe drop the log that's too long to another file for review?), but our network is 1500 and that's not going to change anytime soon. We believe these may be truncated logs that would end in ... that break our JSON parsers and would rather it drop the log at the eNcore streamer.
RHEL is the platform we're using but we were seeing the same issues on Debian before having to migrate. That VM has been wiped since.
Ex:
except OSError as ex:
self.logger.error("Error [{0}] writing to endpoint {1}:{2} -- Restarting UDPStream...".format(ex, self.host, self.port))
break
We have been getting an "[Errno 90] Message too long" for the last few weeks that gets the UDPStreamer in udp.py stuck in a loop.
I noticed the except statement just waits and tries again in an endless loop trying to send the same log. I dropped a break in there instead (left the log line so I could see when it happens) and we are able to continue sending logs (probably on a new source port) and we do not have to kill processes or reboot (./encore.sh stop does not work, just hangs) and this appears to fix the endless loop that stops sending logs requiring manual intervention.
We do have a case open with Cisco on what is sending these longer that 1500 MTU sized logs (maybe drop the log that's too long to another file for review?), but our network is 1500 and that's not going to change anytime soon. We believe these may be truncated logs that would end in ... that break our JSON parsers and would rather it drop the log at the eNcore streamer.
RHEL is the platform we're using but we were seeing the same issues on Debian before having to migrate. That VM has been wiped since.
Ex: