Skip site navigation (1) Skip section navigation (2)

"make check" failures -- PG 8.2 and 8.1

From: Brian Wipf <brian(at)clickspace(dot)com>
To: Brian Wipf <brian(at)shoptoit(dot)ca>
Cc: pgsql-ports(at)postgresql(dot)org
Subject: "make check" failures -- PG 8.2 and 8.1
Date: 2006-12-13 16:50:47
Message-ID: 2C6FCFC6-47F8-49C1-99AF-3DBF61B0D9BA@clickspace.com (view raw or flat)
Thread:
Lists: pgsql-ports
PostgreSQL 8.2.0 is randomly failing "make check" on our SUSE Linux  
10.1 box. Sometimes it goes through saying all 103 tests passed; more  
often though, I get an error of which I've included some below. A  
PostgreSQL 8.1.5 database on this same machine has been running for  
over a month in production AFAICT flawlessly, although running "make  
check" in the 8.1.5 source directory gives similar random errors.

$ uname -a
Linux hulk4 2.6.16.21-0.25-default #2 SMP Wed Oct 18 15:27:44 MDT  
2006 x86_64 x86_64 x86_64 GNU/Linux

$ make --version
GNU Make 3.80

$ gcc --version
gcc (GCC) 4.1.0 (SUSE Linux)

If anyone has any advice as to what might be causing these errors or  
what I might do to ascertain the problem, I would greatly appreciate  
it. Please let me know if I can provide any further information that  
would be helpful.

Thanks,

Brian Wipf
<brian(at)clickspace(dot)com>

$ ./configure
$ make
$ make check
...
...
============== initializing database system           ==============

pg_regress: initdb failed
Examine ./log/initdb.log for the reason.
Command was: "/usr/local/src/postgresql-8.2.0/src/test/regress/./ 
tmp_check/install//usr/local/pgsql/bin/initdb" -D "/usr/local/src/ 
postgresql-8.2.0/src/test/regress/./tmp_check/data" -L "/usr/local/ 
src/postgresql-8.2.0/src/test/regress/./tmp_check/install//usr/local/ 
pgsql/share" --noclean > "./log/initdb.log" 2>&1
make[2]: *** [check] Error 2
make[2]: Leaving directory `/usr/local/src/postgresql-8.2.0/src/test/ 
regress'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/usr/local/src/postgresql-8.2.0/src/test'
make: *** [check] Error 2

$ cat ./src/test/regress/log/initdb.log
Running in noclean mode.  Mistakes will not be cleaned up.
The files belonging to this database system will be owned by user  
"admin".
This user must also own the server process.

The database cluster will be initialized with locale C.

creating directory /usr/local/src/postgresql-8.2.0/src/test/regress/./ 
tmp_check/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers/max_fsm_pages ... 32MB/204800
creating configuration files ... ok
creating template1 database in /usr/local/src/postgresql-8.2.0/src/ 
test/regress/./tmp_check/data/base/1 ... ok
initializing pg_authid ...  
^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)FATAL: 
   1 trigger record(s) not found for relation "pg_authid"
FATAL:  xlog flush request 0/6418 is not satisfied --- flushed only  
to 0/160
CONTEXT:  writing block 0 of relation 1663/1/1259
child process exited with exit code 1
initdb: data directory "/usr/local/src/postgresql-8.2.0/src/test/ 
regress/./tmp_check/data" not removed at user's request


Other errors encountered in the initdb.logs:

...
loading system objects' descriptions ... ok
creating conversions ... ok
setting privileges on built-in objects ... ok
creating information schema ... FATAL:  cache lookup failed for type  
10445
STATEMENT:  UPDATE information_schema.sql_implementation_info   SET  
character_value = '08.02.0000'   WHERE implementation_info_name =  
'DBMS VERSION';
child process exited with exit code 1

...
loading system objects' descriptions ... ok
creating conversions ... ok
setting privileges on built-in objects ... FATAL:  duplicate key  
violates unique constraint "pg_class_oid_index"
STATEMENT:  UPDATE pg_class   SET relacl = E'{"=r/\\"admin\\""}'    
WHERE relkind IN ('r', 'v', 'S') AND relacl IS NULL;
child process exited with exit code 1

...
loading system objects' descriptions ... ok
creating conversions ... ok
setting privileges on built-in objects ... ok
creating information schema ... FATAL:  cache lookup failed for  
relation 1247
child process exited with exit code 1

...
loading system objects' descriptions ... ok
creating conversions ... PANIC:  heap_insert_redo: invalid max offset  
number
CONTEXT:  xlog redo insert: rel 1663/1/1247; tid 3/47
sh: line 1: 25834 Aborted                 "/usr/local/src/ 
postgresql-8.2.0/src/test/regress/tmp_check/install/usr/local/pgsql/ 
bin/postgres" --single -F -O -c search_path=pg_catalog -c  
exit_on_error=true template1 >/dev/null
child process exited with exit code 134

...
loading system objects' descriptions ... ok
creating conversions ... ok
setting privileges on built-in objects ...  
^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)FA 
TAL:  cache lookup failed for relation 1247
child process exited with exit code 1


I also got an error once when the postmaster was started as part of  
make check:

============== starting postmaster                    ==============

pg_regress: postmaster did not respond within 60 seconds
Examine ./log/postmaster.log for the reason
make[2]: *** [check] Error 2

$ cat ./src/test/regress/log/postmaster.log
LOG:  database system was shut down at 2006-12-13 07:03:38 GMT
LOG:  record with zero length at 0/48CC30
LOG:  invalid primary checkpoint record
LOG:  record with zero length at 0/48CBB0
LOG:  invalid secondary checkpoint record
PANIC:  could not locate a valid checkpoint record
LOG:  startup process (PID 22499) was terminated by signal 6
LOG:  aborting startup due to startup process failure



Responses

pgsql-ports by date

Next:From: Brian WipfDate: 2006-12-13 23:46:20
Subject: Re: "make check" failures -- PG 8.2 and 8.1
Previous:From: Tom LaneDate: 2006-11-28 05:56:21
Subject: Re: Compiling PostgreSQL 8.1.5 with 64-bit on a G5 SOLVED

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group