Re: Checkpoint request failed, permission denied

They look right to me. Below are the permissions and process list. I ended
up rebuilding the data directory since it was just a test database, so far
so good. The permissions and setup were exactly the same before I did this.

I was repeatedly dropping and rebuilding this database, could that have
caused this? I also had some user processes stuck so frequently I would
restart postgresql as well.

Cory

[root(at)ittdev1 data]# ls -l pg_xlog
total 16416
-rw------- 1 postgres postgres 16777216 Sep 13 23:16
000000010000000000000000
drwx------ 2 postgres postgres 4096 Sep 13 22:19 archive_status
[root(at)ittdev1 data]# ps -ef|grep postgres
postgres 25752 1 0 Sep13 ? 00:00:00 /usr/bin/postmaster -p 5432
-D /var/lib/pgsql/data
postgres 25754 25752 0 Sep13 ? 00:00:00 postgres: logger process
postgres 25756 25752 0 Sep13 ? 00:00:00 postgres: writer process
postgres 25757 25752 0 Sep13 ? 00:00:00 postgres: wal writer process
postgres 25758 25752 0 Sep13 ? 00:00:00 postgres: autovacuum
launcher process
postgres 25759 25752 0 Sep13 ? 00:00:00 postgres: stats collector
process
postgres 26877 25752 0 00:22 ? 00:00:00 postgres: itt itt_dev
127.0.0.1(49593) idle
postgres 26879 25752 0 00:22 ? 00:00:00 postgres: itt itt_dev
127.0.0.1(49595) idle

> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Date: Mon, 14 Sep 2009 10:29:54 -0400
> To: Cory Isaacson <cory(dot)isaacson(at)compuflex(dot)com>
> Cc: <pgsql-general(at)postgresql(dot)org>
> Subject: Re: [GENERAL] Checkpoint request failed, permission denied
>
> Cory Isaacson <cory(dot)isaacson(at)compuflex(dot)com> writes:
>> When I try and manually perform a checkpoint with version 8.3 on CentOS 5 I
>> get this error:
>
>> ERROR: could not link file "pg_xlog/000000010000000000000000" to
>> "pg_xlog/000000010000000000000002" (initialization of log file 0, segment
>> 2): Permission denied
>
>> Any ideas what is causing this? The pg_xlog dir is owned by the postgres
>> user, as are the log files. Also I have temporarily disabled SELinux to make
>> sure that is not causing it.
>
> It's very hard to see how that could be anything except an
> ownership/permissions problem on the pg_xlog directory. Are you sure
> the directory is mode 700 as well as being owned by postgres?
> (For that matter, are you sure the postmaster is running as postgres?)
> Are you *really* sure selinux is disabled?
>
> regards, tom lane