Currently running 8.1.3. Will be upgrading shortly.
-----Original Message-----
From: Scott Marlowe [mailto:smarlowe@g2switchworks.com]
Sent: Thursday, May 25, 2006 1:44 PM
To: Benjamin Krajmalnik
Cc: pgsql-admin@postgresql.org
Subject: RE: [ADMIN] Strange errors in log file
And the postgresql version?
Are you aware of this bug fix:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2313
On Thu, 2006-05-25 at 14:22, Benjamin Krajmalnik wrote:
> This is running on an HP DL360, SCSI RAID1, 2GB RAM, running Windows
> Server 2003.
>
> -----Original Message-----
> From: Scott Marlowe [mailto:smarlowe@g2switchworks.com]
> Sent: Thursday, May 25, 2006 1:20 PM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin@postgresql.org
> Subject: RE: [ADMIN] Strange errors in log file
>
> Not that I'm sure it'll help much, but what OS, server version et.
al.
> are you running?
>
> On Thu, 2006-05-25 at 14:17, Benjamin Krajmalnik wrote:
> > Neither is the case.
> > I have over 60GB of space left, and the database is currently at
about
> > 800Mb.
> > Restarting the service resolves the problem, so it is not a file
> > permissions issue.
> > As I mentioned, I this sems to happen, internmittently, when
> > postgresql.conf is reloaded.
> >
> > -----Original Message-----
> > From: Scott Marlowe [mailto:smarlowe@g2switchworks.com]
> > Sent: Thursday, May 25, 2006 1:14 PM
> > To: Benjamin Krajmalnik
> > Cc: pgsql-admin@postgresql.org
> > Subject: Re: [ADMIN] Strange errors in log file
> >
> > On Thu, 2006-05-25 at 14:00, Benjamin Krajmalnik wrote:
> > > 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
> >
> > You're likely either out of disk space, or someone's changed the
> > permissions on a pgsql directory or file.