Skip to main content

What the tabadmin status command produces (all four Backgrounders are running):

Inaccurate tabadmin status reporting?

What the Server Status produces before and after the above tabadmin command:

pastedImage_1.png

One is clearly down.  What made me check this is I actually had THREE of my Backgrounders down!  I have a script that executes the tabadmin command and emails me if anything is not RUNNING.  I received no emails so I checked the script and thus the command and discovered this discrepancy.

 

Ideas on what's going on?

5 answers
  1. Apr 27, 2016, 5:56 PM

    I will take a guess based on vague distant memories for a while back.  I want to say that either the "tabadmin status" or "server status page" ping the port that is supposed to be open and if the port isn't open then it reports as down.  But, it may be inconsistent across.

     

    We also have a script that checks status that is deployed within our monitoring app.  It looks at the XML admin status page.  And it seems to work for the most part (99%), but on occasion we do get false alarms.  Are you familiar with the XML status page?  http://my_tableau_server/admin/systeminfo.xml

0/9000