Procd warning in Master/Snapshot build from today

Installing and Using OpenWrt
1

Just build a Master Snapshot for MT6000:

{
        "kernel": "6.12.71",
        "hostname": "MT-6000",
        "system": "ARMv8 Processor rev 4",
        "model": "GL.iNet GL-MT6000",
        "board_name": "glinet,gl-mt6000",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "SNAPSHOT",
                "firmware_url": "https://downloads.openwrt.org/",
                "revision": "r33119-33af3a9f7e",
                "target": "mediatek/filogic",
                "description": "OpenWrt SNAPSHOT r33119-33af3a9f7e",
                "builddate": "1771324042"
        }
}

Seeing this procd warning, anyone else seeing this?

Tue Feb 17 17:17:30 2026 daemon.warn procd: failed adding instance cgroup for dnsmasq: No error information
Tue Feb 17 17:17:31 2026 daemon.warn procd: failed adding instance cgroup for network: No error information
Tue Feb 17 17:17:36 2026 daemon.warn procd: failed adding instance cgroup for dnsmasq: No error information
Tue Feb 17 17:17:38 2026 daemon.warn procd: failed adding instance cgroup for pbr: No error information
Tue Feb 17 17:17:44 2026 daemon.warn procd: failed adding instance cgroup for pbr: No error information
Tue Feb 17 17:17:55 2026 daemon.warn procd: failed adding instance cgroup for pbr: No error information

Seems like a procd problem with the kernel control group?

Everything seems to work though consistent with the fact that it is a warning :slight_smile:

2

Do you have cgroupfs-mount installed?

3

See https://github.com/openwrt/procd/issues/31 ... already fixed but not in master yet.

1 Like
4

Yes,

root@MT-6000:~# mount | grep cgroup
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)

It looks like a problem in procd not able to write to a subtree

I just checked and there are recent commits about cgroups in procd which are not yet in Snapshot as it is only a warning and everything is functioning I will just wait.
No time to research it, testing the new openvpn proto handler and working on PBR and NetBird :slight_smile:

5

HaHa you just beat me, thanks

1 Like
6

My qbittorrent stopped launching. If I delete the profile folder /etc/qbittrorrent, it launches and creates a new folder. Can anyone advise how to resolve this?

root@OpenWrt:~# /etc/init.d/qbittorrent restart
root@OpenWrt:~# logread -e qbittorrent
Thu Feb 19 20:31:09 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:31:14 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:31:20 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:31:26 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:31:31 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:31:32 2026 daemon.info procd: Instance qbittorrent::instance1 s in a crash loop 6 crashes, 1 seconds since last crash
Thu Feb 19 20:43:21 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:43:27 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:43:32 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:43:38 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:43:44 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:43:49 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:43:50 2026 daemon.info procd: Instance qbittorrent::instance1 s in a crash loop 6 crashes, 1 seconds since last crash
Thu Feb 19 20:46:45 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:46:50 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:46:56 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:47:01 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:47:07 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:47:13 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:47:14 2026 daemon.info procd: Instance qbittorrent::instance1 s in a crash loop 6 crashes, 0 seconds since last crash
Thu Feb 19 20:59:41 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:59:47 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:59:53 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 20:59:58 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 21:00:04 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 21:00:10 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
Thu Feb 19 21:00:11 2026 daemon.info procd: Instance qbittorrent::instance1 s in a crash loop 6 crashes, 0 seconds since last crash
Thu Feb 19 21:09:53 2026 daemon.warn procd: failed adding instance cgroup for qbittorrent: No error information
7

It is a known problem, a patch is already underway so wait a few days and get a new build

8

Did you mean this patch? It didn't help. https://github.com/openwrt/openwrt/commit/e95cfd2ad75558be21d01838f816a65c5c016ce5

9

Building today Master/Snapshot which has the patches included is now running much better without all the procd cgroup errors for me

10

Qbittorrent does not start when the /etc/qbittorrent folder already exists. If you delete the folder, it will start once. After rebooting or updating the firmware, qbittorrent it still won't start until you delete the folder.

11

You have to report that via github. Totally unrelated to issue here.

1 Like
12

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.