4 Replies Latest reply on Jan 18, 2017 5:24 PM by dhbtemp

    CentOS-6.6 x86_64 vami problems Failed to start Scheduler Service

    paulhbeckerj Novice

      Are other people successfully building CentOS-6.6 x86_64 appliances with vmware-studio?

      I was finally able to build a CentOS-6.6 x86_64 appliance in vmware-studio after I added i686 glibc and zlib.

      and now when I boot the appliance I can not use vamicli for upgrade.

      Can anyone offer any suggestions for me so we can upgrade these appliances? - thanks

         (we are currently using CentOS-6.6 i686 successfully)

       

      I also attached:  /opt/vmware/var/log/vami/vami-sfcb.log

       

      {noformat}

      example:

      [root@localhost vami]# vamicli version --appliance

      Internal error.  Please make sure sfcbd is running.

      [root@localhost ~]#

      [root@localhost ~]# /etc/init.d/vami-sfcb restart

      Shutting down vami-sfcbd:                                  [  OK  ]

      Starting vami-sfcbd: /usr/bin/dirname: extra operand `-d.pid'

      Try `/usr/bin/dirname --help' for more information.

                                                                [  OK  ]

      Checking vami-sfcbd status:                                [  OK  ]

      Testing vami-sfcbd:                                        [  OK  ]

      Initializing vami-sfcbd:                                  [  OK  ]

      [root@localhost ~]#

      [root@localhost ~]# vamicli version --appliance

      Internal error.  Please make sure sfcbd is running.

      [root@localhost ~]#

      [root@localhost ~]#

      [root@localhost ~]# tail -13 /opt/vmware/var/log/vami/vami-sfcb.log

      22/06/2015 17:32:10 [info] [process id: 2864] Number of sfcbd processes: 7

      22/06/2015 17:32:10 [info] [process id: 2864] VAMI Scheduler provider is present on the system.

      22/06/2015 17:32:10 [ERROR] [process id: 2864] Failed to start Scheduler Service. Unknown error.

      22/06/2015 17:32:10 [ERROR] [process id: 2864] Traceback (most recent call last):

        File "/opt/vmware/share/vami/vami_sfcb_initialize", line 86, in main

          rettuple = vami_cim_util.invokeNonStaticMethod('root/vami', 'VAMI_SchedulerService', 'StartService')

        File "/opt/vmware/share/vami/vami_cim_util.py", line 36, in invokeNonStaticMethod

          insts = cliconn.EnumerateInstanceNames(className)

        File "/opt/vmware/lib/python/site-packages/pywbem/cim_operations.py", line 382, in EnumerateInstanceNames

          **params)

        File "/opt/vmware/lib/python/site-packages/pywbem/cim_operations.py", line 219, in imethodcall

          raise CIMError(code, tt[1]['DESCRIPTION'])

      CIMError: (6, u'Provider not found or not loadable')

      {noformat}

        • 1. Re: CentOS-6.6 x86_64 vami problems Failed to start Scheduler Service
          paulhbeckerj Novice

          I think the source of my issues could be that I have vami i386 RPMs being installed when I should just be getting all x86_64 packages that do exist on the vmware-studio system.

          I am not finding a setting that would give me the x86_64 vami RPMs. I have arch="x86_64" in my template build_profile.xml and build profile.

           

          Could someone tell me what I am missing so I can have x96_64 used for 'arch' in all (vami) parts of the build?

          These vami packages are the only i386 packages installed on the system and require me to install glibc.i686 and other i686 libs.

          I attached my template profile and my project profile.

          --thanks

           

           

          [root@rds32 ~]# rpm -qa | grep -i vami

          vmware-studio-vami-tools-2.6.0.0-631426.i386

          vmware-studio-vami-cimom-2.6.0.0-631426.i386

          vmware-studio-vami-service-core-2.6.0.0-0.x86_64

          vmware-studio-vami-service-system-2.6.0.0-0.x86_64

          vmware-studio-vami-lighttpd-2.6.0.0-631426.i386

          vmware-studio-vami-servicebase-2.6.0.0-631426.i386

          vmware-studio-vami-service-update-2.6.0.0-0.x86_64

          vmware-studio-vami-service-network-2.6.0.0-0.x86_64

           

          and these do exist onthe vmare-studio system

          /opt/vmware/lib/build/include/common/vmware-studio-vami-lighttpd_2.6.0.0-631426_x86_64.rpm

          /opt/vmware/lib/build/include/common/vmware-studio-vami-lighttpd_2.6.0.0-631426_i386.rpm

          /opt/vmware/lib/build/include/common/vmware-studio-vami-lighttpd_2.6.0.0-631426_amd64.deb

          /opt/vmware/lib/build/include/common/vmware-studio-vami-lighttpd_2.6.0.0-631426_i386.deb

          /opt/vmware/lib/build/include/rpm64/vmware-studio-vami-lighttpd_2.6.0.0-631426_x86_64.rpm

          /opt/vmware/lib/build/include/deb64/vmware-studio-vami-lighttpd_2.6.0.0-631426_amd64.deb

          /opt/vmware/lib/build/include/deb/vmware-studio-vami-lighttpd_2.6.0.0-631426_i386.deb

          /opt/vmware/lib/build/include/rpm/vmware-studio-vami-lighttpd_2.6.0.0-631426_i386.rpm

           

          root@vmwarestudio1:~# grep -i arch /root/templates/CentOS-6.6-x86_64/build_profile.xml /opt/vmware/var/lib/build/profiles/Unidesk_MA_msodhyp_azure64.xml

          /root/templates/CentOS-6.6-x86_64/build_profile.xml:    <vadk:Distribution vadk:vendor="" vadk:OSverMajor="" vadk:OSverMinor="" vadk:arch="x86_64" vadk:smp="1" vadk:packageFormat="rpm" vadk:packageManager="yum" vadk:packageRepoDir="packageRepoDir"/>

          /opt/vmware/var/lib/build/profiles/Unidesk_MA_msodhyp_azure64.xml:             <vadk:Distribution vadk:vendor="" vadk:OSverMajor="" vadk:OSverMinor="" vadk:arch="x86_64" vadk:smp="1" vadk:packageFormat="rpm" vadk:packageManager="yum" vadk:packageRepoDir="packageRepoDir"/>

          • 2. Re: CentOS-6.6 x86_64 vami problems Failed to start Scheduler Service
            paulhbeckerj Novice

            Even after I manually force the install of all the x86_64 vami RPMs,

            I am still not able to run vamicli commands. All I get is this:

               Internal error.  Please make sure sfcbd is running.

            So I guess vami-sfcb will not work on CentOS-6.6_x86_64.

            I could not get it work anyway and so we can not use vmware-studio anymore.

            So I guess vmware-studio has been abandoned for some new project

            and we are all stuck to find new solutions. It was a very useful tool.

            I was hoping it would last longer...

            • 3. Re: CentOS-6.6 x86_64 vami problems Failed to start Scheduler Service
              paulhbeckerj Novice

              I had to change thnis in my build profule.

              from:

                  vadk:sourceDir="[VADK.vadkRoot]/lib/build/include/rpm/"

              to

                  vadk:sourceDir="[VADK.vadkRoot]/lib/build/include/rpm64/"

               

              I was not aware that there were 64bit templates for a new os.

              When I used this, things were better.

                  /opt/vmware/etc/build/templates/redhat/6/0_x86_64/build_profile.xml

               

              studiocli --newos --osdesc "CentOS-6.6-x86_64" --profile /opt/vmware/etc/build/templates/redhat/6/0_x86_64/build_profile.xml

              • 4. Re: CentOS-6.6 x86_64 vami problems Failed to start Scheduler Service
                dhbtemp Novice

                Hi, paulhbeckerjpaulhbeckerj

                I am trying to build centOS7 using vmware studio.But there are lots of problems.

                I think it is easier to build centOS6 using vmware stuido. So I use vmware studio to build  centos6 i386.


                but when building the centos6 here are the problems.

                "The flowing probkem occurred on line 62 of the kickstart file: "

                "--bytes-per-inode option does not take a vale"

                can you tell me how to fix this problem?


                In your post you mentioned  "I was finally able to build a CentOS-6.6 x86_64 appliance in vmware-studio after I added i686 glibc and zlib."

                can you tell me where to add the glib and zlib?


                I'll appreciate that If you can offer me centOS6/7 templates and the libs.


                Here are my template file. please check it.Thank you.