Ubuntu
postgresql-7.4 package

After enabled tcpip_socket=true postmaster init fails.

Bug #39110 reported by Mark Derricutt
6
Affects Status Importance Assigned to Milestone
postgresql-7.4 (Ubuntu)
Invalid
Medium
Unassigned

Bug 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.
Please check the log output:
[2006-04-11 08:53:31 PM] Error: GUC variable stats_row_level must be enabled.
[2006-04-11 08:53:31 PM] Please fix the problems and try again.

The rest of the conf file is a stock "fresh from deb" configuration file.

The contents of /var/log/postgresql/postgresql-7.4-main.log shows:

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 2006-04-11 21:23:54 NZST
LOG: checkpoint record is at 0/9FC218
LOG: redo record is at 0/9FC218; undo record is at 0/0; shutdown TRUE
LOG: next transaction ID: 1602; next OID: 17168
LOG: database system is ready
LOG: incomplete startup packet
LOG: incomplete startup packet
LOG: unexpected EOF on client connection

and /var/log/postgresql/pg_autovacuum-7.4-main.log shows:

[2006-04-08 08:38:35 PM] added table: timetrackr."public"."users"
[2006-04-08 08:38:35 PM] added table: timetrackr."pg_catalog"."pg_type"
[2006-04-08 08:38:35 PM] added table: timetrackr."pg_catalog"."pg_database"
[2006-04-08 08:38:35 PM] added table: timetrackr."information_schema"."sql_packages"
[2006-04-08 08:38:35 PM] added table: timetrackr."pg_catalog"."pg_depend"
[2006-04-09 12:06:23 PM] Error: GUC variable stats_row_level must be enabled.
[2006-04-09 12:06:23 PM] Please fix the problems and try again.
[2006-04-11 08:39:13 PM] Error: GUC variable stats_row_level must be enabled.
[2006-04-11 08:39:13 PM] Please fix the problems and try again.
[2006-04-11 08:42:25 PM] Error: GUC variable stats_row_level must be enabled.
[2006-04-11 08:42:25 PM] Please fix the problems and try again.
[2006-04-11 08:43:10 PM] Error: GUC variable stats_row_level must be enabled.
[2006-04-11 08:43:10 PM] Please fix the problems and try again.
[2006-04-11 08:45:57 PM] Error: GUC variable stats_row_level must be enabled.
[2006-04-11 08:45:57 PM] Please fix the problems and try again.
[2006-04-11 08:53:31 PM] Error: GUC variable stats_row_level must be enabled.
[2006-04-11 08:53:31 PM] Please fix the problems and try again.
[2006-04-11 08:59:29 PM] Error: GUC variable stats_row_level must be enabled.
[2006-04-11 08:59:29 PM] Please fix the problems and try again.
[2006-04-11 09:14:54 PM] Error: GUC variable stats_row_level must be enabled.
[2006-04-11 09:14:54 PM] Please fix the problems and try again.

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:

amrk@spawn:~/app/idea-5218$ pg_lsclusters
Version Cluster Port Status Owner Data directory Log file
7.4 main 5432 online postgres /var/lib/postgresql/7.4/main /var/log/postgresql/postgresql-7.4-main.log

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?

Changed in postgresql-7.4:
status: Unconfirmed → Needs Info
Revision history for this message
Mark Derricutt (mark-talios) wrote :

I think I found it - after connecting via psql and issueing "ALTER USER amrk PASSWORD 'foo'" then using that password things went fine.

Seems the default pg_hda.conf file is using md5 password matching which was different on my other machines.

I guess we can close this off.

Revision history for this message
Martin Pitt (pitti) wrote :

OK, thanks for checking again!

Changed in postgresql-7.4:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.