| 2014-06-24 08:32:28 |
KorteX |
description |
Been running Varnish on separate machines on Ubuntu 12.04 for ages to front a large caching infrastructure. 2x 32GB machines, running like a charm.
The need to upgrade the infrastructure with more RAM was necessary, and got my hands on 2x blades with 72GB RAM per machine. Dell Hardware with Registered ECC 1333Mhz DDR3.
Decided to install Ubuntu 14.04 with Varnish 3.05 to give it a try.
Everything ran fine for a day or 2, and then starting getting segfaults with libjemalloc.so.1:
varnishd[22217]: segfault at 18 ip 00007f061ea62565 sp 00007ef8a87e8170 error 4 in libjemalloc.so.1[7f061ea57000+30000]
Unfortunately I do not have an strace nor anymore information, just that segfault from dmesg.
I did a full memory test, with no errors.
I reinstalled the blades with Ubuntu 12.04 with Varnish 3.05, and been running stable since. No segfaults. So ruling out the hardware, hence the bug report. |
Been running Varnish on separate machines on Ubuntu 12.04 for ages to front a large caching infrastructure. 2x 32GB machines, running like a charm.
The need to upgrade the infrastructure with more RAM was necessary, and got my hands on 2x blades with 72GB RAM per machine. Dell Hardware with Registered ECC 1333Mhz DDR3.
Decided to install Ubuntu 14.04 with Varnish 3.05 to give it a try.
Everything ran fine for a day or 2, and then starting getting segfaults with libjemalloc.so.1:
varnishd[22217]: segfault at 18 ip 00007f061ea62565 sp 00007ef8a87e8170 error 4 in libjemalloc.so.1[7f061ea57000+30000]
Unfortunately I do not have an strace nor anymore information, just that segfault from dmesg.
I did a full memory test, with no errors.
I reinstalled the blades with Ubuntu 12.04 with Varnish 3.05, and been running stable since. No segfaults. So ruling out the hardware, hence the bug report.
Kernels running at the time:
On Ubuntu 14.04: 3.13.0-29-generic
On Ubuntu 12.04: 3.11.0-23-generic
All 64bit architecture ;) not multiarch either. |
|
