7 Replies Latest reply on Jul 29, 2018 11:05 PM by Toby Erkson Branched to a new discussion.

    Tableau Server is down because of Gateway is stopped

    lalitha p

      Hello Everyone,

         Tableau server 2018.1 is running fine till yesterday. I have taken backup then clean up and done restart.

       

        Status: Degraded

        Tableau Server Gateway <10800> is stopped.

       

      Not really sure why i am getting this error. Have checked httpd folder for error. But there are no errors registered there.

       

      Urgent help required. 

        • 1. Re: Tableau Server is down because of Gateway is stopped
          Ghouse Shaik

          Hi Lalitha,

           

          Please go through the article Gateway Service Does Not Start and Server Status is Degraded | Tableau Software .

           

          Please let me know if the above provided article will works or not.

           

          Thanks & Regards,

          Ghouse.

          • 2. Re: Tableau Server is down because of Gateway is stopped
            Mark McGhee

            Hi Lalitha,

             

            If this is a Production instance and you're down I would strongly recommend opening a support case if you haven't already. 

             

            That said, it never hurts to ask for additional help from the forums.  The most critical events when Tableau Server is first starting up (or experiencing a restart) is recorded in the tabadmin.log file.  Inside that log you'll actually be able to see individual services attempt to start and what port they are trying to use.  It's not too uncommon after folks reboot their system that an anti-virus program might grab a needed port.

            • 3. Re: Tableau Server is down because of Gateway is stopped
              Muteru Mwangi

              Hi Mark,

               

              For times when the Tableau Server goes down, is there a documented process that we should be following to investigate and correct the issue(s)?

               

              Thanks!

              Muteru Mwangi

              • 4. Re: Tableau Server is down because of Gateway is stopped
                Michael Moore

                Hi Mark,

                 

                Do you know if the services have defined ports or do they just get assigned any available port at random?  If the ports are fixed for these processes then it would probably be a good idea to reserve the ports in the  registry to prevent another process such as virus scan from grabbing the port.

                • 5. Re: Tableau Server is down because of Gateway is stopped
                  Mark McGhee

                  For the ports Tableau Server will try to use the defaults when possible:

                  ------------------

                  Tableau Server Ports

                   

                  Dynamic port remapping

                  When dynamic port remapping is enabled (the default), Tableau Server first attempts to bind to the default ports, or to user-configured ports if they are defined. If the ports are not available, Tableau Server attempts to remap most processes to other ports, starting at port 8000. When next restarted, Tableau Server will revert to using the default or configured ports.

                   

                   

                  In the tabadmin.log file you can see what ports were selected during startup.  Below is a snippet taken from my installation:

                  =====================================================

                  018-07-13 10:45:00.883 -0700_DEBUG_10.46.4.86:MMCGHEE:_pid=3136_0x1b7a52dd__user=__request=__ Hyper::include_component? true

                  2018-07-13 10:45:00.884 -0700_DEBUG_10.46.4.86:MMCGHEE:_pid=3136_0x1b7a52dd__user=__request=__ Checking a range of 1 port(s) for hyper.port, default 7483.

                  2018-07-13 10:45:00.884 -0700_DEBUG_10.46.4.86:MMCGHEE:_pid=3136_0x1b7a52dd__user=__request=__ Checking a range of 1 port(s) for pgsql.port, default 8060.

                  2018-07-13 10:45:00.885 -0700_DEBUG_10.46.4.86:MMCGHEE:_pid=3136_0x1b7a52dd__user=__request=__ Checking a range of 1 port(s) for worker0.vizqlserver.port, default 9100.

                  2018-07-13 10:45:00.885 -0700_DEBUG_10.46.4.86:MMCGHEE:_pid=3136_0x1b7a52dd__user=__request=__ Checking a range of 1 port(s) for worker0.dataserver.port, default 9700.

                  2018-07-13 10:45:00.885 -0700_DEBUG_10.46.4.86:MMCGHEE:_pid=3136_0x1b7a52dd__user=__request=__ Checking a range of 1 port(s) for worker0.cacheserver.port, default 6379.

                  2018-07-13 10:45:00.886 -0700_DEBUG_10.46.4.86:MMCGHEE:_pid=3136_0x1b7a52dd__user=__request=__ Checking a range of 1 port(s) for worker0.searchserver.port, default 11000.

                  2018-07-13 10:45:00.886 -0700_DEBUG_10.46.4.86:MMCGHEE:_pid=3136_0x1b7a52dd__user=__request=__ Checking a range of 1 port(s) for worker0.vizportal.port, default 8600.

                  2018-07-13 10:45:00.887 -0700_DEBUG_10.46.4.86:MMCGHEE:_pid=3136_0x1b7a52dd__user=__request=__ Checking a range of 1 port(s) for worker0.vizportal.authorization.port, default 8625.

                  2018-07-13 10:45:00.887 -0700_DEBUG_10.46.4.86:MMCGHEE:_pid=3136_0x1b7a52dd__user=__request=__ Checking a range of 1 port(s) for worker0.vizportal.recommendations.port, default 8650.

                  • 6. Re: Tableau Server is down because of Gateway is stopped
                    Mark McGhee

                    One other issue that has bubbled up and I think it's already been discussed in the thread on the forum and would have to track that thread down but it's basically an issue with the July OS Windows patches:

                     

                     

                    Tableau Server Becomes Unstable After Applying July 10, 2018 Windows Update

                    https://kb.tableau.com/articles/Issue/kb4338818-windows-update-causing-tableau-server-to-become-unstable

                    1 of 1 people found this helpful
                    • 7. Re: Tableau Server is down because of Gateway is stopped
                      Toby Erkson

                      I set the logging level to DEBUG on my TS and after TABADMIN START finished my Gateway was down   I reset my logging level to the default level and the issue persisted   Prior to the restart the Gateway was functional.  After some searching I saw Mark's reply so I read the article.  Darn, we had a patch this weekend.  So I rebooted both nodes (primary and one worker) and when they came back up everything was working correctly.  I'll need to look through my emails to find the one regarding the patch and see which ones were applied...