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.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...