Comment 1 for bug 39110

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 39110] After enabled tcpip_socket=true postmaster init fails.

 status needsinfo

Hi Mark,

Mark Derricutt [2006-04-11 9:31 -0000]:
> Description:
> After editing my /etc/postgresql/7.4/main/postgresql.conf file to set
> "tcpip_socket=true" and restarting the process the init script reports
> that it failed to run and that I should enable stats_row_level:
>
> amrk@spawn:~/IdeaProjects/timetrackr$ sudo /etc/init.d/postgresql-7.4 restart
> * Stopping PostgreSQL 7.4 database server: main [ ok ]
> * Starting PostgreSQL 7.4 database server: main The PostgreSQL autovacuum daemon failed to start.

Alright, so postmaster itself started just fine (as we already
discovered in IRC); it's just the autovacuum daemon that failed (which
is not such a big deal, but shuold of course be fixed).

> [2006-04-11 08:53:31 PM] Error: GUC variable stats_row_level must be enabled.

Really strange, since that is the default and you didn't touch it. I
could not reproduce this on a current Dapper, it just works fine both
with p-contrib-7.4 (i. e. with automatic autovacuum daemon) and
without.

> If I re-comment the tcpip_socket=true line the server starts up.
>
> pg_lsclusters show the server active, although I can't connect via tcp-
> ip:

Even with tcpip_socket = true? What does

  $ sudo netstat -avpt | grep postmaster

show?

Do you use Breezy or Dapper?

--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org

In a world without walls and fences, who needs Windows and Gates?