Hi,
I have just upgraded to 7.4.1 and since restarting
postmaster I am getting the following error message
in the logfile:
"could not bind socket for statistics collector:
"Cannot assign requested address".
My setup is:
OS :Solaris 9(sparc)
Postgres Version: 7.4.1 (upgr
On Thu, Jan 01, 2004 at 04:58:39PM +0100, Denis Grannell wrote:
>
> I have just upgraded to 7.4.1 and since restarting
> postmaster I am getting the following error message
> in the logfile:
> "could not bind socket for statistics collector:
> "Cannot assign requested address".
> My setup is:
>
> On Thu, Jan 01, 2004 at 04:58:39PM +0100, Denis Grannell wrote:
>> I have just upgraded to 7.4.1 and since restarting
>> postmaster I am getting the following error message
>> in the logfile:
>> "could not bind socket for statistics collector:
>> "Cannot assign requested address".
Is it actuall
On Thu, Jan 01, 2004 at 01:27:16PM -0500, Tom Lane wrote:
> > On Thu, Jan 01, 2004 at 04:58:39PM +0100, Denis Grannell wrote:
> >> I have just upgraded to 7.4.1 and since restarting
> >> postmaster I am getting the following error message
> >> in the logfile:
> >> "could not bind socket for statist
Michael Fuhr <[EMAIL PROTECTED]> writes:
> On Thu, Jan 01, 2004 at 01:27:16PM -0500, Tom Lane wrote:
>> Is it actually an ERROR, or just a LOG? If the latter, ignore it.
>> There's no problem unless you also see
>> "LOG: disabling statistics collector for lack of working socket"
> Dang...I'm not
Hi Michael
> >
> > Is it actually an ERROR, or just a LOG? If the latter, ignore it.
> > There's no problem unless you also see
It's a LOG. I should have mentioned that in my first mail.
So, I'll take your advice and ignore it.
>
> That's what commenting out "::1 localhost" from /etc/inet/ip
Hi Tome
>
> We did have a problem of that sort in 7.4 beta releases --- pgstats
> would give up instead of continuing to try additional results from
> getaddrinfo(). I don't recall at the moment if the fix was in 7.4.0
> or not, but it's definitely there in 7.4.1.
I have also definitely installe
On Fri, Jan 02, 2004 at 12:11:54AM +0100, Denis Grannell wrote:
>
> Anyway, I have now 'commented out' the offending line in
> /etc/inet/ipnodes and the message no longer appears
> in the logfile.
>
> Is there a fair probability that other parts of Solaris mightn't
> need that line 'commented
Hi Michael,
> > Is there a fair probability that other parts of Solaris mightn't
> > need that line 'commented in', for want of a better phrase?
>
> Possibly if you're using IPv6, although if you are, then you probably
> wouldn't be getting the "could not bind socket" messages and this thread
> wo
On Fri, Jan 02, 2004 at 01:09:51AM +0100, Denis Grannell wrote:
> Hi Michael,
>
> > > Is there a fair probability that other parts of Solaris mightn't
> > > need that line 'commented in', for want of a better phrase?
> >
> > Possibly if you're using IPv6, although if you are, then you probably
> >
10 matches
Mail list logo