Services In Thignshub
Restarting services
In the unlikely case that a service gets stuck in an invalid state and does not restart automatically, you can do a manual service restart like this:
$ kubectl -n demo get pods
NAME READY STATUS RESTARTS AGE
asset-management-577f85cd5f-8t695 2/2 Running 3 (3d20h ago) 3d20h
automations-64c59778bc-wkwss 2/2 Running 0 4d13h
business-objects-5fb9d8544f-9n824 3/3 Running 0 14d
engine-6879cd99bd-vff6g 2/2 Running 0 4d13h
iam-65fb97ff68-fpqr6 2/2 Running 0 3d20h
influxdb-c786b9584-d5vwj 1/1 Running 2 (35d ago) 35d
mqtt-5c7df46b5c-v9kzm 1/1 Running 0 3d20h
registry-785477ff8b-sf8kl 2/2 Running 0 3d20h
th-api-fdc6f454-v79zp 1/1 Running 0 4d13h
thingsflow-6576466984-j2wl4 3/3 Running 1 (4d13h ago) 4d13h
trackinghub-bf8d6d48-9hrff 2/2 Running 0 3d20h
tsdb-66fd6bd44-zqj42 2/2 Running 0 4d13h
ui-5c64fd99b6-bqj6x 1/1 Running 0 4d13h
visualizer-7f655c765d-qqdct 4/4 Running 1 (4d13h ago) 4d13h
$ kubectl -n demo delete pod engine-6879cd99bd-vff6g
pod "engine-6879cd99bd-vff6g" deleted
$
This can also be done in a single command by selecting on a service's app label using -l:
Known issues
$ $ kubectl.exe delete pod -lapp=engine -n <tenant>
pod "engine-77f988f5bc-r4429" deleted
$
Uplinks are received, but not processed for decoding
This has been observed to happen rarely after cluster reorganization. Until a final solution has been found, it is recommended to restart the affected tenants' engine service:
$ $ kubectl.exe delete pod -lapp=engine -n <tenant>
pod "engine-xxxxxxxxxx-yyyyy" deleted
$
Data gets decoded, but not passed on via integrations
This has been observed to happen rarely after cluster reorganization. Until a final solution has been found, it is recommended to restart the affected tenants' engine service:
$ $ kubectl.exe delete pod -lapp=engine -n <tenant>
pod "engine-xxxxxxxxxx-yyyyy" deleted
$
Note that this is likely coming from the same root cause as the previous known issue.