RT is encountering an internal error. As I look into error logs, it says that " Error in /usr/sbin/apache2': corrupted double-linked list: 0x00007f1981973a20 *** [Wed Aug 01 15:01:19.519365 2018] [core:notice] [pid 817:tid 139749808720832] AH00051: child pid 12420 exit signal Aborted (6), possible coredump in /etc/apache2 AND *** Error in/usr/sbin/apache2’: corrupted double-linked list: 0x00005562a130c7d0 ***
[Wed Aug 01 15:01:34.548640 2018] [core:notice] [pid 817:tid 139749808720832] AH00051: child pid 12568 exit signal Aborted (6), possible coredump in /etc/apache2"
Unfortunately its challenging to provide suggestions as to how to troubleshoot this. My advice is to comb back through your deployment and note changes that have happened since the error started.
A quick thing to try is pick a different deployment method and use that, or set up another instance of RT with a copy of your database and if it works then “cut over” to that server.
RT is working fine within the 5 months though we still encounter “internal error” when the ticket is too big. We hardly refresh a ticket if it includes images and tables in email or history. But, within the month of July, RT is encountering slowness. We have to refresh every ticket we’ll open. I checked error logs and it was the first time to have a memory corruption error. So, we upgraded RT from 4.4.1 to 4.4.2 and I think it helps get back to its performance again but still encountering some issues when ticket has images and tables included in an email.
You’d have to provide details on your deployment. Server info (bare metal? virtual machine? RAM? CPU info?) and the web server configuration.
If its working fine except for choking on large emails, that suggests the environment that runs RT doesn’t have enough resources dedicated to it, or a configuration setting somewhere that is limiting it. I’d classify 6,500 tickets as still an almost completely empty install.
