3 Replies Latest reply on Aug 27, 2013 10:59 AM by mdnramos

    NDLP service stingray status DESTROY

    qtanit

      Hi Guys!

      help me please!

      Im using vsphere 5.0 to build DLP lab

      I have created DLP manager (1 virtual disk) successfuly as following virtual appliance DLP 9.3 guide

      I turned off DLP manager VM and copied it to create a monitor VM (adding another virtual disks), then install monitor VM by convert the DLP manager installation using the iguard.tgz file

      I keep DLP manager turn off, power on the DLP monitor, configure new IP for new appliance (as it still storing IP of DLP manager), reset the service stingray then start it back

      and i got this error

      stingray(NOTE): Verify stingray_master has finished...

       

       

      current stingray state = STOP

       

       

      /sbin/sysctl -p /data/stingray/etc/sys_ctl

      net.ipv4.tcp_window_scaling = 0

      net.ipv4.tcp_timestamps = 0

      net.ipv4.conf.all.send_redirects = 0

      net.ipv4.conf.all.secure_redirects = 0

      net.ipv4.conf.all.accept_redirects = 0

      net.ipv4.conf.default.accept_redirects = 0

      net.ipv4.conf.default.secure_redirects = 0

      net.ipv4.conf.default.send_redirects = 0

      net.ipv4.conf.eth1.send_redirects = 0

      net.ipv4.conf.eth1.secure_redirects = 0

      net.ipv4.conf.eth1.accept_redirects = 0

       

       

       

       

      /usr/bin/ipcs -m >/data/stingray/tmp/shm_destroy.8895

       

       

      master(): /data/stingray/bin/shm_destroy

      stingray IPC is destroyed

       

       

      current stingray state = STOP

      setting state = DESTROY

       

       

      current stingray state = DESTROY

       

       

      /etc/init.d/stingray[253]: _start: line 124: 8900: Abort(coredump)

      current stingray state = DESTROY

       

       

      [start] requires current state to be INIT

       

      I checked the service stingray status again, it showed status DESTROY

      cheers,

      Tan

        • 1. Re: NDLP service stingray status DESTROY

          Hello qtanit,

           

          Check the /etc/hosts and /etc/sysconfig/network files on the Monitor and check that they have the correct host name for the Monitor.

           

          Whatever host name you use for the monitor, make sure it can be resolved on your DNS server.

           

          If the above checks and Stingray still is in a DESTROY state, load up the log file for the startup process (/data/stingray/log/systemstart.ksh.stdout and .stderr) so we can have a look. Also check if you find any core dump files under /data/ndlp_core/ - if you do please review our KB68826 for details on how to gather the core dump stack trace (you must be a registered user in order to view this article).

           

          Post output of 'cat /data/stingray/etc/version' as well.

           

          If you do not have access to the KB article please contact Support and open a service request so we can provide further assistance.

           

          Hope this helps.

          • 2. Re: NDLP service stingray status DESTROY
            qtanit

            Hi!

            I follow your instruction but i just come to this

             

            [root@monitor ~]# cd /data/ndlp_core

            [root@monitor ndlp_core]# ls -latr

            total 352888

            -rw-------  1 root root  4567040 Aug 21 20:16 core.stingray_config.7437

            -rw-------  1 root root 37048320 Aug 21 20:18 core.stingray_master.8549

            -rw-------  1 root root  4567040 Aug 21 20:23 core.stingray_config.5477

            -rw-------  1 root root 37048320 Aug 21 20:27 core.stingray_master.5717

            -rw-------  1 root root 37048320 Aug 21 20:27 core.stingray_master.6606

            -rw-------  1 root root 37056512 Aug 21 20:27 core.stingray_master.6649

            -rw-------  1 root root 37048320 Aug 21 20:28 core.stingray_master.7561

            -rw-------  1 root root  4567040 Aug 21 20:48 core.stingray_config.5475

            -rw-------  1 root root 37048320 Aug 21 20:53 core.stingray_master.5791

            -rw-------  1 root root 37048320 Aug 21 21:04 core.stingray_master.5884

            -rw-------  1 root root 37056512 Aug 21 21:05 core.stingray_master.6759

            -rw-------  1 root root 37052416 Aug 21 21:13 core.stingray_master.6868

            -rw-------  1 root root  4567040 Aug 21 21:24 core.stingray_config.5565

            drwxr-xr-x 25 root root     4096 Aug 21 21:31 ..

            -rw-------  1 root root  4567040 Aug 21 21:32 core.stingray_config.5561

            -rw-------  1 root root 37056512 Aug 21 21:32 core.stingray_master.5783

            drwxr-xr-x  2 root root     4096 Aug 21 21:32 .

            [root@monitor ndlp_core]# file core.stingray_config.7437

            core.stingray_config.7437: ELF 64-bit LSB core file AMD x86-64, version 1 (SYSV), SVR4-style, from 'stingray_con              fig'

            [root@monitor ndlp_core]# gdb 'stingray_config' /data/ndlp_core.stingray_config.7437

            GNU gdb Red Hat Linux (6.5-37.el5rh)

            Copyright (C) 2006 Free Software Foundation, Inc.

            GDB is free software, covered by the GNU General Public License, and you are

            welcome to change it and/or distribute copies of it under certain conditions.

            Type "show copying" to see the conditions.

            There is absolutely no warranty for GDB.  Type "show warranty" for details.

            This GDB was configured as "x86_64-redhat-linux-gnu"...stingray_config: No such file or directory.

             

             

            /data/ndlp_core.stingray_config.7437: No such file or directory.

            (gdb) bt

            No stack.

            (gdb) Quit

            (gdb)

             

            Cheers

            • 3. Re: NDLP service stingray status DESTROY

              Hi qtanit,

               

              When you start gdb, you need to provide the full path of the binary and of the core file.

               

              Also, check the output of the file command, it should tell you which stingray_config command core dumped (there are several stingray_config in /data/stingray/bin/).

               

              More importantly, did you check the network configuration as I suggested in the first two steps of my previous post?

               

              If you are having difficulties with troubleshooting this I strongly suggest you open a case with Technical Support, who may be able to assist over the phone or on a remote assistance session.