Re: Invalid length of startup packet - Mailing list pgsql-general
From | Henrik Steffen |
---|---|
Subject | Re: Invalid length of startup packet |
Date | |
Msg-id | 01ed01c20616$0d9968c0$7100a8c0@topconcepts.net Whole thread Raw |
In response to | Re: Invalid length of startup packet (Ron Snyder <snyder@roguewave.com>) |
List | pgsql-general |
Dear Ron, thanks for your answer. This is what happens if I telnet or portscan, too. The thing is, that noone is actually telnetting or portscanning in. The server is located inside the DMZ of a firewall. There is only one webserver which is allowed to connect. This server is located inside the same DMZ. This can't be the reason. On the Webserver the Pg.pm perl-module is used to connect to the DB-Server. This seems to be the origin of the error messages because this is the only process which is allowed to connect. If I run the same perl-scripts from the command prompt theres is no problem. But using Apache 1.3.24 with latest mod_perl the error message in /var/log/messages is generated. This is really weird. I upgraded to the latest postgresql-rpm yesterday on both the Webserver and the Db-Server, this didn't change anything. Additionally, the error is non-fatal: The connection is not dropped. Anyway, the message has got to have some reason, hasn't it? Any comments? 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 -------------------------------------------------------- ----- Original Message ----- From: "Ron Snyder" <snyder@roguewave.com> To: "'Henrik Steffen'" <steffen@city-map.de>; <pgsql-general@postgresql.org> Sent: Tuesday, May 28, 2002 6:37 AM Subject: Re: [GENERAL] Invalid length of startup packet 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 > ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
pgsql-general by date: