• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

CENTOS 5.4, there is Karnel panic

J Cole

Basic Pleskian
i have a server that will not boot, CENTOS 5.4, there is Karnel panic, unable to load SELint policy.

The problem was after upgrade Plesk to 9.5 the email would not work and I reboot. It will not boot

How do i install a fix without boot up the michine.
I need to instal kernel-2.6.18-194.el5.i686.rpm

Am not a pro.


J Cole
 
Try to boot with any Linux LiveCD, mount your disk and edit /etc/sysconfig/selinux with

SELINUX=disabled

After that try to boot with your kernel.
 
Hello, I got it boot.
in the boot setting i add enforcing=0 and after boot i add enforcing=0 to /etc/grub.conf

J Cole
 
Here is a small script for this.

#!/bin/bash

# This file will load at every start (add to /etc/rc.local)
# Will verify if the kernel is different with the older started kernel and send a mail to you.
# in /boot/grub/grub.conf you need to put panic=5

# Checking whether Root Runs the Application
if [ "$(id -u)" != "0" ]; then
echo "This script must be run as root !" 1>&2
exit 1
fi
MAIL='YOURMEMAIL-HERE' // edit this line

RUNKERNEL=`uname -a |awk '{print $3}'`
FILEKERNEL='/etc/krnversion'


# If Kernel Version File does not exist, create it from the current running kernel
if [ ! -f $FILEKERNEL ]; then
echo $RUNKERNEL > $FILEKERNEL
else
GETFILEKERNEL=`cat $FILEKERNEL`
# if the file exists, compare the running kernel with the one on file and if they differ, update the kernel record file with the current kernel & notify the administration
if [ "$RUNKERNEL" != "$GETFILEKERNEL" ]; then
echo $RUNKERNEL > $FILEKERNEL
echo "!!! Warning !!!

Difference found in Kernel Versions between the Running Kernel Version and the Kernel Version File !
This probably happened because of a Kernel Upgrade or the loading of an Older Kernel to compensate for a newer Kernel panic.
Please check the versions below, make a determination and act accordingly:

Running Kernel Version is $RUNKERNEL while the Kernel Version on File is $GETFILEKERNEL

* However, the Kernel Version File was updated to match the Running Kernel Version *
#" > ~anquietas/Desktop/KERNEL_SCRIPT_LOG
| mail -s "Kernel Versios Difference Detected !" MAIL
fi
fi
 
Back
Top