Re: [pcp] Help with Python API

[Rohan Arora <rarora2012@xxxxxxxxx>]

The output for bothÂ$ pminfo -v -Dcontext -h <remotehost> disk.all

andÂ$ echo "log mandatory on once { disk.dev }" | pmlogger -Dcontext -h <remotehost> -l /dev/tty foobar:

__pmSetDataIPC: fd=1024 data="">

IPC table fd(PDU version):

__pmSetSocketIPC: fd=1024

IPC table fd(PDU version):

__pmConnectPMCD(<remote_host>): pmcd connection port=44321 failed: Connection timed out

pmNewContext(1,<remote_host>) -> -110, curcontext=-1

pminfo: Cannot connect to PMCD on host "<remote_host>": Connection timed out

On the remote host, the contents of /etc/pcp/pmcd/pmcd.conf:

# Performance Metrics Domain Specifications

#

# This file is automatically generated during the build

# Name ÂId   ÂIPC   IPC Params   ÂFile/Cmd

pmcd  Â2    dso   pmcd_init    /var/lib/pcp/pmdas/pmcd/pmda_pmcd.so

linux  60   Âdso   linux_init   Â/var/lib/pcp/pmdas/linux/pmda_linux.so

proc  Â3    pipe  Âbinary     Â/var/lib/pcp/pmdas/proc/pmdaproc -d 3

mmv   70   Âdso   mmv_init    Â/var/lib/pcp/pmdas/mmv/pmda_mmv.so

xfs   11   Âpipe  Âbinary     Â/var/lib/pcp/pmdas/xfs/pmdaxfs -d 11

jbd2  Â122   dso   jbd2_init    /var/lib/pcp/pmdas/jbd2/pmda_jbd2.so

[access]

disallow ".*" : store;

disallow ":*" : store;

allow "local:*" : all;

And the contents of /var/log/pcp/pmcd/pmcd.log:

Log for pmcd on <remote_host> started Fri Jul 10 19:50:30 2015

[Fri Jul 10 19:50:30] pmcd(46460) Error: Unable to configure SSL session ID cache: Access Denied

active agent dom  pid Âin out ver protocol parameters

============ === ===== === === === ======== ==========

pmcd      2         2 dso i:5 Âlib=/var/lib/pcp/pmdas/pmcd/pmda_pmcd.so entry=pmcd_init [0x7f103ad68920]

linux     60         2 dso i:4 Âlib=/var/lib/pcp/pmdas/linux/pmda_linux.so entry=linux_init [0x7f103a937700]

proc      3 46466 Â13 Â14  2 bin pipe cmd=/var/lib/pcp/pmdas/proc/pmdaproc -d 3

mmv      70         2 dso i:4 Âlib=/var/lib/pcp/pmdas/mmv/pmda_mmv.so entry=mmv_init [0x7f103a72a7f0]

xfs      11 46467 Â15 Â16  2 bin pipe cmd=/var/lib/pcp/pmdas/xfs/pmdaxfs -d 11

jbd2 Â Â Â Â 122 Â Â Â Â Â Â Â Â 2 dso i:4 Âlib=/var/lib/pcp/pmdas/jbd2/pmda_jbd2.so entry=jbd2_init [0x7f103a5275f0]

Host access list:

00 01 Cur/MaxCons host-spec                host-mask                lvl host-name

== == =========== ======================================= ======================================= === ==============

Ây Ây   0   0 10.0.0.4                Â255.255.255.255              0 localhost

Ây Ây   0   0 /                    /                     1 unix:

  n   0   0 0.0.0.0                 0.0.0.0                  4 .*

  n   0   0 ::                   Â::                    Â8 :*

User access list empty: user-based access control turned off

Group access list empty: group-based access control turned off

pmcd: PID = 46460, PDU version = 2

pmcd request port(s):

 sts fd  port Âfamily address

 === ==== ===== ====== =======

 ok Â1026    unix  /var/run/pcp/pmcd.socket

 ok Â1024 44321 inet  INADDR_ANY

 ok Â1025 44321 ipv6  INADDR_ANY

I'm not really sure what to make of all of this output. When trying to use telnet, I do get Connection refused, and I tried to restart pmcd on both machines, but that didn't work. I also tried to turn off the firewalls temporarily using "service iptables stop" so that all traffic was allowed, but that didn't change anything.

Best,

Rohan

On Wed, Jul 1, 2015 at 6:17 PM Ken McDonell <kenj@xxxxxxxxxxxxxxxx> wrote:

On 02/07/15 02:07, Rohan Arora wrote:
> I tried following the directions on that page, the telnet error that I
> get is "Connect failed" rather than "Connection refused". I have
> verified that pmcd is running on the host I am trying to connect to as
> it is shown as running as a service, and I am able to use pminfo as
> well. Does it matter that the host is protected using a putty private
> key when using ssh? I am not sure where to go from here really.

Are you able to use pminfo on the same system connecting to the remote pmcd (i.e. the same client-server arrangement where pmlogger is not working)? That would be odd.

In any event the following output would help diagnose ...

On the client system

$ pminfo -v -Dcontext -h <remotehost> disk.all
$ echo "log mandatory on once { disk.dev }" | pmlogger -Dcontext -h <remotehost> -l /dev/tty foobar
^C
$ pminfo -a foobar

And on the remote system, the contents of:

/etc/pcp/pmcd/pmcd.conf
/var/log/pcp/pmcd/pmcd.log

_______________________________________________
pcp mailing list
pcp@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/pcp