Обсуждение: Write to transaction logs, Permission Denied

Hi

I am running:
Intel P4, 512Mb Memory, 20Gb Hard Drive
Windows2000 Pro, Service Pack 2
PostgreSQL 7.2.1-2
cygwin dll 1.3.12-2
ipc 1.11-1

The problem is, sometimes the server dies and when I look at the log,
this is what I get. (see below)

We have it running on two identical machines and both have the same
problem. Both were running without any problems up until a few weeks
ago.

We are running with fsync off, does this have anything to do with this?

Does PostgreSQL 7.2.1 have an issue with recyclying the transaction logs?
Could this problem be network related?
Should we upgrade cygwin and postgresql?

Thanks you

Colin


DEBUG:  recycled transaction log file 0000000400000015
DEBUG:  recycled transaction log file 0000000400000016
DEBUG:  recycled transaction log file 0000000400000017
ERROR:  cannot read block 0 of modem_pkey: Permission denied
NOTICE:  Error occurred while executing PL/pgSQL function modem_updatesignalstrength
NOTICE:  line 7 at SQL statement
ERROR:  cannot read block 0 of modem_pkey: Permission denied
NOTICE:  Error occurred while executing PL/pgSQL function modem_updatesignalstrength
NOTICE:  line 7 at SQL statement
DEBUG:  mdblindwrt: write() failed: Permission denied
ERROR:  cannot write block 262 of 16557/16572 blind: Permission denied
NOTICE:  Error occurred while executing PL/pgSQL function modem_updatesignalstrength
NOTICE:  line 7 at SQL statement
ERROR:  cannot extend messages: Permission denied.
    Check free disk space.
FATAL 2:  write of log file 4, segment 24, offset 12312576 failed: Permission denied
DEBUG:  server process (pid 2324) exited with exit code 2
DEBUG:  terminating any other active server processes
NOTICE:  Message from PostgreSQL backend:
    The Postmaster has informed me that some other backend
    died abnormally and possibly corrupted shared memory.
    I have rolled back the current transaction and am
    going to terminate your database system connection and exit.
    Please reconnect to the database system and repeat your query.
NOTICE:  Message from PostgreSQL backend:
    The Postmaster has informed me that some other backend
    died abnormally and possibly corrupted shared memory.
    I have rolled back the current transaction and am
    going to terminate your database system connection and exit.
    Please reconnect to the database system and repeat your query.
NOTICE:  Message from PostgreSQL backend:
    The Postmaster has informed me that some other backend
    died abnormally and possibly corrupted shared memory.
    I have rolled back the current transaction and am
    going to terminate your database system connection and exit.
    Please reconnect to the database system and repeat your query.
DEBUG:  all server processes terminated; reinitializing shared memory and semaphores
IpcMemoryCreate: shmget(key=5432001, size=2048000, 03600) failed: Not enough core

This error usually means that PostgreSQL's request for a shared
memory segment exceeded available memory or swap space.
To reduce the request size (currently 2048000 bytes), reduce
PostgreSQL's shared_buffers parameter (currently 100) and/or
its max_connections parameter (currently 50).

The PostgreSQL Administrator's Guide contains more information about
shared memory configuration.

Colin,

On Tue, Feb 11, 2003 at 01:38:54PM +0200, Colin Mangiagalli wrote:
> I am running:
> PostgreSQL 7.2.1-2
             ^^^^^^^

If you are really running the above, then you already have the
InstallXLogFileSegment() rename() patch:

    http://cygwin.com/ml/cygwin-announce/2002-06/msg00003.html

Maybe there is another link()/unlink() that needs to be replaced by a
rename()?

> Should we upgrade cygwin and postgresql?

Sounds like a reasonable thing to try.

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

Colin,

Please keep your replies on-list.  Isn't your concerns below better
answered by many instead of one?

On Wed, Feb 12, 2003 at 12:57:38PM +0200, Colin Mangiagalli wrote:
> Thanks for the response.

You are welcome.

> I downloaded the latest cygwin (dll 1.3.20-1 & 7.3.1-1) and also ipc
> 1.13-2 and 7.3 jdbc driver

Did the above solve your log recycle problem?

> I installed it and got everything working ok.

Good.

> My concern is, should we even be using PostgreSQL under Windows, as a
> production database and how stable is this new configuration going to
> be.

Unfortunately, I can't really answer the above.  I got involved with
Cygwin PostgreSQL in a previous life that ended with the dot com crash.
Hence, I never had the chance to experience Cygwin PostgreSQL in a real
production environment.

One poster reported good success with Cygwin PostgreSQL for about 30
users under Windows NT or 2000.  Other NT/2000 users reported positively
for what I would consider medium sized installations.

Note that PostgreSQL 7.4 will support a native Win32 port.  Maybe you
can use the Cygwin version for the time being and then switch over, if
necessary?

> I keep seeing on the mailing list, "cygwin keeps crashing, etc"
>
> The only trouble we have had up until now is the database going
> down while recycling the logs, which hopefully will not happen
> anymore in 7.3.1
>
> Otherwise, the database has been working fine.
>
> The company that I work for is now getting really worried about the
> fact that we used PostgreSQL under Windows, because the clients are
> not to happy at the moment.
>
> Thanks a lot for your time.

You are welcome.

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6