pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Benjamin Krajmalnik <kraj@illumen.com>
To: pgsql-admin@postgresql.org
Subject: Strange errors in log file
Date: Thu, 25 May 2006 13:00:33 -0600
Message-ID: <8511B4970E0D124898E973DF496F9B432516DD@stash.stackdump.local> (raw)

I am running PostgreSQL 8.1.3/Win

 

Earlier yesterday, it appeared that the server stopped responding.

I went through the log files and noticed the following type of entries.

 

 

22462 is the filenode for my database.  I could not find what the other
two are.

 

 

2006-05-24 12:16:35 LOG:  could not fsync segment 0 of relation
1663/22462/18193301: Permission denied

 

2006-05-24 12:16:35 ERROR:  storage sync failed on magnetic disk:
Permission denied

 

Today, I managed to get the server to act up in the same manner.

Using pgAdmin, I had turned on logging to isolate a problem coming on
from a query being autogenetrated by a monitoring system.

 

When I turned off the logging, saved the file, and sent a trigger to to
reload the config it happened again.

 

The log entries for that chain of events are as follows:

 

2006-05-25 12:42:53 LOG:  statement: SELECT pg_reload_conf()

2006-05-25 12:42:53 LOG:  duration: 31.000 ms

2006-05-25 12:42:53 LOG:  received SIGHUP, reloading configuration files

2006-05-25 12:42:53 LOG:  duration: 422.000 ms

2006-05-25 12:42:53 LOG:  could not fsync segment 0 of relation
1663/22462/18329383: Permission denied

2006-05-25 12:42:53 ERROR:  storage sync failed on magnetic disk:
Permission denied

2006-05-25 12:42:54 LOG:  could not fsync segment 0 of relation
1663/22462/18329383: Permission denied

 

 

 

Thanks in advance.

 

Regards,

 

Benjamin

 

view thread (10+ messages)  latest in thread

Message-ID: <8511B4970E0D124898E973DF496F9B432516DD@stash.stackdump.local>
Permalink:  ../8511B4970E0D124898E973DF496F9B432516DD@stash.stackdump.local/
Also on:    postgresql.org/message-id/8511B4970E0D124898E973DF496F9B432516DD@stash.stackdump.local

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: kraj@illumen.com
  Subject: Re: Strange errors in log file
  In-Reply-To: <8511B4970E0D124898E973DF496F9B432516DD@stash.stackdump.local>
  References: <8511B4970E0D124898E973DF496F9B432516DD@stash.stackdump.local>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox