2

Everytime I start chromium on debian 9, I get the following syslog error, which is very annoying:

ERROR:browser_dm_token_storage_linux.cc(93)] \
    Error: /etc/machine-id contains 32 characters (32 were expected).

The message makes no sense to me as my /etc/machine contains 32 random characters as it should. But maybe someone knows why this happens?

closed as unclear what you're asking by Braiam, schily, Jeff Schaller, Archemar, RalfFriedl Oct 24 '18 at 7:54

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • Did you look to actually find out what /etc/machine-id contains? Answerers have no access to your machine and cannot look for you, and are not telepathic so cannot reach into your mind to find out something that you know that you have not edited into the question. – JdeBP Oct 23 '18 at 7:10
  • @JdeBP - yeah, very smart. You don't need to be "telepathic", as the error message already implies, that my machine-id contains 32 characters. Anyway, I edited my question, thanks for your hint. – chevallier Oct 23 '18 at 8:12
  • 4
    Actually, answerers still do have to be telepathic, because the error message is known to be wrong and you still have not shown them in the question what is in the file. Your description of what it should contain is erroneous. Show answerers a hexdump of the file. Do not hand-wave an erroneous description of what it contains, because that just muddies the waters and requires more telepathy. – JdeBP Oct 23 '18 at 8:18
  • 3
    FWIW, od -c /etc/machine-id's output might be useful, to verify it doesn't contain some extra non-printing characters or similar. – muru Oct 23 '18 at 8:41
6

There was a mistake in the logging code, which printed machine_id_size instead of the size of input read. That's why it says 32 both times. Since the mistake has been fixed, a more sensible message can be expected in a future release.

It's likely caused by some error in reading /etc/machine-id. If /etc/machine-id doesn't exist, try looking for /var/lib/dbus/machine-id or /var/db/dbus/machine-id. If one of those exists, move it to /etc/machine-id and make it a symlink to /etc/machine-id. (See JdeBP's answer for more.)

Sources:

  • 1
    It's important to make that symbolic link that way around and not the other. unix.stackexchange.com/a/395460/5132 unix.stackexchange.com/a/396053/5132 – JdeBP Oct 23 '18 at 8:05
  • As the error message implies: I truly do have a machine ID, which contains 32 characters. – chevallier Oct 23 '18 at 8:15
  • @chevallier and you're sure your version of chromium doesn't have the buggy logging code? – muru Oct 23 '18 at 8:17
  • 1
    Can someone please explain how this is the answer to the question? @chevallier says that his /etc/machine-id is not empty and his Chromium install is up to date. This reply only seems to address cases where those conditions are not met. I seem to be having the same issue. I'm using google-chrome-stable (71.0.3578.98-1), instead of of chromium, though, so I'm not sure how to check if the fix that @muru mentions has been fixed. FYI 0000000 3 4 8 e a 5 f a a 5 d 1 9 6 b 7 0000020 5 c b d 2 3 2 1 5 9 1 c b 6 a d 0000040 \n – carpiediem Dec 19 '18 at 8:19
  • @carpiediem that doesn't seem to be valid. Two nonprinting characters in it. See JdeBP's answer on how to generate a valid one. – muru Dec 19 '18 at 9:08

Not the answer you're looking for? Browse other questions tagged or ask your own question.