How to Check Teleport Service Status via CLI in SynetoOS 6

Written By Sebastian Sime (Draft Writer)

Updated at January 16th, 2026

→ Applies to: SynetoOS 6.x

 

Step 1. Connect to SynetoOS appliance via SSH as admin

ssh admin@<your_ip_address_or_hostname>

 

Step 2. Become Super User

sudo su

 

Step 3. Check DNS servers

cat /etc/resolv.conf

EXAMPLE

nameserver 192.168.4.25
nameserver 8.8.8.8

 

Step 4. Check if the configured DNS can resolve the Teleport web address (replace <DNS_Server_IP> with the IPs of the DNS servers from Step 3)

/var/lib# host proxy.t.syneto.eu <DNS_Server_IP>

EXAMPLE OUTPUT

root@syneto-os-c83cc061:/var/lib# host proxy.t.syneto.eu 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:

proxy.t.syneto.eu has address 34.154.214.5

 

Step 5 (optional). Check that no errors occur

If you receive this error:

root@syneto-os-c83cc061:/var/lib# host proxy.t.syneto.eu 8.8.8.8
;; connection timed out; no servers could be reached

Run the following command:

systemctl stop teleport
rm -rf /var/lib/teleport
rm /etc/teleport.yaml
kubectl delete pod -l app=mercurio
curl -X POST mercurio.edge.local/remote-management/register > /etc/teleport.yaml
systemctl start teleport
config sup en

 

Step 6. Check Teleport service status

systemctl status teleport

EXAMPLE OUTPUT

[root@syneto-os admin]# systemctl status teleport.service 
● teleport.service - Teleport Service
     Loaded: loaded (/usr/lib/systemd/system/teleport.service; enabled; preset: disabled)
     Active: active (running) since Mon 2025-12-22 20:47:58 CET; 1 week 0 days ago
   Main PID: 2066620 (teleport)
      Tasks: 50 (limit: 819930)
     Memory: 303.8M
        CPU: 15min 1.781s
     CGroup: /system.slice/teleport.service
             ├─2066620 /usr/local/bin/teleport start --pid-file=/run/teleport.pid
             ├─3105644 /usr/local/bin/teleport exec
             └─3105664 -bash

Dec 23 14:25:45 syneto-os-611cda75 teleport[2066620]: Stack Trace:
Dec 23 14:25:45 syneto-os-611cda75 teleport[2066620]:         github.com/gravitational/teleport/lib/events/complete.go:353 github.com/gravitational/teleport/lib/events.(*UploadCompleter).ensureSessi>
Dec 23 14:25:45 syneto-os-611cda75 teleport[2066620]:         github.com/gravitational/teleport/lib/events/complete.go:241 github.com/gravitational/teleport/lib/events.(*UploadCompleter).checkUpload>
Dec 23 14:25:45 syneto-os-611cda75 teleport[2066620]:         runtime/asm_amd64.s:1598 runtime.goexit
Dec 23 14:25:45 syneto-os-611cda75 teleport[2066620]: User Message: invalid session, could not find session start] session:7fb0fc44-16ba-47fb-b5e6-8be955f0f2c7 upload:01ccbddb-b9fe-4c31-85c7-69f78f2>
Dec 30 09:13:23 syneto-os-611cda75 teleport[2066620]: 2025-12-30T09:13:23+01:00 INFO [NODE]      Creating (interactive) session 46380001-a00b-4bc0-923d-1382820c6fb4. id:6 local:10.10.10.2:43582 logi>
Dec 30 09:13:23 syneto-os-611cda75 teleport[2066620]: 2025-12-30T09:13:23+01:00 INFO [AUDIT]     session.start addr.remote:34.154.214.5:443 cluster_name:proxy.t.syneto.eu code:T2000I ei:0 event:sess>
Dec 30 09:13:24 syneto-os-611cda75 teleport[2066620]: 2025-12-30T09:13:24+01:00 INFO [SESSION:N] New party ServerContext(34.154.214.5:443->10.10.10.2:43582, user=support, id=6) party(id=043dbac6-6de>
Dec 30 09:13:32 syneto-os-611cda75 sudo[3106105]:  support : TTY=pts/3 ; PWD=/home/support ; USER=root ; COMMAND=/bin/su
lines 1-22/22 (END)