Documentation Data Sources FAQs

Restart the tunnel connection client

The Connection Client has been deprecated for new connections. If your connection was created after mid-2015, you're likely using autossh instead. Check out our autossh documentation.

The tunnel client can be restarted by logging on to the database server and running the following:
```
 crontab -l
```
The results of crontab -l should list a command used to start the Chartio client. For example:
```
 @reboot /usr/local/bin/chartio_connect -d --prefix=/home/username/instance
```
If this entry exists, run the following to terminate any running connections:
```
 pkill chartio_connect
```
Then copy the command from crontab (see Step 2) without @reboot and run it from the command line:
```
 /usr/local/bin/chartio_connect -d --prefix=/home/username/instance
```

If restarting the client doesn’t fix your connection, try the steps below.

Run the following to terminate any running connections:
```
 pkill chartio_connect
```
Then, run the commands to start the Chartio client without the daemon option (-d). For example, if crontab -l gives:
```
 @reboot /usr/local/bin/chartio_connect -d --prefix=/home/username/instance
```
Then run the following for each instance:
```
 /usr/local/bin/chartio_connect --prefix=/home/username/instance
```
It may prompt you to confirm you want to connect with the current version/ssh key. If it does, answer yes.
Then, kill the processes again using pkill chartio_connect and restart them in daemon mode (with the -d prefix).

If this becomes a recurring issue, please email support@chartio.com and include the chartio_connect.log file. It’ll be located in the logs subdirectory of your installation path. For example: /home/username/instance/logs