rsyslogd - logging across filesystem boundaries

Hi all,

I recently upgraded to trixie (from bookworm). Most things seemed to go well, but I've had a problem with rsyslog. I have the following configuration:

# /home is mounted on its own filesystem

casey@machine:~$ mount | grep 'on \/$home$\? '

/dev/sdd2 on / type ext4 (rw,relatime,errors=remount-ro)

/dev/mapper/vg01-home on /home type ext4 (rw,relatime,errors=remount-ro)

# local6 gets logged to /home/foobar/foobar.log

casey@quartet:~$ cat /etc/rsyslog.d/70-foobar.conf

$FileCreateMode 0644

local6.* -/home/foobar/foobar.log

# Running Debian 13.3

casey@quartet:~$ cat /etc/debian_version

13.3

# rsyslog 8.2504.0-1

casey@quartet:~$ dpkg --list | grep rsyslog

ii rsyslog 8.2504.0-1 amd64 reliable system and kernel logging daemon

So, in essence syslog is configured to log things with facility local6 to /home/foobar/foobar.log, which is on a separate filesystem than root. Everything worked just fine prior to the upgrade. Afterwards, I get the following in my /var/log/syslog:

2026-01-20T13:07:09.725140-07:00 quartet rsyslogd: error during config processing: omfile: creating parent directories for file '/home/foobar/foobar.log' failed: Read-only file system [v8.2504.0 try https://www.rsyslog.com/e/2207 ]

But when I modify the conf file:

# local6 gets logged to /var/log/foobar.log

casey@quartet:~$ cat /etc/rsyslog.d/70-foobar.conf

$FileCreateMode 0644

local6.* -/var/log/foobar.log

Everything works as I would expect it to. This has happened on two both servers that I've upgraded to trixie.

Any ideas?

Thanks,

Casey