spamd crashing the server

[Francisco]

Recently cpanel update ran overnight (RELEASE branch). It caused the server to crash, the cause:

Oct 28 00:15:32 server10 pure-ftpd: (?@94.72.7.95) [INFO] Logout.
Oct 28 03:37:10 server10 kernel: spamd[13013]: segfault at 0000000000000030 rip 00002b3bef2d9acf rsp 00007fffb4249540 error 4
Oct 28 08:02:17 server10 pure-ftpd: (?@) [INFO] New connection from
Oct 28 09:34:36 server10 syslogd 1.4.1: restart.
Oct 28 09:34:36 server10 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Oct 28 09:34:36 server10 kernel: Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 console=xvc0 graphical utf8)
Oct 28 09:34:36 server10 kernel: Linux version 2.6.18-164.el5xen (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1$

Platform is Citrix Xenserver 5.5 - CentOS 5.4 x64 and cPanel. Any ideas??

[cPanelDon]

Recently cpanel update ran overnight (RELEASE branch). It caused the server to crash, the cause:

Oct 28 00:15:32 server10 pure-ftpd: (?@94.72.7.95) [INFO] Logout.
Oct 28 03:37:10 server10 kernel: spamd[13013]: segfault at 0000000000000030 rip 00002b3bef2d9acf rsp 00007fffb4249540 error 4
Oct 28 08:02:17 server10 pure-ftpd: (?@) [INFO] New connection from 
Oct 28 09:34:36 server10 syslogd 1.4.1: restart.
Oct 28 09:34:36 server10 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Oct 28 09:34:36 server10 kernel: Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 console=xvc0 graphical utf8)
Oct 28 09:34:36 server10 kernel: Linux version 2.6.18-164.el5xen (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1$[/

Platform is Citrix Xenserver 5.5 - CentOS 5.4 x64 and cPanel. Any ideas??

According to the provided log data there is a 4.5-to-6-hour time frame between the spamd segmentation fault and the next logged entry of FTP usage followed by the restart; this would lead me to believe that the spamd segfault alone is less likely to be the sole direct cause.

To more accurately diagnose or at least have a better idea what may be contributing or related, it will help to know more information. The following questions would be where I would start researching to help pinpoint the issue:

1.) Was this a one-time event, or is it recurring with the same or very similar log detail produced at each occurrence?
2.) Are there other similarly-configured VPS systems running on the same hardware node?
3.) Has the hardware and RAM been thoroughly tested; for RAM, one could run "Memtest86+" at boot-time from the hardware node.
4.) If available, what was the load and level of activity that was occurring on the system at the time?
5.) Has a forced re-install of SpamAssassin been attempted (to re-install spamd)?
6.) Were any corrective measures performed?
7.) Was the OS of the VPS a fresh install of CentOS 5.4, or was it upgraded from an earlier CentOS release (e.g., earlier 5.x releases, or 4.x releases)?

General questions about the cPanel install:
8.) What is your full cPanel version number?
9.) What was the full cPanel version number before the update (available via the update logs)?

/var/cpanel/updatelogs

10.) Is the system updated manually or was it configured for automatic updates?
11.) If updated manually, was the update performed using the force option? (e.g., via SSH "--force" could be used when executing "/scripts/upcp")