LFD Hung Task Timeout Error

theluli

• October 25, 2018 03:23

Hi everyone INFO: task lfd - (child) p:21289 blocked for more than 120 seconds "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this messages This error is appearing every morning on my server, and web pages are not loaded then Anyone can give me advice

• 

  cPanelMichael

  • October 26, 2018 18:46

  Hello @theluli, Here's a similar thread where that kernel message is discussed: Let us know if you have additional questions. Thank you.

  0
• 

  theluli

  • October 26, 2018 20:49

  Hello @theluli, Here's a similar thread where that kernel message is discussed:

  0
• 

  cPanelMichael

  • October 29, 2018 15:16

  Hello @theluli, Can you run the below command and let us know the output? grep "blocked for more than 120 seconds" /var/log/messages
  Additionally, please post the output from the following command: cat /etc/redhat-release
  Thank you.

  0
• 

  theluli

  • October 30, 2018 21:05

  Hello @theluli, Can you run the below command and let us know the output? grep "blocked for more than 120 seconds" /var/log/messages
  Additionally, please post the output from the following command: cat /etc/redhat-release
  Thank you.

  
  Hi Michael l am using CentOS Linux release 7.5.1804 (Core) Please see the photo below, since with grep l dont get aanything Also the server it freeze every-night round 00:08, l have to restart otherwise websites dont work

  0
• 

  cPanelMichael

  • October 31, 2018 15:08

  Also the server it freeze every-night round 00:08

  
  Hello @theluli, The information you provided suggests this is happening due to a lack of available resources on the server. I recommend accessing the server before and during the times it routinely freezes and checking the resource usage. We provide a guide here that offers some commands you can use to check the load, memory usage, and disk I/O: Let us know what you find. Thank you.

  0
• 

  theluli

  • November 01, 2018 08:32

  Hello @theluli, The information you provided suggests this is happening due to a lack of available resources on the server. I recommend accessing the server before and during the times it routinely freezes and checking the resource usage. We provide a guide here that offers some commands you can use to check the load, memory usage, and disk I/O:

  0
• 

  cPanelMichael

  • November 01, 2018 15:12

  Hello @theluli, Feel free to open a

  0
• 

  theluli

  • November 02, 2018 07:47

  Hello @theluli, Feel free to open a

  0
• 

  cPanelMichael

  • November 02, 2018 16:30

  Hello @theluli, I'm glad to see it worked out. Thanks for sharing the outcome.

  0

Please sign in to leave a comment.