Policy server HTTP error: Absolute request timeout expired (Request queued 3.000 secs ago, 1 send attempts in 3.000 secs, 3.000 in other ioloops)

microvax

• November 11, 2025 14:03

I have recently noticed several error messages like the ones seen below in the maillog file and I would like to know what they are caused by:

 

Nov 10 21:11:32 server dovecot[3561844]: auth: Error: policy(almacen@domainx,IPx,<3PkOAUlDSN6EnYAS>): Policy server HTTP error: Absolute request timeout expired (Request queued 3.000 secs ago, 1 send attempts in 3.000 secs, 3.000 in other ioloops)
Nov 10 21:11:35 server dovecot[3561844]: auth: Error: policy(almacen@domainx,IPx,<3PkOAUlDSN6EnYAS>): Policy server HTTP error: Absolute request timeout expired (Request queued 3.000 secs ago, 1 send attempts in 2.997 secs, 2.997 in other ioloops)

• 

  cPRex Jurassic Moderator

  • November 12, 2025 18:54

  Hey there!  This is usually caused by an issue with cPHulk.  Can you ensure that is running, or attempt to restart it with the /scripts/restartsrv_cphulkd command?

  If that doesn't work, you may need to reset cPHulk using the details here: https://support.cpanel.net/hc/en-us/articles/360050920233-cphulkd-marked-as-crashed

  0
• 

  microvax

  • December 03, 2025 02:18

  Hello, you can see below the results of the suggested commands

   

  [root@server:~]$ grep "marked as crashed" /usr/local/cpanel/logs/cphulkd_errors.log

  [root@server:~]$ grep "marked as crashed" /var/lib/mysql/$hostname.err

  grep: /var/lib/mysql/.err: No such file or directory

  0
• 

  cPRex Jurassic Moderator

  • December 04, 2025 03:35

  You'd need to use the actual hostname instead of a placeholder.  Also, since it's been a few weeks since the original post it's possible the data is no longer there.

  You can open the file to see the oldest entry or run "head -n 1 /full/path/to/error/log" to see the first entry.

  0

Please sign in to leave a comment.