Your message dated Mon, 12 Sep 2011 10:57:01 +0200
with message-id <[email protected]>
and subject line Re: Bug#641139: postgresql works but still causes error
message in /var/log/postgresql/postgresql-9.1-main.log
has caused the Debian Bug report #641139,
regarding pg_ctl triggers "Incomplete startup packet" debug log message
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
641139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641139
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql-common
Version: 87
Bug also opened in Launchpad:
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/309496
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)
Additional information:
# /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
--- End Message ---
--- Begin Message ---
Re: Georg 2011-09-10 <[email protected]>
> Package: postgresql-9.1
> Version: 9.1~rc1-3
> Severity: minor
>
> The error message "unvollständiges Startpaket" within it's context:
> 2011-09-08 16:42:27 CEST LOG: Datenbanksystem ist bereit, um Verbindungen
> anzunehmen
> 2011-09-08 16:42:27 CEST LOG: Autovacuum-Launcher startet
> 2011-09-08 16:42:28 CEST LOG: unvollst?ndiges Startpaket
> 2011-09-08 19:32:27 CEST LOG: unvollst?ndiges Startpaket
> 2011-09-08 19:32:27 CEST LOG: schnelles Herunterfahren verlangt
Hi Georg,
thanks for the report. However, this is not really a bug:
$ telnet localhost 5432
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
2011-09-12 10:48:45 CEST [8693]: [1-1] [unbekannt]@[unbekannt] LOG: Verbindung
empfangen: Host=127.0.0.1 Port=33163
^]
telnet> Connection closed.
2011-09-12 10:48:48 CEST [8693]: [2-1] [unbekannt]@[unbekannt] LOG:
unvollst?ndiges Startpaket
pg_ctlcluster polls the database on startup, so this is an expected
message. You also get lots of these if you have TCP connect tests
configured in your monitoring software.
Christoph
--
[email protected] | http://www.df7cb.de/
signature.asc
Description: Digital signature
--- End Message ---
