Mixing
Error: /etc/machine-id contains 32 characters (32 were expected)
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
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?
debian chrome chromium-browser
asked 3 hours ago
chevallier
8711116
add a comment |Â
up vote
1
down vote
favorite
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?
debian chrome chromium-browser
asked 3 hours ago
chevallier
8711116
Did you look to actually find out what/etc/machine-idcontains? 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
2 hours ago
@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
1 hour ago
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
1 hour ago
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
1 hour ago
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
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?
debian chrome chromium-browser
asked 3 hours ago
chevallier
8711116
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?
debian chrome chromium-browser
debian chrome chromium-browser
asked 3 hours ago
chevallier
8711116
asked 3 hours ago
chevallier
8711116
edited 1 hour ago
asked 3 hours ago
chevallier
8711116
asked 3 hours ago
chevallier
8711116
asked 3 hours ago
chevallier
8711116
8711116
Did you look to actually find out what/etc/machine-idcontains? 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
2 hours ago
@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
1 hour ago
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
1 hour ago
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
1 hour ago
add a comment |Â
Did you look to actually find out what/etc/machine-idcontains? 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
2 hours ago
@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
1 hour ago
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
1 hour ago
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
1 hour ago
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
2 hours ago
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
2 hours ago
@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
1 hour ago
@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
1 hour ago
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
1 hour ago
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
1 hour ago
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
1 hour ago
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
1 hour ago
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
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:
- comp.os.linux.misc post
- Linux Questions post
answered 2 hours ago
muru
34.2k578148
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
2 hours ago
As the error message implies: I truly do have a machine ID, which contains 32 characters.
– chevallier
1 hour ago
@chevallier and you're sure your version of chromium doesn't have the buggy logging code?
– muru
1 hour ago
It does, thanks @muru
– chevallier
1 hour ago
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
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:
- comp.os.linux.misc post
- Linux Questions post
answered 2 hours ago
muru
34.2k578148
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
2 hours ago
As the error message implies: I truly do have a machine ID, which contains 32 characters.
– chevallier
1 hour ago
@chevallier and you're sure your version of chromium doesn't have the buggy logging code?
– muru
1 hour ago
It does, thanks @muru
– chevallier
1 hour ago
add a comment |Â
up vote
3
down vote
accepted
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:
- comp.os.linux.misc post
- Linux Questions post
answered 2 hours ago
muru
34.2k578148
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
2 hours ago
As the error message implies: I truly do have a machine ID, which contains 32 characters.
– chevallier
1 hour ago
@chevallier and you're sure your version of chromium doesn't have the buggy logging code?
– muru
1 hour ago
It does, thanks @muru
– chevallier
1 hour ago
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
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:
- comp.os.linux.misc post
- Linux Questions post
answered 2 hours ago
muru
34.2k578148
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:
- comp.os.linux.misc post
- Linux Questions post
answered 2 hours ago
muru
34.2k578148
edited 2 hours ago
answered 2 hours ago
muru
34.2k578148
answered 2 hours ago
muru
34.2k578148
answered 2 hours ago
muru
34.2k578148
34.2k578148
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
2 hours ago
As the error message implies: I truly do have a machine ID, which contains 32 characters.
– chevallier
1 hour ago
@chevallier and you're sure your version of chromium doesn't have the buggy logging code?
– muru
1 hour ago
It does, thanks @muru
– chevallier
1 hour ago
add a comment |Â
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
2 hours ago
As the error message implies: I truly do have a machine ID, which contains 32 characters.
– chevallier
1 hour ago
@chevallier and you're sure your version of chromium doesn't have the buggy logging code?
– muru
1 hour ago
It does, thanks @muru
– chevallier
1 hour ago
1
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
2 hours ago
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
2 hours ago
As the error message implies: I truly do have a machine ID, which contains 32 characters.
– chevallier
1 hour ago
As the error message implies: I truly do have a machine ID, which contains 32 characters.
– chevallier
1 hour ago
@chevallier and you're sure your version of chromium doesn't have the buggy logging code?
– muru
1 hour ago
@chevallier and you're sure your version of chromium doesn't have the buggy logging code?
– muru
1 hour ago
It does, thanks @muru
– chevallier
1 hour ago
It does, thanks @muru
– chevallier
1 hour ago
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f477180%2ferror-etc-machine-id-contains-32-characters-32-were-expected%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Did you look to actually find out what
/etc/machine-idcontains? 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
2 hours ago
@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
1 hour ago
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
1 hour ago
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
1 hour ago