You are not logged in.

Pages: 1 2

#1 2024-09-13 12:22:16

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

[SOLVED] systemd kills my service after 10 mins

Hi, I have a shell script to listening to a mqtt broker and power on/off my computer.
It works well, so I'm considering installing it as a system service.
But the service keeps restarting every 10 mins which doesn't when executing it manually.
And even if I set Restart=no, it still restarts.

# /etc/systemd/system/wol.service
[Unit]
Description=Listen to mqtt server and perform WOL actions
After=network-online.target
Requires=zerotier-one.service tailscaled.service


[Service]
Type=simple
ExecStart=/usr/bin/zsh /etc/cron/watch_wol_file.sh
Restart=no

[Install]
WantedBy=multi-user.target



#!/bin/zsh

set -euo pipefail
set -x

trap 'echo "Signal SIGINT received"; exit 0' SIGINT


trap 'echo "Signal SIGTERM received"; exit 0' SIGTERM

WOL_TOPIC="home-assistant/dhy/livingroom/computer/power/set"
HOST=100.88.1.4
PORT=1883

if ! command -v mqtt &> /dev/null; then
    echo "mqtt could not be found, please install mqtt-cli first."
    exit 1
fi

mqtt sub -t "$WOL_TOPIC" -h "$HOST" -p "$PORT" |
while read -t 60 -r payload; do
        echo "payload = $payload"
        if [[ "$payload" == "ON" ]]; then
                if sudo -u sxing ssh -o ConnectTimeout=10 root@192.168.51.5 etherwake -i br-lan 04:7c:16:75:7c:e9; then
                        echo "success turn on"
                else
                        echo "failed turn on ($?)" >&2
                fi
        elif [[ "$payload" == "OFF" ]]; then
                if sudo -u sxing ssh -o ConnectTimeout=10 sxing@100.88.1.3 shutdown -s -t 15; then
                        echo "success turn off"
                else
                        echo "failed turn off ($?)" >&2
                fi
        fi
done


