| From: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com> |
|---|---|
| To: | alfred <alfred(at)arrivusystems(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: incomplete startup packet |
| Date: | 2013-08-21 12:54:22 |
| Message-ID: | CAJghg4+rfaE8vJLbfmLOBnij=bkjKLZZ6WrqeSMQZCx7=2-mhA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Aug 21, 2013 at 3:11 AM, alfred <alfred(at)arrivusystems(dot)com> wrote:
> Hi
>
> -am monitoring the postgresql9.2.4 using monit in my virtual private
> server. Am always getting following log
> 2013-08-21 06:02:33 UTC LOG: incomplete startup packet
> 2013-08-21 06:04:33 UTC LOG: incomplete startup packet
> 2013-08-21 06:06:33 UTC LOG: incomplete startup packet
>
>
Looks like this is happening at each 2 minutes, so it is probably some
monitoring tool (like Nagios, Cacti, Zabbix, etc.) is opening a socket to
PostgreSQL's port only to check if it is responding, and them
disconnecting. Check if you have this kind of service on your environment.
You would have the same effect with nc:
$ nc -zv <host> 5432
As what you can do, if that is the case, just ignore this message, it
should cause no harm.
Regards,
--
Matheus de Oliveira
Analista de Banco de Dados
Dextra Sistemas - MPS.Br nível F!
www.dextra.com.br/postgres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Arlashin | 2013-08-21 17:35:23 | Standalone Hot Backups |
| Previous Message | alfred | 2013-08-21 06:11:53 | incomplete startup packet |