From: Michael Fuhr <mike@fuhr.org>
To: mcelroy, tim <tim.mcelroy@bostonstock.com>
Cc: 'pgsql-admin@postgresql.org' <pgsql-admin@postgresql.org>
Subject: Re: Postmaster errors
Date: Thu, 2 Feb 2006 09:10:19 -0700
Message-ID: <20060202161019.GA87776@winnie.fuhr.org> (raw)
In-Reply-To: <0C4841B42F87D51195BD00B0D020F5CB044B2340@morpheus.bostonstock.com>
References: <0C4841B42F87D51195BD00B0D020F5CB044B2340@morpheus.bostonstock.com>
On Thu, Feb 02, 2006 at 10:58:52AM -0500, mcelroy, tim wrote:
> Has anyone encountered these errors? They repeat every five (5) minutes in
> my log file. Is there something I may have set incorrectly in my
> postgresql.conf file? Odd as I find them in my DEV & QA logs but not
> Production....
>
> 2006-02-02 10:52:33 EST USER=[unknown] DB=[unknown] [8931] LOG: 08P01:
> incomplete startup packet
> 2006-02-02 10:52:33 EST USER=[unknown] DB=[unknown] [8931] LOCATION:
> ProcessStartupPacket, postmaster.c:1311
Something connected to your server without carrying out a proper
PostgreSQL conversation. One of the usual suspects is a probe that
connects to the port and then immediately disconnects, like a port
scan or a network management system. Since it's happening every
five minutes I'd guess the latter.
--
Michael Fuhr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: mike@fuhr.org, tim.mcelroy@bostonstock.com
Subject: Re: Postmaster errors
In-Reply-To: <20060202161019.GA87776@winnie.fuhr.org>
References: <0C4841B42F87D51195BD00B0D020F5CB044B2340@morpheus.bostonstock.com> <20060202161019.GA87776@winnie.fuhr.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox