Обсуждение: Strange errors in log file
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
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.
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.
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.
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.
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.
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.
Let's hope that's the fix. Note that I'd probably not run a high load PostgreSQL server on Windows just yet myself. But somebody's gotta be the test case. :) On Thu, 2006-05-25 at 14:48, Benjamin Krajmalnik wrote: > 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.
"Benjamin Krajmalnik" <kraj@illumen.com> writes:
> Restarting the service resolves the problem, so it is not a file
> permissions issue.
It sure *looks* like a file permissions issue.
FWIW, I see that port/win32/error.c translates these Windows
error codes to EACCES:
ERROR_ACCESS_DENIED
ERROR_CURRENT_DIRECTORY
ERROR_LOCK_VIOLATION
ERROR_SHARING_VIOLATION
ERROR_NETWORK_ACCESS_DENIED
ERROR_CANNOT_MAKE
ERROR_FAIL_I24
ERROR_DRIVE_LOCKED
ERROR_SEEK_ON_DEVICE
ERROR_NOT_LOCKED
ERROR_LOCK_FAILED
It would appear that the underlying problem is one of these.
regards, tom lane
If it were a file permissions issue, I would suspect it would be an all
or nothing situation, would you not? As I mentioned, the strange thing
is that once you stop and restart the service everything is fine, and it
appears to be triggered by sometimes reloading the config file.
I have gone on and explicitly added the postgresql service account and
given it full access rights to the directory.
Maybe this will keep it from recurring.
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Thursday, May 25, 2006 1:59 PM
To: Benjamin Krajmalnik
Cc: Scott Marlowe; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Strange errors in log file
"Benjamin Krajmalnik" <kraj@illumen.com> writes:
> Restarting the service resolves the problem, so it is not a file
> permissions issue.
It sure *looks* like a file permissions issue.
FWIW, I see that port/win32/error.c translates these Windows
error codes to EACCES:
ERROR_ACCESS_DENIED
ERROR_CURRENT_DIRECTORY
ERROR_LOCK_VIOLATION
ERROR_SHARING_VIOLATION
ERROR_NETWORK_ACCESS_DENIED
ERROR_CANNOT_MAKE
ERROR_FAIL_I24
ERROR_DRIVE_LOCKED
ERROR_SEEK_ON_DEVICE
ERROR_NOT_LOCKED
ERROR_LOCK_FAILED
It would appear that the underlying problem is one of these.
regards, tom lane