Transmission won't start

Hello,

I installed transmission-daemon-mbedtls 2.94-11.9 and the enabled it in /etc/config/transmission

I then enabled the service, tweaked the config to point on /srv/ and started it.

I can see in /var/log/messages

2020-04-13 18:46:42 info procd[]: Instance transmission::instance1 s in a crash loop 6 crashes, 0 seconds since last crash

but I have no information on why it does crash.
I have tried to start it manually as root with the same command and the daemon starts properly.

I have tried to comment the seccomp and jail lines in the init script, but nothing change.
There is zero info on why the instance is crashing.

The PROCD_DEBUG=1 result to this:

    { "name": "transmission" }
    { "name": "transmission", "script": "\/etc\/init.d\/transmission", "instances": { "instance1": { "command": [ "\/usr\/bin\/transmission-daemon", "-f", "-g", "\/srv\/transmission" ], "user": "transmission", "nice": 10, "stderr": true, "respawn": [ "3600", "5", "5" ], "seccomp": "\/etc\/seccomp\/transmission-daemon.json", "limits": { "core": "0 0", "as": "1033990000 1033990000" }, "jail": { "name": "transmission", "log": true, "mount": { "\/srv\/transmission\/settings.json": "0", "\/srv\/transmission\/resume": "1", "\/srv\/transmission\/torrents": "1", "\/srv\/transmission\/blocklists": "1", "\/srv\/transmission\/stats.json": "1", "\/srv\/transmission\/done": "1" } } } }, "triggers": [ ], "data": { } }

seccomp config looks like this:

    {
            "whitelist": [
                    "accept4",
                    "access",
                    "arm_fadvise64_64",
                    "bind",
                    "brk",
                    "clock_gettime",
                    "clone",
                    "close",
                    "connect",
                    "epoll_create1",
                    "epoll_ctl",
                    "epoll_pwait",
                    "exit",
                    "exit_group",
                    "fadvise64",
                    "fallocate",
                    "fcntl",
                    "fcntl64",
                    "fstat",
                    "fstat64",
                    "fsync",
                    "futex",
                    "getdents64",
                    "getpeername",
                    "getpid",
                    "getsockname",
                    "getsockopt",
                    "ioctl",
                    "listen",
                    "_llseek",
                    "lseek",
                    "madvise",
                    "membarrier",
                    "mkdir",
                    "mmap",
                    "mmap2",
                    "mprotect",
                    "munmap",
                    "nanosleep",
                    "_newselect",
                    "open",
                    "pipe",
                    "pipe2",
                    "poll",
                    "pread64",
                    "prlimit64",
                    "pwrite64",
                    "read",
                    "readlink",
                    "readv",
                    "recvfrom",
                    "rename",
                    "rmdir",
                    "rt_sigaction",
                    "rt_sigprocmask",
                    "rt_sigreturn",
                    "select",
                    "sendto",
                    "setsockopt",
                    "shutdown",
                    "sigreturn",
                    "socket",
                    "stat",
                    "stat64",
                    "umask",
                    "uname",
                    "unlink",
                    "write",
                    "writev"
            ],
            "policy": 1
    }

Hi,

run transmission-daemon from console witch switcher -c (patch for config dir)

Hi,

run transmission-daemon from console witch switcher -c (patch for config dir)

It works that way, but does not benefit from the integration of the procd start scripts (security jail, run as specific user, and luci integration)

Hi!

Based on your bug report, I was able to reproduce it. It should be related to seccomp, but it requires further investigation. That’s why I re-opened issue for Turris OS 5.0 and will look at it!