Re: PANIC: could not write to log file 0

isaiah82(at)gmail(dot)com wrote:

> 2008-07-23 23:06:16 PANIC: could not write to log file 0, segment 29
> at offset 4915200, length 16384: Permission denied
>
> 2008-07-23 23:06:16 STATEMENT: UPDATE Host_Users SET
> User_Failed_Login_Count = 0 WHERE (UserID = 4)
>
> This application has requested the Runtime to terminate it in an
> unusual way.
> Please contact the application's support team for more information.

I guess you're using Windows, then.

I don't suppose there's a virus scanner installed? Reports here suggest
that they cause a *lot* of problems, even if you set them to ignore
PostgreSQL.

Have you checked that the PostgreSQL data directory is in fact writable
by the user/role PostgreSQL runs as? Check ACLs and also make sure there
aren't any read-only flags set.

Information such as which version of Windows you're using, what
filesystem type the database is on, details of the ACLs set on the
PostgreSQL data directory and pg_xlog subdirectory, etc would also be
helpful.

> 2008-07-23 23:06:16 LOG: server process (PID 2100) was terminated by
> signal 3

On a UNIX machine that's SIGQUIT. Since PostgreSQL 8.1 used Cygwin for
Windows support I guess it's probably SIGQUIT there, too.

--
Craig Ringer