*BOOT FULL ALARM

Boot full alarms happen when we have several kernels installed. In case of boot full alarms:

1. Check how many kernels are installed:

 [root@dashb-ai-581 ~]# rpm -qa |grep kernel-2
kernel-2.6.32-573.8.1.el6.x86_64
kernel-2.6.32-573.7.1.el6.x86_64
2. Check the running kernel
[root@dashb-ai-581 ~]# uname -a
Linux dashb-ai-581.cern.ch 2.6.32-573.7.1.el6.x86_64 #1 SMP Wed Sep 23 10:12:03 CEST 2015 x86_64 x86_64 x86_64 GNU/Linux
2.a If the running is not the latest , reboot the machine
[root@dashb-ai-581 ~]# reboot
Broadcast message from root@dashb-ai-581.cern.ch
    (/dev/pts/3) at 9:08 ...

The system is going down for reboot NOW!

3. Clean old kernels

[root@dashb-ai-581 ~]#  package-cleanup --oldkernels --count=1  -y
Loaded plugins: kernel-module, priorities, rpm-warm-cache, versionlock
--> Running transaction check
---> Package kernel.x86_64 0:2.6.32-573.7.1.el6 will be erased
---> Package kernel-debug.x86_64 0:2.6.32-573.7.1.el6 will be erased

4. Close the GNI ticket

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2015-11-12 - PabloSaiz
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    ArdaGrid All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback