Steve Oualline wrote:
We have an interesting problem here. We have a server at a customer's site
on which the database will not come up. Because of the nature of the
product we make, we don't turn on Postgresql logs, so no log data
is avaliable.
That's the biggest problem you've got right th
We have an interesting problem here. We have a server at a customer's site
on which the database will not come up. Because of the nature of the
product we make, we don't turn on Postgresql logs, so no log data
is avaliable.
What we see is that when we start postmaster it starts, but anyone who
Michael Korotun wrote:
Yes, this is oom
Firstly it killed httpd and then postmaster. But who took all the memory? I
see there Free swap: 0Kb in the messages log - was it a reason?
Sounds likely.
I have 1GB of RAM. For shared memory I took about 262MB.
/etc/sysctl.conf
===
#shared me
On Fri, 2005-05-06 at 07:54, Michael Korotun wrote:
> Hi Guys,
>
>
>
> I am writing here again. Here is the scenario of my problem:
>
>
>
> I have Postgres 8.0.1 on Linux FC3 and everything goes fine, except
> that a one time per week approximately I am getting server crash with
> a message
Michael Korotun wrote:
I have Postgres 8.0.1 on Linux FC3 and everything goes fine, except that a
one time per week approximately I am getting server crash with a message in
log:
LOG: server process (PID 5252) was terminated by signal 9
Sounds like something is sending SIGKILL (kill -9) to your b
Hi Guys,
I am writing here again. Here is the scenario of my
problem:
I have Postgres 8.0.1 on Linux FC3 and everything
goes fine, except that a one time per week approximately I am getting server
crash with a message in log:
==
LOG: server process (PID
