Log issues after upgrade to 2.2.3
Posted: Tue Nov 22, 2016 6:59 pm
Hi,
After upgrading to version 2.2.3, the customer has a concern that the /var/log/message file is being flooded with the following messages:
Nov 23 09:50:59 host001 nfcapd[17532]: Process_v9: flowset zero length error.
Nov 23 09:50:59 host001 nfcapd[17532]: Process_v9: flowset zero length error.
Nov 23 09:50:59 host001 nfcapd[17532]: Process_v9: flowset length error. Expected bytes: 60983 > buffersize: 1
Nov 23 09:50:59 host001 nfcapd[17524]: Process_v9: flowset zero length error.
There is approximately 1200 of these messages per minute.
[root@host001 log]# cat /var/log/messages | grep 'Nov 23 09:50' | wc -l
1281
The server appears to be collecting netflow data without issue.
1. How do we eliminate these errors in the log file?
2. Can we write nfcapd related messages to a different log file, as the /var/log/messages file is also used to log other important system information.
Regards
Zee
After upgrading to version 2.2.3, the customer has a concern that the /var/log/message file is being flooded with the following messages:
Nov 23 09:50:59 host001 nfcapd[17532]: Process_v9: flowset zero length error.
Nov 23 09:50:59 host001 nfcapd[17532]: Process_v9: flowset zero length error.
Nov 23 09:50:59 host001 nfcapd[17532]: Process_v9: flowset length error. Expected bytes: 60983 > buffersize: 1
Nov 23 09:50:59 host001 nfcapd[17524]: Process_v9: flowset zero length error.
There is approximately 1200 of these messages per minute.
[root@host001 log]# cat /var/log/messages | grep 'Nov 23 09:50' | wc -l
1281
The server appears to be collecting netflow data without issue.
1. How do we eliminate these errors in the log file?
2. Can we write nfcapd related messages to a different log file, as the /var/log/messages file is also used to log other important system information.
Regards
Zee