Troubleshooting Your Installation
You can use log files to troubleshoot your installation. The log files are saved to the following locations:
Installation logs: <ThingWorx_Flow_Install_Location>\installer\logs\install.log
ThingWorx Flow running logs: <ThingWorx_Flow_Install_Location>\.pm2\logs\
Abort or failure logs
<system_temp_directory>/ThingWorxFlow_Failed_installs/
Example: /tmp/ThingWorxFlow_Failed_installs/
Uninstall logs
<system_temp_directory>/bitrock_installer_<pid>.log
The log file name has prefix bitrock.
Example: /tmp/bitrock_installer_3008.log
Scenario
Resolution
To validate ThingWorx Flow connectivity
If the ThingWorx Flow server URL is not accessible or returns an error code 502 or 504
If the ThingWorx Foundation host is not accessible from the ThingWorx Flow virtual machine
1. Navigate to the RabbitMQ log files under the <ThingWorx_Flow_Install_Location>\modules\RabbitMQ\log folder.
2. Open the log file and check if the following line is available in the log file:
user 'flowuser' authenticated and granted access to vhost 'orchestration'
3. If the line is not available, do the following:
Check the firewall connection on the ThingWorx Foundation virtual machine.
Ensure that the RabbitMQ port is accessible on both hosts.
Check if ThingWorx Foundation and ThingWorx Flow hosts can reach each other using the DNS name or the host name.
If flow execution in the engine stops abruptly
Review your software before you make any changes:
Set the ephemeral ports for services on your operating system between 5000 and 65535.
For information about ephemeral ports and its range, see The Ephemeral Port Range.
Reduce TIME_WAIT on sockets to 30 seconds.
If you have updated the password of the ThingWorx Flow database administrator, and if you want to update the same password in ThingWorx Flow
Was this helpful?