systemd38 + rsyslog

systemd38 + rsyslog

[Allin Cottrell]

Sorry to be a pest, but I have one more issue with the 
systemd-38 update (I'm actually using systemd from git 
e6520a0fcebb4d5e07f4c81a51382501b0beb22f to get the update to 
make ACLs optional).

I'm running rsyslog; I have an rsyslog.service file in 
/lib/systemd/system which reads as follows:

<service>
[Unit]
Description=System Logging Service

[Service]
ExecStart=/usr/sbin/rsyslogd -n -c6
Sockets=syslog.socket
StandardOutput=null

[Install]
WantedBy=multi-user.target
</service>

Logging apparently works OK (/var/log/messages contains what 
you'd expect), but I'm seeing this from dmesg on booting:

systemd[1]: Socket service syslog.service not loaded, 
refusing.

On looking into the syslog.socket file installed by current 
systemd, I noticed a recommendation to make a symlink 
named syslog.service, pointing to rsyslog.service, in
/lib/systemd/system.

I made the symlink, and the boot-up error disappeared. But it 
had a nasty side-effect: now systemctl poweroff and systemctl 
reboot stopped working. These commands put the machine into a 
zombie-like state (blank screen with a blinking cursor at the 
top left); it was necessary to stop the machine with the power 
button. It took me a while to figure out what was responsible 
for this behavior, but when I deleted the syslog.service 
symlink, poweroff and reboot started working again -- though 
of course the boot-error message is back.

-- 
Allin Cottrell
Department of Economics
Wake Forest University, NC

Re: systemd38 + rsyslog

[Miklos Vajna]

[-- Attachment #1: Type: text/plain, Size: 741 bytes --]

On Thu, Jan 19, 2012 at 03:26:18PM -0500, Allin Cottrell <cottrell@wfu.edu> wrote:
> I made the symlink, and the boot-up error disappeared. But it 
> had a nasty side-effect: now systemctl poweroff and systemctl 
> reboot stopped working. These commands put the machine into a 
> zombie-like state (blank screen with a blinking cursor at the 
> top left); it was necessary to stop the machine with the power 
> button. It took me a while to figure out what was responsible 
> for this behavior, but when I deleted the syslog.service 
> symlink, poweroff and reboot started working again -- though 
> of course the boot-error message is back.

Sound like the issue commit ead51eb4ed55981f290e40a871ffbca6480c4cd3
already solved.

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: systemd38 + rsyslog

[Allin Cottrell]

On Thu, 19 Jan 2012, Miklos Vajna wrote:

> On Thu, Jan 19, 2012 at 03:26:18PM -0500, Allin Cottrell <cottrell@wfu.edu> wrote:
>> I made the symlink, and the boot-up error disappeared. But it
>> had a nasty side-effect: now systemctl poweroff and systemctl
>> reboot stopped working. These commands put the machine into a
>> zombie-like state (blank screen with a blinking cursor at the
>> top left); it was necessary to stop the machine with the power
>> button. It took me a while to figure out what was responsible
>> for this behavior, but when I deleted the syslog.service
>> symlink, poweroff and reboot started working again -- though
>> of course the boot-error message is back.
>
> Sound like the issue commit ead51eb4ed55981f290e40a871ffbca6480c4cd3
> already solved.

Thanks, that's a nice easy change to try out.

-- 
Allin Cottrell
Department of Economics
Wake Forest University, NC