Splunk Search

What does "PollableDescriptor:writeWithTimeout failed" error mean?

the_wolverine
Champion

Seeing the following error in LWF splunkd.log every 5 minutes:

10-28-2010 08:37:37.048 WARN  NetUtils - PollableDescriptor::writeWithTimeout failed. Bad select_for_loop rv = -2
10-28-2010 08:37:37.048 WARN  TcpOutputProc - TcpSendThread: Connection to server the_indexer_ip:9443, fd:33 lost - retrying: Resource temporarily unavailable

What does it mean? Data is coming through, but there's a serious lag (1 hour) at times. Currently it is caught up so seems to be an intermittent problem.

Tags (2)
0 Karma
1 Solution

jkerai
Splunk Employee
Splunk Employee

This warning is logged on forwarder when it is unable to write data to network for more than 5 mins. This may be why you are seeing the lag. Please check the 'current_size' of queues on the indexer to see if they are always near their max capacity of 1000 events around the time this warning is seen. If the queues on indexer look healthy, then check to see if there network issue during the time this warning is reported. You can probably look for the same warning on other forwarders to see if other forwarders also experienced the same problem. May be indicative of network or indexer saturation.

View solution in original post

jkerai
Splunk Employee
Splunk Employee

This warning is logged on forwarder when it is unable to write data to network for more than 5 mins. This may be why you are seeing the lag. Please check the 'current_size' of queues on the indexer to see if they are always near their max capacity of 1000 events around the time this warning is seen. If the queues on indexer look healthy, then check to see if there network issue during the time this warning is reported. You can probably look for the same warning on other forwarders to see if other forwarders also experienced the same problem. May be indicative of network or indexer saturation.

Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...