You are not logged in.
Hi,
I have an arch server running where I don't have physical access to the server to reboot it, should it ever go down (hang). What can I do in terms of making sure the server kernel never throws in something like kernel panic. I don't mind it restarting itself, and resuming operations, but I do mind it getting hung
I'm running out of the box archlinxux
Linux archie 2.6.28-ARCH #1 SMP PREEMPT Fri Feb 13 10:23:36 UTC 2009 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
top - 20:32:54 up 45 days, 6:41, 1 user, load average: 0.00, 0.00, 0.00
Tasks: 54 total, 1 running, 53 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0%us, 0.0%sy, 0.0%ni, 99.6%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 506636k total, 500404k used, 6232k free, 165768k buffers
Swap: 1028152k total, 1420k used, 1026732k free, 311120k cached
Thanks for your suggestions
Last edited by T0MAS (2009-06-29 19:36:36)
Offline
Well your concern is OK, but you should expect *a lot* of other stuff to break before your kernel ever does. Most often people lock them selves out with a firewall rule, a network interface can go down, routes get messed up, hardware failure etc. etc.
We can say "you should be careful with kernel, modules and initram changes and updates". But you need to watch out what you are doing in general. Administration is not editing xorg.conf and watching sh*t compile. You need to plan things, be prepared for problems, have backup plans and know what you are doing at all times (measure twice, cut once, always).
If the worst happens good service providers can give you a virtual console connected directly to the server so you can be there on boot.
You need to install an RTFM interface.
Offline