Joerg,
I had this problem MANY times. Most often it was:
- the service account lost it privilege to log on as a service
we suspect it were some interfering group policies.
It was possible to "reactivate" by opening service control panel,
reappling password. Windows then reported, that the "log
>Joerg,
>
>I had this problem MANY times. Most often it was:
>
> - the service account lost it privilege to log on as a service
>
>we suspect it were some interfering group policies.
...
>that is NOT a postgreSQL problem, as long talks with magnus revealed
>... the rights are lost within windows,
The typical way to do this is to use .pgpass in the user's home
directory. Does that help?
---
Olivier Thauvin wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1567
> Logged by: Olivie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a server running 8.0.1 which keeps terminating. I first noticed this
today: it has happened about 7 times already. Periodically, the background
writer process is killed and drags the rest of the server down with it.
Most times PG restarts on i
On Mon, Mar 28, 2005 at 11:45:06PM -, Greg Sabino Mullane wrote:
>
> I have a server running 8.0.1 which keeps terminating. I first noticed this
> today: it has happened about 7 times already.
Could the situation have been going on longer than just today? How
far back do your logs go? What,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Could the situation have been going on longer than just today? How
> far back do your logs go? What, if anything, has changed on the
> system since the last time you're certain this problem wasn't
> happening?
Logs go back to February 22, when 8
On Tue, 29 Mar 2005, Greg Sabino Mullane wrote:
> Not many data points yet, but here's all the occurances:
>
> $ grep "signal 9" 5810.log
> <2005-03-28 03:38:14 EST >LOG: server process (PID 29216) was terminated by
> signal 9
> <2005-03-28 10:15:45 EST >LOG: background writer process (PID 2927
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Well, it seems to be saying that it was terminated by SIGKILL which I
> can't see a reason to be internally generated. Is there anything else
> running on the system that might (for example) be taxing memory to cause
> an OOM killing spree or some
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> <2005-03-28 12:28:27 EST >LOG: background writer process (PID 17409) was
> terminated by signal 9
> Memory seems to be ok. No entries in /var/log/messages (this is a Linux
> 2.4 series kernel, gcc 3.4.1, dual 686 CPU, 1 SCSI drive system).
Sig
When grilled further on (Sun, 27 Mar 2005 02:26:02 -0500),
Tom Lane <[EMAIL PROTECTED]> confessed:
>
> We need to change the function APIs so that date2isoweek passes back
> some indication of which year it thought the week belongs to, and then
> isoweek2date must use that instead of the original
10 matches
Mail list logo
