Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 5A626650419 for ; Thu, 18 Dec 2008 19:34:42 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 44411-02 for ; Thu, 18 Dec 2008 19:34:39 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by mail.postgresql.org (Postfix) with ESMTP id 249756503D6 for ; Thu, 18 Dec 2008 19:34:39 -0400 (AST) Received: by yx-out-2324.google.com with SMTP id 8so264240yxb.73 for ; Thu, 18 Dec 2008 15:34:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=Mpnhv01Q31AaliMUcM5k/xXKwUjhRXdaS7KFqKfz6jo=; b=fMf5/CdfuH5MuY8dP8cxhiSMiEWIhCjTiMF1AczQ8xRaKT9A1tQ2jjNcMpTFyHyMAc mAfPg9rmz1hNMsUBC0fDmzP9PQhcdpz+JkVzKR/yhViFWXWzjI3muDZkvdrzWYniexXS wDmlhPKrIU2ixUYhTRl0y1fPmSeiSzcG93KLw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=O1aIYKXncDaMGRe5SXWjgF/n3LfElHiyNWNqGJ9IdKPvcOlSPRsBYL9wWqAr3lMNRI rknVQPOAAJescAkT4ZhVpsvD6F1ogw/6Pv8kOAqu4roxvG86D5P+C1lNk1i1YdEPOasP bU6ZJHEFF+073u1spXseDb70bYNT9VSwTo2m4= Received: by 10.100.154.9 with SMTP id b9mr1862845ane.73.1229643277916; Thu, 18 Dec 2008 15:34:37 -0800 (PST) Received: by 10.100.173.3 with HTTP; Thu, 18 Dec 2008 15:34:37 -0800 (PST) Message-ID: <93f118f0812181534w1f78f0a5tda3a21a7074b04e6@mail.gmail.com> Date: Thu, 18 Dec 2008 15:34:37 -0800 From: "Jennifer Redman" To: pgsql-admin@postgresql.org Subject: Re: Incomplete Startup Packet on startup and when pg_maintenance --analyze runs in cron In-Reply-To: <93f118f0812181248s122a93d3vaa09831d64d9e6ae@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_24012_12925107.1229643277903" References: <93f118f0812181248s122a93d3vaa09831d64d9e6ae@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200812/154 X-Sequence-Number: 30987 ------=_Part_24012_12925107.1229643277903 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline It looks like this is a problem with the Ubuntu package postgresql-common. I opened a bug there: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/309496 And for those of you who may have the same issue: Running # /etc/init.d/postgresql-8.3 autovac-restart * Restarting PostgreSQL 8.3 autovacuum daemon Results in: * Error: PostgreSQL 8.1 and above has an integrated autovacuum daemon which cannot be controlled by this program. Looks like /etc/cron.d/postgresql-common # Run VACUUM ANALYSE on all databases every 5 hours if pg_autovacuum is not # running 2 0,5,10,15,20 * * 1-6 root if [ -x /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze >/dev/null; fi Is deprecated for postgresql versions 8.1 and higher and needs to be commented out by default in those packages. The same error message appears on start-up ( incomplete startup packet) but I could not figure out where in /usr/share/postgresql-common/init.d-functions the pg_maintenance script was being called. Additionally, Running: #/sbin/pg_maintenance --analyze results in: Skipping cluster 8.3/main since autovacuuming is enabled for it and the subsequent: 2008-12-18 15:21:18 PST LOG: 08P01: incomplete startup packet 2008-12-18 15:21:18 PST LOCATION: ProcessStartupPacket, postmaster.c:1396 in /postgresql-8.3-main.log On Thu, Dec 18, 2008 at 12:48 PM, Jennifer Redman wrote: > Running Ubuntu 8.04 LTS, with postgresql-8-3, postgresql-client-8.3, > postgresql-common - standard Ubuntu stable postgresql package. The same > error occurs on a system with postgresql-8-2. Both boxes are also running > python-psycopg2. Connections limited to localhost. Nothing monitoring or > scanning port 5432 at a 5 hour interval. > > I'm get the following error in the logs at startup and at the exact > interval that -x /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance > --analyze appears to run in cron: > > From /postgresql-8.3-main.log : > > 2008-12-17 00:02:01 PST LOG: incomplete startup packet > 2008-12-17 05:02:01 PST LOG: incomplete startup packet > 2008-12-17 10:02:01 PST LOG: incomplete startup packet > 2008-12-17 15:02:01 PST LOG: incomplete startup packet > 2008-12-17 20:02:01 PST LOG: incomplete startup packet > > Verbose on startup: > > 2008-12-18 12:15:48 PST LOCATION: StartupXLOG, xlog.c:4816 > 2008-12-18 12:15:48 PST LOG: 00000: autovacuum launcher started > 2008-12-18 12:15:48 PST LOCATION: AutoVacLauncherMain, autovacuum.c:520 > 2008-12-18 12:15:48 PST LOG: 00000: database system is ready to accept > connections > 2008-12-18 12:15:48 PST LOCATION: reaper, postmaster.c:2156 > 2008-12-18 12:15:49 PST LOG: 08P01: incomplete startup packet > 2008-12-18 12:15:49 PST LOCATION: ProcessStartupPacket, postmaster.c:1396 > > From /syslog > > Dec 17 00:02:01 nameofserver /USR/SBIN/CRON[26124]: (root) CMD (if [ -x > /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze > >/dev/null; fi) > Dec 17 05:02:01 nameofserver /USR/SBIN/CRON[1879]: (root) CMD (if [ -x > /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze > >/dev/null; fi) > Dec 17 10:02:01 nameofserver /USR/SBIN/CRON[9264]: (root) CMD (if [ -x > /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze > >/dev/null; fi) > Dec 17 15:02:01 nameofserver /USR/SBIN/CRON[15886]: (root) CMD (if [ -x > /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze > >/dev/null; fi) > Dec 17 20:02:01 nameofserver /USR/SBIN/CRON[12183]: (root) CMD (if [ -x > /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze > >/dev/null; fi) > > This seems like a missed configuration option -- but I'm not sure where. > Any ideas? > > Thanks, > Jennifer > ------=_Part_24012_12925107.1229643277903 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline It looks like this is a problem with the Ubuntu package postgresql-common.  I opened a bug there:

