[BUGS] 8rc5 on OpenBSD

#1

Hi,

I try a "make check" without success.

The compilation is done correctly.
But "make check" throws:

Quote:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D creating temporary installatio=
n =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D initializing database system =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D starting postmaster =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
running on port 65432 with pid 17114
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D creating database "regression"=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
createdb: could not connect to database template1: could not connect=20
to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.65432"?
pg_regress: createdb failed
gmake[2]: *** [check] Error 2
rm regress.o
gmake[2]: Leaving directory=20
`/admin/install/pg/postgresql-8.0.0rc5/src/test/regress'
gmake[1]: *** [check] Error 2
gmake[1]: Leaving directory=20
`/admin/install/pg/postgresql-8.0.0rc5/src/test'
gmake: *** [check] Error 2
*** Error code 2

Stop in /admin/install/pg/postgresql-8.0.0rc5 (line 19 of Makefile).
admin has logged on ttyp1 from imac.

# cat src/test/regress/log/postmaster.log

Quote:

WARNING: could not create Unix-domain socket
LOG: database system was shut down at 2005-01-12 14:25:10 CET
LOG: checkpoint record is at 0/A3E614
LOG: redo record is at 0/A3E614; undo record is at 0/0; shutdown TRUE
LOG: next transaction ID: 544; next OID: 17230
LOG: database system is ready
LOG: received fast shutdown request
LOG: shutting down
LOG: database system is shut down

I recompile with the option for configure from the 7.4 ports. Nothing=20
better.

Any help welcomed.

Cordialement,
Jean-G=E9rard Pailloncy

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

#2

Pailloncy Jean-Gerard <jg (AT) rilk (DOT) com> writes:

Quote:

# cat src/test/regress/log/postmaster.log
WARNING: could not create Unix-domain socket

Hmm. That's pretty odd --- the warning indicates that
StreamServerPort() failed to open a local socket, but all of the
expected failure paths will log an additional message saying why
it couldn't open the socket.

The only code path I see offhand in which no message would be logged
is if the ListenSocket[] array is already full. Is it possible that
you have 10 or more IP addresses that "localhost" would bind to?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

#3

Pailloncy Jean-Gerard <jg (AT) rilk (DOT) com> writes:

Quote:

The only code path I see offhand in which no message would be logged
is if the ListenSocket[] array is already full. Is it possible that
you have 10 or more IP addresses that "localhost" would bind to?

2 IPs + 3 alias on 2 interfaces
1 IPs + 27 alias on 1 loopback interface

Wow. Try increasing the MAXLISTEN constant in
src/backend/postmaster/postmaster.c.

Bump it to 100. Good.
I sugess a better error message.

Done. It never occurred to anyone that that limit would actually be
reached, I suppose.

Quote:

=======================
8 of 96 tests failed.
=======================

Seems like you've still got some issues though. What do the detailed
diffs look like?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

#4

Pailloncy Jean-Gerard <jg (AT) rilk (DOT) com> writes:

Quote:

=======================
8 of 96 tests failed.
=======================

The failures all seem to be due to individual tests not getting run:

Quote:

! psql: could not fork new process for connection: Resource temporarily unavailable
! psql: could not fork new process for connection: Resource temporarily unavailable
! psql: could not fork new process for connection: Resource temporarily unavailable
! psql: could not fork new process for connection: Resource temporarily unavailable
! psql: could not send startup packet: Broken pipe
! psql: could not send startup packet: Broken pipe

(the other two failures are because tables these tests should have
created didn't get created)

The fork failures are easy enough to explain: you have the per-user
process limit set too low. I suspect the "broken pipe" failures
have the same root cause, but they do seem a bit odd.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

[BUGS] 8rc5 on OpenBSD

mailing.database.pgsql-bugs mailing.database.pgsql-bugs

[BUGS] 8rc5 on OpenBSD - 01-12-2005 , 07:36 AM

Re: [BUGS] 8rc5 on OpenBSD - 01-12-2005 , 09:38 AM

Re: [BUGS] 8rc5 on OpenBSD - 01-12-2005 , 10:43 AM

Re: [BUGS] 8rc5 on OpenBSD - 01-12-2005 , 12:20 PM