On 01/03/2019 4:09 pm, Venkat Jaligama wrote:
Gordon,
Previously attached logs consists of Log metadata also, the actual log messages
are as follows
2019-02-28 13:07:44 [System] error [0x7f89e3fff700] Error reading socket:
Encountered end of file [-5938]
2019-02-28 13:07:44 [System] error [0x7f89e9d18700] Error reading socket:
Encountered end of file [-5938]
2019-02-28 13:07:44 [System] error [0x7f89e8d16700] Error reading socket:
Encountered end of file [-5938]
2019-02-28 13:07:43 [System] error [0x7f89e2ffd700] Error reading socket:
Encountered end of file [-5938]
2019-02-28 13:07:43 [System] error [0x7f89e2ffd700] Error reading socket:
Encountered end of file [-5938]
2019-02-28 13:07:43 [System] error [0x7f89ead1a700] Error reading socket:
Encountered end of file [-5938]
Does these error indicate something with the memory issue, out of 3.4 million
logs 2.4 million logs are these error messages which is almost 70 percent
The errors indicate a TLS based client connection that ended
unexpectedly. In itself that is not a memory issue. However given the
volume of these errors, it sounds like something that needs to be
explained and that might be a clue as to the cause of the other issue.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
