Hi Daryl, Typically when I see a core dump when running siege, it is a resource issue. Out of memory, and/or I've reached the ulimit on my machine and need to set it higher. The limit is 1024 (displayed via ulimit -n), and can be changed via ulimit -n <value>. This change isn't persistent - and the setting can be changed permanently by editing /etc/sysconfig/security/limits.conf.
I typically set it to something unrealistically high, and the machine will always run out of memory before hitting the ulimit. - Ryan On Fri, Aug 21, 2015 at 9:49 AM, Daryl King <allnatives.onl...@gmail.com> wrote: > I am running Apache 2.4.10 with mpm_event on a Debian 8 vps. When I run > Siege on my setup it runs well, except for a Segmentaion Fault at the very > end [child pid xxxx exit signal Segmentation fault (11)]. I have run GDB on > a core dump of the segfault and returned this: > [Using host libthread_db library > "/lib/x86_64-linux-gnu/libthread_db.so.1". > Core was generated by `/usr/sbin/apache2 -k start'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x00007f53a4ac8add in read () at ../sysdeps/unix/syscall-template.S:81 > 81 ../sysdeps/unix/syscall-template.S: No such file or directory. > (gdb)] > Im at a loss as to how to proceed with this, but am willing to keep > digging until I find the answer. Any advice appreciated.. >
