Thread: postgresql 8.0 beta - fail to collect statsistic

Hi,
I got this error message:

LOG:  could not create IPv6 socket: Address family not
supported by protocol
LOG:  could not bind socket for statistics collector:
Cannot assign requested address
LOG:  disabling statistics collector for lack of
working socket
LOG:  database system was shut down at 2004-08-24
00:07:21 EST
LOG:  checkpoint record is at 0/A45360
LOG:  redo record is at 0/A45360; undo record is at
0/0; shutdown TRUE
LOG:  next transaction ID: 492; next OID: 17228
LOG:  database system is ready


I already have a look at pgstat.c but dun know where
to fix it ( with 7.3.1 i just change the line
inet_aton("127.0.0.1", &(pgStatAddr.sin_addr));
to inet_aton("<myip>", &(pgStatAddr.sin_addr)); then
it works
this is the config of the computer:
$ uname -a
Linux grieg 2.4.26-general-64G #1 SMP Tue May 18
09:31:45 EST 2004 i686 GNU/Linux

Any help would be really appreciated.
MT




__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail

my thi ho <mthoatbanjo@yahoo.com> writes:
> I got this error message:

> LOG:  could not create IPv6 socket: Address family not
> supported by protocol
> LOG:  could not bind socket for statistics collector:
> Cannot assign requested address
> LOG:  disabling statistics collector for lack of
> working socket

You have a broken networking setup, or possibly a broken DNS setup.
The machine should accept connections to 127.0.0.1 ... if it does not,
find out why not.

> I already have a look at pgstat.c but dun know where
> to fix it ( with 7.3.1 i just change the line
> inet_aton("127.0.0.1", &(pgStatAddr.sin_addr));
> to inet_aton("<myip>", &(pgStatAddr.sin_addr)); then
> it works

You were fixing the symptom and not the problem.

            regards, tom lane

If IPv6 doesn't work, shouldn't it fall back to IPv4, or check IPv4
first, or something?  Just wondering.

-Steve Bergman

Steve Bergman <steve@rueb.com> writes:
> If IPv6 doesn't work, shouldn't it fall back to IPv4,

It does.  That was all debugged in 7.4 --- we have not seen any cases
since 7.4 beta in which failures of this kind did not mean a
misconfigured networking setup.

            regards, tom lane