4 Replies Latest reply on Oct 30, 2017 12:37 PM by Seaf Al-Munayer Branched from an earlier discussion.

    Primary unable to ping Workers

    Seaf Al-Munayer

      Hi,

       

       

      I am running into a similar problem:

      I've started a support ticket in the meantime, but would appreciate any help otherwise.

       

       

      I attempted to onboard two worker nodes to my single node install.

      Late in the setup process, the primary node wasn't able to ping the worker nodes, with errors as follows:

       

       

      Status: STOPPED

      [workernode1name]:

      com.tableausoftware.tabctl.dll.NoServiceError: No service named 'tabsvc' is installed (1060).

      [workernode2name]:

      com.tableausoftware.tabctl.dll.NoServiceError: No service named 'tabsvc' is installed (1060).

       

       

      -0400_DEBUG_[primaryNodeName]_:_pid=14948_0x188ac8a3__user=__request=__ Failed to load configuration yamls

       

       

      Now I am unable to restart the server, even if I remove the workde nodes from the Server tab on the Primary's TS Configuration module.

       

       

      Any help is appreciated.

       

       

      I'm curious as to what and where you guys copied and replaced the missing files.

       

       

      Please and thank you!

        • 1. Re: Primary unable to ping Workers
          patrick.byrne.0

          Hello Seaf,

           

          Please verify that the tabadmin.exe is in the Tableau Server bin folder and that the tabadmin.exe size is not=0kb

           

          + Replace the tabadmin.exe if it either is not there or is at 0.

           

          I hope this helps!

           

          Cheers,

          Byrne, Patrick

          • 2. Re: Primary unable to ping Workers
            Jeff Strauss

            Hi Seaf.  Are you installing to the default location, and is it the same location on the workers as the primary?  Also, do you have proper rights (i.e. admin) on the workers?

            • 3. Re: Primary unable to ping Workers
              Jeff Strauss

              Also, when you setup the workers, did you specify the name of the primary?  This is necessary I believe for whitelisting.

              • 4. Re: Primary unable to ping Workers
                Seaf Al-Munayer

                Hey gang!

                 

                Thank you for your responses!

                 

                I ended up starting from scratch and took 3 clean virtual servers and attempted to setup a quick cluster install with one primary and two workers.

                 

                The primary installation went smooth, even setup Kerberos delegation successfully.

                Worker installations went smooth as well and I provided the server (computer) name rather than IP address.

                 

                Please verify that the tabadmin.exe is in the Tableau Server bin folder and that the tabadmin.exe size is not=0kb

                 

                • verified that on primary node, tabadmin.exe is present and size is not=0kb
                • The workers did not have any tabadmin.exe in their …\worker\admin directory (should there be?)

                 

                Are you installing to the default location, and is it the same location on the workers as the primary? 

                • No. I am installing on the D: drive on both the primary node and the workers

                 

                Also, do you have proper rights (i.e. admin) on the workers?

                • Yes, the RUN AS ACCOUNT as well as the account used for installation are both admins on all of the boxes

                 

                The point I get stuck at now is deep into the last steps of configuring the workers via the Tableau Server Configuration Panel on the Primary.

                 

                This is the log output of interest:

                 

                 

                2017-10-30 10:57:53.271 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Zip bundle is 122745801 bytes.

                2017-10-30 10:57:53.490 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Sending worker.zip to worker 1

                2017-10-30 10:57:53.505 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Connected to otvba007.seaf.gc.ca:3731

                2017-10-30 10:57:54.381 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Finished writing 122745801 bytes.

                2017-10-30 10:57:54.381 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Finished sending to worker 1

                2017-10-30 10:57:54.615 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Sending worker.zip to worker 2

                2017-10-30 10:57:54.615 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Connected to otvba006.seaf.gc.ca:3731

                2017-10-30 10:57:55.443 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Finished writing 122745801 bytes.

                2017-10-30 10:57:55.443 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Finished sending to worker 2

                2017-10-30 10:57:55.459 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Upgrading the administrative server on Worker 1

                2017-10-30 10:58:41.946 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Restarting  the administrative server on Worker 1

                2017-10-30 10:58:42.800 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Worker 1 upgraded successfully

                2017-10-30 10:58:42.800 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Upgrading the administrative server on Worker 2

                2017-10-30 10:58:42.992 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Restarting  the administrative server on Worker 2

                2017-10-30 10:58:43.710 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Worker 2 upgraded successfully

                2017-10-30 10:58:43.710 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Pinging worker 1 to see if it restarted.

                2017-10-30 11:00:23.279 -0400_ERROR_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Ping failed after admin restart on Worker #1: DRb::DRbConnError:druby://otvba007.seaf.gc.ca:3730 - #<Errno::ECONNREFUSED: Connection refused - Connection refused>

                2017-10-30 11:00:23.295 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ prep_worker Handling MultiCommand::ReportableError Workers not running: #1

                2017-10-30 11:00:23.295 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ Received ExitWithStatus, code 207

                2017-10-30 11:00:23.295 -0400_DEBUG_[OBFUSCATED IP]:OTVBA005_:_pid=4180_0x188ac8a3__user=__request=__ file:/D:/Tableau Server/10.3/bin/tabadmin.jar!/lib/commands/prep_workers.rb:56:in `run'

                file:/D:/Tableau Server/10.3/bin/tabadmin.jar!/lib/multicommand.rb:248:in `dispatch'

                file:/D:/Tableau Server/10.3/bin/tabadmin.jar!/bin/tabadmin.rb:35:in `(root)'

                org/jruby/RubyKernel.java:1058:in `load'

                file:/D:/Tableau Server/10.3/bin/tabadmin.jar!/bin/tabadmin.rb:1:in `(root)'

                org/jruby/RubyKernel.java:1033:in `require'

                file:/D:/Tableau Server/10.3/bin/tabadmin.jar!/META-INF/main.rb:36:in `require'

                <script>:3:in `(root)'

                 

                 

                 

                Please help!