Raspiban error twingate-connector on Raspberry Pi

Hello,

I constantly receive following error when trying to start service on old Raspberry Pi Model B+ V1.2 as installation of twingate conector local service, while there is no support of arm on docker.

cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

and error :


> :~ $ sudo journalctl -u twingate-connector --no-pager | tail -n 20
> avg 13 11:19:26 hostname systemd[1]: twingate-connector.service: Main process exited, code=killed, status=4/ILL
> avg 13 11:19:26 hostname systemd[1]: twingate-connector.service: Failed with result 'signal'.
> avg 13 11:19:36 hostname systemd[1]: twingate-connector.service: Service RestartSec=10s expired, scheduling restart.
> avg 13 11:19:36 hostname systemd[1]: twingate-connector.service: Scheduled restart job, restart counter is at 95.
> avg 13 11:19:36 hostname systemd[1]: Stopped Twingate Connector service.
> avg 13 11:19:37 hostname systemd[1]: Started Twingate Connector service.
> avg 13 11:19:37 hostname systemd[1]: twingate-connector.service: Main process exited, code=killed, status=4/ILL
> avg 13 11:19:37 hostname systemd[1]: twingate-connector.service: Failed with result 'signal'.
> avg 13 11:19:47 hostname systemd[1]: twingate-connector.service: Service RestartSec=10s expired, scheduling restart.
> avg 13 11:19:47 hostname systemd[1]: twingate-connector.service: Scheduled restart job, restart counter is at 96.
> avg 13 11:19:47 hostname systemd[1]: Stopped Twingate Connector service.
> avg 13 11:19:47 hostname systemd[1]: Started Twingate Connector service.
> avg 13 11:19:48 hostname systemd[1]: twingate-connector.service: Main process exited, code=killed, status=4/ILL
> avg 13 11:19:48 hostname systemd[1]: twingate-connector.service: Failed with result 'signal'.
> avg 13 11:19:58 hostname systemd[1]: twingate-connector.service: Service RestartSec=10s expired, scheduling restart.
> avg 13 11:19:58 hostname systemd[1]: twingate-connector.service: Scheduled restart job, restart counter is at 97.
> avg 13 11:19:58 hostname systemd[1]: Stopped Twingate Connector service.
> avg 13 11:19:58 hostname systemd[1]: Started Twingate Connector service.
> avg 13 11:19:59 hostname systemd[1]: twingate-connector.service: Main process exited, code=killed, status=4/ILL
> avg 13 11:19:59 hostname systemd[1]: twingate-connector.service: Failed with result 'signal'.

and systemctl:


sudo systemctl status twingate-connector.service 
● twingate-connector.service - Twingate Connector service
   Loaded: loaded (/lib/systemd/system/twingate-connector.service; enabled; vendor preset: disabled)
   Active: activating (auto-restart) (Result: signal) since Sun 2023-08-13 12:12:44 CEST; 7s ago
  Process: 581 ExecStart=/usr/bin/twingate-connector --systemd-watchdog (code=killed, signal=ILL)
 Main PID: 581 (code=killed, signal=ILL)

When try to see twingate version :


twingate@hostname:~ $ twingate-connector -v
Illegal instruction
twingate@hostname:~ $ sudo !!
sudo twingate-connector -v
Illegal instruction
twingate@hostname:~ $

Thanx for any of help.

I really don’t want to toss in trash my oldest Raspberry Pi :frowning:

Unfortunately I think the age of the RPi is causing the issue - as the ARM connector is built using a newer instruction set than what the early models can support.

I apologize for the inconvenience.

Thanks,

-arthur