service rc-local.service fails to execute /etc/rc.local

[aspymid]

Describe the bug

In a headless installation the rc-local.service will fail to execute the /etc/rc.local file. The failure is as follows:

Jan 21 18:29:16 dclock3 systemd[1]: Starting /etc/rc.local Compatibility...
Jan 21 18:29:16 dclock3 systemd[324]: rc-local.service: Failed to set up standard output: No such device
Jan 21 18:29:16 dclock3 systemd[324]: rc-local.service: Failed at step STDOUT spawning /etc/rc.local: No such device
Jan 21 18:29:16 dclock3 systemd[1]: rc-local.service: Control process exited, code=exited, status=209/STDOUT
Jan 21 18:29:16 dclock3 systemd[1]: rc-local.service: Failed with result 'exit-code'.
Jan 21 18:29:16 dclock3 systemd[1]: Failed to start /etc/rc.local Compatibility.

Work around:
Modify /etc/systemd/system/rc-local.service.d/ttyoutput.conf to read as follows:
[Service]
StandardOutput=journal+console
StandardError=journal+console

instead of:
[Service]
StandardOutput=tty

This bug is also found on raspberry pi 2w and I suspect all the others.

Steps to reproduce the behaviour

The reproduce:

1. make a fresh installation of raspbian, (a headless installation)
2. make sure that the servide rc-local.service is enabled.
3. reboot
4. get disagnostic of the failure with : journalctl -u rc-local

Device (s)

Raspberry Pi 1 Mod. B+

System

Raspberry Pi reference 2023-12-05
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 446f3e34c8ceb33dfe7bd38578f1cd6b6afe19da, stage4
root@dclock3:# vcgencmd version
Mar 17 2023 10:52:42
Copyright (c) 2012 Broadcom
version 82f3750a65fadae9a38077e3c2e217ad158c8d54 (clean) (release) (start)
root@dclock3:# uname -a
Linux dclock3 6.1.21+ #1642 Mon Apr 3 17:19:14 BST 2023 armv6l GNU/Linux

Logs

No response

Additional context

No response

[pelwell]

That's not a kernel problem - please report it here instead: https://github.com/RPi-Distro/repo/issues
I'd transfer the Issue over, but that's not possible between two GitHub organisation.

[aspymid]

Thanks. Sorry for my mistake. Will do ...On Jan 22, 2024 04:40, Phil Elwell ***@***.***> wrote: That's not a kernel problem - please report it here instead: https://github.com/RPi-Distro/repo/issues I'd transfer the Issue over, but that's not possible between two GitHub organisation. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>