This page provides answers to frequently asked questions and tips for troubleshooting your Teamwork Cloud (TWCloud) system.
tocFor additional frequently asked questions and tips regarding the authentication server check the following sections:
Children Display
Warning
title
Warning
When configuring cassandra.yaml, take note of the following:
There is a space before each IP address for parameters "listen_address" and "broadcast_rpc_address". The space is required for Cassandra to start.
When entering the parameters to configure cassandra.yaml, be sure that there is no '#' (pound sign) or 'space' before the parameter name. If there is a #, for example, #broadcast_rpc_address: 10.1.1.123, this value will become a comment. If there is a space before the parameter name, for example, <space>#broadcast_rpc_address: 10.1.1.123, you will get an error after starting Cassandra.
Frequently Asked Questions
I cannot
login
log in with the default Administrator user via TWCloud Admin UI. What could be the cause of the problem?
There are several causes of AdministratiorAdministrator's login failure such as:
Cassandra is not started so TWCloud cannot connect to it.
Cassandra is started but TWCloud cannot connect to it due to Cassandra and/or network configuration problem.
To find out what the cause of the problem is, you need to look at the log file and check the status of Cassandra. SeeTroubleshooting section Troubleshooting section for more information.
Where can I find the TWCloud log file?
The default log file location is is <user home folder>/.twcloud/<version number>.
The log file of TWCloud is called server.log.The log file of TWCloud Admin is called clientcalled server.log.
How do I check the Cassandra status?
Cassandra provides a nodetool utility, which is a command-line interface for managing a cluster. You can use it for checking the cluster status.
On Linux, type:
Code Block
language
bash
theme
DJango
linenumbers
true
$ nodetool status
On Windows, type:
Code Block
language
bash
theme
DJango
linenumbers
true
C:\> "%CASSANDRA_HOME%"\bin\nodetool status
The following is an example output from running the nodetool status.
Code Block
Starting NodeTool
Datacenter: datacenter1
========================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--
Address Load Tokens Owns Host ID RackUN
Address Load Tokens Owns Host ID Rack
UN 10.1.1.
123
123 16.71
MB 256 ?
MB 256 ? 32f17f36-baec-409a-a389-
f002d1dd0f9b
f002d1dd0f9b rack1
UN means that the status is up and normal.
How do I check if TWCloud has a problem connecting to Cassandra?
You can check it from the log file of TWCloud. If TWCloud cannot connect to Cassandra during the TWCloud startup process, a log message similar to the following will appear and the server will shut itself down.
Code Block
INFO
INFO 2016-01-04 11:12:32.131 Connecting to Cassandra [CoreManagerComponent, Component Resolve Thread]
ERROR 2016-01-04 11:12:50.351 Connection to Cassandra failed due to timeout [CoreManagerComponent, Component Resolve Thread]
You may also find yourself in a situation where TWCloud has been started successfully but the problem connecting to Cassandra occurs later. If this happens, a log message similar to the following will appear.
WARN
Code Block
WARN 2016-01-04 13:57:26.034 There was a problem with the connection between the TWCLOUD server and Cassandra
I cannot see the project history or branch or perform any operations related to the project history from MagicDraw. What could be the cause of the problem and how to solve it?
You need to check if it is the a known issue by looking at the the server.logfile file. If you see the following ERROR message, it is the a known issue.
You can solve this issue by adding the following code line at the end of the configuration file,<TWC install folder>/configuration/application.conf.
Code Block
language
text
esi.serializer.max-buffersize = -1
After updating the configuration, you will need to restart TeamworkCloud.
Anchor
Troubleshooting
Troubleshooting
Troubleshooting
The TWCloud installer is not started on Windows
If you run the installer file and the installer UI does not show up or receive the message: "Windows error 2", try the following workaround.
Start the command prompt by selecting "Run as administrator".
Start the installer from the command line and use the option LAX_VM followed by the location of java.exe. For example: C:\> twcloud_190_beta_installer_win64.exe LAX_VM "C:\Program Files\java\jdk1.8.0_152\bin\java.exe"
I cannot uninstall TWCloud using uninstall.exe
If you rununinstall uninstall.exeand and the uninstall UI does not show up or receive the message "Windows errors", try the following workaround.
Start the command prompt by selecting "Run as administrator".
Start Start uninstall.exefrom from the command line and using use the option LAX_VM followed by the location of java.exe. For example: C:\> uninstall.exe LAX_VM "C:\Program Files\java\jdk1.8.0_152\bin\java.exe
TWCloud cannot connect to Cassandra
If the TWCloud server log shows the following message:
INFO
Code Block
INFO 2016-01-04 11:12:32.131 Connecting to Cassandra [CoreManagerComponent, Component Resolve Thread]
ERROR 2016-01-04 11:12:50.351 Connection to Cassandra failed due to timeout [CoreManagerComponent, Component Resolve Thread]
It means that TWCloud cannot connect to Cassandra and this is usually caused by the following reasons:
Cassandra is not started.
Cassandra is started but it is not properly configured for TWCloud cloud. You need to make sure that you follow the Cassandra configuration instruction and that you restart Cassandra after updating the configuration. You can find the configuration instruction from the following links:
Error [Association failed with [akka.tcp://twcloud@10.1.1.123:2552]] [akka.remote.EndpointAssociationException:
Association failed with [akka.tcp://twcloud@10.1.1.123:2552]
You need to check if the hostname can be resolved to the IP that you specified while installing TWCloud.
From the log message given in the example above, you will see two IP addresses in the message message 127.0.0.1and and 10.1.1.123. They mean that you have specified the IP address10 10.1.1.123during during TWCloud installation, however, your hostname is resolved to loopback IP127 127.0.0.1.
You can configure how your machine resolves the hostname from the hosts file. The location of the hosts file:
On Linux:/etc/hosts
On Windows:%SystemRoot%\system32\drivers\etc\hosts
You can check what IP address is resolved from the hostname by using the following steps:
On Linux:
Execute the following command
command
Code Block
$ resolveip -s $(hostname)
On Windows
Step 1: Find hostname of the machine.
Code Block
C:\>hostname
Step 2: Use the ping command followed by the hostname you got from Step 1. For example, if your hostname is is my-machine, use the command.
c
Code Block
C:\> ping my-machine
TWCloud Admin UI does not refresh information when opened with Internet Explorer
Every time you edit and save information on the TWCloud Admin, the updates will appear in the TWCloud Admin UI. If you are using the IE browser and your UI does not reflect what you have just updated, you may need to configure the internet settings.
To make sure that your TWCloud Admin UI refreshes new updates every time you edit and save information
On the IE browser, click click > > Internet options to open theInternet Internet Optionsdialog dialog.
On the the Generaltab tab, click click . The The Website Data Settingsdialog dialog will open.
Select the option option Every time I visit the webpage to update website data.
Click Click > > .
Compatibility issue when logging into TWCloud Admin using Internet Explorer 11
You may experience some incompatibility issue issues while logging into TWCloud Admin using Internet Explorer 11, which might cause an error in the display.
To fix the problem
On the Internet Explorer browser, click click > > Compatibility View Settings.
Clear the option Display intranet sites in Compatibility View.