Sep 13 19:52:50 archlinux systemd[1]: Started Listen to mqtt server and perform WOL actions.
Sep 13 19:52:50 archlinux zsh[1598632]: +/etc/cron/watch_wol_file.sh:6> trap 'echo "Signal SIGINT received"; exit 0' SIGINT
Sep 13 19:52:50 archlinux zsh[1598632]: +/etc/cron/watch_wol_file.sh:9> trap 'echo "Signal SIGTERM received"; exit 0' SIGTERM
Sep 13 19:52:50 archlinux zsh[1598632]: +/etc/cron/watch_wol_file.sh:11> WOL_TOPIC=home-assistant/dhy/livingroom/computer/power/set
Sep 13 19:52:50 archlinux zsh[1598632]: +/etc/cron/watch_wol_file.sh:12> HOST=100.88.1.4
Sep 13 19:52:50 archlinux zsh[1598632]: +/etc/cron/watch_wol_file.sh:13> PORT=1883
Sep 13 19:52:50 archlinux zsh[1598632]: +/etc/cron/watch_wol_file.sh:15> command -v mqtt
Sep 13 19:52:50 archlinux zsh[1598632]: +/etc/cron/watch_wol_file.sh:21> read -t 60 -r payload
Sep 13 19:52:50 archlinux zsh[1598658]: +/etc/cron/watch_wol_file.sh:20> mqtt sub -t home-assistant/dhy/livingroom/computer/power/set -h 100.88.1.4 -p 1883
Sep 13 20:03:20 archlinux systemd[1]: Stopping Listen to mqtt server and perform WOL actions...
Sep 13 20:03:20 archlinux zsh[1598632]: +/etc/cron/watch_wol_file.sh:21> echo 'Signal SIGTERM received'
Sep 13 20:03:20 archlinux zsh[1598632]: Signal SIGTERM received
Sep 13 20:03:20 archlinux zsh[1598632]: +/etc/cron/watch_wol_file.sh:21> exit 0
Sep 13 20:03:20 archlinux systemd[1]: wol.service: Deactivated successfully.
Sep 13 20:03:20 archlinux systemd[1]: Stopped Listen to mqtt server and perform WOL actions.
Sep 13 20:03:20 archlinux systemd[1]: wol.service: Consumed 3.597s CPU time, 117.7M memory peak.
Sep 13 20:03:20 archlinux systemd[1]: Started Listen to mqtt server and perform WOL actions.
Sep 13 20:03:20 archlinux zsh[1609794]: +/etc/cron/watch_wol_file.sh:6> trap 'echo "Signal SIGINT received"; exit 0' SIGINT
Sep 13 20:03:20 archlinux zsh[1609794]: +/etc/cron/watch_wol_file.sh:9> trap 'echo "Signal SIGTERM received"; exit 0' SIGTERM
Sep 13 20:03:20 archlinux zsh[1609794]: +/etc/cron/watch_wol_file.sh:11> WOL_TOPIC=home-assistant/dhy/livingroom/computer/power/set
Sep 13 20:03:20 archlinux zsh[1609794]: +/etc/cron/watch_wol_file.sh:12> HOST=100.88.1.4
Sep 13 20:03:20 archlinux zsh[1609794]: +/etc/cron/watch_wol_file.sh:13> PORT=1883
Sep 13 20:03:20 archlinux zsh[1609794]: +/etc/cron/watch_wol_file.sh:15> command -v mqtt
Sep 13 20:03:20 archlinux zsh[1609794]: +/etc/cron/watch_wol_file.sh:21> read -t 60 -r payload
Sep 13 20:03:20 archlinux zsh[1609795]: +/etc/cron/watch_wol_file.sh:20> mqtt sub -t home-assistant/dhy/livingroom/computer/power/set -h 100.88.1.4 -p 1883
Sep 13 20:13:48 archlinux systemd[1]: Stopping Listen to mqtt server and perform WOL actions...
Sep 13 20:13:48 archlinux zsh[1609794]: +/etc/cron/watch_wol_file.sh:21> echo 'Signal SIGTERM received'
Sep 13 20:13:48 archlinux zsh[1609794]: Signal SIGTERM received
Sep 13 20:13:48 archlinux zsh[1609794]: +/etc/cron/watch_wol_file.sh:21> exit 0
Sep 13 20:13:48 archlinux systemd[1]: wol.service: Deactivated successfully.
Sep 13 20:13:48 archlinux systemd[1]: Stopped Listen to mqtt server and perform WOL actions.
Sep 13 20:13:48 archlinux systemd[1]: wol.service: Consumed 3.765s CPU time, 118.9M memory peak.
Sep 13 20:13:48 archlinux systemd[1]: Started Listen to mqtt server and perform WOL actions.
Sep 13 20:13:48 archlinux zsh[1619078]: +/etc/cron/watch_wol_file.sh:6> trap 'echo "Signal SIGINT received"; exit 0' SIGINT
Sep 13 20:13:48 archlinux zsh[1619078]: +/etc/cron/watch_wol_file.sh:9> trap 'echo "Signal SIGTERM received"; exit 0' SIGTERM
Sep 13 20:13:48 archlinux zsh[1619078]: +/etc/cron/watch_wol_file.sh:11> WOL_TOPIC=home-assistant/dhy/livingroom/computer/power/set
Sep 13 20:13:48 archlinux zsh[1619078]: +/etc/cron/watch_wol_file.sh:12> HOST=100.88.1.4
Sep 13 20:13:48 archlinux zsh[1619078]: +/etc/cron/watch_wol_file.sh:13> PORT=1883
Sep 13 20:13:48 archlinux zsh[1619078]: +/etc/cron/watch_wol_file.sh:15> command -v mqtt
Sep 13 20:13:48 archlinux zsh[1619078]: +/etc/cron/watch_wol_file.sh:21> read -t 60 -r payload
Sep 13 20:13:48 archlinux zsh[1619099]: +/etc/cron/watch_wol_file.sh:20> mqtt sub -t home-assistant/dhy/livingroom/computer/power/set -h 100.88.1.4 -p 1883

Last edited by freeeeezing (2024-09-15 05:17:17)

Offline

#2 2024-09-13 12:55:59

mithrial
Member
Registered: 2017-03-05
Posts: 52

Re: [SOLVED] systemd kills my service after 10 mins

Does your script maybe stop after 10 minutes?

You could add

RuntimeMaxSec=infinity

to tell the service to run forever. (However, I doubt that there is 10min default setting.)

Offline

#3 2024-09-13 15:49:24

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

Thanks for your reply.

I found this in `systemctl show wol.service`
RuntimeMaxUSec=infinity

maybe indicates that the default is 'infinity'

I tried to add it too, problem still 

# /etc/systemd/system/wol.service
[Unit]
Description=Listen to mqtt server and perform WOL actions
After=network-online.target
Requires=zerotier-one.service tailscaled.service


[Service]
Type=simple
ExecStart=/usr/bin/zsh /etc/cron/watch_wol_file.sh
Restart=no
RuntimeMaxSec=infinity

[Install]
WantedBy=multi-user.target

also the output of `systemctl show wol`

