Error msgs from PostgreSQL server : specified item offset is too large, failed to add item to the page - Mailing list pgsql-novice

From Rajan Bhide
Subject Error msgs from PostgreSQL server : specified item offset is too large, failed to add item to the page
Date
Msg-id FF851C7EEB75954F9BCFB5CA117AB1EC6742DE@delta.nulinkinc.com
Whole thread Raw
Responses Re: Error msgs from PostgreSQL server : specified item offset is too large, failed to add item to the page
List pgsql-novice
Hello All,

I am getting following error msgs from my PostgreSQL server:
I am using PostgreSQL server as my database server (version 7.4.1)
After getting the error messages, the PostgreSQL server terminates all the client connection.


Following are the last few messages from the logfile:

====================================================================================
LOG:  recycled transaction log file "000000800000007F"
LOG:  recycled transaction log file "0000008000000080"
WARNING:  specified item offset is too large
PANIC:  failed to add item to the page for "transid_req_idx"
STATEMENT:  INSERT INTO cdr VALUES(18214842419009354, 3232253462, 0, 0, 15, 2, 25125, 1768131,
'«\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000ü{\\000ºµ·€ƒT\\000—‡X8ò¤‚208.231.231.1…Z+㦂208.231.232.2‡
mip.comˆñ!© ‚30.35.53.202‹ÿ¬301"rs–@H†@H‚"rs–@H†@Hƒ\\000ƒ„g…†
(3-\\000(3-\\000Ž<‘+•–‘‰gE•$—\\000˜\\000›Tð€\\000¹µ¶€ƒT\\000—‡X8ñ¤‚208.231.231.1…Z+⦂208.231.232.2‡
mip.comˆñ!© ‚30.31.53.176‹ÿ¬200"rs–@H†@H‚"rs–@H†@Hƒ\\000„\\000…†   (3-\\000
(3-\\000Ž<‘+•–‘‰gE•—\\000˜\\000›TðZ+ã\\000\\000\\000+Z+â\\000\\000\\000+');
LOG:  server process (PID 2049) was terminated by signal 6
LOG:  terminating any other active server processes
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
FATAL:  the database system is in recovery mode
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted at 2004-05-28 01:19:51 GMT
LOG:  checkpoint record is at 80/8435C038
LOG:  redo record is at 80/8400E238; undo record is at 0/0; shutdown FALSE
LOG:  next transaction ID: 124183952; next OID: 237863670
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  redo starts at 80/8400E238
LOG:  record with zero length at 80/86810CE0
LOG:  redo done at 80/86810CB8
LOG:  recycled transaction log file "0000008000000081"
LOG:  recycled transaction log file "0000008000000082"
LOG:  recycled transaction log file "0000008000000083"
LOG:  database system is ready
====================================================================================


PostgreSQL info:

du -k data/
4655    data/base/1
4655    data/base/17141
1       data/base/234353116/pgsql_tmp
37401   data/base/234353116
46712   data/base
130     data/global
131137  data/pg_xlog
31282   data/pg_clog
209279  data


System Info:
uname -a
SunOS firerunner 5.9 Generic_112233-01 sun4u sparc SUNW,UltraAX-i2

prtconf | grep Memory
Memory size: 1024 Megabytes


swap -l
swapfile             dev  swaplo blocks   free
/dev/dsk/c1t0d0s1   32,1      16 4194800 4161392

df -k
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/dsk/c1t0d0s0    2326681 2172260  107888    96%    /
/proc                      0       0       0     0%    /proc
mnttab                     0       0       0     0%    /etc/mnttab
fd                         0       0       0     0%    /dev/fd
swap                 2822232     168 2822064     1%    /var/run
swap                 2822504     440 2822064     1%    /tmp
/dev/md/dsk/d0       274620142 8353182 263520759     4%    /cvserver
pasta:/home          339066240 259172084 76449428    78%    /home


Content added to /etc/system

 set msgsys:msginfo_msgmnb=65536
 set msgsys:msginfo_msgtql=1024

 set shmsys:shminfo_shmmax=0x2000000
 set shmsys:shminfo_shmmin=1
 set shmsys:shminfo_shmmni=256
 set shmsys:shminfo_shmseg=256

 set semsys:seminfo_semmap=256
 set semsys:seminfo_semmni=512
 set semsys:seminfo_semmns=512
 set semsys:seminfo_semmsl=32



Can anybody help me out to understand and debug this problem?

Thanks,
Rajan Bhide

pgsql-novice by date:

Previous
From: Robert Morgan
Date:
Subject: Date
Next
From: xier@in.tum.de
Date:
Subject: PostgreSQL delete the blank in the end of the String automatically. how can I avoid it?