hello simon, while i was working on your site, i learnt what these files really mean.
these files are generated upon a segfault of php processor. these segfaults should never happen under normal circumstances and they are usually caused by a bug within the php processor itself. if the problem would be replicable by repeating the same action which creates them, i could trace the problem to a single buggy function which i could replace by another one.
BUT to fix this problem for 100% i suggest that you update your php. as you said that you are running your own VPS i would suggest to upgrade php to 5.5.x which is much more faster than the 5.3.x and i have a good personnal experience with it on our production servers. i must say that we see much much less such segfaults than we did on old 5.2.x.
since php 5.6 was just released, the php 5.3 is no longer supported and thus if any security problem is found, you will have lot's of problems with your sites.
if you can afford some downtime, i can help you update your php over ssh access if you have root priviliges as i do also linux administration.
example of the segfaults:
- when you are running your php (fpm) under chroot-ed enviroment, which you probably do, you may be missing links to the proper directories such as /dev /lib /run or similar within the home of the chroot
- this would cause a missing linked libraries from php and thus could trigger the segfault (dns would not work, email would probably not work)
another examples:
- i see lot's fixe from php5.3.26 to the latest here:
http://php.net/ChangeLog-5.php#5.3.29any part of the code using any of the functions or objects listed at the above changelog would trigger the segfault.
best regards, stan