Re: Initdb panic: invalid record offset at 0/0 creating - Mailing list pgsql-general

Hello Tom,

We have generated a new rpm as we haven't found a 8.1.0 rpm for IA-64 on
Red Hat Enterprise Linux 4 on the PostGreSQL web site. We have compiled
PostGreSQL v8.1.0 and generated the rpm with the intel compiler "icc".
In the spec file, we have used these options for ./configure :
./configure CC=/opt/intel_cc_80/bin/icc CFLAGS="-no-gcc -O2 -w
-ansi_alias -D__ICC".

When we have tried to install the rpm generated, we have got an error an
the shared library "libimf.so.6" of the intel compiler. Consequently, we
have launched the command : rpm -ivh --nodeps file.rpm
The error was

error: Failed dependencies:

        libimf.so.6()(64bit) is needed by postgresql-8.1.1-1.ia64

and has occured because the intel compiler wasn't installed from an rpm
but from a tar.gz file.


Once PostGreSQL installed, we have tried to launch the "initdb" and got
the error :
DEBUG:  invoking IpcMemoryCreate(size=11083776)
LOG:  database system was shut down at 2006-01-20 07:13:57 CET
LOG:  invalid primary checkpoint link in control file
PANIC:  invalid record offset at 0/0
child process was terminated by signal 6
initdb: removing contents of data directory "/home/PGS/V811"


In the ".bash_profile"  file of the user used to launched initdb, we
have set the following variables :
PGDIR=/opt/pg_811/PGHOME
PGDATA=/home/PGS/V811
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:.
PATH=$PGDIR/bin:$PATH
LD_LIBRARY_PATH=$PGDIR/lib:/opt/intel_cc_80/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
export  PGDIR PGDATA PATH


I have launched the commands you have asked, and you will find below the
results :

*[pg_811@bt3 ~]$ initdb --noclean*
Running in noclean mode.  Mistakes will not be cleaned up.
The files belonging to this database system will be owned by user "pg_811".
This user must also own the server process.

The database cluster will be initialized with locale en_US.UTF-8.
The default database encoding has accordingly been set to UTF8.

fixing permissions on existing directory /home/PGS/V811 ... ok
creating directory /home/PGS/V811/global ... ok
creating directory /home/PGS/V811/pg_xlog ... ok
creating directory /home/PGS/V811/pg_xlog/archive_status ... ok
creating directory /home/PGS/V811/pg_clog ... ok
creating directory /home/PGS/V811/pg_subtrans ... ok
creating directory /home/PGS/V811/pg_twophase ... ok
creating directory /home/PGS/V811/pg_multixact/members ... ok
creating directory /home/PGS/V811/pg_multixact/offsets ... ok
creating directory /home/PGS/V811/base ... ok
creating directory /home/PGS/V811/base/1 ... ok
creating directory /home/PGS/V811/pg_tblspc ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
creating configuration files ... ok
creating template1 database in /home/PGS/V811/base/1 ... PANIC:  invalid
record offset at 0/0
child process was terminated by signal 6
initdb: data directory "/home/PGS/V811" not removed at user's request
[pg_811@bt3 ~]$

---------------------------------------------------------------------------------------------------

*[pg_811@bt3 V811]$ pg_controldata $PGDATA*
pg_control version number:            812
Catalog version number:               200510211
Database system identifier:           4886687050337353727
Database cluster state:               shut down
pg_control last modified:             Fri 20 Jan 2006 04:21:31 PM CET
Current log file ID:                  0
Next log file segment:                1
Latest checkpoint location:           0/20
Prior checkpoint location:            0/0
Latest checkpoint's REDO location:    0/20
Latest checkpoint's UNDO location:    0/20
Latest checkpoint's TimeLineID:       1
Latest checkpoint's NextXID:          3
Latest checkpoint's NextOID:          10000
Latest checkpoint's NextMultiXactId:  1
Latest checkpoint's NextMultiOffset:  0
Time of latest checkpoint:            Fri 20 Jan 2006 04:21:31 PM CET
Maximum data alignment:               8
Database block size:                  8192
Blocks per segment of large relation: 131072
Bytes per WAL segment:                16777216
Maximum length of identifiers:        64
Maximum columns in an index:          32
Date/time type storage:               floating-point numbers
Maximum length of locale name:        128
LC_COLLATE:                           en_US.UTF-8
LC_CTYPE:                             en_US.UTF-8
[pg_811@bt3 V811]$

---------------------------------------------------------------------------------------------------

*[pg_811@bt3 V811]$ od -x $PGDATA/pg_xlog/000000010000000000000000*
0000000 d05d 0002 0001 0000 0000 0000 0000 0000
0000020 ffff 43db fffb 43d0 0000 0100 0000 0000
0000040 68f5 5b77 0000 0000 0000 0000 0000 0000
0000060 0050 0000 0030 0000 0000 0000 0000 0000
0000100 0000 0000 0020 0000 0000 0000 0020 0000
0000120 0001 0000 0003 0000 2710 0000 0001 0000
0000140 0000 0000 0000 0000 fffb 43d0 0000 0000
0000160 0000 0000 0000 0000 0000 0000 0000 0000
*
100000000

The result file is about 16MB... I don't post it, but I can do an
archive of this file if you want...

I hope you would explain us with initdb fails.

Thank you for your help.
Regards,
Alexandra DANTE



Tom Lane a écrit :

>DANTE ALEXANDRA <ALEXANDRA.DANTE@BULL.NET> writes:
>
>
>>we recompiled and built an RPM on IA64, release of postgresql : 8.1.1,
>>on RHEL4 update 2,
>>the installation of the rpm seem to be good,
>>we install with --nodeps , and we indicate the path for the library's
>>/opt/intel_cc_80/lib
>>but when trying to init with the user account "pg_811",
>>it fall in panic,
>>
>>
>
>Whose RPM did you use, and did you use any special options?  Why did
>you feel it necessary to use --nodeps?
>
>
>
>>DEBUG:  invoking IpcMemoryCreate(size=11083776)
>>LOG:  database system was shut down at 2006-01-20 07:13:57 CET
>>LOG:  invalid primary checkpoint link in control file
>>PANIC:  invalid record offset at 0/0
>>child process was terminated by signal 6
>>
>>
>
>Hm, I wonder what's getting written into the files ... would you run
>initdb with --noclean and then post the results of
>    * pg_controldata $PGDATA
>    * od -x $PGDATA/pg_xlog/000000010000000000000000
>(I'm assuming that the file is there and od won't produce much output
>... if it comes to megabytes don't post it ...)
>
>            regards, tom lane
>
>
>