Agent data is not graphed

jrodriguez
jrodriguez
in LPAR2RRD

Hi Team,


This same thing happened to me in previous versions, right now we have installed:

LPAR2RRD 7.92 (Linux OVA)

LPAR2RRD Agent 7.90-1 (OS agent check OK)

Client environment: AIX with VIO


In LPAR2RRD I cannot see the information collected from the agents (installed only in AIX VIOs)


Agent side OK, the information is generated and the server agent collects it but the corresponding tabs are not displayed. Example of one:

image.png
image.png


As a curiosity, the only tab that is not storing anything on the server is "JOBS"

image.png


No errors on agent side:

image.png


Server Daemon running and listening:

image.png
image.png

It had not been working for a while, on September 14, I updated LPAR2RRD + agents to the latest version and restarted lpar2rrd-daemon and for a short time it graphed (approximately 20 minutes)

image.png


image.png


In the daemon error log you can see entries from the last daemon restart, that day I did several and only the last one registered an error (the first error I don't know why it originated):

image.png


Today I restarted the daemon again (kill with user lpar2rrd + run load.sh) and it gave me the same error as on September 14, but with today's date (sorry, I don't have the screenshot)

image.png


Thanks and regards

Comments

  • Pavel
    Pavel

    send us gzipped cpu.mm


    https://upload.lpar2rrd.com

  • jrodriguez
    jrodriguez

    Done.


    Thx

  • Pavel
    Pavel

    on the agent side:

    su - lpar2rrd

    date

    crontab -l

    ls -ltr /var/tmp/lpar*|tail

    ps -ef| grep lpar2rrd

  • jrodriguez
    jrodriguez

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd> date

    Thu Sep 12 11:10:55 CEST 2024

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd>

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd> crontab -l

    * * * * * /usr/bin/perl /opt/lpar2rrd-agent/lpar2rrd-agent.pl xoruxdad01 > /var/tmp/lpar2rrd-agent.out 2>&1


    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd> ls -ltr /var/tmp/lpar*|tail

    -rw-r--r--  1 lpar2rrd staff       0 Sep 12 10:16 /var/tmp/lpar2rrd-agent-xorux-lpar2rrd-multipath.stamp

    -rw-r--r--  1 lpar2rrd staff      388 Sep 12 10:16 /var/tmp/lpar2rrd-agent-xorux-lpar2rrd-fs.txt

    -rw-r--r--  1 lpar2rrd staff     5446 Sep 12 11:00 /var/tmp/lpar2rrd-agent-xorux-lpar2rrd-ps_job.txt

    -rw-r--r--  1 lpar2rrd staff       1 Sep 12 11:11 /var/tmp/lpar2rrd-agent-xorux-lpar2rrd-wlmstat-23265616.txt

    -rw-r--r--  1 lpar2rrd staff    8763169 Sep 12 11:11 /var/tmp/lpar2rrd-agent-xorux-lpar2rrd.txt

    -rw-r--r--  1 lpar2rrd staff       0 Sep 12 11:11 /var/tmp/lpar2rrd-agent-xorux-lpar2rrd.stamp

    -rw-r--r--  1 lpar2rrd staff    8763169 Sep 12 11:11 /var/tmp/lpar2rrd-agent-xorux-lpar2rrd-last.txt

    -rw-r--r--  1 lpar2rrd staff     46500 Sep 12 11:11 /var/tmp/lpar2rrd-agent-xorux-lpar2rrd.err

    -rw-r--r--  1 lpar2rrd staff     4390 Sep 12 11:11 /var/tmp/lpar2rrd-agent.out

    -rw-r--r--  1 lpar2rrd staff    8763169 Sep 12 11:11 /var/tmp/lpar2rrd-agent-xorux-lpar2rrd.txtorig

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd>

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd> ps -ef| grep lpar2rrd

    lpar2rrd 19923420 27591016  0 11:11:28 pts/0 0:00 grep lpar2rrd

    lpar2rrd 20185492 23265616  0 11:11:00   - 0:00 vmstat -I -W -t 60 1

    lpar2rrd 21365222 27591016  0 11:11:28 pts/0 0:00 ps -ef

    lpar2rrd 21758382 23265616  0         0:00 <defunct>

    lpar2rrd 22872378 25231832  0 11:11:00   - 0:00 iostat -Dsal 60 1

    lpar2rrd 23265616 9896278  0 11:11:00   - 0:00 /usr/bin/perl /opt/lpar2rrd-agent/lpar2rrd-agent.pl xorux

    lpar2rrd 25231832 23265616  0 11:11:00   - 0:00 /usr/bin/perl /opt/lpar2rrd-agent/lpar2rrd-agent.pl xorux

    lpar2rrd 27591016 16581034  1 11:10:48 pts/0 0:00 -ksh

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd>

  • Pavel
    Pavel

    tail /var/tmp/lpar2rrd-agent-xorux-lpar2rrd.err

  • Pavel
    Pavel

    on the agent side

  • jrodriguez
    jrodriguez

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd> tail /var/tmp/lpar2rrd-agent-xorux-lpar2rrd.err

    Thu Sep 12 11:44:05 2024: LPAR2RRD server xorux was not resolved, try to ping it to confirm DNS works as expect: /opt/lpar2rrd-agent/lpar2rrd-agent.pl:493

    Thu Sep 12 12:06:02 2024: LPAR2RRD server xorux was not resolved, try to ping it to confirm DNS works as expect: /opt/lpar2rrd-agent/lpar2rrd-agent.pl:493

    Thu Sep 12 12:15:07 2024: LPAR2RRD server xorux was not resolved, try to ping it to confirm DNS works as expect: /opt/lpar2rrd-agent/lpar2rrd-agent.pl:493

    Thu Sep 12 12:37:08 2024: LPAR2RRD server xorux was not resolved, try to ping it to confirm DNS works as expect: /opt/lpar2rrd-agent/lpar2rrd-agent.pl:493

    Thu Sep 12 12:49:10 2024: LPAR2RRD server xorux was not resolved, try to ping it to confirm DNS works as expect: /opt/lpar2rrd-agent/lpar2rrd-agent.pl:493

    Thu Sep 12 12:56:07 2024: LPAR2RRD server xorux was not resolved, try to ping it to confirm DNS works as expect: /opt/lpar2rrd-agent/lpar2rrd-agent.pl:493

    Thu Sep 12 13:15:08 2024: LPAR2RRD server xorux was not resolved, try to ping it to confirm DNS works as expect: /opt/lpar2rrd-agent/lpar2rrd-agent.pl:493

    Thu Sep 12 13:30:07 2024: LPAR2RRD server xorux was not resolved, try to ping it to confirm DNS works as expect: /opt/lpar2rrd-agent/lpar2rrd-agent.pl:493

    Thu Sep 12 13:47:02 2024: LPAR2RRD server xorux was not resolved, try to ping it to confirm DNS works as expect: /opt/lpar2rrd-agent/lpar2rrd-agent.pl:493

    Thu Sep 12 13:54:08 2024: LPAR2RRD server xorux was not resolved, try to ping it to confirm DNS works as expect: /opt/lpar2rrd-agent/lpar2rrd-agent.pl:493



    I see the problem now, they haven't put the entry in the DNS:


    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd> nslookup

    > server 10.0.150.1

    Default server: 10.0.150.1

    Address: 10.0.150.1#53

    > xoruxdad01

    Server:     10.0.150.1

    Address:    10.0.150.1#53


    ** server can't find xoruxdad01: SERVFAIL

    L



    But this VIO is configured to resolve locally first, I will request that the corresponding entries be added to the DNS, until then is there any way to tell the agent not to use DNS resolution and to choose the one established by the system (local) first?

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd> host xoruxdad01

    xoruxdad01 is 10.0.152.235

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd>


    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd> grep xoruxdad01 /etc/hosts

    10.0.152.235  xoruxdad01

    198.18.17.235  xoruxdad01colt

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd>

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd> tail /etc/netsvc.conf

    # To specify alias ordering to the sendmail command, enter the following:

    # alias = value [, value]

    #

    # Use one or more of the following values for the alias keyword:

    # files  Searches the local /etc/aliases file for the alias

    # nis   Uses NIS services for resolving alias

    # Example:

    # aliases = nis, files

    #

    hosts = local, bind


    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd> crontab -l

    * * * * * /usr/bin/perl /opt/lpar2rrd-agent/lpar2rrd-agent.pl xoruxdad01 > /var/tmp/lpar2rrd-agent.out 2>&1



    From what I can see, it resolves the xorux server well:

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd> ping -c4 xoruxdad01

    PING xoruxdad01: (10.0.152.235): 56 data bytes

    64 bytes from 10.0.152.235: icmp_seq=0 ttl=64 time=0 ms

    64 bytes from 10.0.152.235: icmp_seq=1 ttl=64 time=0 ms

    64 bytes from 10.0.152.235: icmp_seq=2 ttl=64 time=0 ms

    64 bytes from 10.0.152.235: icmp_seq=3 ttl=64 time=0 ms


    --- xoruxdad01 ping statistics ---

    4 packets transmitted, 4 packets received, 0% packet loss

    round-trip min/avg/max = 0/0/0 ms

    lpar2rrd@DAD-PWR-013-VIOS1:/home/lpar2rrd>



    Thx

  • Pavel
    Pavel

    it will be ok

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Categories

In this Discussion