If you suspect you've got an aborted install, the best move is probably to send the logs from the worker and primary to Tableau Support.
I don't know of any particular "partial-install-failure" problems myself.
Thanks for the response James. I just found the other files for my secondary server. So it looks like the installation was successful. Now, when I'm trying to add the secondary server, the primary server is simply telling me that my server worker is not responding. I am running this in the Amazon cloud but have opened all the ports for TCP between my primary and secondary servers.
There is nothing in the log other than the following:
"Worker '###.###.###.###' is not responding.
Make sure the worker is installed and running."
Is there anything basic I should look for?
Don't you have to do something funky like hook up S3 as a disk to your EC2 instance in order to have persistent storage? (This is just from a very very passing knowledge of EC2.) I remember someone telling me that there were several issues that made EC2 not a good candidate for scaling out a distributed Tableau Server. Unfortunately, I don't remember much more than that.
Yeah we've got Tableau up and running fine using EBS (not S3). It's just the worker I'm having a problem with. Again. Thanks.
Hi David, I am having the same issue. did you manage to get the worker "Working" ?