Re: again... (win32 logging errors)

From: Martin Gainty <mgainty(at)hotmail(dot)com>
To: Klint Gore <kgore4(at)une(dot)edu(dot)au>, Ati Rosselet <ati(dot)rosselet(at)gmail(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: again... (win32 logging errors)
Date: 2008-10-27 02:28:25
Message-ID: BLU142-W216F7638C33C244A7744EAAE240@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


Agreed!
make SURE the user you used to login has rights
cmd
cacls LogFileName

HTH
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.

> Date: Mon, 27 Oct 2008 13:11:36 +1100
> From: kgore4(at)une(dot)edu(dot)au
> To: ati(dot)rosselet(at)gmail(dot)com
> CC: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] again... (win32 logging errors)
>
> Ati Rosselet wrote:
> > I'm still getting a lot of these entries in my eventlog whenever I
> > have a reasonably large amount of logging:
> >
> > Event Type: Error
> > Event Source: PostgreSQL
> > Event Category: None
> > Event ID: 0
> > Date: 10/22/2008
> > Time: 9:36:28 AM
> > User: N/A
> > Computer: ----------
> > Description:
> > could not write to log file: Bad file descriptor
> >
> > production server 8.3.3 (tried with 8.3.4 - same thing), win 2003
> > server. I'd send this to psql-bugs, but I can't figure out how to
> > reproduce it.. and
> > apparently noone else has seen this? Or is noone else running
> > postgres on win2003??? (survey says??)
> >
> > The timing of each appears to be when log is rolled over (size limited
> > to 10MB) and postgres attempts to write a log entry at the same time:
> >
> > Any ideas? help? How to proceed???
>
> Change the log settings to panic and up the size limit. Almost nothing
> gets written to the log and the log never gets full enough to rotate.
> Other than that, you'll need to get visual studio and the source and
> work it out.
>
> Reproducing it is relatively easy - make a function that does raise
> notice and call it a lot. I had one that essentially took out the server.
> http://archives.postgresql.org/pgsql-general/2008-08/msg00615.php
>
> +1 for survey.
>
> klint.
>
> --
> Klint Gore
> Database Manager
> Sheep CRC
> A.G.B.U.
> University of New England
> Armidale NSW 2350
>
> Ph: 02 6773 3789
> Fax: 02 6773 3266
> EMail: kgore4(at)une(dot)edu(dot)au
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

_________________________________________________________________
Stay organized with simple drag and drop from Windows Live Hotmail.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_102008

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruno Baguette 2008-10-27 03:39:03 [PLPGSQL] PERFORM into an EXECUTE allowed ?
Previous Message Klint Gore 2008-10-27 02:11:36 Re: again... (win32 logging errors)

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-10-27 03:02:59 Re: array_agg and array_accum (patch)
Previous Message Klint Gore 2008-10-27 02:11:36 Re: again... (win32 logging errors)