Bug#764298: Still an issue

Am 2015-03-04 01:13, schrieb Michael Biebl: Am 04.03.2015 um 01:34 schrieb Michael Biebl: Am 04.03.2015 um 01:07 schrieb Daurnimator: Did you dist-upgrade the VM and those failures are from before the upgrade? Can you attach your /var/log/dpkg.log The reason why I'm asking is, that the fixed

Bug#764298: Still an issue

Am 04.03.2015 um 01:34 schrieb Michael Biebl: > Am 04.03.2015 um 01:07 schrieb Daurnimator: > Did you dist-upgrade the VM and those failures are from before the upgrade? > Can you attach your /var/log/dpkg.log The reason why I'm asking is, that the fixed version 215-12 migrated to testing on 2015-

Bug#764298: Still an issue

Am 04.03.2015 um 01:07 schrieb Daurnimator: > On 3 March 2015 at 18:42, Michael Biebl wrote: >> What's the output of >> systemctl cat systemd-logind.service >> systemctl status systemd-logind.service > > $ sudo systemctl cat systemd-logind.service > # /lib/systemd/system/systemd-logind.service >

Bug#764298: Still an issue

On 3 March 2015 at 18:42, Michael Biebl wrote: > What's the output of > systemctl cat systemd-logind.service > systemctl status systemd-logind.service $ sudo systemctl cat systemd-logind.service # /lib/systemd/system/systemd-logind.service # This file is part of systemd. # # systemd is free sof

Bug#764298: Still an issue

Am 04.03.2015 um 00:19 schrieb Daurnimator: > I just installed a fresh systemd (via amazon AMI: > https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie) that includes systemd > 215-12 > I still got the log message: > > Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service... > Mar 03 2

Bug#764298: Still an issue

Am 04.03.2015 um 00:37 schrieb Daurnimator: > On 3 March 2015 at 18:35, Michael Biebl wrote: >> >> What's the output of >> systemctl status dbus.service dbus.socket? > > > I do not have dbus installed. > > $ sudo systemctl status dbus.service > ● dbus.service >Loaded: not-found (Reason: No

Bug#764298: Still an issue

On 3 March 2015 at 18:35, Michael Biebl wrote: > > What's the output of > systemctl status dbus.service dbus.socket? I do not have dbus installed. $ sudo systemctl status dbus.service ● dbus.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) $ sudo sys

Bug#764298: Still an issue

I just installed a fresh systemd (via amazon AMI: https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie) that includes systemd 215-12 I still got the log message: Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service... Mar 03 20:02:56 ip-10-80-175-145 systemd-logind[323]: Failed to co

Bug#762700: systemd: journald fails to forward most boot messages to syslog

Am 03.03.2015 um 16:26 schrieb Christian Seiler: > Am 2015-03-03 15:33, schrieb Michael Biebl: >> Am 02.03.2015 um 15:42 schrieb Christian Seiler: >> >>> - SOLUTION (mostly the same as before, but SendBuffer is set on a >>>different unit and a Condition is added to the service): >>> >>>

Bug#762700: systemd: journald fails to forward most boot messages to syslog

Am 2015-03-03 16:26, schrieb Michael Biebl: I did a couple more reboots and did indeed run into the problem, that systemd-sysctl.service was started after syslog.socket, so I got the "missed XXX messages" again. Adding the After=systemd-sysctl.service ordering to syslog.socket fixed that. In [1]

Bug#762700: systemd: journald fails to forward most boot messages to syslog

Am 2015-03-03 15:33, schrieb Michael Biebl: Am 02.03.2015 um 15:42 schrieb Christian Seiler: - SOLUTION (mostly the same as before, but SendBuffer is set on a different unit and a Condition is added to the service): 1. Increase max_dgram_qlen to a reasonable value. The easiest

Bug#762700: systemd: journald fails to forward most boot messages to syslog

Am 03.03.2015 um 16:00 schrieb Michael Biebl: > Am 03.03.2015 um 15:33 schrieb Michael Biebl: >> Am 02.03.2015 um 15:42 schrieb Christian Seiler: >> >>> - SOLUTION (mostly the same as before, but SendBuffer is set on a >>>different unit and a Condition is added to the service): >>> >>> 1

Bug#762700: systemd: journald fails to forward most boot messages to syslog

Am 03.03.2015 um 15:33 schrieb Michael Biebl: > Am 02.03.2015 um 15:42 schrieb Christian Seiler: > >> - SOLUTION (mostly the same as before, but SendBuffer is set on a >>different unit and a Condition is added to the service): >> >> 1. Increase max_dgram_qlen to a reasonable value. The

Bug#762700: systemd: journald fails to forward most boot messages to syslog

Am 02.03.2015 um 15:42 schrieb Christian Seiler: > - SOLUTION (mostly the same as before, but SendBuffer is set on a >different unit and a Condition is added to the service): > > 1. Increase max_dgram_qlen to a reasonable value. The easiest > way is via a systemd service: > >