pcp
[Top] [All Lists]

Re: pmhostname failing - urgent

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: pmhostname failing - urgent
From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Date: Fri, 15 Nov 2013 14:33:41 -0500
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5286702D.1000101@xxxxxxxxxxxxxxxx>
References: <000201cee1ed$6a1171f0$3e3455d0$@internode.on.net> <y0m7gc91x0f.fsf@xxxxxxxx> <5286702D.1000101@xxxxxxxxxxxxxxxx>
User-agent: Mutt/1.4.2.2i
Hi, Ken -

> >There have been no material changes to pmhostname in recent releases.
> 
> pmhostname does next to nothing, so I'd expect the changes to be in 
> libpcp below __pmGetAddrInfo() or __pmHostEntGetName().

OK, there were several changes in e.g. src/libpcp/src/auxconnect.c,
but again nothing jumps out that should result in not-resolved
messages.

> >However, current pmlogger_check doesn't use pmhostname.  The host
> >field from the control file is passed to pmlogconf/pmlogger pretty
> >much verbatim.  Can you give an extract of the control file and the
> >pmlogger log files to see what's up?
> 
> in pcp-3.8.0-1.el6.x86_64
> 
> $ grep pmhostname /usr/libexec/pcp/bin/pmlogger_check
>         if [ "X$host" != "X$LOCALHOSTNAME" -a "X$host" != "X`pmhostname`" ]
>       fqdn=`pmhostname $host | sed -e 's/@.*//'`

I realize pmhostname used to be used; it's not any more, to get away
from various non-universal assumptions between system hostnames and
DNS.  As the current code is not working for you, would you be able to
forward the relevant log and pmlogger-control snippets?

- FChE

<Prev in Thread] Current Thread [Next in Thread>