Security

PipelineComponent - Process delayed by 46.548 seconds, perhaps system was suspended?

manikandankasi
Explorer

i'm getting below log in almost all my scheduled summary. what does it mean will it affect the quality of search results.
Could you please advice how to fix this issue ?

DispatchManager::dispatchHasFinished(id='scheduler_c3ZjX2FwbV9ucF9kMnNwbHVuaw_YXBtX3NucG0__RMD5ef03de80f9dfee83_at_1547538000_374_2F96A993-8827-50B3-BBAC-FD84F8BCBD22', username='svc_apm_np_d2splunk')
01-15-2019 18:40:48.269 INFO UserManager - Unwound user context: svc_apm_np_d2splunk -> NULL
01-15-2019 18:40:48.269 INFO PipelineComponent - Process delayed by 46.548 seconds, perhaps system was suspended?

Thanks in Advance,
Mani

Tags (1)

p_gurav
Champion

Try doing health check in Monitoring console, which will tell you if there are any resource issues.

0 Karma

manikandankasi
Explorer

thanks Gurav for quick response.

actually i want know what is causing this issue.
i checked the indexer performance. its looking good.
but this issue happening randomly.
please advice me anything specifically i need to check.

0 Karma
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 ...