Review troubleshooting tasks for common issues.
Troubleshoot Connect by using log files and the solutions to common issues. If you cannot resolve the issues, collect support information.
To collect logs, click Help and open the Troubleshooting tab. Select whether you want to include database backups and click Create Package. After the support package is created, click Download Package to download the package that includes logs to send to support. If you included database backups, the backup files are named connect-<version>-<migrationCount>.db.bak-<backupTimestamp> where:
- <version> is the current version or pre-4.12.1
- <migrationCount> is the state of the database schema
- <backupTimestamp> is the milliseconds since epoch timestamp format when the backup was created
Adjust log expiration
To adjust the number of days before log files are removed, click Settings on the Connect Overview page and navigate to the Configuration tab. Edit the number of days in the Connection Run Log Expiration field and click Save.
Adjust log level
To adjust the log level, choose a log level from the Connect Service Log Level menu and click Save.
The Connect service records logs in the \Program Files\Tanium\Tanium Module Server\services\connect-files\logs\server.log file. This file is in JSON format by default, but you can use the Bunyan CLI tool to view the logs. From the \Program Files\Tanium\Tanium Module Server\services\connect-files\ directory, run the following command:
..\connect-service\node ..\connect-service\node_modules\bunyan\bin\bunyan logs\server.log
Search this log for the following message to tell when the Connect service starts:
Tanium Connect Starting
Connection run logs
Connections generate a log file for each run of the connection. The run logs are in the \Program Files\Tanium\Tanium Module Server\services\connect-files\logs\connections\ directory.
Connect configuration state
Connect stores information about connections and user settings in the \Program Files\Tanium\Tanium Module Server\services\connect-files\config\connect.db file.
Do not edit the connect.db file unless advised by Tanium Support.
If you have trouble with a connection, you can run the connection outside of the scheduled intervals.
- Send a test connection.
From the Connect Overview page, scroll to the Connections section. Select the checkbox next to the connection, click Run Now, and confirm to run the connection.
- Click the connection and open the Logs tab to view information about each run for that connection. Expand an individual row to view the log.
If you need more log data, open the Details tab, update the Log Level value, and click Save. Run the connection again to view the log with the updated log level.
- If the IP address for a connection is on an internal network, only a Tanium administrator can run the connection by default.
Click Settings on the Connect Overview page. On the Configuration tab, select Internal IPs to allow anyone to run connections to IPs on an internal network.
If a connection fails to send any data in a 60 minute period, Connect automatically terminates the connection.
- Verify that the Connect service is running on your Module Server.
To view the running services, click Start > Run. Type services.msc and click OK. Verify that Connect is in the list and that the service is running.
- Check the service logs for any errors or messages about insufficient rights for the user. The Connect service records logs in the \Program Files\Tanium\Tanium Module Server\services\connect-files\logs\server.log file.
Before your connections can successfully send data to a destination, your Tanium as a Service instance must be configured. Contact Tanium Support with the destination URL or IP and service port to submit a request.
For more information, see Tanium as a Service Deployment Guide: Proxy access.
- Verify that the sensor for the saved question is registered. For more information, see Tanium Console User Guide: Display sensor collection registration details.
- If the sensor is not registered, register it for collection. For more information, see Tanium Console User Guide: Register or unregister sensors for collection.
- If you recently registered a sensor and want to see immediate results before the next scheduled collection, you can manually start the collection. For more information, see Tanium Console User Guide: Manually start collection.
Scheduled connections require an existing Tanium user account owner to run scheduled instances. If the scheduled connection owner is deleted, future scheduled instances of that connection do not run.
Do one of the following:
Transfer ownership of the connection to an existing user. For more information, see Tanium Console User Guide: Delete or transfer ownership for the content of a non-active user.
The basic Connect module uninstallation is designed so that the data you have collected is restored if you later decide to reinstall Connect. In some cases, you might want to start "clean" and not restore the data. To do this, you must manually remove some files.
Consult with Tanium Support before you uninstall or reinstall Connect.
- Sign in to the Tanium Console as a user with the Administrator role.
- From the Main menu, go to Administration > Configuration > Solutions.
- Under Connect, click Uninstall.
- Review the summary and click Uninstall.
- When prompted to confirm, enter your password.
If you later import the Connect solution, the previous data is restored.
Uninstall Connect so you start fresh when you reinstall
- Uninstall Connect so data is restored on reinstall.
- Manually delete the \Program Files\Tanium\Tanium Module Server\services\connect-files\ directory.
Deleting the connect-files directory removes all existing Connect data. All logs, output, the Connect database, and any other Connect data is deleted. If you later import the Connect solution, the previous data is not restored.
To contact Tanium Support for help, sign in to https://support.tanium.com.
Last updated: 8/2/2021 2:00 PM | Feedback