System crash - strange chars in syslog
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I have a small server which I use for testing and programming. Currently it runs Debian 9.4 stretch with 4.14.0-0.bpo.3-amd64 kernel.
Today I tried to connect through SSH but I couldn't then I tried to ping it and it was unreachable. Therefore I had to hard-restart it by unplugging power cable. Then I went to /var/log/syslog and I found a strange line containing exactly 6140 characters like the following
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
then nothing else until new log entries of system restart. This is actually the first time it happens.
Does someone know what could it be?
debian logs
New contributor
add a comment |Â
up vote
3
down vote
favorite
I have a small server which I use for testing and programming. Currently it runs Debian 9.4 stretch with 4.14.0-0.bpo.3-amd64 kernel.
Today I tried to connect through SSH but I couldn't then I tried to ping it and it was unreachable. Therefore I had to hard-restart it by unplugging power cable. Then I went to /var/log/syslog and I found a strange line containing exactly 6140 characters like the following
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
then nothing else until new log entries of system restart. This is actually the first time it happens.
Does someone know what could it be?
debian logs
New contributor
1
Well I wrote about this at askubuntu.com/a/1020373/43344 , for one. (-: Then there are unix.stackexchange.com/questions/227173 and unix.stackexchange.com/questions/237321 â¦
â JdeBP
2 hours ago
1
@JdeBP I prefer your first answer/link, that is indeed it. Odd has a question with 1500+ visits you have not got a single vote, +1.
â Rui F Ribeiro
1 hour ago
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I have a small server which I use for testing and programming. Currently it runs Debian 9.4 stretch with 4.14.0-0.bpo.3-amd64 kernel.
Today I tried to connect through SSH but I couldn't then I tried to ping it and it was unreachable. Therefore I had to hard-restart it by unplugging power cable. Then I went to /var/log/syslog and I found a strange line containing exactly 6140 characters like the following
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
then nothing else until new log entries of system restart. This is actually the first time it happens.
Does someone know what could it be?
debian logs
New contributor
I have a small server which I use for testing and programming. Currently it runs Debian 9.4 stretch with 4.14.0-0.bpo.3-amd64 kernel.
Today I tried to connect through SSH but I couldn't then I tried to ping it and it was unreachable. Therefore I had to hard-restart it by unplugging power cable. Then I went to /var/log/syslog and I found a strange line containing exactly 6140 characters like the following
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
then nothing else until new log entries of system restart. This is actually the first time it happens.
Does someone know what could it be?
debian logs
debian logs
New contributor
New contributor
edited 2 hours ago
Jeff Schaller
34.4k951114
34.4k951114
New contributor
asked 2 hours ago
DrKey
1161
1161
New contributor
New contributor
1
Well I wrote about this at askubuntu.com/a/1020373/43344 , for one. (-: Then there are unix.stackexchange.com/questions/227173 and unix.stackexchange.com/questions/237321 â¦
â JdeBP
2 hours ago
1
@JdeBP I prefer your first answer/link, that is indeed it. Odd has a question with 1500+ visits you have not got a single vote, +1.
â Rui F Ribeiro
1 hour ago
add a comment |Â
1
Well I wrote about this at askubuntu.com/a/1020373/43344 , for one. (-: Then there are unix.stackexchange.com/questions/227173 and unix.stackexchange.com/questions/237321 â¦
â JdeBP
2 hours ago
1
@JdeBP I prefer your first answer/link, that is indeed it. Odd has a question with 1500+ visits you have not got a single vote, +1.
â Rui F Ribeiro
1 hour ago
1
1
Well I wrote about this at askubuntu.com/a/1020373/43344 , for one. (-: Then there are unix.stackexchange.com/questions/227173 and unix.stackexchange.com/questions/237321 â¦
â JdeBP
2 hours ago
Well I wrote about this at askubuntu.com/a/1020373/43344 , for one. (-: Then there are unix.stackexchange.com/questions/227173 and unix.stackexchange.com/questions/237321 â¦
â JdeBP
2 hours ago
1
1
@JdeBP I prefer your first answer/link, that is indeed it. Odd has a question with 1500+ visits you have not got a single vote, +1.
â Rui F Ribeiro
1 hour ago
@JdeBP I prefer your first answer/link, that is indeed it. Odd has a question with 1500+ visits you have not got a single vote, +1.
â Rui F Ribeiro
1 hour ago
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
5
down vote
That is corruption of the filesystem/syslog writing.
The crash caught the system mid-writing to the syslog file, and that is the end result. Already have seen it several times over the years, in Linux VMs and a couple more times in Raspberries and Banana Pis.
Nothing to obsess about or lose time to investigate a lot why you have this for a one-time event. I would be more worried at finding out why it crashed, especially if it is a regular event.
PS getting into anecdotal territory, last time I had this happening regularly in a Banana Pi R1, I managed to trace the cause to a (faulty) realtek wifi chipset.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
That is corruption of the filesystem/syslog writing.
The crash caught the system mid-writing to the syslog file, and that is the end result. Already have seen it several times over the years, in Linux VMs and a couple more times in Raspberries and Banana Pis.
Nothing to obsess about or lose time to investigate a lot why you have this for a one-time event. I would be more worried at finding out why it crashed, especially if it is a regular event.
PS getting into anecdotal territory, last time I had this happening regularly in a Banana Pi R1, I managed to trace the cause to a (faulty) realtek wifi chipset.
add a comment |Â
up vote
5
down vote
That is corruption of the filesystem/syslog writing.
The crash caught the system mid-writing to the syslog file, and that is the end result. Already have seen it several times over the years, in Linux VMs and a couple more times in Raspberries and Banana Pis.
Nothing to obsess about or lose time to investigate a lot why you have this for a one-time event. I would be more worried at finding out why it crashed, especially if it is a regular event.
PS getting into anecdotal territory, last time I had this happening regularly in a Banana Pi R1, I managed to trace the cause to a (faulty) realtek wifi chipset.
add a comment |Â
up vote
5
down vote
up vote
5
down vote
That is corruption of the filesystem/syslog writing.
The crash caught the system mid-writing to the syslog file, and that is the end result. Already have seen it several times over the years, in Linux VMs and a couple more times in Raspberries and Banana Pis.
Nothing to obsess about or lose time to investigate a lot why you have this for a one-time event. I would be more worried at finding out why it crashed, especially if it is a regular event.
PS getting into anecdotal territory, last time I had this happening regularly in a Banana Pi R1, I managed to trace the cause to a (faulty) realtek wifi chipset.
That is corruption of the filesystem/syslog writing.
The crash caught the system mid-writing to the syslog file, and that is the end result. Already have seen it several times over the years, in Linux VMs and a couple more times in Raspberries and Banana Pis.
Nothing to obsess about or lose time to investigate a lot why you have this for a one-time event. I would be more worried at finding out why it crashed, especially if it is a regular event.
PS getting into anecdotal territory, last time I had this happening regularly in a Banana Pi R1, I managed to trace the cause to a (faulty) realtek wifi chipset.
edited 43 mins ago
answered 2 hours ago
Rui F Ribeiro
37.4k1374118
37.4k1374118
add a comment |Â
add a comment |Â
DrKey is a new contributor. Be nice, and check out our Code of Conduct.
DrKey is a new contributor. Be nice, and check out our Code of Conduct.
DrKey is a new contributor. Be nice, and check out our Code of Conduct.
DrKey is a new contributor. Be nice, and check out our Code of Conduct.
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%2f477537%2fsystem-crash-strange-chars-in-syslog%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
1
Well I wrote about this at askubuntu.com/a/1020373/43344 , for one. (-: Then there are unix.stackexchange.com/questions/227173 and unix.stackexchange.com/questions/237321 â¦
â JdeBP
2 hours ago
1
@JdeBP I prefer your first answer/link, that is indeed it. Odd has a question with 1500+ visits you have not got a single vote, +1.
â Rui F Ribeiro
1 hour ago