https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/309496

And for those of you who may have the same issue:

Running
# /etc/init.d/postgresql-8.3 autovac-restart
 * Restarting PostgreSQL 8.3 autovacuum daemon

Results in:
 * Error: PostgreSQL 8.1 and above has an integrated autovacuum daemon which cannot be controlled by this program.

Looks like /etc/cron.d/postgresql-common

# Run VACUUM ANALYSE on all databases every 5 hours if pg_autovacuum is not
# running
2 0,5,10,15,20 * * 1-6 root if [ -x /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze >/dev/null; fi

Is deprecated for postgresql versions 8.1 and higher and needs to be commented out by default in those packages.

The same error message appears on start-up
( incomplete startup packet)

but I could not figure out where in /usr/share/postgresql-common/init.d-functions the pg_maintenance script was being called.

Additionally,

Running:

#/sbin/pg_maintenance --analyze

results in:
Skipping cluster 8.3/main since autovacuuming is enabled for it

and the subsequent:
2008-12-18 15:21:18 PST LOG: 08P01: incomplete startup packet
2008-12-18 15:21:18 PST LOCATION: ProcessStartupPacket, postmaster.c:1396

in /postgresql-8.3-main.log

On Thu, Dec 18, 2008 at 12:48 PM, Jennifer Redman <jenred@gmail.com> wrote:
Running Ubuntu 8.04 LTS, with postgresql-8-3, postgresql-client-8.3, postgresql-common - standard Ubuntu stable postgresql package.  The same error occurs on a system with postgresql-8-2.  Both boxes are also running python-psycopg2.  Connections limited to localhost. Nothing monitoring or scanning port 5432 at a 5 hour interval.

I'm get the following error in the logs at startup and at the exact interval that -x /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze appears to run in cron:

From /postgresql-8.3-main.log :

2008-12-17 00:02:01 PST LOG:  incomplete startup packet
2008-12-17 05:02:01 PST LOG:  incomplete startup packet
2008-12-17 10:02:01 PST LOG:  incomplete startup packet
2008-12-17 15:02:01 PST LOG:  incomplete startup packet
2008-12-17 20:02:01 PST LOG:  incomplete startup packet

Verbose on startup:

2008-12-18 12:15:48 PST LOCATION:  StartupXLOG, xlog.c:4816
2008-12-18 12:15:48 PST LOG:  00000: autovacuum launcher started
2008-12-18 12:15:48 PST LOCATION:  AutoVacLauncherMain, autovacuum.c:520
2008-12-18 12:15:48 PST LOG:  00000: database system is ready to accept connections
2008-12-18 12:15:48 PST LOCATION:  reaper, postmaster.c:2156
2008-12-18 12:15:49 PST LOG:  08P01: incomplete startup packet
2008-12-18 12:15:49 PST LOCATION:  ProcessStartupPacket, postmaster.c:1396

From /syslog

Dec 17 00:02:01 nameofserver /USR/SBIN/CRON[26124]: (root) CMD (if [ -x /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze >/dev/null; fi)
Dec 17 05:02:01 nameofserver /USR/SBIN/CRON[1879]: (root) CMD (if [ -x /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze >/dev/null; fi)
Dec 17 10:02:01 nameofserver /USR/SBIN/CRON[9264]: (root) CMD (if [ -x /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze >/dev/null; fi)
Dec 17 15:02:01 nameofserver /USR/SBIN/CRON[15886]: (root) CMD (if [ -x /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze >/dev/null; fi)
Dec 17 20:02:01 nameofserver /USR/SBIN/CRON[12183]: (root) CMD (if [ -x /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze >/dev/null; fi)

This seems like a missed configuration option -- but I'm not sure where.  Any ideas?

Thanks,
Jennifer

------=_Part_24012_12925107.1229643277903--