Internal Server Error 500 No response from subprocess (php): subprocess was killed with signal 11

[PPNSteve]

Trying to view the INBOX in horde webmail app I'm getting this error:

Internal Server Error

500

No response from subprocess (php): subprocess was killed with signal 11

Al the other mailboxes including a rather full spam box work, its only affection this one inbox on this one specific user.

Fixed mailbox permissions, restarted cpsrvd and forced an cPanel update - still getting error..

UPDATE: adding error logs from Roundcube;

[email protected] [/var/cpanel/roundcube/log]# tail -100 errors
[08-Jan-2014 22:19:10 UTC] Unexpected condition from IMAP server, closed or corrupt connection to IMAP. Possible mailbox corruption.
[08-Jan-2014 22:19:10 UTC] PHP Warning:  fclose() expects parameter 1 to be resource, null given in /usr/local/cpanel/base/3rdparty/roundcube/program/lib/Roundcube/rcube_imap_generic.php on line 201
[08-Jan-2014 22:19:18 UTC] Unexpected condition from IMAP server, closed or corrupt connection to IMAP. Possible mailbox corruption.
[08-Jan-2014 22:19:18 UTC] PHP Warning:  fclose() expects parameter 1 to be resource, null given in /usr/local/cpanel/base/3rdparty/roundcube/program/lib/Roundcube/rcube_imap_generic.php on line 201
[08-Jan-2014 22:19:25 UTC] Unexpected condition from IMAP server, closed or corrupt connection to IMAP. Possible mailbox corruption.
[08-Jan-2014 22:19:25 UTC] PHP Warning:  fclose() expects parameter 1 to be resource, null given in /usr/local/cpanel/base/3rdparty/roundcube/program/lib/Roundcube/rcube_imap_generic.php on line 201

Any suggestions on a fix???

 

[PPNSteve]

Re: Internal Server Error 500 No response from subprocess (php): subprocess was killed with signal

OK desperation sat in and we ended up doing a swap between mail services, switched from dovecot to courier and then back again, to resolve this.

This may work for you as well.

 

[cPanelMichael]

Re: Internal Server Error 500 No response from subprocess (php): subprocess was killed with signal

Hello

There are a few different potential causes of this type of error message. I have seen this happen due to a corrupted dovecot.index file within the email account's mail directory. Thank you for updating us with the outcome. Feel free to let us know if the issue occurs again.