Thread: Application EventLog: could not write to log file: Bad file descriptor
Using postgresql 8.3 on windows 2003 server. I keep seeing this message in my system log. Checking the times, it seems to coincide with a log rollover each time, almost as though the db were trying to log something at precisely the same time as it is closing access to the old file, and before opening the new file.. and so fails to write.. does this make sense? has anyone else seen this? Solutions? Ideas? I reduced logging, and disabled the debugging plugin (still don't know how that got enabled.. I must have missed something on the install). Hope that helps....
Any ideas what is causing this error to be logged?
Cheers
Ati
Any ideas what is causing this error to be logged?
Cheers
Ati
Re: Application EventLog: could not write to log file: Bad file descriptor
From
Alvaro Herrera
Date:
Ati Rosselet escribió: > Using postgresql 8.3 on windows 2003 server. I keep seeing this message in > my system log. Checking the times, it seems to coincide with a log > rollover each time, almost as though the db were trying to log something at > precisely the same time as it is closing access to the old file, and before > opening the new file.. and so fails to write.. does this make sense? has > anyone else seen this? Solutions? Ideas? I reduced logging, and disabled > the debugging plugin (still don't know how that got enabled.. I must have > missed something on the install). Hope that helps.... Do you have CSV logging enabled? -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
Re: Application EventLog: could not write to log file: Bad file descriptor
From
"Ati Rosselet"
Date:
sorry, forgot to cc: to the group..
To: Alvaro Herrera <alvherre@commandprompt.com>
not as far as I can tell... I have log_destination='stderr'. unless csv logging is enabled in another location?
Since I disabled the following line:
shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll'
and changed logging from 'all' to 'mod'
I have not seen the error, although that may just be because the amount logged is reduced drastically
(from verbose due to logging all selects - to pretty much zero for normal website usage - very few modifying queries:))
Thanks.
Ati
not as far as I can tell... I have log_destination='stderr'. unless csv logging is enabled in another location?
Since I disabled the following line:
shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll'
and changed logging from 'all' to 'mod'
I have not seen the error, although that may just be because the amount logged is reduced drastically
(from verbose due to logging all selects - to pretty much zero for normal website usage - very few modifying queries:))
Thanks.
Ati
On Fri, Jun 6, 2008 at 11:24 PM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
Ati Rosselet escribió:Do you have CSV logging enabled?> Using postgresql 8.3 on windows 2003 server. I keep seeing this message in
> my system log. Checking the times, it seems to coincide with a log
> rollover each time, almost as though the db were trying to log something at
> precisely the same time as it is closing access to the old file, and before
> opening the new file.. and so fails to write.. does this make sense? has
> anyone else seen this? Solutions? Ideas? I reduced logging, and disabled
> the debugging plugin (still don't know how that got enabled.. I must have
> missed something on the install). Hope that helps....
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
Re: Application EventLog: could not write to log file: Bad file descriptor
From
Alvaro Herrera
Date:
Ati Rosselet escribió: > sorry, forgot to cc: to the group..To: Alvaro Herrera < > alvherre@commandprompt.com> > > > not as far as I can tell... I have log_destination='stderr'. unless csv > logging is enabled in another location? No, that should mean it's disabled. > Since I disabled the following line: > shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' > and changed logging from 'all' to 'mod' > I have not seen the error, although that may just be because the amount > logged is reduced drastically > (from verbose due to logging all selects - to pretty much zero for normal > website usage - very few modifying queries:)) Yes, the problem is probably not gone but just made rarer. ISTM it would be good to debug it. The Windows logger code does use two threads for the logging (as opposed to everywhere else which uses a single process) so it's quite possible that the locking is bogus somewhere. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
Re: Application EventLog: could not write to log file: Bad file descriptor
From
"Ati Rosselet"
Date:
Well.. I guess I'll just have to hope it pops up rarely enough to not be a problem since I really don't have the capacity to try to debug postgres code for the foreseeable future :) Should I log a bugreport, or a suspected bug report (if such an animal exists...)? :)
Cheers
Ati
Cheers
Ati
On Mon, Jun 9, 2008 at 5:11 PM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
Ati Rosselet escribió:> sorry, forgot to cc: to the group..To: Alvaro Herrera <No, that should mean it's disabled.
> alvherre@commandprompt.com>
>
>
> not as far as I can tell... I have log_destination='stderr'. unless csv
> logging is enabled in another location?Yes, the problem is probably not gone but just made rarer. ISTM it
> Since I disabled the following line:
> shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll'
> and changed logging from 'all' to 'mod'
> I have not seen the error, although that may just be because the amount
> logged is reduced drastically
> (from verbose due to logging all selects - to pretty much zero for normal
> website usage - very few modifying queries:))
would be good to debug it. The Windows logger code does use two threads
for the logging (as opposed to everywhere else which uses a single
process) so it's quite possible that the locking is bogus somewhere.
--
Re: Application EventLog: could not write to log file: Bad file descriptor
From
"Ati Rosselet"
Date:
yup.. still there.. just reduced frequency... just got the first one since reducing the logging... darn.. :(
I checked the fixes for the new release, but no mention of it. Does this mean no-one else has run into this? Or am I the only idiot running postgres on windows? :))
Cheers
Ati
I checked the fixes for the new release, but no mention of it. Does this mean no-one else has run into this? Or am I the only idiot running postgres on windows? :))
Cheers
Ati
On Mon, Jun 9, 2008 at 5:11 PM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
Ati Rosselet escribió:> sorry, forgot to cc: to the group..To: Alvaro Herrera <No, that should mean it's disabled.
> alvherre@commandprompt.com>
>
>
> not as far as I can tell... I have log_destination='stderr'. unless csv
> logging is enabled in another location?Yes, the problem is probably not gone but just made rarer. ISTM it
> Since I disabled the following line:
> shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll'
> and changed logging from 'all' to 'mod'
> I have not seen the error, although that may just be because the amount
> logged is reduced drastically
> (from verbose due to logging all selects - to pretty much zero for normal
> website usage - very few modifying queries:))
would be good to debug it. The Windows logger code does use two threads
for the logging (as opposed to everywhere else which uses a single
process) so it's quite possible that the locking is bogus somewhere.
--