pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedinvalid length of startup packet
3+ messages / 3 participants
[nested] [flat]
* invalid length of startup packet
@ 2005-11-29 21:45 Dan The Man <bitsandbytes88@hotmail.com>
2005-11-29 21:49 ` Re: invalid length of startup packet Guido Barosio <gbarosio@gmail.com>
2005-11-29 22:28 ` Re: invalid length of startup packet Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 3+ messages in thread
From: Dan The Man @ 2005-11-29 21:45 UTC (permalink / raw)
To: pgsql-admin
Hi,
I've been using postgresql v810 for a couple of weeks. I notice when I
start it up I get 'invalid lenth of startup packet' On a database that I
just initialized I get ' incomplete startup packet' after I first started
it. This never happened that I can see in 8.0.3.
Does any one know if that can be safely ignored?
~DjK
< % %2005-11-28 07:31:10 EST>LOG: database system was interrupted at
2005-11-28 03:57:12 EST
< % %2005-11-28 07:31:10 EST>LOG: checkpoint record is at 13/89BD9728
< % %2005-11-28 07:31:10 EST>LOG: redo record is at 13/89BD9728; undo
record is at 0/0; shutdown FALSE
< % %2005-11-28 07:31:10 EST>LOG: next transaction ID: 81691647; next OID:
92997625
< % %2005-11-28 07:31:10 EST>LOG: next MultiXactId: 1; next
MultiXactOffset: 0
< % %2005-11-28 07:31:10 EST>LOG: database system was not properly shut
down; automatic recovery in progress
< % %2005-11-28 07:31:10 EST>LOG: record with zero length at 13/89BD9778
< % %2005-11-28 07:31:10 EST>LOG: redo is not required
< % %2005-11-28 07:31:10 EST>LOG: database system is ready
< % %2005-11-28 07:31:10 EST>LOG: transaction ID wrap limit is 1155432042,
limited by database "dan_test_bum"
<[unknown] %[unknown] %2005-11-28 09:03:07 EST>LOG: invalid length of
startup packet
< % %2005-11-28 09:43:37 EST>LOG: autovacuum: processing database
"initial_db"
< % %2005-11-28 09:53:37 EST>LOG: autovacuum: processing data
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: invalid length of startup packet
2005-11-29 21:45 invalid length of startup packet Dan The Man <bitsandbytes88@hotmail.com>
@ 2005-11-29 21:49 ` Guido Barosio <gbarosio@gmail.com>
1 sibling, 0 replies; 3+ messages in thread
From: Guido Barosio @ 2005-11-29 21:49 UTC (permalink / raw)
To: Dan The Man <bitsandbytes88@hotmail.com>; +Cc: pgsql-admin
I can notice:
< % %2005-11-28 07:31:10 EST>LOG: database system was not properly shut
down; automatic recovery in progress
At a first sight, you didn't shut down the database as expected. (pg_ctl
stop -m smart/fast/immediate). Now I don't know if this is the root cause
for that message, but a clean stop, and start should show you if this is
related or not.
Just 2 cents, every little helps, best regards,
Guido Barosio
On 11/29/05, Dan The Man <bitsandbytes88@hotmail.com> wrote:
>
> Hi,
>
> I've been using postgresql v810 for a couple of weeks. I notice when I
> start it up I get 'invalid lenth of startup packet' On a database that I
> just initialized I get ' incomplete startup packet' after I first started
> it. This never happened that I can see in 8.0.3.
>
> Does any one know if that can be safely ignored?
>
> ~DjK
>
>
> < % %2005-11-28 07:31:10 EST>LOG: database system was interrupted at
> 2005-11-28 03:57:12 EST
> < % %2005-11-28 07:31:10 EST>LOG: checkpoint record is at 13/89BD9728
> < % %2005-11-28 07:31:10 EST>LOG: redo record is at 13/89BD9728; undo
> record is at 0/0; shutdown FALSE
> < % %2005-11-28 07:31:10 EST>LOG: next transaction ID: 81691647; next
> OID:
> 92997625
> < % %2005-11-28 07:31:10 EST>LOG: next MultiXactId: 1; next
> MultiXactOffset: 0
> < % %2005-11-28 07:31:10 EST>LOG: database system was not properly shut
> down; automatic recovery in progress
> < % %2005-11-28 07:31:10 EST>LOG: record with zero length at 13/89BD9778
> < % %2005-11-28 07:31:10 EST>LOG: redo is not required
> < % %2005-11-28 07:31:10 EST>LOG: database system is ready
> < % %2005-11-28 07:31:10 EST>LOG: transaction ID wrap limit is
> 1155432042,
> limited by database "dan_test_bum"
> <[unknown] %[unknown] %2005-11-28 09:03:07 EST>LOG: invalid length of
> startup packet
> < % %2005-11-28 09:43:37 EST>LOG: autovacuum: processing database
> "initial_db"
> < % %2005-11-28 09:53:37 EST>LOG: autovacuum: processing data
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
--
"Adopting the position that you are smarter than an automatic
optimization algorithm is generally a good way to achieve less
performance, not more" - Tom Lane.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: invalid length of startup packet
2005-11-29 21:45 invalid length of startup packet Dan The Man <bitsandbytes88@hotmail.com>
@ 2005-11-29 22:28 ` Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 3+ messages in thread
From: Tom Lane @ 2005-11-29 22:28 UTC (permalink / raw)
To: Dan The Man <bitsandbytes88@hotmail.com>; +Cc: pgsql-admin
"Dan The Man" <bitsandbytes88@hotmail.com> writes:
> I've been using postgresql v810 for a couple of weeks. I notice when I
> start it up I get 'invalid lenth of startup packet' On a database that I
> just initialized I get ' incomplete startup packet' after I first started
> it. This never happened that I can see in 8.0.3.
That has nothing to do with the state of the database --- it's an
indication of broken client software trying to connect, or possibly
something portscanning your system.
regards, tom lane
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2005-11-29 22:28 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-11-29 21:45 invalid length of startup packet Dan The Man <bitsandbytes88@hotmail.com>
2005-11-29 21:49 ` Guido Barosio <gbarosio@gmail.com>
2005-11-29 22:28 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox