4 Replies Latest reply on Nov 1, 2016 7:43 PM by Bill Robinson Branched from an earlier discussion.

    Re: nexec hang randomly

    Ronald van Gogh

      Gents,

       

      I have a similar issue. We're running BSA 8.7.00.263 and I'm trying to issue the command below on a Red Hat 7 server from a NSH script. As you can see it results only in a string "Hangup".

       

      % nexec -e ip addr show

      Hangup

       

      The rscd logging shows like this:

       

      10/31/16 12:33:31.890 INFO     rscd -  156.150.177.152 31128 0/0 (BLAdmins:user@domain.com): nexec: nexec -D //redhat7.test.com -e ip addr show

      10/31/16 12:33:31.986 INFO1    rscd -  156.150.177.152 31128 0/0 (BLAdmins:user@domain.com): nexec: > 01010 Execute remote command: ip addr show

       

      How can I collect this kind of information?

       

      Kind regards,  Ronald van Gogh

        • 1. Re: nexec hang randomly
          Olivier Renault

          I'm happy not to be alone with this problem!

          You can use nnet which is easy to parse. Nexec is powerfull but not very reliable

           

          I have a cron that each 10 min kills nexec processes if its PID is 1

          • 2. Re: nexec hang randomly
            Ronald van Gogh

            I wasn't aware of the nnet command, so it's nice to know.

            However I'm missing information on the bonds itself. See below the difference in outputs. I have changed the hostnames and the ip address for security purposes.

             

            How can I determine with nnet if a vlan1197 is defined on bond2? As you can see nnet shows the vlans, but not the bonds where they are defined on. With the command "ip a" I can search on "1197.*bond2". I use this syntax as this works on Red Hat and SuSE systems.

             

            --- Output of ip a --------------------------------------------------------------------------------------

            1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN

                link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

                inet 127.0.0.1/8 brd 127.255.255.255 scope host lo

                inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo

            2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000

                link/ether 38:63:bb:3d:a3:30 brd ff:ff:ff:ff:ff:ff

            3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000

                link/ether 38:63:bb:3d:a3:30 brd ff:ff:ff:ff:ff:ff

            4: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP qlen 1000

                link/ether 38:63:bb:3d:a3:32 brd ff:ff:ff:ff:ff:ff

            5: eth3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP qlen 1000

                link/ether 38:63:bb:3d:a3:32 brd ff:ff:ff:ff:ff:ff

            6: eth4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond2 state UP qlen 1000

                link/ether 38:63:bb:3d:a3:33 brd ff:ff:ff:ff:ff:ff

            7: eth5: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond2 state UP qlen 1000

                link/ether 38:63:bb:3d:a3:33 brd ff:ff:ff:ff:ff:ff

            8: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP

                link/ether 38:63:bb:3d:a3:30 brd ff:ff:ff:ff:ff:ff

                inet 999.999.999.999/23 brd 10.70.207.255 scope global bond0

            9: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP

                link/ether 38:63:bb:3d:a3:32 brd ff:ff:ff:ff:ff:ff

            10: bond2: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP

                link/ether 38:63:bb:3d:a3:33 brd ff:ff:ff:ff:ff:ff

            11: vlan1197@bond2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP

                link/ether 38:63:bb:3d:a3:33 brd ff:ff:ff:ff:ff:ff

                inet 999.999.999.999/23 brd 10.70.225.255 scope global vlan1197

            12: vlan1198@bond1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP

                link/ether 38:63:bb:3d:a3:32 brd ff:ff:ff:ff:ff:ff

                inet 999.999.999.999/23 brd 192.168.131.255 scope global vlan1198

            13: vlan1292@bond1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP

                link/ether 38:63:bb:3d:a3:32 brd ff:ff:ff:ff:ff:ff

                inet 999.999.999.999/23 brd 999.999.999.999 scope global vlan1292

                inet 999.999.999.999/23 brd 999.999.999.999 scope global secondary vlan1292

                inet 999.999.999.999/23 brd 999.999.999.999 scope global secondary vlan1292

                inet 999.999.999.999/23 brd 999.999.999.999 scope global secondary vlan1292

             

             

            --- Output of nnet -c --------------------------------------------------------------------------------------

            "HOSTNAME","NAME","SPEED","MAC","IP","SUBNET","BROADCAST",

            "servername","bond0","10","38:63:bb:3d:a3:30","999.999.999.999","999.999.999.999","999.999.999.999",

            "servername","lo","N/A","00:00:00:00:00:00","127.0.0.1","255.0.0.0","N/A",

            "servername","lo","N/A","00:00:00:00:00:00","127.0.0.2","255.0.0.0","N/A",

            "servername","vlan1197","10","38:63:bb:3d:a3:33","999.999.999.999","999.999.999.999","999.999.999.999",

            "servername","vlan1198","10","38:63:bb:3d:a3:32","999.999.999.999","999.999.999.999","999.999.999.999",

            "servername","vlan1292","10","38:63:bb:3d:a3:32","999.999.999.999","999.999.999.999","999.999.999.999",

            "servername","vlan1292","10","38:63:bb:3d:a3:32","999.999.999.999","999.999.999.999","999.999.999.999",

            "servername","vlan1292","10","38:63:bb:3d:a3:32","999.999.999.999","999.999.999.999","999.999.999.999",

            "servername","vlan1292","10","38:63:bb:3d:a3:32","999.999.999.999","999.999.999.999","999.999.999.999",

             

            Kind regards,  Ronald

            • 3. Re: nexec hang randomly
              Bill Robinson

              but 'Hangup' is the return from the ip command here.  nexec isn't actually hanging.

              • 4. Re: nexec hang randomly
                Bill Robinson

                if you turn off x11 forwarding on the rscd it returns:

                % nexec -i -l blapp88-1 sh -c "ip  -o addr show"

                1: lo    inet 127.0.0.1/8 scope host lo\       valid_lft forever preferred_lft forever

                1: lo    inet6 ::1/128 scope host \       valid_lft forever preferred_lft forever

                2: ens192    inet 192.168.52.51/24 brd 192.168.52.255 scope global ens192\       valid_lft forever preferred_lft forever

                2: ens192    inet6 fe80::250:56ff:fe9e:c464/64 scope link \       valid_lft forever preferred_lft forever

                 

                 

                not sure what's up w/ that though.