Tip: The Restart Trifacta button in the Admin Settings page is the preferred method for restarting the platform.

NOTE: The restart button is not available when high availability is enabled for the .

See Admin Settings Page in the Admin Guide.

Command Line

NOTE: In an Azure HDI environment, you must perform platform start and stop operations from /opt/trifacta. Running these commands from other directories, such as /root, can cause service issues.


NOTE: These operations must be executed under the root user.


service trifacta start

Verify operations


  1. Check logs for errors:



    1. You can also access logs through the  for each service. See System Services and Logs in the Admin Guide. 

  2. Login to the . If available, perform a simple transformation operation. See  Login.

  3. Run a simple job. See Verify Operations in the Admin Guide.



service trifacta restart

When the login page is available, the system has been restarted. See Login.



service trifacta stop

Configure Platform Restart

By default, the  waits for a period of time for the  to restart before re-activating the user interface. As needed, you can review and modify the following settings, which define the parameters of these restarts.


  1. Locate the following parameters, and adjust settings as needed:

    "webapp.waitForRestart.initialWait": 45000,
    "webapp.waitForRestart.intervalWait": 5000,
    "webapp.waitForRestart.maxChecks": 60,

    Number of seconds to wait for the before checking it for a successful restart. Default is 45000 milliseconds (45 seconds).


    After the initial wait period has failed, this value is the number of seconds to wait before checking the for a successful restart. Default is 5000 milliseconds (5 seconds).


    Total number of checks for a successful restart before failing the .

  2. Save your changes and restart the application.


You can verify operations of WebHDFS. Command:

curl -i  "http://<hadoop_node>:<port_number>/webhdfs/v1/?op=LISTSTATUS&user.name=trifacta"

Error - "ImportError: No module named pkg_resources" error in supervisord

When you start the platform for the first time, you may receive the following error:

Traceback (most recent call last):
File "/usr/local/bin/supervisord", line 5, in <module>
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

This error occurs when the supervisord process is starting. The   fails to complete startup.


This issue is caused by a missing package for supervisord. The simplest solution is to install the Python setup tools on the . Commands are listed below.

NOTE: These commands must be executed as root user.


yum install python-setuptools


wget https://bootstrap.pypa.io/ez_setup.py -O - | python

After installation is complete, restart the platform.

Error - SequelizeConnectionRefusedError: connect ECONNREFUSED

If you have attempted to start the platform after an operating system reboot, you may receive the following error message, and the platform start fails to complete: 

2016-10-04T14:03:17.883Z - error: [ENVIRONMENT] Environment Sanity Test Failed
2016-10-04T14:03:17.883Z - error: [ENVIRONMENT] Exception Type: Error
2016-10-04T14:03:17.883Z - error: [ENVIRONMENT] Exception Message: SequelizeConnectionRefusedError: connect ECONNREFUSED


NOTE: This solution applies to PostgreSQL 12 only. Please modify for your installed database version.

This error can occur when the operating system is restarted. Please execute the following commands to check the PostgreSQL configuration and restart the databases. 

chkconfig postgresql-12 on

Then, restart the platform as normal. 

service trifacta restart