after upgrade xormon graphs empty

prenkema

Hi, yesterday I was unable to logon to xormon and decided to upgrade to xormon latest version, but now my graphs are not updated anymore. I have lpar2rrd and stor2rrd (latest version) running.
I myself suspect an issue with some symlinks. 
I running on Centos and use it mainly to monitoring IBM i. On my IBM i I see "ER: Quit UnixTime protocol" in SND_SYSSTS jobs. Help would be greatly appreciated

TomasJetelina

Graphs are not updated just in Xormon or in LPAR2RRD/STOR2RRD also?

Pavel

it seems to be connected to IBM i OS agent, have not expired license?

try as per https://lpar2rrd.com/IBM-Power-Systems-performance-monitoring-installation.php?5.0#IBMi  accept license: go menu --> F14

check if SND_SYSSTS

check also lpar2rrd server, process lpar2rrd-daemon must running, check logs/error.log-daemon if anything connected to that client

prenkema

Sorry, I'm unable to attach log files as a tar ?

Pavel

I do not need logs so far, have you checked above, what are results?

prenkema

I've checked SND_SYSSTS on all IBM i Lpar's is up- and running, and the licenses are accepted, but I see a lot of re-connects, 

IF: C_SNDSTS - re-connect().            

IF: C_SNDSTS  - connection Established()

ER: Quit UnixTime protocol.             

IF: C_SNDSTS - re-connect().            

IF: C_SNDSTS  - connection Established()

ER: Quit UnixTime protocol.            

On Server

[syspre@lpar2rrd ~]$ ps aux | grep lpar2rrd-daemon

lpar2rrd 11777  0.0  0.3  77244 20888 ?        S    Mar11   0:27 /usr/bin/perl -w /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl

syspre   12309  0.0  0.0 112636   992 pts/0    S+   19:21   0:00 grep --color=auto lpar2rrd-daemon

[syspre@lpar2rrd ~]$ 

this is ok!, or do I need to see something else?

Pavel

1. is connection working?

as per: https://lpar2rrd.com/IBM-Power-Systems-performance-monitoring-installation.php?5.0#IBMi

Test network connectivity
For example if hostname of LPAR2RRD server is LPAR2RRD-SERVER.SERVER.COM.

    ping:

    PING RMTSYS('LPAR2RRD-SERVER.SERVER.COM')
      Verifying connection to host system LPAR2RRD-SERVER.SERVER.COM at address 192.168.1.2.
      Connection verification statistics: 5 of 5 successful (100 %).

    telnet:

    TELNET RMTSYS('LPAR2RRD-SERVER.SERVER.COM') PORT(8162) RMTUSER(TESTSTRING) INZWAIT(15)
      Connecting to remote host 192.168.1.2 using port 8162

    If you get after 15 seconds "No response from remote host system within open time-out." then it is wrong!.
    Either LPAR2RRD server daemon is not running or TCP connection is filtered on the network by a firewall.
    If connection hanging (it times out in 10 mins) then it is ok, you can interrupt it by:
       SysRq ➡ Enter ➡ 2. End previous request

2. if so, then send us logs from lpar2rrd server

Note a short problem description in the text field of the upload form.

cd /home/lpar2rrd/lpar2rrd  # or where is your LPAR2RRD working dir

tar cvhf logs.tar logs tmp/*txt tmp/*json

gzip -9 logs.tar

Send us logs.tar.gz via https://upload.lpar2rrd.com

prenkema

I've send you the logs, since I check point 1 connection is working....

prenkema

some IBM i shows

CALL PGM(C_SNDSTS) PARM('10.70.11.99' '8162' X'0001D740404040C9C4F0F0F0C34

0404040F1F04BF7F04BF1F14BF9F9' 'PH_DTAQRCV*LIBL' 'PH_DTAQSND*LIBL' 'PH_USR

SPC *LIBL' '*UTF8' 1 'N' '/home/LPAR2RRD')                                

IF: C_SNDSTS  - protocol 5.4 UTF8 conv                                    

IF: C_SNDSTS  - connection Established()                                  

ER: Quit UnixTime protocol.                                               

IF: C_SNDSTS - re-connect().                                              

IF: C_SNDSTS  - connection Established()                                  

ER: Quit UnixTime protocol.                                               

IF: C_SNDSTS - re-connect().                                              

I see a lot of re-connects ...

And I think it is happening to more servers, will try to check, but we have a lot of lpars

prenkema

Did some corrections in authorisation as suggested by you, things are looking a lot better now but we'll still have to check the rest of all the lpar's..., hopefully we get back to you soon, but I feel convided now....