Thread: Data corruption
Hi all,
We have a database installed on Intel Xeon (Dell) and running on postgreSQL 8.1.
And the database couldn't start. Here is the logfile of what happend:
2006-11-14 00:28:38 PANIC: could not write to log file 6, segment 239 at offset 6430720, length 16384: Permission denied
2006-11-14 00:28:38 CONTEXT: writing block 557 of relation 1663/16403/985708
2006-11-14 00:28:38 STATEMENT: VACUUM client
abnormal program termination
2006-11-14 00:28:38 LOG: server process (PID 2868) was terminated by signal 3
2006-11-14 00:28:38 LOG: terminating any other active server processes
2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process
2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process
2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process
2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process
2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process
2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process
2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process
2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process
2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process
2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process
2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2006-11-14 00:28:38 LOG: all server processes terminated; reinitializing
2006-11-14 00:28:38 LOG: database system was interrupted at 2006-11-14 00:17:21 Eastern Standard Time
2006-11-14 00:28:38 LOG: checkpoint record is at 6/EEE1ED60
2006-11-14 00:28:38 LOG: redo record is at 6/EEE1ED60; undo record is at 0/0; shutdown FALSE
2006-11-14 00:28:38 LOG: next transaction ID: 13802854; next OID: 4807439
2006-11-14 00:28:38 LOG: next MultiXactId: 1; next MultiXactOffset: 0
2006-11-14 00:28:38 LOG: database system was not properly shut down; automatic recovery in progress
2006-11-14 00:28:38 LOG: redo starts at 6/EEE1EDA8
2006-11-14 00:28:40 LOG: could not read from log file 6, segment 239, offset 0: Permission denied
2006-11-14 00:28:40 LOG: redo done at 6/EEFFE740
2006-11-14 00:28:43 LOG: database system is ready
2006-11-14 00:28:43 LOG: transaction ID wrap limit is 2147484148, limited by database "postgres"
2006-11-14 01:50:58 LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2006-11-14 01:50:58 LOG: unexpected EOF on client connection
2006-11-14 01:51:18 ERROR: xlog flush request 6/EF5FB6B8 is not satisfied --- flushed only to 6/EEFFE7D0
2006-11-14 01:51:18 CONTEXT: writing block 21 of relation 1663/16403/2696
2006-11-14 01:51:19 ERROR: xlog flush request 6/EF5F8C50 is not satisfied --- flushed only to 6/EEFFE7D0
2006-11-14 01:51:19 CONTEXT: writing block 384 of relation 1663/16403/2619
Could someone tell us the cause of this. Or it's simply the command Vacuum client who caused all of this
Thanks
On Tue, 2006-11-14 at 13:34 -0500, Ardian Xharra wrote:
> Hi all,
>
> We have a database installed on Intel Xeon (Dell) and running on
> postgreSQL 8.1.
> And the database couldn't start. Here is the logfile of what happend:
>
> 2006-11-14 00:28:38 PANIC: could not write to log file 6, segment 239
> at offset 6430720, length 16384: Permission denied
>
Are you running PostgreSQL as a user other than the one that owns the
data directory? Did the filesystem somehow get mounted in RO mode?
Regards,
Jeff Davis
----- Original Message ----- From: "Jeff Davis" <pgsql@j-davis.com> To: "Ardian Xharra" <axharra@boxxo.info> Cc: "postgreSQL postgreSQL" <pgsql-general@postgresql.org> Sent: Tuesday, November 14, 2006 2:12 PM Subject: Re: [GENERAL] Data corruption > On Tue, 2006-11-14 at 13:34 -0500, Ardian Xharra wrote: >> Hi all, >> >> We have a database installed on Intel Xeon (Dell) and running on >> postgreSQL 8.1. >> And the database couldn't start. Here is the logfile of what happend: >> >> 2006-11-14 00:28:38 PANIC: could not write to log file 6, segment 239 >> at offset 6430720, length 16384: Permission denied >> > > Are you running PostgreSQL as a user other than the one that owns the > data directory? Did the filesystem somehow get mounted in RO mode? > > Regards, > Jeff Davis I'm running under Windows. PostgreSQL runs through user postgres created during the installation. The filesystem is NTFS > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.409 / Virus Database: 268.14.5/533 - Release Date: 13/11/2006 > >
Do you have antivirus software installed on the server? I seem to recall A/V software being a common source of "permissiondenied" errors when running Postgresql on Windows. Regards, Shelby Cain ----- Original Message ---- From: Ardian Xharra <axharra@boxxo.info> To: Jeff Davis <pgsql@j-davis.com> Cc: postgreSQL postgreSQL <pgsql-general@postgresql.org> Sent: Tuesday, November 14, 2006 1:36:48 PM Subject: Re: [GENERAL] Data corruption I'm running under Windows. PostgreSQL runs through user postgres created during the installation. The filesystem is NTFS ____________________________________________________________________________________ Sponsored Link Mortgage rates near 39yr lows. $420k for $1,399/mo. Calculate new payment! www.LowerMyBills.com/lre
Yes, the Symantec Antivirus. We are going to modify A/V to not scan the database Thanks for your time ----- Original Message ----- From: "Shelby Cain" <alyandon@yahoo.com> To: "Ardian Xharra" <axharra@boxxo.info> Cc: "postgreSQL postgreSQL" <pgsql-general@postgresql.org> Sent: Wednesday, November 15, 2006 11:38 AM Subject: Re: [GENERAL] Data corruption Do you have antivirus software installed on the server? I seem to recall A/V software being a common source of "permission denied" errors when running Postgresql on Windows. Regards, Shelby Cain ----- Original Message ---- From: Ardian Xharra <axharra@boxxo.info> To: Jeff Davis <pgsql@j-davis.com> Cc: postgreSQL postgreSQL <pgsql-general@postgresql.org> Sent: Tuesday, November 14, 2006 1:36:48 PM Subject: Re: [GENERAL] Data corruption I'm running under Windows. PostgreSQL runs through user postgres created during the installation. The filesystem is NTFS ____________________________________________________________________________________ Sponsored Link Mortgage rates near 39yr lows. $420k for $1,399/mo. Calculate new payment! www.LowerMyBills.com/lre -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.14.5/534 - Release Date: 14/11/2006