When openwrt installs the service using cloudflared, there’s a compatibility issue. The problem lies in the service script under /etc/init.d/, which defaults to SysVinit, while cloudflared uses procd. So we need to modify the service script to the procd format.

SysVinit is the traditional init system used by many early Linux distributions. It uses a series of shell scripts to start various services in a specific order. These scripts are usually located in /etc/init.d/, with one script per service. SysVinit’s main drawback is that it starts services linearly and can’t start them in parallel, which can lead to longer boot times.

procd is the init system used by OpenWrt. Unlike SysVinit, procd can start services in parallel, speeding up system boot time. procd also provides other advanced features such as process monitoring, automatic restart, and cgroup management. procd’s service scripts are usually located in /etc/init.d/, similar to SysVinit, but their format and syntax differ.

After modifying /etc/init.d/cloudflared, just restart the service with /etc/init.d/cloudflared restart.

1
#!/bin/sh /etc/rc.common
2
# Copyright (C) 2021 Tianling Shen <cnsztl@immortalwrt.org>
3

4
USE_PROCD=1
5
START=99
6

7
CONF="cloudflared"
8
PROG="/usr/bin/cloudflared"
9

10
start_service() {
11
    procd_open_instance
12
    procd_set_param command "$PROG" "--pidfile" "/var/run/$CONF.pid" "--logfile" "/var/log/cloudflared.log" "--protocol" "http2" "--no-autoupdate" "tunnel" "run" "--token" "xxxxxxxxxxxxxxxx"
13
    procd_set_param stdout 1
14
    procd_set_param stderr 1
15
    procd_set_param pidfile "/var/run/$CONF.pid"
16
    procd_close_instance
17
}
18

19
stop_service() {
20
    procd_kill $CONF
21
}
22

23
reload_service() {
24
    stop
25
    start
26
}
27

28
service_triggers() {
29
    procd_add_reload_trigger "$CONF"
30
}