Type=simple
ExitType=main
Restart=no
RestartMode=normal
NotifyAccess=none
RestartUSec=100ms
RestartSteps=0
RestartMaxDelayUSec=infinity
RestartUSecNext=100ms
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
TimeoutAbortUSec=1min 30s
TimeoutStartFailureMode=terminate
TimeoutStopFailureMode=terminate
RuntimeMaxUSec=infinity
RuntimeRandomizedExtraUSec=0
WatchdogUSec=0
WatchdogTimestampMonotonic=0
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=1828835
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
FileDescriptorStorePreserve=restart
StatusErrno=0
Result=success
ReloadResult=success
CleanResult=success
UID=[not set]
GID=[not set]
NRestarts=0
OOMPolicy=stop
ReloadSignal=1
ExecMainStartTimestamp=Fri 2024-09-13 23:42:35 CST
ExecMainStartTimestampMonotonic=1222120198019
ExecMainExitTimestampMonotonic=0
ExecMainHandoffTimestamp=Fri 2024-09-13 23:42:35 CST
ExecMainHandoffTimestampMonotonic=1222120205755
ExecMainPID=1828835
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/zsh ; argv[]=/usr/bin/zsh /etc/cron/watch_wol_file.sh ; ignore_errors=no ; start_time=[Fri 2024-09-13 23:42:35 CST] ; stop_time=[n/a] ; pid=1828835 ; code=(null) ; status=0/0 }
ExecStartEx={ path=/usr/bin/zsh ; argv[]=/usr/bin/zsh /etc/cron/watch_wol_file.sh ; flags= ; start_time=[Fri 2024-09-13 23:42:35 CST] ; stop_time=[n/a] ; pid=1828835 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/wol.service
ControlGroupId=772048
MemoryCurrent=117764096
MemoryPeak=119836672
MemorySwapCurrent=0
MemorySwapPeak=0
MemoryZSwapCurrent=0
MemoryAvailable=11482091520
EffectiveMemoryMax=16153690112
EffectiveMemoryHigh=16153690112
CPUUsageNSec=2588163000
EffectiveCPUs=0-15
EffectiveMemoryNodes=0
TasksCurrent=29
EffectiveTasksMax=18391
IPIngressBytes=[no data]
IPIngressPackets=[no data]
IPEgressBytes=[no data]
IPEgressPackets=[no data]
IOReadBytes=[not set]
IOReadOperations=[not set]
IOWriteBytes=[not set]
IOWriteOperations=[not set]
Delegate=no
CPUAccounting=yes
CPUWeight=[not set]
StartupCPUWeight=[not set]
CPUShares=[not set]
StartupCPUShares=[not set]
CPUQuotaPerSecUSec=infinity
CPUQuotaPeriodUSec=infinity
IOAccounting=no
IOWeight=[not set]
StartupIOWeight=[not set]
BlockIOAccounting=no
BlockIOWeight=[not set]
StartupBlockIOWeight=[not set]
MemoryAccounting=yes
DefaultMemoryLow=0
DefaultStartupMemoryLow=0
DefaultMemoryMin=0
MemoryMin=0
MemoryLow=0
StartupMemoryLow=0
MemoryHigh=infinity
StartupMemoryHigh=infinity
MemoryMax=infinity
StartupMemoryMax=infinity
MemorySwapMax=infinity
StartupMemorySwapMax=infinity
MemoryZSwapMax=infinity
StartupMemoryZSwapMax=infinity
MemoryZSwapWriteback=yes
MemoryLimit=infinity
DevicePolicy=auto
TasksAccounting=yes
TasksMax=18391
IPAccounting=no
ManagedOOMSwap=auto
ManagedOOMMemoryPressure=auto
ManagedOOMMemoryPressureLimit=0
ManagedOOMPreference=none
MemoryPressureWatch=auto
MemoryPressureThresholdUSec=200ms
CoredumpReceive=no
UMask=0022
LimitCPU=infinity
LimitCPUSoft=infinity
LimitFSIZE=infinity
LimitFSIZESoft=infinity
LimitDATA=infinity
LimitDATASoft=infinity
LimitSTACK=infinity
LimitSTACKSoft=8388608
LimitCORE=infinity
LimitCORESoft=infinity
LimitRSS=infinity
LimitRSSSoft=infinity
LimitNOFILE=524288
LimitNOFILESoft=1024
LimitAS=infinity
LimitASSoft=infinity
LimitNPROC=61304
LimitNPROCSoft=61304
LimitMEMLOCK=8388608
LimitMEMLOCKSoft=8388608
LimitLOCKS=infinity
LimitLOCKSSoft=infinity
LimitSIGPENDING=61304
LimitSIGPENDINGSoft=61304
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=infinity
LimitRTTIMESoft=infinity
RootEphemeral=no
OOMScoreAdjust=0
CoredumpFilter=0x33
Nice=0
IOSchedulingClass=2
IOSchedulingPriority=4
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
CPUAffinityFromNUMA=no
NUMAPolicy=n/a
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
LogLevelMax=-1
LogRateLimitIntervalUSec=0
LogRateLimitBurst=0
SecureBits=0
CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend cap_audit_read cap_perfmon cap_bpf cap_checkpoint_restore
DynamicUser=no
SetLoginEnvironment=no
RemoveIPC=no
PrivateTmp=no
PrivateDevices=no
ProtectClock=no
ProtectKernelTunables=no
ProtectKernelModules=no
ProtectKernelLogs=no
ProtectControlGroups=no
PrivateNetwork=no
PrivateUsers=no
PrivateMounts=no
PrivateIPC=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=2147483646
LockPersonality=no
RuntimeDirectoryPreserve=no
RuntimeDirectoryMode=0755
StateDirectoryMode=0755
CacheDirectoryMode=0755
LogsDirectoryMode=0755
ConfigurationDirectoryMode=0755
TimeoutCleanUSec=infinity
MemoryDenyWriteExecute=no
RestrictRealtime=no
RestrictSUIDSGID=no
RestrictNamespaces=no
MountAPIVFS=no
KeyringMode=private
ProtectProc=default
ProcSubset=all
ProtectHostname=no
MemoryKSM=no
RootImagePolicy=root=verity+signed+encrypted+unprotected+absent:usr=verity+signed+encrypted+unprotected+absent:home=encrypted+unprotected+absent:srv=encrypted+unprotected+absent:tmp=encrypted+unprotected+absent:var=encrypted+unprotected+absent
MountImagePolicy=root=verity+signed+encrypted+unprotected+absent:usr=verity+signed+encrypted+unprotected+absent:home=encrypted+unprotected+absent:srv=encrypted+unprotected+absent:tmp=encrypted+unprotected+absent:var=encrypted+unprotected+absent
ExtensionImagePolicy=root=verity+signed+encrypted+unprotected+absent:usr=verity+signed+encrypted+unprotected+absent:home=encrypted+unprotected+absent:srv=encrypted+unprotected+absent:tmp=encrypted+unprotected+absent:var=encrypted+unprotected+absent
KillMode=control-group
KillSignal=15
RestartKillSignal=15
FinalKillSignal=9
SendSIGKILL=yes
SendSIGHUP=no
WatchdogSignal=6
Id=wol.service
Names=wol.service
Requires=system.slice zerotier-one.service tailscaled.service sysinit.target
WantedBy=multi-user.target
Conflicts=shutdown.target
Before=shutdown.target multi-user.target
After=basic.target system.slice systemd-journald.socket network-online.target sysinit.target
Description=Listen to mqtt server and perform WOL actions
LoadState=loaded
ActiveState=active
FreezerState=running
SubState=running
FragmentPath=/etc/systemd/system/wol.service
UnitFileState=enabled
UnitFilePreset=disabled
StateChangeTimestamp=Fri 2024-09-13 23:42:35 CST
StateChangeTimestampMonotonic=1222120198567
InactiveExitTimestamp=Fri 2024-09-13 23:42:35 CST
InactiveExitTimestampMonotonic=1222120198567
ActiveEnterTimestamp=Fri 2024-09-13 23:42:35 CST
ActiveEnterTimestampMonotonic=1222120198567
ActiveExitTimestamp=Fri 2024-09-13 23:42:35 CST
ActiveExitTimestampMonotonic=1222120117752
InactiveEnterTimestamp=Fri 2024-09-13 23:42:35 CST
InactiveEnterTimestampMonotonic=1222120174119
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
CanFreeze=yes
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
SurviveFinalKillSignal=no
OnSuccessJobMode=fail
OnFailureJobMode=replace
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobRunningTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Fri 2024-09-13 23:42:35 CST
ConditionTimestampMonotonic=1222120196491
AssertTimestamp=Fri 2024-09-13 23:42:35 CST
AssertTimestampMonotonic=1222120196496
Transient=no
Perpetual=no
StartLimitIntervalUSec=10s
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
SuccessAction=none
InvocationID=d21b6203c414451bbd937126d36d9175
CollectMode=inactive

Offline

#4 2024-09-13 16:13:33

cryptearth
Member
Registered: 2024-02-03
Posts: 1,072

Re: [SOLVED] systemd kills my service after 10 mins

is there a reason why to run it as a service?
another option is to start it as cronjob with the @reboot flag

Offline

#5 2024-09-13 17:53:12

mithrial
Member
Registered: 2017-03-05
Posts: 52

Re: [SOLVED] systemd kills my service after 10 mins

Yeah, it probably was a long shot anyway. I would have been surprised , if it worked right away.

Does the journal list a reason?

Offline

#6 2024-09-13 21:05:08

dimich
Member
From: Kharkiv, Ukraine
Registered: 2009-11-03
Posts: 265

Re: [SOLVED] systemd kills my service after 10 mins

Does zerotier-one.service or tailscaled.service restart as well?

Offline

#7 2024-09-14 01:05:33

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

cryptearth wrote:

is there a reason why to run it as a service?
another option is to start it as cronjob with the @reboot flag

Like auto-restart and journal storage things. For me, service is more configurable.

Okay, the problem becomes zerotier now. it crashes every 10 mins. 

# /usr/lib/systemd/system/zerotier-one.service
[Unit]
Description=ZeroTier One
After=network-online.target network.target
Wants=network-online.target

[Service]
ExecStart=/usr/bin/zerotier-one
Restart=always
KillMode=process

[Install]
WantedBy=multi-user.target


Sep 14 08:24:17 archlinux systemd[1]: Started ZeroTier One.
Sep 14 08:24:17 archlinux zerotier-one[1962869]: Starting Control Plane...
Sep 14 08:24:17 archlinux zerotier-one[1962869]: Starting V6 Control Plane...
Sep 14 08:34:36 archlinux systemd[1]: zerotier-one.service: Main process exited, code=dumped, status=11/SEGV
Sep 14 08:34:36 archlinux systemd[1]: zerotier-one.service: Failed with result 'core-dump'.
Sep 14 08:34:36 archlinux systemd[1]: zerotier-one.service: Consumed 1.851s CPU time, 12.2M memory peak.
Sep 14 08:34:36 archlinux systemd[1]: zerotier-one.service: Scheduled restart job, restart counter is at 2006.
Sep 14 08:34:36 archlinux systemd[1]: Started ZeroTier One.
Sep 14 08:34:36 archlinux zerotier-one[1965694]: Starting Control Plane...
Sep 14 08:34:36 archlinux zerotier-one[1965694]: Starting V6 Control Plane...
Sep 14 08:45:01 archlinux systemd[1]: zerotier-one.service: Main process exited, code=dumped, status=11/SEGV
Sep 14 08:45:01 archlinux systemd[1]: zerotier-one.service: Failed with result 'core-dump'.
Sep 14 08:45:01 archlinux systemd[1]: zerotier-one.service: Consumed 1.927s CPU time, 11.5M memory peak.
Sep 14 08:45:02 archlinux systemd[1]: zerotier-one.service: Scheduled restart job, restart counter is at 2007.
Sep 14 08:45:02 archlinux systemd[1]: Started ZeroTier One.
Sep 14 08:45:02 archlinux zerotier-one[1967861]: Starting Control Plane...
Sep 14 08:45:02 archlinux zerotier-one[1967861]: Starting V6 Control Plane...
Sep 14 08:55:26 archlinux systemd[1]: zerotier-one.service: Main process exited, code=dumped, status=11/SEGV
Sep 14 08:55:26 archlinux systemd[1]: zerotier-one.service: Failed with result 'core-dump'.
Sep 14 08:55:26 archlinux systemd[1]: zerotier-one.service: Consumed 1.877s CPU time, 12.7M memory peak.
Sep 14 08:55:26 archlinux systemd[1]: zerotier-one.service: Scheduled restart job, restart counter is at 2008.
Sep 14 08:55:26 archlinux systemd[1]: Started ZeroTier One.
Sep 14 08:55:27 archlinux zerotier-one[1974846]: Starting V6 Control Plane...
Sep 14 08:55:27 archlinux zerotier-one[1974846]: Starting Control Plane...

Offline

#8 2024-09-14 01:14:08

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

the dump:

           PID: 1974846 (zerotier-one)
           UID: 966 (zerotier-one)
           GID: 966 (zerotier-one)
        Signal: 11 (SEGV)
     Timestamp: Sat 2024-09-14 09:05:49 CST (6min ago)
  Command Line: /usr/bin/zerotier-one
    Executable: /usr/bin/zerotier-one
 Control Group: /system.slice/zerotier-one.service
          Unit: zerotier-one.service
         Slice: system.slice
       Boot ID: f26e6dd161e14381872d4b9dd9e977ad
    Machine ID: f2ad2b1043564a10896dbe96acd89c72
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.zerotier-one.966.f26e6dd161e14381872d4b9dd9e977ad.1974846.1726275949000000.zst (present)
  Size on Disk: 411.6K
       Message: Process 1974846 (zerotier-one) of user 966 dumped core.

                Stack trace of thread 1974861:
                #0  0x000077471777fe2a n/a (libc.so.6 + 0x170e2a)
                #1  0x0000774718325c36 UPNP_GetValidIGD (libminiupnpc.so.18 + 0x9c36)
                #2  0x0000629ec9997a4e n/a (zerotier-one + 0x1daa4e)
                #3  0x0000629ec99978cd n/a (zerotier-one + 0x1da8cd)
                #4  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #5  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974866:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974868:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974846:
                #0  0x0000774717725c57 __select (libc.so.6 + 0x116c57)
                #1  0x0000629ec994f1c3 n/a (zerotier-one + 0x1921c3)
                #2  0x0000629ec9967bfd n/a (zerotier-one + 0x1aabfd)
                #3  0x0000629ec99a7f0c n/a (zerotier-one + 0x1eaf0c)
                #4  0x0000629ec9807861 n/a (zerotier-one + 0x4a861)
                #5  0x0000774717634e08 n/a (libc.so.6 + 0x25e08)
                #6  0x0000774717634ecc __libc_start_main (libc.so.6 + 0x25ecc)
                #7  0x0000629ec9807d45 n/a (zerotier-one + 0x4ad45)

                Stack trace of thread 1974870:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974871:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974872:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974873:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974874:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974876:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974875:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974877:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974878:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974880:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974879:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974881:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974884:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974852:
                #0  0x00007747176f0733 clock_nanosleep (libc.so.6 + 0xe1733)
                #1  0x00007747176fc827 __nanosleep (libc.so.6 + 0xed827)
                #2  0x0000629ec983c7b8 n/a (zerotier-one + 0x7f7b8)
                #3  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #4  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #5  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974882:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974869:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974862:
                #0  0x00007747176f0733 clock_nanosleep (libc.so.6 + 0xe1733)
                #1  0x00007747176fc827 __nanosleep (libc.so.6 + 0xed827)
                #2  0x0000629ec9904dc3 n/a (zerotier-one + 0x147dc3)
                #3  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #4  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #5  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974886:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974863:
                #0  0x00007747176f0733 clock_nanosleep (libc.so.6 + 0xe1733)
                #1  0x00007747176fc827 __nanosleep (libc.so.6 + 0xed827)
                #2  0x0000629ec98acf1b n/a (zerotier-one + 0xeff1b)
                #3  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #4  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #5  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974885:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974888:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974894:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974895:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974867:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974896:
                #0  0x000077471772a40a recv (libc.so.6 + 0x11b40a)
                #1  0x0000629ec9994c1c n/a (zerotier-one + 0x1d7c1c)
                #2  0x0000629ec9996b44 n/a (zerotier-one + 0x1d9b44)
                #3  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #4  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974887:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974889:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974890:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974897:
                #0  0x0000774717725c57 __select (libc.so.6 + 0x116c57)
                #1  0x0000629ec998f6aa n/a (zerotier-one + 0x1d26aa)
                #2  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #3  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #4  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974864:
                #0  0x000077471772a02d accept (libc.so.6 + 0x11b02d)
                #1  0x0000629ec996faf1 n/a (zerotier-one + 0x1b2af1)
                #2  0x0000629ec9949624 n/a (zerotier-one + 0x18c624)
                #3  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #4  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #5  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974891:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974865:
                #0  0x000077471772a02d accept (libc.so.6 + 0x11b02d)
                #1  0x0000629ec996faf1 n/a (zerotier-one + 0x1b2af1)
                #2  0x0000629ec99494e4 n/a (zerotier-one + 0x18c4e4)
                #3  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #4  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #5  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974883:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974892:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)

                Stack trace of thread 1974893:
                #0  0x000077471769fa19 n/a (libc.so.6 + 0x90a19)
                #1  0x00007747176a2479 pthread_cond_wait (libc.so.6 + 0x93479)
                #2  0x00007747178d6c31 __gthread_cond_wait (libstdc++.so.6 + 0xd6c31)
                #3  0x0000629ec996b99b n/a (zerotier-one + 0x1ae99b)
                #4  0x00007747178e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)
                #5  0x00007747176a339d n/a (libc.so.6 + 0x9439d)
                #6  0x000077471772849c n/a (libc.so.6 + 0x11949c)
                ELF object binary architecture: AMD x86-64

Offline

#9 2024-09-14 04:57:35

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

It might have something to do with this
https://github.com/zerotier/ZeroTierOne/issues/2332

Offline

#10 2024-09-14 06:39:42

cryptearth
Member
Registered: 2024-02-03
Posts: 1,072

Re: [SOLVED] systemd kills my service after 10 mins

I don't see the connection - but why does your script require zerotier in the first place?
also: the linked bug is related to upnp - something that should be disabled anyway

Offline

#11 2024-09-14 06:42:17

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

192.168.51.5 is a zerotier ip

Upnp is helpful digging through nat networks, isn't it?

Offline

#12 2024-09-14 07:39:09

seth
Member
Registered: 2012-09-03
Posts: 59,718

Re: [SOLVED] systemd kills my service after 10 mins

If the nat allows it. But should™ not. Ideally use port forwarding, upnp is one gaping security hole.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2024-09-14 08:26:36

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

Ok, I’ll take your advice

Offline

#14 2024-09-14 09:54:59

cryptearth
Member
Registered: 2024-02-03
Posts: 1,072

Re: [SOLVED] systemd kills my service after 10 mins

freeeeezing wrote:

192.168.51.5 is a zerotier ip

Upnp is helpful digging through nat networks, isn't it?

I still don't know what zerotier is or what you require it for
wake-on-lan is as simple as this:

import java.net.*;
public final class Wake3
{
        public final static void main(final String... args) throws Exception
        {
                byte[] packet=new byte[102];
                byte[] mac=new byte[] { (byte)0x04, (byte)0x7C, (byte)0x16, (byte)0x19, (byte)0x98, (byte)0x71 };
                for(int i=0; i<(packet.length/6); i++)
                {
                        for(int j=0; j<6; j++)
                        {
                                packet[(i*6)+j]=mac[j];
                        }
                }
                for(int i=0; i<6; i++)
                {
                        packet[i]=(byte)0xFF;
                }
                DatagramPacket magicPacket=new DatagramPacket(packet, packet.length, new InetSocketAddress(InetAddress.getByAddress(new byte[] { (byte)0xFF, (byte)0xFF, (byte)0xFF, (byte)0xFF }), 9));
                DatagramSocket socket=new DatagramSocket();
                socket.setBroadcast(true);
                socket.send(magicPacket);
                socket.close();
        }
}

as for upnp: although it's design had good intentions these days it's often abused by malware to silently bypass router security and expose your network to the internet and hence became a security concern - should be disabled

Last edited by cryptearth (2024-09-14 12:29:00)

Offline

#15 2024-09-14 10:47:37

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

I’m happy to share my network set if you’re interested in.

I have an old laptop running ArchLinux as a server at my house A and my gaming PC running windows at my house B. The script will run on my laptop and turn on/off my PC. But they are not in one LAN, and I didn’t figure out hot to send magic packet to another LAN.

So I exec etherwake command through ssh on the router running openwrt of house B to send the packet to PC. Zerotier is the way I connect to router from laptop. For turn off I exec shutdown through ssh on PC which I connect to with tailscale.

I mainly use tailscale to access them between networks. But my router happens to not support tailscale, so I turned to zerotier.

As for mqtt, it’s how I integrated the script to homeassistent. I made a simple virtual on/off switch on it.

Now I’m aware of the potential threaten of upnp thanks to you and will try not to rely on it. I appreciate that.

Welcome to any advice for my solution.

Offline

#16 2024-09-14 12:32:45

cryptearth
Member
Registered: 2024-02-03
Posts: 1,072

Re: [SOLVED] systemd kills my service after 10 mins

can't you just connect via ssh remotely to router B?
I never used openwrt - but from what I understand it's just linux and hence likely exposes ssh to the internet
for non-static ip: dynamic dns

another option how I do it:
I have the luck to have a static ip for my internet access and own a domain
so I just exposed ssh runin on my home server via port-forwarding through my router and just call the above posted java code to start my system
for shutdown I also use ssh

Last edited by cryptearth (2024-09-14 12:34:24)

Offline

#17 2024-09-14 12:40:46

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

Yes, DDNS is another option. But free DDNS providers are so unreliable that failed many times when I used to use it. And it's not worth using a paid service just for wake on lan. Also, vpn is a bit more secure to me.

Unfortunately we usually don’t have static ip at home, even a public ip. Haha.

Openwrt is not a full-functional Linux. I actually doing as you said on the archlinux side. DDNS is depend on a domain hosted on CloudFlare and I wrote a script to change A record intervally through some api.

Last edited by freeeeezing (2024-09-14 12:46:17)

Offline

#18 2024-09-14 12:51:20

cryptearth
Member
Registered: 2024-02-03
Posts: 1,072

Re: [SOLVED] systemd kills my service after 10 mins

well, if both systems on different networks both with non-static IPs I don't see any way to get them connect reliable wthout stuff like dyndns or at least a 3rd external system with a static ip
you can get a vps and a domain for less than 5 bucks a month - also there're many very reliable dyndns providers out there - some several decades in the business
I do see you problem - but your solution to me is like "I want to get away with some free service because other free services failed on me in the past" - that's a XY-problem: you'Re so focused on get your way to work you ignore that there're other options - some may work better - some may require additional work or even money

tldr: unless one of the networks has either a fixed static ip or a reliable dynamic dns sevice you likely have to invest at least some small amount if you want to get something more reliable/stable - as the current zerotier issue is as bad as an unreliable dyndns
maybe contact your isp(s) if they can provide a static ip at least for one of your networks - maybe you're lucky and get it for free or just a small fee (I pay a fee of 2,65/month ontop for a static public ip - and it payed for itself so many times already I see it worth and would even be pay more if they raise it)

Offline

#19 2024-09-14 13:16:12

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

I’m afraid that I don’t agree with you.

The vpn solution works well in my situation. Even if I don’t have static ip on any side. The problem in this topic didn’t make it not works. Just behaving a little weird.

I have figure out how to disable upnp of zerotier and solved the problem.

Also asking for a static ip is nearly impossible here in China, you have to pay for enterprise plans to get that which costs thousands dollars a year.

Offline

#20 2024-09-14 15:14:15

cryptearth
Member
Registered: 2024-02-03
Posts: 1,072

Re: [SOLVED] systemd kills my service after 10 mins

well - ok ... china, huh? I rather don't write anything before writing something wrong
to keep it on topic: so if I get you right you use a vpn service to conenect two networks to control a pc in one of them from the other?
I guess I'm not the one to ask your motives as I do similar - but as I live in germany and have the luck to have a local isp offering my fixed public ip and reverse dns along with a few other things I can't really relate
also: my second hop isn't a second network but rather my phone I use from time to time to access my system remotely - like building new ZFS packages (doing that right now) or share some files when I'm over at my sister and brother-in-law

anyway - we figured that the root cause of your issues is acutally something you depend on because you chosen so although there're other options - and I'm sure even in china it's possible to get a cheap vps as a public relay and a sbc which connects to it to perform a wake-on-lan via a reverse connection - and I guess it's even cheaper than paying for the vpn service (unless that's free)

Offline

#21 2024-09-14 15:52:44

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

Don’t worry, I’m glad to discuss these things with you， and you don't have to care what country I'm from.

Yes, I often access my laptop from my phone to visit home assistant and stream video game and stream films.

Something you might not know is that personal use of zerotier and tailscale is for free. Using them can be a better solution than getting a vps as a relay with things like frp. Because if the nat condition suits (in my situation, both dynamic public ip), connection between hosts are *direct* (if not, delay and bandwidth are no good after forwarding) so that upload bandwidth can be fully utilized. vps is certainly a relay.

Offline

#22 2024-09-14 16:05:20

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

cryptearth wrote:

and I'm sure even in china it's possible to get a cheap vps as a public relay and a sbc which connects to it to perform a wake-on-lan via a reverse connection

Can you make it more clear?  What is “reverse connection”? How to send a wake on lan packet through internet? As I know it should be sent to broadcast address in the lan network which means the router should forward the packet to a broadcast address. I think it is not possible on my router.

Offline

#23 2024-09-14 20:08:27

seth
Member
Registered: 2012-09-03
Posts: 59,718

Re: [SOLVED] systemd kills my service after 10 mins

https://man.archlinux.org/man/extra/wol/wol.1.en
WOL usually happens on ports 7 or 9, ie. you can send the WOL to the openwrt router and have it forward the package to a selected host (you can also use various ports on the router and forward them to different hosts on the relevant ports)

https://forum.archive.openwrt.org/viewt … =33442&p=1

That doesn't address any questions of "how do I find my router on the internet if there's no static IP nor a dynamic domain name".

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#24 2024-09-15 03:33:13

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

Currently I’m doing as #3 in https://forum.archive.openwrt.org/viewt … =33442&p=1

Offline

#25 2024-09-15 03:35:26

freeeeezing
Member
Registered: 2024-03-29
Posts: 22

Re: [SOLVED] systemd kills my service after 10 mins

Guess I should mark this topic solved.

Offline

Pages: 1 2

Board footer

Powered by FluxBB