Re: Curious UDP packets - Mailing list pgsql-general

From Magnus Hagander
Subject Re: Curious UDP packets
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCEA352AD@algol.sollentuna.se
Whole thread Raw
In response to Curious UDP packets  (Kari Pahula <kaol@iki.fi>)
List pgsql-general
> > > omega kernel: Shorewall:all2all:REJECT:IN= OUT=lo SRC=x.x.x.x
> > > DST=x.x.x.x LEN=1016 TOS=0x00 PREC=0x00
> > > TTL=64 ID=21629 DF PROTO=UDP SPT=32769 DPT=32769 LEN=996
> >
> > The PostgreSQL stats collector uses UDP over a random
> loopback port.
> > It should normally use localhost, though and not a "real" IP.
>
> It's a virtual server, that (currently) has no loopback device.

Aha. That explains it.


> Is it possible to tell the stats collector to use a specific port?

No.


> > To see if that's it, turn of the stats collector
> > (start_stats_collector=off), restart postgresql (restart
> needed ,not
> > enough to just HUP) and see if they go away.
>
> Apparently this didn't prevent those UDP packets...  I'm not
> certain about this one, though, since I wasn't the one testing this.

That sounds strange - if it was the stats collector, it shuodl be gone.
Verify by running "ps axuwf" (or such) to see if there are two processes
named "stats collector" and "stats bufferer" running. If they are, you
failed to turn them off :-)

If not, it's some other process, try something like "netstat -nap" to
figure out which process is listening for them.

//Magnus

pgsql-general by date:

Previous
From: "Shoaib Mir"
Date:
Subject: Re: 21 bit number for sequence
Next
From: "surabhi.ahuja"
Date:
Subject: i have a core file on running gdb the op