this post was submitted on 09 Sep 2023
95 points (93.6% liked)

Linux

48375 readers
1554 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

Hi everyone

My proxmox server is crashing daily. And I've been checking the logs. But the thing is. What do I look for? Syslog, kern and daemonlogs. I would like to fix this problem. Need advice ! Thanks

all 15 comments
sorted by: hot top controversial new old
[–] [email protected] 47 points 1 year ago (2 children)

When I look a the logs, I'm mostly looking for as least knots as possible, but also to make sure they are cedar, pine, or oak depending on the project.

Oh shit, this isn't the carpentry community. NVM then

[–] couscouscivil 7 points 1 year ago

lol!

Thanks, you are the reason I look at comments.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

When I am reading the logs, I usually check who was the last seaman in charge when the ship crashed through the pier.

[–] [email protected] 38 points 1 year ago

The picture made me lol :D

[–] [email protected] 33 points 1 year ago

If you know the times of the crash, check whatever is logged right before and after

[–] couscouscivil 11 points 1 year ago* (last edited 1 year ago)

grep -Ri 'error/|warning' /var/log/

Then you can further pipe 'grep' or 'grep -v' based on what you see or for a specific time.

[–] [email protected] 10 points 1 year ago (1 children)

On Linux systems running systems I usually use the journalctl tool to look at messages. Ex.

journalctl --list-boots journalctl --since="2012-10-30 18:17:16"

Looking for anything obvious.

[–] [email protected] 3 points 1 year ago (1 children)

I'm -to be honest- quite the noob. What is obvious?

[–] [email protected] 3 points 1 year ago (1 children)

Anything looking like this: http://i.stack.imgur.com/RMcUY.jpg

Anything saying "error" or "fatal" in the kernel log.

It's quite likely that you will not find anything because the machine reboots before it can write to disk. In that case, I'd start with memtest86.

Protip: view the logs in vim, it highlights errors in red.

[–] [email protected] 1 points 1 year ago

Alright. That is what i see on my screen.

[–] [email protected] 6 points 1 year ago

I do this all the time when I look at logs, I don't even really know why

[–] [email protected] 3 points 1 year ago

Pill bugs, moss, snakes, etc.

[–] [email protected] 2 points 1 year ago

A good place to start because it's a likely culprit is anything mentioning "OOM" (which refers to Out Of Memory)