Re: PGSTAT: bind(2): Can't assign requested address

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: PGSTAT: bind(2): Can't assign requested address
Дата
Msg-id 200206072247.g57Mlq702565@candle.pha.pa.us
обсуждение исходный текст
Ответ на PGSTAT: bind(2): Can't assign requested address  ("Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>)
Ответы Re: PGSTAT: bind(2): Can't assign requested address  ("Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>)
Список pgsql-bugs
Well, you are the first to report that 127.0.0.1 doesn't work for stats.
Unless someone else has a problem, I think we will leave it unchanged.

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

Bjoern A. Zeeb wrote:
> PRIO: low
>
> Hi,
>
> in src/backend/postmaster/pgstat.c there is a hard coded bind to
> 127.0.0.1 that fails if 127.0.0.1 is not configured on loopback
> interface (e.g. administrator explicitly removed this IP).
> This should _not_ be the case in normal setups.
>
> --- gmake check ---
> ...
> ============== creating temporary installation        ==============
> ============== initializing database system           ==============
> ============== starting postmaster                    ==============
>
> pg_regress: postmaster did not start
> Examine ./log/postmaster.log for the reason.
>
> kill: 97857: No such process
> rm regress.o
> gmake[2]: Leaving directory `/u1/local/src/postgresql/postgresql-7.2.1/src/test/regress'
> gmake[1]: Leaving directory `/u1/local/src/postgresql/postgresql-7.2.1/src/test'
> % cat src/test/regress/log/postmaster.log
> PGSTAT: bind(2): Can't assign requested address
> --- snipp ---
>
> With postgresql-7.2.1 (and perhaps also earlier versions ?) this
> prevents postmaster from starting if one does not configure
>     'stats_start_collector = false'.
> This works as a workaround.
> One may also patch the sources and recompile of course.
>
> I have seen that there were changes in CVS already but the 127.0.0.1 is
> still hard coded in there.
>
> I discovered that after playing with some routing daemons on my test
> machine and therefor had removed 127.0.0.1. OS was FreeBSD 4.5-STABLE
> but that shouldn't matter.
>
> --
> Greetings
>
> Bjoern A. Zeeb                bzeeb at Zabbadoz dot NeT
> 56 69 73 69 74                http://www.zabbadoz.net/
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: [PATCHES] A bug in gist code with fetch/move
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: PQescapeString and PQescapeBytea not exported during win