Error in Job Log SND_SYSSTS

Miguel
Miguel
in IBM i
Hi Pavel
We have this error on Job Log SND_SYSSTS
Er: C_SNDSTS  - connect() errno = 3447
Er: C_SNDSTS  - connect() errno = 3447


Comments

  • Pavel
    Pavel
    Hi,

    errno = 3447 Error while connecting for error socket
    Looks like your agent canot communicate with LPAR2RRD server.

    have you correctly set lpar2rrd server hostname/IP?
    As per docu:

    1.
    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 %).

    2.
    CHGCMDDFT CMD(LPAR2RRD/RTV_SYSSTS) NEWDFT('IPADR(LPAR2RRD-SERVER.SERVER.COM)')

    Using IP address instead of hostanme example:
    CHGCMDDFT CMD(LPAR2RRD/RTV_SYSSTS) NEWDFT('IPADR(''192.168.1.2'')')

    3.
    is 8162 port opened? agent --> lpar2rrd server:8162

    4. is lpar2rrd server running?
    on lpar2rrd server: ps -ef| grep lpar2rrd-daemon

    5. anything related in lpar2rrd daemon log?
    on lpar2rrd server:
    tail logs/error.log-daemon





  • Miguel
    Miguel
    How can I restart or refresh the conection because i see the ip server in status close-wait and the process lapr2trrd daemon is running?

    tcp        0      0 0.0.0.0:8162            0.0.0.0:*               LISTEN
    tcp        0      0 172.19.149.175:8162     172.19.131.98:64073     CLOSE_WAIT

    lpar2rrd 10383     1  0  2016 ?        00:24:00 /usr/bin/perl -w /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl
    root     27784 27406  0 14:17 pts/1    00:00:00 grep --color=auto lpar2rrd-daemon




  • Pavel
    Pavel
    kill 10383    
    su - lpar2rrd
    cd lpar2rrd
    ./load.sh

    It starts lpar2rrd-daemon process on its start.
    What LPAR2RRD server version do you use?


  • Miguel
    Miguel
    4.95
  • Miguel
    Miguel
    I kill 10383, run .load.sh, restart agent on ibm i and the error still exist.

     Er: C_SNDSTS  - connect() errno = 3447   

    lpar2rrd@lpar2rrd:~/lpar2rrd> ps -ef| grep lpar2rrd-daemon
    lpar2rrd 32507 31442  0 15:17 pts/1    00:00:00 grep --color=auto lpar2rrd-daemon

    Now, I cant view any conection to port 8162


  • Miguel
    Miguel
    tcp        0      0 0.0.0.0:8162            0.0.0.0:*               LISTEN
    tcp        0      0 172.19.149.175:8162     172.19.148.56:11102     ESTABLISHED
    tcp        0      0 172.19.149.175:8162     172.16.12.5:51926       ESTABLISHED
    tcp        0      0 172.19.149.175:8162     172.15.50.4:58023       ESTABLISHED
    tcp        0      0 172.19.149.175:8162     172.15.50.30:23388      ESTABLISHED


  • Pavel
    Pavel
    this is ok, it is working fine, 5 sessions concurently tere can be.

    1.What about your agent, had it ever workedd or is that new installation?
    2. anyting related in logs/error.log-daemon?
  • Miguel
    Miguel
    it was working until the last week, its not a new installation
    The last weekend I apllied an ipl to the power.
  • Pavel
    Pavel
    can you see any comunication on lpar2rrd server from IBM i agent?
    (change IP and interface "en1")
    tcpdump -ni en1 host <IBM i OS agent IP>

    leave it running for 30mins at least.

    send us logs/error.log-daemon if there was any communication
    https://upload.lpar2rrd.com

    Are you sure your lpar2rrd hostaname is correct set in IBm i client?

  • Miguel
    Miguel
    how can i validate in the server the correct name hostname of the agent ibm i?
  • Pavel
    Pavel
    use this cmd to set it up when the agent is not running

    1. hostanme example
    CHGCMDDFT CMD(LPAR2RRD/RTV_SYSSTS) NEWDFT('IPADR(LPAR2RRD-SERVER.SERVER.COM)')
    2. IP example
    CHGCMDDFT CMD(LPAR2RRD/RTV_SYSSTS) NEWDFT('IPADR(''192.168.1.2'')')



  • Miguel
    Miguel
    I executed this command and leave it running for more 30mins at least.
     :

    tcpdump -v -ni eth0 host <ip agent ibm i> > outfile.txt

    and no have any data in outfile.txt

    After I see this in error.log-daemon

    lpar2rrd:/home/lpar2rrd/lpar2rrd/logs # more error.log-daemon
    Use of uninitialized value $mins in multiplication (*) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $secs in addition (+) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $mins in multiplication (*) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $secs in addition (+) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $mins in multiplication (*) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $secs in addition (+) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $mins in multiplication (*) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $secs in addition (+) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $mins in multiplication (*) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $secs in addition (+) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $mins in multiplication (*) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $secs in addition (+) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $mins in multiplication (*) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $secs in addition (+) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $mins in multiplication (*) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $secs in addition (+) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $mins in multiplication (*) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $secs in addition (+) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $mins in multiplication (*) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $secs in addition (+) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.
    Use of uninitialized value $mins in multiplication (*) at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 4217.


    How can I do?
  • Pavel
    Pavel
    if there is no packet captured then it means that agent does not send any data to lpar2rrd server what confirm that there is a connection error on the agent side.
    (suppose that eth0 is the right interface where agent should communicate)

    Assure that lpar2rrd hostanme is ok:
    ADDLIBLE LPAR2RRD
    GO MENU --> option 50 --> SND_SYSSTS line--> type 5--> type 10 --> F10
    and you should see lpar2rrd server hostname (IP) and port (8162) like on attached screenshot.


    AS400 screenshot 2






  • Miguel
    Miguel
     CALL PGM(C_SNDSTS) PARM('172.19.149.175' '8162' X'0001D740404040C9C4F0F0F0
     C340404040F1F7F24BF1F94BF1F4F94BF1F7F5' 'PH_DTAQRCV*LIBL' 'PH_DTAQSND*LIBL
     ' 'PH_USRSPC *LIBL' '*UTF8' 1 'N' '/home/LPAR2RRD')                       
     IF: C_SNDSTS  - protocol 5.1 UTF8 conv                                    
     Er: C_SNDSTS  - connect() errno = 3447                                    
     Er: C_SNDSTS  - connect() errno = 3447                                    
     Er: C_SNDSTS  - connect() errno = 3447                                    
     Er: C_SNDSTS  - connect() errno = 3447                                    
     Er: C_SNDSTS  - connect() errno = 3447                                    
     Er: C_SNDSTS  - connect() errno = 3447                                    
     Er: C_SNDSTS  - connect() errno = 3447                                    
     Er: C_SNDSTS  - connect() errno = 3447                                    
     Er: C_SNDSTS  - connect() errno = 3447                                    
     Er: C_SNDSTS  - connect() errno = 3447      

    This is the correct ip server and the correct port.                              
  • Pavel
    Pavel
    Try this cmd, is that fail in 5 secs or does it time out in 10 minutes?

    TELNET RMTSYS('172.19.149.175') PORT(8163) SSL(*NO)  INZWAIT(5)



  • Pavel
    Pavel
    If above cmd is hanging (it times out in 10 mins) then it is ok, you can interrupt it by:
       SysRq ➡ Enter ➡ 2. End previous request


  • Miguel
    Miguel
    Morning Pavel.

    I executes the TELNET and fail in 5 seconds.

    Mensaje . . . . :   No se ha obtenido respuesta del sistema principal remoto
      dentro del tiempo de espera de apertura.                                  


  • Pavel
    Pavel
    opss, wrong port name in example, this is the right one:
    TELNET RMTSYS('172.19.149.175') PORT(8162) SSL(*NO)  INZWAIT(5)

  • Miguel
    Miguel
    Equal failure
  • Pavel
    Pavel
    ok, then there is not allowed network connection.
    it is what says initial error, just confirmed trough the system tool (telnet)
     Er: C_SNDSTS  - connect() errno = 3447

    Sorry we cannot help you more here, something is blocking that communication, it is all.

    Try that telnet from other machine whoich work, you will see different behaviour.

  • Miguel
    Miguel
    With another lpar with same version in the same power it works succesfully.

    Can you help me in determinate the problem, i can provide some log´s or anything that allows me what is the issue?
  • Pavel
    Pavel
    verify it with your network/security department if communication is allowed:
    <your IBM i host> --> 72.19.149.175:8162 (TCP)

  • Miguel
    Miguel
    I am validating this it.

    Is that correct in the server?

    lpar2rrd:/home/lpar2rrd/lpar2rrd/logs # netstat -an |grep 8162
    tcp        0      0 0.0.0.0:8162            0.0.0.0:*               LISTEN
    tcp        0      0 172.19.149.175:8162     172.19.131.6:65267      CLOSE_WAIT
  • Pavel
    Pavel
    well, there was a connection from 172.19.131.6 which waiting for TCP close now
  • Miguel
    Miguel
    I validated with security department and no exist any block for user or ip address. At the network level the package or petition don't pass to the default gateway, in other words, it doesn't out of the os400.

  • Pavel
    Pavel
    if you run telnet as per above then you have to see at least 1 TCP syn packet on the default gateway. It is not about our agent.

    You might have wrong route on IBM i, use wrong interface, or anything is filtering it in IBM i. I am not an IBM i expert so I cannot advice more.
    As soon as telnet works then even our agent starts working.
    Try to trace it somehow in IBM i ...

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