- This topic has 5 replies, 5 voices, and was last updated 14 years, 10 months ago by .
We receive these errors from one of our feeds. Typically this message is repeated several thousand times per minute. Eventually (roughly 2 hours), the log file and error file grow to 2Gig in size each and the process crashes. That leads to the logical volume running out of space when those crash files are copied to the errors directory.
[prod:prod:WARN/0: engine_cmd:05/21/2008 23:45:17] Output log file cycled
[pdl :PDL :ERR /0: FEED1:05/22/2008 01:46:38] read failed: Connection timed out
[pdl :PDL :ERR /0: FEED1:05/22/2008 01:46:38] read returned error 110 (Connection timed out)
Followed by this message a little later (probably when the connection is restored).
[pdl :PDL :ERR /0: FEED1:05/22/2008 19:28:37] read returned error 0 (Success)
Whatever is happening at this point it is telling me the error message is 0 “Success”.
These feeds are connected via a vpn to a vendor. The EOConfig for these is disable_all. I know it is a protocol error but am at a loss in how to troubleshoot the best way to fix the problem. Has anyone every seen this type of behavior? It does not happen at the same time.
- The forum ‘Cloverleaf’ is closed to new topics and replies.