On Thu, 6 Nov 2014 13:40:14 +0100
Francisco Olarte wrote:
> Hi Juan Antonio:
>
> On Tue, Nov 4, 2014 at 9:54 PM, memtec
> wrote:
>
> > You can force this message executing:
> > $ echo | nc SERVER_IP 5432
> > 2014-11-04 21:44:37 CET LOG: incomplete startup packet
> >
>
> What do you need help
Hi Juan Antonio:
On Tue, Nov 4, 2014 at 9:54 PM, memtec
wrote:
> You can force this message executing:
> $ echo | nc SERVER_IP 5432
> 2014-11-04 21:44:37 CET LOG: incomplete startup packet
>
What do you need help on? PG uses a binary protocol, you sent it bad data
( I think this will open conn
You can force this message executing:
$ echo | nc SERVER_IP 5432
2014-11-04 21:44:37 CET LOG: incomplete startup packet
-
http://www.administracion-linux.com
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Incomplete-startup-packet-help-needed-tp5199030p5825683.
We have it too.
I think it might be samba related, or just some SNMP software running.
I had indentifed the root of the situation some years ago, do not remember it
now.
It is 100% harmless.
On Τρι 24 Ιαν 2012 10:26:25 Florian Weimer wrote:
> * David Johnston:
> > Immediately upon starting the se
* David Johnston:
> Immediately upon starting the server I get an "incomplete startup
> packet" log message. Just prior there is an "autovacuum launcher
> started" message.
Like this?
2012-01-23 10:42:55.245 UTC 11545 LOG: database system is ready to accept
connections
2012-01-23 10:42:55.2
On Monday, January 23, 2012 5:00:17 pm David Johnston wrote:
> On Jan 23, 2012, at 19:38, Adrian Klaver wrote:
> > On Monday, January 23, 2012 4:24:50 pm David Johnston wrote:
> >> Immediately upon starting the server I get an "incomplete startup
> >> packet" log message. Just prior there is an "
GOOD NEWS
On Jan 23, 2012, at 20:00, David Johnston wrote:
> On Jan 23, 2012, at 19:38, Adrian Klaver wrote:
>
>> On Monday, January 23, 2012 4:24:50 pm David Johnston wrote:
>>> Immediately upon starting the server I get an "incomplete startup packet"
>>> log message. Just prior there is an
On Jan 23, 2012, at 19:38, Adrian Klaver wrote:
> On Monday, January 23, 2012 4:24:50 pm David Johnston wrote:
>> Immediately upon starting the server I get an "incomplete startup packet"
>> log message. Just prior there is an "autovacuum launcher started"
>> message.
>
> Do you have other prog
On 1/23/2012 5:24 PM, David Johnston wrote:
Immediately upon starting the server I get an "incomplete startup packet" log message.
Just prior there is an "autovacuum launcher started" message.
We've found that this message is printed in the log if a client makes a
TCP connection to the PG ser
On Monday, January 23, 2012 4:24:50 pm David Johnston wrote:
> Immediately upon starting the server I get an "incomplete startup packet"
> log message. Just prior there is an "autovacuum launcher started"
> message.
Do you have other programs connecting to server on startup?
>
> Any thoughts?
>
On 01/23/12 4:24 PM, David Johnston wrote:
Immediately upon starting the server I get an "incomplete startup packet" log message.
Just prior there is an "autovacuum launcher started" message.
Any thoughts?
based on the given information: something is probably wrong.
--
john r pierce
Immediately upon starting the server I get an "incomplete startup packet" log
message. Just prior there is an "autovacuum launcher started" message.
Any thoughts?
David J.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.
Ahmad,
Do you have something monitoring PostgreSQL by connecting to port 5432
(or whatever you have it listening on) such as Nagios or Zenoss?
- Chris
Ahmad Rumman wrote:
> I am getting WARNING at log file:
>
> Jan 6 11:19:54 dev04 postgres[14624]: [1622-1] DEBUG: name: unnamed;
> blo
I am getting WARNING at log file:
Jan 6 11:19:54 dev04 postgres[14624]: [1622-1] DEBUG: name: unnamed;
blockState: DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1,
children:
Jan 6 11:19:54 dev04 postgres[14624]: [1623-1] LOG: could not send data to
client: Broken pipe
Jan 6 11
David Rysdam wrote:
David Rysdam wrote:
Tom Lane wrote:
David Rysdam <[EMAIL PROTECTED]> writes:
Just finished building and installing on *Sun* (also
"--without-readline", not that I think that could be the issue):
Works fine. So it's something to do with the SGI build in particular.
David Rysdam wrote:
Tom Lane wrote:
David Rysdam <[EMAIL PROTECTED]> writes:
Just finished building and installing on *Sun* (also
"--without-readline", not that I think that could be the issue):
Works fine. So it's something to do with the SGI build in particular.
More likely it's
Tom Lane wrote:
David Rysdam <[EMAIL PROTECTED]> writes:
Just finished building and installing on *Sun* (also
"--without-readline", not that I think that could be the issue): Works
fine. So it's something to do with the SGI build in particular.
More likely it's something to do with
David Rysdam <[EMAIL PROTECTED]> writes:
> Just finished building and installing on *Sun* (also
> "--without-readline", not that I think that could be the issue): Works
> fine. So it's something to do with the SGI build in particular.
More likely it's something to do with weird behavior of the
David Rysdam <[EMAIL PROTECTED]> writes:
> Just finished building and installing on *Sun* (also
> "--without-readline", not that I think that could be the issue): Works
> fine. So it's something to do with the SGI build in particular.
IRIX buggy, film at 11. :)
-Doug
-
Just finished building and installing on *Sun* (also
"--without-readline", not that I think that could be the issue): Works
fine. So it's something to do with the SGI build in particular.
David Rysdam wrote:
I have a working 8.1 server running on Linux and I can connect to it
from other Linu
I have a working 8.1 server running on Linux and I can connect to it
from other Linux clients. I built postgresql 8.1 on an SGI (using
--without-readline but otherwise stock) and it compiled OK and installed
fine. But when I try to connect to the Linux server I get "could not
send startup pac
Markus Wollny wrote:
We're getting "incomplete startup packet" messages in our logfiles due
to some sort of system probe run by our service provider which checks if
PG is still running. In our case they're harmless of course. Are you
sure that you're not running something along those lines, to
Title: [GENERAL] Incomplete Startup Packet
?
Hi!
We're getting "incomplete startup packet"
messages in our logfiles due to some sort of system probe run by our service
provider which checks if PG is still running. In our case they're harmless of
course. Are you
Mott Leroy <[EMAIL PROTECTED]> writes:
> How can I go about tracking down the source of these?
I think if you turn on log_connections, you'll at least get log entries
showing what machine(s) the bad connection attempts are coming from.
Not sure if that'll be enough for you.
> My db clients are JD
Tom Lane wrote:
It's impossible to believe that that's even slightly related.
"Incomplete startup packet" means that you've got broken client-side
software, or perhaps that something is portscanning you. You sure you
weren't seeing those beforehand?
I'm not certain I wasn't seeing those befo
Mott Leroy <[EMAIL PROTECTED]> writes:
> Some time ago, I accidentally did a kill -9 on the postmaster (yes, I
> know, I know), when trying to kill -9 one of the child processes (er,
> yeah, probably bad too). This turned out to be pretty bad for us. It put
> the database in a bad state. I had t
Some time ago, I accidentally did a kill -9 on the postmaster (yes, I
know, I know), when trying to kill -9 one of the child processes (er,
yeah, probably bad too). This turned out to be pretty bad for us. It put
the database in a bad state. I had to run some kind of hacky command (I
don't reca
27 matches
Mail list logo
