David Harvey
2017-05-11 14:25:01 UTC
Hi Packetfence-users,
In my attempts to replace an ageing centos install with a Debian one, I've
found that yesterdays install went OK (which I proceeded to break) but on
doing a fresh install today I keep getting variants on t he following -
preventing me from running the configurator.
May 11 15:03:22 packetfence kernel: [ 1111.928053] apache2[1487]: segfault
at 7fae2c5066b0 ip 00007fae3cc6629c sp 00007ffc7a7db6e8 error 4 in
libc-2.19.so[7fae3cbe6000+1a1000]
apache seems to start OK on it's own, and as I paved yesterdays install I
can't see an apt history log to point the finger at a specific package
change.
So far I can reproduce on a qemu instance running from proxmox, and from a
virtualbox instance.
Running apache2 -e debug -D debian -X -f
/usr/local/pf/var/conf/httpd.conf.d/httpd.admin segfaults after a little
while, regardless of adjusting the deprecated setting in httpd.admin that
it's spits warnings about. Alas, no useful output and my strace foo is a
little weak for working out what in the site config is upsetting it.
Assuming the file is processed top to bottom it at least seems to parse the
MaxClients block, so it looks like one of the aspects below that..
Anyone else seen similar or got any ideas?
Best,
David
In my attempts to replace an ageing centos install with a Debian one, I've
found that yesterdays install went OK (which I proceeded to break) but on
doing a fresh install today I keep getting variants on t he following -
preventing me from running the configurator.
May 11 15:03:22 packetfence kernel: [ 1111.928053] apache2[1487]: segfault
at 7fae2c5066b0 ip 00007fae3cc6629c sp 00007ffc7a7db6e8 error 4 in
libc-2.19.so[7fae3cbe6000+1a1000]
apache seems to start OK on it's own, and as I paved yesterdays install I
can't see an apt history log to point the finger at a specific package
change.
So far I can reproduce on a qemu instance running from proxmox, and from a
virtualbox instance.
Running apache2 -e debug -D debian -X -f
/usr/local/pf/var/conf/httpd.conf.d/httpd.admin segfaults after a little
while, regardless of adjusting the deprecated setting in httpd.admin that
it's spits warnings about. Alas, no useful output and my strace foo is a
little weak for working out what in the site config is upsetting it.
Assuming the file is processed top to bottom it at least seems to parse the
MaxClients block, so it looks like one of the aspects below that..
Anyone else seen similar or got any ideas?
Best,
David