systemd-journald fails to start due to corrupted /etc/machine-id (was: Re: systemd-journald fails)

From	Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.com>
Newsgroups	linux.debian.user
Subject	systemd-journald fails to start due to corrupted /etc/machine-id (was: Re: systemd-journald fails)
Date	2016-12-11 09:40 +0100
Message-ID	<sN7PP-5jB-5@gated-at.bofh.it> (permalink)
References	<sMWKK-6RV-15@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Rainer Dorsch:
>
> But to my surprise even on a fresh install of the jessie image 
> /etc/machine-id is already broken:
>
>> root@scw-790923:~# cat /etc/machine-id
>>
>> 9d1b906dd5ea40359e2071d29c12aabe
>>
>> 71f
>>
>> root@scw-790923:~#
>>
> But it seems the systemd version in jessie seems to be more tolerant 
> against broken machine-id fails (?).

It is.  Lennart Poettering introduced this intolerance on 2016-07-21.  
Before then, /etc/machine-id could contain other stuff after the first 
line, and systemd would ignore it because it only ever read and wrote 
the 32-character ID and the newline of the first line of the file.  
Lennart Poettering changed an I/O function call from an exact length 
read of 33 characters to a variable length read of up to 38 characters 
followed by a check that the number of characters read is only ever 33, 
and the intolerance is as you see now.

So your machine IDs have possibly been like this for a long time.

Your next stops are https://github.com/systemd/systemd/issues/4025 and 
https://github.com/scaleway/image-tools/issues/181 .

Thread

systemd-journald fails Rainer Dorsch <ml@bokomoko.de> - 2016-12-04 16:40 +0100
  Re: systemd-journald fails deloptes <deloptes@gmail.com> - 2016-12-05 00:10 +0100
    Re: systemd-journald fails emetib <chadbrabec@gmail.com> - 2016-12-05 02:10 +0100
      Re: systemd-journald fails Rainer Dorsch <ml@bokomoko.de> - 2016-12-05 11:10 +0100
  Re: systemd-journald fails emetib <chadbrabec@gmail.com> - 2016-12-05 18:10 +0100
    Re: systemd-journald fails Greg Wooledge <wooledg@eeg.ccf.org> - 2016-12-05 19:10 +0100
    Re: systemd-journald fails Rainer Dorsch <ml@bokomoko.de> - 2016-12-05 19:30 +0100
      Re: systemd-journald fails Greg Wooledge <wooledg@eeg.ccf.org> - 2016-12-05 19:50 +0100
      Re: systemd-journald fails Dan Ritter <dsr@randomstring.org> - 2016-12-05 20:10 +0100
  Re: systemd-journald fails emetib <chadbrabec@gmail.com> - 2016-12-05 20:40 +0100
  Re: systemd-journald fails Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.com> - 2016-12-06 01:30 +0100
    Re: systemd-journald fails Rainer Dorsch <ml@bokomoko.de> - 2016-12-09 22:00 +0100
    Re: systemd-journald fails Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.com> - 2016-12-09 23:40 +0100
      Re: systemd-journald fails Rainer Dorsch <contact@bokomoko.de> - 2016-12-10 14:20 +0100
        systemd-journald fails to start due to corrupted /etc/machine-id  (was: Re: systemd-journald fails) Michael Biebl <biebl@debian.org> - 2016-12-10 17:00 +0100
          Re: systemd-journald fails to start due to corrupted /etc/machine-id (was: Re: systemd-journald fails) Rainer Dorsch <fdbaut@bokomoko.de> - 2016-12-10 21:50 +0100
            systemd-journald fails to start due to corrupted /etc/machine-id  (was: Re: systemd-journald fails) Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.com> - 2016-12-11 09:40 +0100
  Re: systemd-journald fails Michael Biebl <biebl@debian.org> - 2016-12-09 23:10 +0100
    Re: systemd-journald fails Rainer Dorsch <ml@bokomoko.de> - 2016-12-10 14:00 +0100

csiph-web