|
From: | hamish |
Subject: | Re: [fluid-dev] Running Fluidsynth as a systemd service |
Date: | Fri, 24 Feb 2023 10:45:29 +1100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 |
Hi,
I'm having problems running Fluidsynth as a service
fluidsynth --version
FluidSynth runtime version 2.3.1
FluidSynth executable version 2.3.1
Sample type=double
If I run Fluidsynth as a service, this is what gets written to the systemd log:
systemctl status fluidsynth
○ fluidsynth.service - FluidSynth Daemon
Loaded: loaded (/lib/systemd/system/fluidsynth.service; enabled; preset: disabled)
Active: inactive (dead) since Tue 2023-02-21 16:09:38 EST; 1s ago
Duration: 39.409s
Docs: man:fluidsynth(1)
Process: 48529 ExecStart=/usr/bin/fluidsynth -is $OTHER_OPTS $SOUND_FONT (code=killed, signal=TERM)
Main PID: 48529 (code=killed, signal=TERM)
CPU: 2.623s
Feb 21 16:09:27 dragon fluidsynth[48529]: Failed to symlink /root/.config/pulse/5e02be2510074b4d841b6f739518d755-runtime.tmp to /tmp/pulse-4iyRmKxiKg9I: Read-only file system
Feb 21 16:09:27 dragon fluidsynth[48529]: Failed to symlink /root/.config/pulse/5e02be2510074b4d841b6f739518d755-runtime.tmp: Read-only file system
Feb 21 16:09:32 dragon fluidsynth[48529]: Failed to symlink /root/.config/pulse/5e02be2510074b4d841b6f739518d755-runtime.tmp to /tmp/pulse-DUPmkLrvifSk: Read-only file system
Feb 21 16:09:32 dragon fluidsynth[48529]: Failed to symlink /root/.config/pulse/5e02be2510074b4d841b6f739518d755-runtime.tmp: Read-only file system
Feb 21 16:09:37 dragon fluidsynth[48529]: Failed to symlink /root/.config/pulse/5e02be2510074b4d841b6f739518d755-runtime.tmp to /tmp/pulse-FKEvi8dcgARs: Read-only file system
Feb 21 16:09:37 dragon fluidsynth[48529]: Failed to symlink /root/.config/pulse/5e02be2510074b4d841b6f739518d755-runtime.tmp: Read-only file system
This looks like errors from Pulse Audio (/tmp/pulse-...). So maybe your Fluidsynth is not being started with the right options/configuration.
You didn't post your systemd service file, but you've prevented it from writing to /tmp, which appears to be the issue. You could use PrivateTmp=true to allow it to write to its own /tmp.
Hamish
[Prev in Thread] | Current Thread | [Next in Thread] |