Jeff wrote:
Do you have any system monitoring scripts that may be killing it as it
may look like a "runaway" process?
We've had this happen to us before. You tend to forget about things like
that.
This got me thinking, and i rechecked all possibilities.
It turned out that we changed rlimit polici
"Magnus Naeslund(t)" <[EMAIL PROTECTED]> writes:
> Doug McNaught wrote:
>> Linux is probably killing your process because it (the kernel) is low
>> on memory. Unfortunately, this happens more often with older versions
>> of the kernel. Add more RAM/swap or figure out how to make your query
>> u
On Thu, 04 Dec 2003 03:35:49 +0100
"Magnus Naeslund(t)" <[EMAIL PROTECTED]> wrote:
>
> Well this just isn't the case.
> There is no printout in kernel logs/dmesg (as it would be if the
> kernel killed it in an OOM situation).
> I have 1 GB of RAM, and 1.5 GB of swap (swap never touched).
>
Do y
Doug McNaught wrote:
"Magnus Naeslund(t)" <[EMAIL PROTECTED]> writes:
I have this big table running on an old linux install (kernel 2.2.25).
I've COPYed some tcpip logs into a table created as such:
Linux is probably killing your process because it (the kernel) is low
on memory. Unfortunately,
"Magnus Naeslund(t)" <[EMAIL PROTECTED]> writes:
> I have this big table running on an old linux install (kernel 2.2.25).
> I've COPYed some tcpip logs into a table created as such:
Linux is probably killing your process because it (the kernel) is low
on memory. Unfortunately, this happens more
I have this big table running on an old linux install (kernel 2.2.25).
I've COPYed some tcpip logs into a table created as such:
create table ipstats (time timestamp, src inet, dst inet, npackets int8,
nbytes int8);
Big:
select count(*) from ipstats;
count
--
99173733
When i do two s
