2 Replies Latest reply on Aug 14, 2008 3:06 AM by rrdharan

    Timeout (30000 milliseconds) waiting for the VMware Authorization Service service to connect.

    ctr99 Lurker

       

      I have just upgraded from VMWare Server 1.0.3 to Beta 2 RC1 on a Windows XP SP2 x86 system.

       

       

      Now, whenever I start this machine, I see errors in the event log:

       

       

      First: Timeout (30000 milliseconds) waiting for the VMware Authorization Service service to connect.

       

       

      Second: The VMware Authorization Service service failed to start due to the following error:

       

       

      The service did not respond to the start or control request in a timely fashion.

       

       

      Third: The VMware Host Agent service depends on the VMware Authorization Service service which failed to start because of the following error:

       

       

      The service did not respond to the start or control request in a timely fashion.

       

       

      But if I start them manually after logging in, they start up fine.

       

       

       

       

       

      When I start these services manually, I also see an error:

       

       

      Cannot connect to VMX: C:\Virtual Machines\FedoraCore6\Other Linux 2.6.x kernel.vmx

       

       

       

       

       

      How can I resolve these problems?

       

       

       

       

       

      Thanks,

       

       

       

       

       

      Chris.

       

       

        • 1. Re: Timeout (30000 milliseconds) waiting for the VMware Authorization Service service to connect.
          afred Lurker

           

          I have similiar problem with the Beta 2rc1, but on linux fedora9, x86_64

           

           

          the install was succesful. (apparently but...)

           

           

          netstat -alpn shows

           

           

          tcp 0  0 0.0.0.0:902   0.0.0.0:* LISTEN 6855/vmware-authdla

           

           

          I have disabled ip6

           

           

          It must be reading something, because if connect with http://127.0.0.1:902

           

           

          the reply is the complaint about SSL etc...

           

           

          but https://127.0.0.1:902 never responds

           

           

           

           

           

          The other i/f (not sure what that is)  https://127.0.0.1:8333/ui

           

           

          well I get a login dialog for "VMware infrastructure Web Access"

           

           

          but the result is "The server is not responding.Please check that the server is running and accepting connections"

           

           

          What server would it specifically be referring to ?    vmware-hostd apparently is doing the listening on port 8333

           

           

           

           

           

          • 2. Re: Timeout (30000 milliseconds) waiting for the VMware Authorization Service service to connect.
            Expert
            afred wrote:

             

            I have similiar problem with the Beta 2rc1, but on linux fedora9, x86_64

             

            It is very unlikely that the Linux and Windows issues you guys are talking about are related. I'm not sure what is causing the Windows issue.

             

            netstat -alpn shows

             

            tcp 0  0 0.0.0.0:902   0.0.0.0:* LISTEN 6855/vmware-authdla

             

             

            I have disabled ip6

             

            It must be reading something, because if connect with http://127.0.0.1:902

             

             

            the reply is the complaint about SSL etc...

             

             

            but https://127.0.0.1:902 never responds

             

            vmware-authdlauncher is just a simple wrapper which listens on 902 and launches the vmware-authd binary. I wrote it because it was the simplest way to get rid of our dependence on inetd/xinetd which are not installed on many Linux systems, and for which configuration is difficult when you're trying to distribute standalone/distro-independent packages. Neither authdlauncher nor authd implement or communicate by HTTP, they use a simple (but proprietary authentication mechanism) and are basically just plumbing services which we use to establish a secure channel to talk to various VM-specific services like the remote display channel (which is just VNC over SSL with a bunch of VMware VNC extensions to improve performance).

             

            The other i/f (not sure what that is)  https://127.0.0.1:8333/ui

             

            well I get a login dialog for "VMware infrastructure Web Access"

             

            That's the main/real web UI, and the one that you should be pointing your browser at.

             

            but the result is "The server is not responding.Please check that the server is running and accepting connections"

             

            What server would it specifically be referring to ?    vmware-hostd apparently is doing the listening on port 8333

             

            You should check that both vmware-webAccess and vmware-hostd are running. vmware-hostd listens on port 8333 but, similar to authd/authdlauncher, it proxies requests for the /ui URL namespace over to the vmware-webAccess service. vmware-webAccess and vmware-hostd communicate with each other via a local pipe. It sounds like that local pipe communication is broken on your machine.

             

            If you could attach /var/log/vmware/hostd.log that would probably help in diagnosing your problem.