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.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
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
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
lol!
Thanks, you are the reason I look at comments.
When I am reading the logs, I usually check who was the last seaman in charge when the ship crashed through the pier.
The picture made me lol :D
If you know the times of the crash, check whatever is logged right before and after
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.
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.
I'm -to be honest- quite the noob. What is obvious?
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.
Alright. That is what i see on my screen.
You know what the various logs are, that's good to help out. So you have any crash dumps enabled? I think on Debian (what promox is based on), you have to install kdump tools and reboot. Then it should cause a the kernel to log a dump file you can read with crash if it's a kernel crash and not something else.
Ok will do this. It chrashed again. And I need this thing up and running and keep running.
I do this all the time when I look at logs, I don't even really know why
Pill bugs, moss, snakes, etc.
A good place to start because it's a likely culprit is anything mentioning "OOM" (which refers to Out Of Memory)
