5 Replies Latest reply on Mar 10, 2011 6:23 AM by kwouellette

    vami-sfcbd not responding on CentOS 5.3

    kwouellette Novice

      We've encountered this a couple of times where this service doesn't respond to commands. Specifically, we are calling "/opt/vmware/bin/vamicli version --appliance" commannd and this hangs. I do see vami-sfcbd running in the background (see below). We also tried the "update --check" command with the same results. Restarting the service cleared the condition. Any ideas what might be causing this or what information I should grab to diagnose the problem.

       

      Thanks,

       

      Ken

       

       2725 ?        Ssl    0:00 /opt/vmware/sbin/vami-sfcbd -d CONSOLE=/dev/console
      SELINUX_INIT=YES TERM=linux LD_LIBRARY_PATH=/opt/vmware/lib:
      INIT_VERSION=sysvinit-2.86 PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin
      runlevel=3 RUNLEVE
       2747 ?        S      0:00  \_ /opt/vmware/sbin/vami-sfcbd -d
      CONSOLE=/dev/console SELINUX_INIT=YES TERM=linux
      LD_LIBRARY_PATH=/opt/vmware/lib: INIT_VERSION=sysvinit-2.86
      PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=3 RUN
       4090 ?        S      0:00  |   \_ /opt/vmware/sbin/vami-sfcbd -d
      CONSOLE=/dev/console SELINUX_INIT=YES TERM=linux
      LD_LIBRARY_PATH=/opt/vmware/lib: INIT_VERSION=sysvinit-2.86
      PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=3
       7971 ?        S      0:00  |   \_ /opt/vmware/sbin/vami-sfcbd -d
      CONSOLE=/dev/console SELINUX_INIT=YES TERM=linux
      LD_LIBRARY_PATH=/opt/vmware/lib: INIT_VERSION=sysvinit-2.86
      PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=3
       8198 ?        S      0:00  |   \_ /opt/vmware/sbin/vami-sfcbd -d
      CONSOLE=/dev/console SELINUX_INIT=YES TERM=linux
      LD_LIBRARY_PATH=/opt/vmware/lib: INIT_VERSION=sysvinit-2.86
      PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=3
      15372 ?        S      0:00  |   \_ /opt/vmware/sbin/vami-sfcbd -d
      CONSOLE=/dev/console SELINUX_INIT=YES TERM=linux
      LD_LIBRARY_PATH=/opt/vmware/lib: INIT_VERSION=sysvinit-2.86
      PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=3
      15471 ?        S      0:00  |   \_ /opt/vmware/sbin/vami-sfcbd -d
      CONSOLE=/dev/console SELINUX_INIT=YES TERM=linux
      LD_LIBRARY_PATH=/opt/vmware/lib: INIT_VERSION=sysvinit-2.86
      PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=3
      15565 ?        S      0:00  |   \_ /opt/vmware/sbin/vami-sfcbd -d
      CONSOLE=/dev/console SELINUX_INIT=YES TERM=linux
      LD_LIBRARY_PATH=/opt/vmware/lib: INIT_VERSION=sysvinit-2.86
      PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=3
      15625 ?        S      0:00  |   \_ /opt/vmware/sbin/vami-sfcbd -d
      CONSOLE=/dev/console SELINUX_INIT=YES TERM=linux
      LD_LIBRARY_PATH=/opt/vmware/lib: INIT_VERSION=sysvinit-2.86
      PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=3
       2748 ?        S      0:00  \_ /opt/vmware/sbin/vami-sfcbd -d
      CONSOLE=/dev/console SELINUX_INIT=YES TERM=linux
      LD_LIBRARY_PATH=/opt/vmware/lib: INIT_VERSION=sysvinit-2.86
      PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=3 RUN
       2749 ?        Sl     0:00  \_ /opt/vmware/sbin/vami-sfcbd -d
      CONSOLE=/dev/console SELINUX_INIT=YES TERM=linux
      LD_LIBRARY_PATH=/opt/vmware/lib: INIT_VERSION=sysvinit-2.86
      PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=3 RUN
       3674 ?        Sl     0:00  \_ /opt/vmware/sbin/vami-sfcbd -d
      CONSOLE=/dev/console SELINUX_INIT=YES TERM=linux
      LD_LIBRARY_PATH=/opt/vmware/lib: INIT_VERSION=sysvinit-2.86
      PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=3 RUN
       3725 ?        Sl     0:00  \_ /opt/vmware/sbin/vami-sfcbd -d
      CONSOLE=/dev/console SELINUX_INIT=YES TERM=linux
      LD_LIBRARY_PATH=/opt/vmware/lib: INIT_VERSION=sysvinit-2.86
      PATH=/opt/vmware/sbin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=3 RUN
        • 1. Re: vami-sfcbd not responding on CentOS 5.3
          Jogarem Enthusiast

          Hello Ken,

           

           

           

          hm have you taken a look into the vami-sfcb logfile?

           

          You can find it on the appliance at:

           

           

           

          /opt/vmware/var/log/vami/vami-sfcb.log
          

           

           

          Maybe there are some more hints in there why. You can also look into the other logfiles under

           

           

           

          /opt/vmware/var/log
          
          /opt/vmware/var/log/vami/vami-sfcb.log

           

          Regards

          Thomas

          • 2. Re: vami-sfcbd not responding on CentOS 5.3
            kwouellette Novice

            Good tip Thomas. I see this in the vami-sfcb.log file:

             

             

            08/03/2011 09:42:08 [info] [process id: 2728] Starting a new initialization script.
            08/03/2011 09:42:08 [info] [process id: 2728] Pids passed in are 2725. Sleeping for 300 (secs).
            08/03/2011 09:47:07 [info] [process id: 2728] ran command: ps -p 2725
            08/03/2011 09:47:07 [info] [process id: 2728] ps returned process:   PID TTY          TIME CMD
            08/03/2011 09:47:07 [info] [process id: 2728] ps returned process:  2725 ?        00:00:00 vami-sfcbd
            08/03/2011 09:47:07 [info] [process id: 2728] Number of sfcbd processes: 1
            08/03/2011 09:47:07 [info] [process id: 2728] VAMI Scheduler provider is present on the system.
            08/03/2011 16:45:03 [ERROR] [process id: 2728] Failed to start Scheduler Service. Unknown error.
            08/03/2011 16:45:03 [ERROR] [process id: 2728] Traceback (most recent call last):
              File "/opt/vmware/share/vami/vami_sfcb_initialize", line 85, in main
                rettuple = vami_cim_util.invokeNonStaticMethod('root/vami', 'VAMI_SchedulerService', 'StartService')
              File "/opt/vmware/share/vami/vami_cim_util.py", line 74, in invokeNonStaticMethod
                insts = cliconn.EnumerateInstanceNames(className)
              File "/opt/vmware/lib/python/site-packages/pywbem/cim_operations.py", line 369, in EnumerateInstanceNames
                ClassName = CIMClassName(ClassName),
              File "/opt/vmware/lib/python/site-packages/pywbem/cim_operations.py", line 169, in imethodcall
                raise CIMError(0, str(arg))
            CIMError: (0, "The web server returned a bad status line: ''")

             

            Thanks,

             

            Ken

            • 3. Re: vami-sfcbd not responding on CentOS 5.3
              Jogarem Enthusiast

              Ok that's something which must be analyzed by VMware.. (or some python guy).

              Sorry but here I can't help further

              • 4. Re: vami-sfcbd not responding on CentOS 5.3
                Enthusiast

                Hi Ken,

                 

                Could you give me some more information.

                 

                1) What version of Studio is being used?

                 

                2) What is the best way to reproduce this?  Does the VM need to be runnig for a long time first, does it need to have an update done first, does it need  to have many near-simultaneous call to sfcbd, many web pages concurrently opened sitting on the update page?

                 

                Thanks,

                -Matt

                • 5. Re: vami-sfcbd not responding on CentOS 5.3
                  kwouellette Novice

                  Hi Matt,

                   

                  Sure, the Studio version is "Version - 2.0.0.1017 Build 185256".

                   

                  We've seen it a couple of times, once where the VM was up and running for a few hours and the other where it was up and running for a few minutes. No updates done in either case, just the display of the version information. There shouldn't be any concurrent access to sfcbd. We only use it for accessing the version info when logging into the CLI and for updating which is also part of the CLI. We don't have any web access to the update page.

                   

                  Thanks,

                   

                  Ken