Best way to find out why Ubuntu 18.04 crashed. Where to find appropriate logs?Ubuntu crash - how to read log files16.04 LTS hard crashesUbuntu 17.04 Suddenly Crashed And No Idea WhyWhere do I find stderr logs?Ubuntu 18.04 immediately logs out with a specific userUbuntu 18.04 LTS installer crashed halfway during the installation
How can a signal be both periodic and random?
Why are Buddhist concepts so difficult?
Applying a function on several columns of a dataset fails on Missing
What can I wear to avoid getting frisked and crotch searched by TSA at the airport?
Why is Microwaved mac & cheese burnt where they touch?
What's the short and accented note at the very end of a song called?
Is the EU Settlement Scheme legal?
How are astronauts in the ISS protected from electric shock?
Are homeless people protected by antidiscrimination laws?
What happened to the SEV instruction on the 6502?
Would there be a difference between boiling whole black peppercorns or fine ground black pepp in a stew?
At what point can you walk out of a restaurant if they make you wait to pay the bill?
529 accounts for multiple kids
ASCII TURNED SHAPE
Is there any physical evidence for motion?
What is an idiom, phrase or expression for situation such as "throw a pigeon among cats"
How does one "become like water"?
Response to referee after rejection
Why are one-word titles so dominant in books, film, and games?
Is rent considered a debt?
How are hillsides farmed?
SpaceX Starship landing on Moon or Mars: why doesn't it fall over?
should I include offer letter from a different institution in my application for a faculty position
Flatten an array
Best way to find out why Ubuntu 18.04 crashed. Where to find appropriate logs?
Ubuntu crash - how to read log files16.04 LTS hard crashesUbuntu 17.04 Suddenly Crashed And No Idea WhyWhere do I find stderr logs?Ubuntu 18.04 immediately logs out with a specific userUbuntu 18.04 LTS installer crashed halfway during the installation
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I just found out that my Ubuntu 18.04 machine crashed 20 hrs ago and switched off.
How can I find out why? Is there an event logger?
Thank you for your help!
crash logging
asked Jan 21 at 8:11
ssssstutssssstut
511 silver badge7 bronze badges
add a comment
|
I just found out that my Ubuntu 18.04 machine crashed 20 hrs ago and switched off.
How can I find out why? Is there an event logger?
Thank you for your help!
crash logging
asked Jan 21 at 8:11
ssssstutssssstut
511 silver badge7 bronze badges
See askubuntu.com/questions/545504/… and serverfault.com/questions/611207/… and help.ubuntu.com/community/DebuggingSystemCrash
– Rinzwind
Jan 21 at 8:31
It could also be your hardware that shut itself down (not the OS). If cpu gets above a certain temp it can slow down, but if it reaches its max threshold (same with some other pieces of hardware) it just forces the psu to instantly shutdown (to protect itself from destruction). The OS doesn't know about this as hardware is just off. You won't find any logs in your OS if this is the case, but machine logs (if a good device that keeps it) will report the raising temperature & near threshold (but not the breach of threshold as it just turns off).
– guiverc
Jan 21 at 8:39
kernel and syslog where both empty. I installed smartctl afterwards but there was nothing either. A few weeks I replaced the SSD from mSATA m1 to a SATA SSD. Never had any issues with the M1 SSD.
– ssssstut
Jan 21 at 20:27
add a comment
|
I just found out that my Ubuntu 18.04 machine crashed 20 hrs ago and switched off.
How can I find out why? Is there an event logger?
Thank you for your help!
crash logging
asked Jan 21 at 8:11
ssssstutssssstut
511 silver badge7 bronze badges
I just found out that my Ubuntu 18.04 machine crashed 20 hrs ago and switched off.
How can I find out why? Is there an event logger?
Thank you for your help!
crash logging
crash logging
asked Jan 21 at 8:11
ssssstutssssstut
511 silver badge7 bronze badges
asked Jan 21 at 8:11
ssssstutssssstut
511 silver badge7 bronze badges
asked Jan 21 at 8:11
ssssstutssssstut
511 silver badge7 bronze badges
asked Jan 21 at 8:11
ssssstutssssstut
511 silver badge7 bronze badges
asked Jan 21 at 8:11
ssssstutssssstut
511 silver badge7 bronze badges
511 silver badge7 bronze badges
See askubuntu.com/questions/545504/… and serverfault.com/questions/611207/… and help.ubuntu.com/community/DebuggingSystemCrash
– Rinzwind
Jan 21 at 8:31
It could also be your hardware that shut itself down (not the OS). If cpu gets above a certain temp it can slow down, but if it reaches its max threshold (same with some other pieces of hardware) it just forces the psu to instantly shutdown (to protect itself from destruction). The OS doesn't know about this as hardware is just off. You won't find any logs in your OS if this is the case, but machine logs (if a good device that keeps it) will report the raising temperature & near threshold (but not the breach of threshold as it just turns off).
– guiverc
Jan 21 at 8:39
kernel and syslog where both empty. I installed smartctl afterwards but there was nothing either. A few weeks I replaced the SSD from mSATA m1 to a SATA SSD. Never had any issues with the M1 SSD.
– ssssstut
Jan 21 at 20:27
add a comment
|
See askubuntu.com/questions/545504/… and serverfault.com/questions/611207/… and help.ubuntu.com/community/DebuggingSystemCrash
– Rinzwind
Jan 21 at 8:31
It could also be your hardware that shut itself down (not the OS). If cpu gets above a certain temp it can slow down, but if it reaches its max threshold (same with some other pieces of hardware) it just forces the psu to instantly shutdown (to protect itself from destruction). The OS doesn't know about this as hardware is just off. You won't find any logs in your OS if this is the case, but machine logs (if a good device that keeps it) will report the raising temperature & near threshold (but not the breach of threshold as it just turns off).
– guiverc
Jan 21 at 8:39
kernel and syslog where both empty. I installed smartctl afterwards but there was nothing either. A few weeks I replaced the SSD from mSATA m1 to a SATA SSD. Never had any issues with the M1 SSD.
– ssssstut
Jan 21 at 20:27
See askubuntu.com/questions/545504/… and serverfault.com/questions/611207/… and help.ubuntu.com/community/DebuggingSystemCrash
– Rinzwind
Jan 21 at 8:31
See askubuntu.com/questions/545504/… and serverfault.com/questions/611207/… and help.ubuntu.com/community/DebuggingSystemCrash
– Rinzwind
Jan 21 at 8:31
It could also be your hardware that shut itself down (not the OS). If cpu gets above a certain temp it can slow down, but if it reaches its max threshold (same with some other pieces of hardware) it just forces the psu to instantly shutdown (to protect itself from destruction). The OS doesn't know about this as hardware is just off. You won't find any logs in your OS if this is the case, but machine logs (if a good device that keeps it) will report the raising temperature & near threshold (but not the breach of threshold as it just turns off).
– guiverc
Jan 21 at 8:39
It could also be your hardware that shut itself down (not the OS). If cpu gets above a certain temp it can slow down, but if it reaches its max threshold (same with some other pieces of hardware) it just forces the psu to instantly shutdown (to protect itself from destruction). The OS doesn't know about this as hardware is just off. You won't find any logs in your OS if this is the case, but machine logs (if a good device that keeps it) will report the raising temperature & near threshold (but not the breach of threshold as it just turns off).
– guiverc
Jan 21 at 8:39
kernel and syslog where both empty. I installed smartctl afterwards but there was nothing either. A few weeks I replaced the SSD from mSATA m1 to a SATA SSD. Never had any issues with the M1 SSD.
– ssssstut
Jan 21 at 20:27
kernel and syslog where both empty. I installed smartctl afterwards but there was nothing either. A few weeks I replaced the SSD from mSATA m1 to a SATA SSD. Never had any issues with the M1 SSD.
– ssssstut
Jan 21 at 20:27
add a comment
|
2 Answers
2
active
oldest
votes
You can use dmesg command from terminal, it may show some useful information of the kernel from device drivers.
answered Jan 21 at 10:49
G.H.G.H.
12 bronze badges
thank you, I couldn't find any suspicious information, however I'm a linux newbie
– ssssstut
Jan 21 at 20:38
add a comment
|
Consider this message a 'kick-starter' for a collaborative effor to resolve these kinds of mystery problems. It is not really an answer -- Yet. (See process).
**notion / seed **
It begins with this idea (I had)...
mkdir ~/trace-system
cd ~/trace-system
tail -f /var/log/syslog | tee syslog.feed.log
background
My Ubuntu 18.10 system has been stable since I updated to 18.04 LTS.
Recently it developed a syndrome where I can boot and work on the screen for a good while -- Today it ran all day long. Only to resume the cycle of freeze/reboot just when I wanted to USE the blessed thing.
But there is no error or message or log entry that I've detected or find even interesting.
I set-up the above tail command in term on the hope that when the system freezes-up, the last thing few things in the file will be pointers or clues to the problem and/or cause.
So far that approach has yielded little information. True it does record the final last words of Ubuntu's syslog before the crash, not that interesting.
I feel that the procedure is on-track, it is time to add to the discussion and see how / if this may work with more appropriate "target" logs or commands -- Such as the dmesg suggestion posted earlier.
Looking forward to your additions/comments.
process
- this post is a "seed" for an idea I had to capture these kinds of problems.
- Others are invited to edit this post with methods that enhance the concept or get similar result.
- If you can only comment on the ideas, that's OK. I will test your comment, if it proves workable or helps I'll update this post myself.
- I can up-vote useful ideas we add to the body of knowledge.
Also, it is OK for you (others) to improve the process. I reserve the right to keep things trim.
answered May 29 at 13:12
willwill
2162 silver badges8 bronze badges
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1111580%2fbest-way-to-find-out-why-ubuntu-18-04-crashed-where-to-find-appropriate-logs%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can use dmesg command from terminal, it may show some useful information of the kernel from device drivers.
answered Jan 21 at 10:49
G.H.G.H.
12 bronze badges
thank you, I couldn't find any suspicious information, however I'm a linux newbie
– ssssstut
Jan 21 at 20:38
add a comment
|
You can use dmesg command from terminal, it may show some useful information of the kernel from device drivers.
answered Jan 21 at 10:49
G.H.G.H.
12 bronze badges
thank you, I couldn't find any suspicious information, however I'm a linux newbie
– ssssstut
Jan 21 at 20:38
add a comment
|
You can use dmesg command from terminal, it may show some useful information of the kernel from device drivers.
answered Jan 21 at 10:49
G.H.G.H.
12 bronze badges
You can use dmesg command from terminal, it may show some useful information of the kernel from device drivers.
answered Jan 21 at 10:49
G.H.G.H.
12 bronze badges
answered Jan 21 at 10:49
G.H.G.H.
12 bronze badges
answered Jan 21 at 10:49
G.H.G.H.
12 bronze badges
answered Jan 21 at 10:49
G.H.G.H.
12 bronze badges
12 bronze badges
thank you, I couldn't find any suspicious information, however I'm a linux newbie
– ssssstut
Jan 21 at 20:38
add a comment
|
thank you, I couldn't find any suspicious information, however I'm a linux newbie
– ssssstut
Jan 21 at 20:38
thank you, I couldn't find any suspicious information, however I'm a linux newbie
– ssssstut
Jan 21 at 20:38
thank you, I couldn't find any suspicious information, however I'm a linux newbie
– ssssstut
Jan 21 at 20:38
add a comment
|
Consider this message a 'kick-starter' for a collaborative effor to resolve these kinds of mystery problems. It is not really an answer -- Yet. (See process).
**notion / seed **
It begins with this idea (I had)...
mkdir ~/trace-system
cd ~/trace-system
tail -f /var/log/syslog | tee syslog.feed.log
background
My Ubuntu 18.10 system has been stable since I updated to 18.04 LTS.
Recently it developed a syndrome where I can boot and work on the screen for a good while -- Today it ran all day long. Only to resume the cycle of freeze/reboot just when I wanted to USE the blessed thing.
But there is no error or message or log entry that I've detected or find even interesting.
I set-up the above tail command in term on the hope that when the system freezes-up, the last thing few things in the file will be pointers or clues to the problem and/or cause.
So far that approach has yielded little information. True it does record the final last words of Ubuntu's syslog before the crash, not that interesting.
I feel that the procedure is on-track, it is time to add to the discussion and see how / if this may work with more appropriate "target" logs or commands -- Such as the dmesg suggestion posted earlier.
Looking forward to your additions/comments.
process
- this post is a "seed" for an idea I had to capture these kinds of problems.
- Others are invited to edit this post with methods that enhance the concept or get similar result.
- If you can only comment on the ideas, that's OK. I will test your comment, if it proves workable or helps I'll update this post myself.
- I can up-vote useful ideas we add to the body of knowledge.
Also, it is OK for you (others) to improve the process. I reserve the right to keep things trim.
answered May 29 at 13:12
willwill
2162 silver badges8 bronze badges
add a comment
|
Consider this message a 'kick-starter' for a collaborative effor to resolve these kinds of mystery problems. It is not really an answer -- Yet. (See process).
**notion / seed **
It begins with this idea (I had)...
mkdir ~/trace-system
cd ~/trace-system
tail -f /var/log/syslog | tee syslog.feed.log
background
My Ubuntu 18.10 system has been stable since I updated to 18.04 LTS.
Recently it developed a syndrome where I can boot and work on the screen for a good while -- Today it ran all day long. Only to resume the cycle of freeze/reboot just when I wanted to USE the blessed thing.
But there is no error or message or log entry that I've detected or find even interesting.
I set-up the above tail command in term on the hope that when the system freezes-up, the last thing few things in the file will be pointers or clues to the problem and/or cause.
So far that approach has yielded little information. True it does record the final last words of Ubuntu's syslog before the crash, not that interesting.
I feel that the procedure is on-track, it is time to add to the discussion and see how / if this may work with more appropriate "target" logs or commands -- Such as the dmesg suggestion posted earlier.
Looking forward to your additions/comments.
process
- this post is a "seed" for an idea I had to capture these kinds of problems.
- Others are invited to edit this post with methods that enhance the concept or get similar result.
- If you can only comment on the ideas, that's OK. I will test your comment, if it proves workable or helps I'll update this post myself.
- I can up-vote useful ideas we add to the body of knowledge.
Also, it is OK for you (others) to improve the process. I reserve the right to keep things trim.
answered May 29 at 13:12
willwill
2162 silver badges8 bronze badges
add a comment
|
Consider this message a 'kick-starter' for a collaborative effor to resolve these kinds of mystery problems. It is not really an answer -- Yet. (See process).
**notion / seed **
It begins with this idea (I had)...
mkdir ~/trace-system
cd ~/trace-system
tail -f /var/log/syslog | tee syslog.feed.log
background
My Ubuntu 18.10 system has been stable since I updated to 18.04 LTS.
Recently it developed a syndrome where I can boot and work on the screen for a good while -- Today it ran all day long. Only to resume the cycle of freeze/reboot just when I wanted to USE the blessed thing.
But there is no error or message or log entry that I've detected or find even interesting.
I set-up the above tail command in term on the hope that when the system freezes-up, the last thing few things in the file will be pointers or clues to the problem and/or cause.
So far that approach has yielded little information. True it does record the final last words of Ubuntu's syslog before the crash, not that interesting.
I feel that the procedure is on-track, it is time to add to the discussion and see how / if this may work with more appropriate "target" logs or commands -- Such as the dmesg suggestion posted earlier.
Looking forward to your additions/comments.
process
- this post is a "seed" for an idea I had to capture these kinds of problems.
- Others are invited to edit this post with methods that enhance the concept or get similar result.
- If you can only comment on the ideas, that's OK. I will test your comment, if it proves workable or helps I'll update this post myself.
- I can up-vote useful ideas we add to the body of knowledge.
Also, it is OK for you (others) to improve the process. I reserve the right to keep things trim.
answered May 29 at 13:12
willwill
2162 silver badges8 bronze badges
Consider this message a 'kick-starter' for a collaborative effor to resolve these kinds of mystery problems. It is not really an answer -- Yet. (See process).
**notion / seed **
It begins with this idea (I had)...
mkdir ~/trace-system
cd ~/trace-system
tail -f /var/log/syslog | tee syslog.feed.log
background
My Ubuntu 18.10 system has been stable since I updated to 18.04 LTS.
Recently it developed a syndrome where I can boot and work on the screen for a good while -- Today it ran all day long. Only to resume the cycle of freeze/reboot just when I wanted to USE the blessed thing.
But there is no error or message or log entry that I've detected or find even interesting.
I set-up the above tail command in term on the hope that when the system freezes-up, the last thing few things in the file will be pointers or clues to the problem and/or cause.
So far that approach has yielded little information. True it does record the final last words of Ubuntu's syslog before the crash, not that interesting.
I feel that the procedure is on-track, it is time to add to the discussion and see how / if this may work with more appropriate "target" logs or commands -- Such as the dmesg suggestion posted earlier.
Looking forward to your additions/comments.
process
- this post is a "seed" for an idea I had to capture these kinds of problems.
- Others are invited to edit this post with methods that enhance the concept or get similar result.
- If you can only comment on the ideas, that's OK. I will test your comment, if it proves workable or helps I'll update this post myself.
- I can up-vote useful ideas we add to the body of knowledge.
Also, it is OK for you (others) to improve the process. I reserve the right to keep things trim.
answered May 29 at 13:12
willwill
2162 silver badges8 bronze badges
answered May 29 at 13:12
willwill
2162 silver badges8 bronze badges
answered May 29 at 13:12
willwill
2162 silver badges8 bronze badges
answered May 29 at 13:12
willwill
2162 silver badges8 bronze badges
2162 silver badges8 bronze badges
add a comment
|
add a comment
|
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1111580%2fbest-way-to-find-out-why-ubuntu-18-04-crashed-where-to-find-appropriate-logs%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
See askubuntu.com/questions/545504/… and serverfault.com/questions/611207/… and help.ubuntu.com/community/DebuggingSystemCrash
– Rinzwind
Jan 21 at 8:31
It could also be your hardware that shut itself down (not the OS). If cpu gets above a certain temp it can slow down, but if it reaches its max threshold (same with some other pieces of hardware) it just forces the psu to instantly shutdown (to protect itself from destruction). The OS doesn't know about this as hardware is just off. You won't find any logs in your OS if this is the case, but machine logs (if a good device that keeps it) will report the raising temperature & near threshold (but not the breach of threshold as it just turns off).
– guiverc
Jan 21 at 8:39
kernel and syslog where both empty. I installed smartctl afterwards but there was nothing either. A few weeks I replaced the SSD from mSATA m1 to a SATA SSD. Never had any issues with the M1 SSD.
– ssssstut
Jan 21 at 20:27