On Sun, Feb 24, 2013 at 7:08 AM, Andre wrote:
> Hi,
> Since our upgrade of hardware, OS and Postgres we experience server stalls
> under certain conditions, during that time (up to 2 minutes) all CPUs show
> 100% system time. All Postgres processes show BIND in top.
> Usually the server only has a
Andre writes:
> Since our upgrade of hardware, OS and Postgres we experience server stalls
> under certain conditions, during that time (up to 2 minutes) all CPUs show
> 100% system time. All Postgres processes show BIND in top.
Odd. I wonder if you are seeing some variant of the old context s
On 25/02/2013 12:13 AM, Bèrto ëd Sèra wrote:
and your /etc/sysctl.conf is?
/etc/sysctl.conf only had unrelated options set, here is the output of sysctl
-a:
abi.vsyscall32 = 1
debug.exception-trace = 1
dev.hpet.max-user-freq = 64
kernel.acct = 4230
kernel.acpi_video_flags = 0
kernel.
and your /etc/sysctl.conf is?
Cheers
Bèrto
On 24 February 2013 14:08, Andre wrote:
> Hi,
> Since our upgrade of hardware, OS and Postgres we experience server stalls
> under certain conditions, during that time (up to 2 minutes) all CPUs show
> 100% system time. All Postgres processes show BIND
Hi,
Since our upgrade of hardware, OS and Postgres we experience server stalls
under certain conditions, during that time (up to 2 minutes) all CPUs show 100%
system time. All Postgres processes show BIND in top.
Usually the server only has a load of < 0.5 (12 cores) with up to 30
connections,
