If we portscan our database server and include the postgres port in the list
of scanned ports, we'll get that error in our logs. You can also get that
message by attempting to telnet to your postgres port. I'm a little
surprised that postgres doesn't list some source ip information with the
message.
-ron
> -----Original Message-----
> From: Henrik Steffen [mailto:steffen@city-map.de]
> Sent: Monday, May 27, 2002 2:16 AM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Invalid length of startup packet
>
>
> (my apologies for the attachement in the last mail)
>
> Hello all,
>
> does anyone what the message "invalid length of startup packet"
> in /var/log/messages means? It says it's "fatal" - so what is
> the reason
> for this message, what does it mean and what can I do against it?
>
> I use the latest postgresql-release on a heavily loaded
> dedicated pentium iv
> machine.
>
> Any help or information appreciated,
>
> thanks
>
>
> Mit freundlichem Gruß
>
> Henrik Steffen
> Geschäftsführer
>
> top concepts Internetmarketing GmbH
> Am Steinkamp 7 - D-21684 Stade - Germany
> --------------------------------------------------------
> http://www.topconcepts.com Tel. +49 4141 991230
> mail: steffen@topconcepts.com Fax. +49 4141 991233
> --------------------------------------------------------
> 24h-Support Hotline: +49 1908 34697 (EUR 1.86/Min,topc)
> --------------------------------------------------------
> System-Partner gesucht: http://www.franchise.city-map.de
> --------------------------------------------------------
> Handelsregister: AG Stade HRB 5811 - UstId: DE 213645563
> --------------------------------------------------------
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>