| From: | Steve Atkins <steve(at)blighty(dot)com> |
|---|---|
| To: | PG mailing List <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: incomplete startup packet messages in logs |
| Date: | 2018-11-01 13:44:27 |
| Message-ID: | 44CB294D-DC48-4F70-9ABC-9AB30EB4A9C1@blighty.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Nov 1, 2018, at 1:27 PM, Vijaykumar Jain <vjain(at)opentable(dot)com> wrote:
>
> Hi Team,
>
> I know this is has been answered a lot on the internet wrt ignoring,
> but i am unable to figure out why I get these messages in logs
> "incomplete startup packet"
Check which of your monitoring systems is configured to
check postgresql liveness 15 times an hour.
If you can't find it, and you care about the log entries, start
sniffing packets to see where the traffic is coming from.
>
> tail -1000 /var/log/postgresql/postgresql-10-main.log| grep
> 'incomplete startup packet'
>
> 2018-11-01 13:04:18 UTC LOG: incomplete startup packet
>
> 2018-11-01 13:08:18 UTC LOG: incomplete startup packet
>
> 2018-11-01 13:12:18 UTC LOG: incomplete startup packet
>
>
> Note: exactly at 4 min interval.
Cheers,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vijaykumar Jain | 2018-11-01 13:47:27 | Re: incomplete startup packet messages in logs |
| Previous Message | Vijaykumar Jain | 2018-11-01 13:27:58 | incomplete startup packet messages in logs |