Skip to main content

FHTrap was not closed properly and was unable to return the result

Comments

4 comments

  • rpvw
    The only thing I can find (translated from a Russian site) talked about this error being generated from the Max cPanel process memory (maxmem) being low. You should be able to alter this in Tweak Settings > System > Max cPanel process memory You could try and increase the amount of memory you are allocating to the cPanel processes, and see if the error goes away :) Hope this helps.
    0
  • RobinF28
    The only thing I can find (translated from a Russian site) talked about this error being generated from the Max cPanel process memory (maxmem) being low. You should be able to alter this in Tweak Settings > System > Max cPanel process memory You could try and increase the amount of memory you are allocating to the cPanel processes, and see if the error goes away :) Hope this helps.

    Thanks rpvw, I've checked this, but it set the same as my other VPS, at the default value of 768MB, and I don't think it's maxing out on any processes thus far. I've checked for any cpanel processes that are being killed off or terminated, but the server is quite quiet and not under any strain. < 0.2 for 5min load average! Thank you for your input however.
    0
  • cPanelMichael
    Cpanel::FHTrap was not closed properly and was unable to return the result

    Hello, These messages are harmless, and appear when the coppermine cpaddon is enabled. We've fixed this in cPanel version 68 with the following case: Fixed case CPANEL-14544: Don't warn when trapping output across a fork. Thank you.
    0
  • RobinF28
    Many thanks Michael, I'll ignore them so. :)
    0

Please sign in to leave a comment.