X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 851209F9B01 for ; Thu, 25 May 2006 17:12:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 27521-07 for ; Thu, 25 May 2006 17:12:42 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from stash.illumen.com (unknown [64.207.29.137]) by postgresql.org (Postfix) with ESMTP id B66B19F94EA for ; Thu, 25 May 2006 17:12:42 -0300 (ADT) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: Strange errors in log file X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Thu, 25 May 2006 14:12:41 -0600 Message-ID: <8511B4970E0D124898E973DF496F9B432516E5@stash.stackdump.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ADMIN] Strange errors in log file thread-index: AcaANbkMtNHbpkEzRLi0Q47CPJgVVQAACGCw From: "Benjamin Krajmalnik" To: "Tom Lane" Cc: "Scott Marlowe" , X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/364 X-Sequence-Number: 21896 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]=20 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=20 "Benjamin Krajmalnik" 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