×

Join the Conversation

Without signing in, you're just watching from the sidelines. Sign in or Register to connect, share, and be part of the Splunk Community.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Ask a Question
minhvt
Loves-to-Learn
Member since: ‎03-31-2024
‎04-08-2024
Community Statistics
Posts 1
Solutions 0
Karma Given 0
Karma Received 0
Member Since ‎03-31-2024
View All

Heavy forwarder has many "TcpInputProc - Input que...

by in Installation
‎03-31-2024 07:02 PM
‎03-31-2024 07:02 PM
After upgrade from 9.1.0 to 9.2.1, my heavy forwarder has many following lines in log:   04-01-2024 08:56:16.812 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:16.887 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:16.951 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:16.982 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.008 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.013 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.024 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.041 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.079 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.097 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.146 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.170 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.190 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.257 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.292 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.327 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.425 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.522 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.528 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.549 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.551 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped.     How to disable this log? Does any error related this INFO log? ... View more
Labels
Contact Me
Online Status
Offline
Date Last Visited
‎04-08-2024 12:23 AM