(The box, 2 years now, never had issues before all you will read...)
I do have a box at the IP xxx.xxx.xxx.xxx, which on 15th Nov. was: AMD 4200+
with 300 GB hdd for OS, and CentOS 4.5 on it...
Because the system was facing few load problems of wrong installed applications, we decided to do a fresh OS reload to the latest OS version and
cPanel.
on 16th Nov, the box was up and running with CentOS 5, and cPanel 11.
the kernel is: 2.6.18-8.1.15.el5
After few hrs the box was done and IO restored all backups in it anbd all worked fine, I realized that I couldnt access cPanel, page was blank for
everything.
Also, most pages (except simple html) where showing internal error 500.
I did a reboot. probelm was fixed.
After few hrs, problem came up again...
I left ssh logged in to see whats wrong.
I found out that every few hrs, that issue was happening:
Message from syslogd@server at Sun Nov 16 11:47:21 2007 ...
server kernel: journal commit I/O error
Then, we had techs to check HDD for errors. they did fsck, and said disk has to be replaced (at this point, without wanting to offend anyone, I have to state that 90% of techs in datacenters, or at least at mine --won't name them, 99% you guess which DC it is...-- are just low paid students that don't know SIMPLE things...) so we told them to replace the HDD and do OS reload in new drive...
So, on 17th Nov. we had online a new HDD, 400 GB with CentOS 5 loaded in it, and cPanel 11...
After few hrs and all working and backups recovered, the issue came up again!
This time, with exactly same error, techs told us it may be RAM, so they replaced the RAM and we waited...
In 2,5 hrs, bang, it happens again, same error.
They say, it might be the sata cable...
we replace it...
AGAIN ERROR.
we ask them to loook at it seriously, and after lot pressure, to avoid case that mo/bo or controller is wrong, they do upgrade us in a BRAND NEW colocated box, which was this time: Intel Core 2 DUO, 6300, with brand new 500 GB HDD and new RAM.
We recover in the new box the backups.
Box is online today at 18th Nov...
and the issue comes up again!
Message from syslogd@server at Sun Nov 18 11:47:21 2007 ...
server kernel: journal commit I/O error
I ask them what the **** is going on now and why after having all hardware replaced with new, and all OS reinstalled clean on new drives and new devices, 3 times, why we have again the same error...
And their response: power cable was loose, we replaced power cable...
Guys, sorry, this is really DUMP... loose cable cannot give that error...
and the error... continues!
Also, at this point, I have to let you know, that when this error comes up, (Message from syslogd@server at Sun Nov 18 11:47:21 2007 ...
server kernel: journal commit I/O error) the filesystem becomes READ-ONLY and
nothing gets affected, if we do a cold reboot by reset button, it comes up
again and all work PERFECT, until the issue comes back again.....
I am desperate with that, let me know what I have to do!
there is a bug in the version of libxml2 (2.7.2)that i'm using that removes angle brackets from html in uploaded wordpress posts. to get round this i need to downgrade libxml2.
i'm running apache 2.2.10/php 5.2.6, i'm not entirely sure how to tell which version of libxml2 i'm running as "libxml -v" doesn't work, but in my custombuild folder there's a libxml2-2.7.2 folder. but if i try and "yum remove libxml2" it mentions 2.6.26-2.1.2.6. i tried "yum remove libxml2" but it lists loads of dependencies including bind.
so basically i need to downgrade libxml2 to version 2.6.32 (libxml2-2.6.32) which apparently doesn't have this bug. has anyone got any idea how i can do this without breaking something?
I was wondering how I would go about ensuring my kernel is up to date on my vps. I am running centos and I have cpanel, so I am not sure if there is anything special that has to be done or avoided when running cpanel.
Last year I ordered a new server with Centos 4.3 and it had the kernel kernel 2.6.9-34.0.2ELsmp installed. It runned fine and I didn't update any packages since then.
Today I started getting a problem where both mysqld and kswapd0 uses very high amounts of CPU, spiking up to 100% and my memory usage is at 99% all the time. The problem seems exactly the same as the one mentioned in this thread.
In that thread the exact same kernel is said to be insecure and to cause this problem. I also came across a centOS bug that reports this problem with high cpu, mem usage and mysql & kswapd0 consuming all resources.
In the linked thread the person solved the problem by upgrading to kernel 2.6.9-42 using rpms but others recommended a newer kernel or a custom compiled kernel for CentOS.
Apparently when they used yum it said 34.0.2 was the latest kernel.
What should I do to upgrade the kernel, which version should i upgrade to, and where do I get it from? I won't be able to compile a custom kernel and I've only installed basic rpm packages before.
i have a 32bit centos running with 8 gigs, but only 7 is registering when i contacted support they told me
Your server does in fact have 8GB of physical memory however the reason it is not being recognized is due to the fact that you are using a 32 bit operating system. By default, the 8GB would be recognized if it were a 64 bit OS however on a 32 bit operating system, you must install and boot into the PAE kernel (physical address extension) for the 8GB to be recognized and utilized. The PAE kernel can be installed through yum when connected to your server as root over SSH. Once you have installed the kernel, you will need to reboot the server for these changes to take effect
i tried
yum pae install
yum pae kernel install
both didnt work can anyone give me a quick step by step guide on how to go about this.
Just to make things clear, i am not new at setting up VPS nodes, i have set up all of my servers with the HyperVM/OpenVZ setup and they work perfectly, but im having a problem with a new server.
Just received my new server, installed HyperVM-Slave, rebooted but the OpenVZ kernel was not installed for some reason, so i manually installed the OpenVZ Kernel using the RPM as yum seemed to install the wrong kernel.
I then installed the kernel using RPM and got this error at the end of installation:
grubby: unable to open /dev/hda: No such file or directory grubby: unable to open /boot/boot.b: No such file or directory grubby fatal error: unable to find a suitable template
I have never encountered this error with any of my other servers before...
Also after installation everything seems to be correct. /etc/grub.conf has the new OpenVZ kernel displayed, and default is set to 0, so upon startup it should be booting the correct kernel, but the thing is, when i reboot the machine the default kernel is loaded even though the grub.conf is configured to load the OpenVZ Kernel.
Im thinking that this may be due to the error i got when installing the kernel.
I'm not sure if anyone else has come across this but I'm sure you are all aware that CentOS 5.3 default kernel comes with realtek support.
But the default realtek drivers have a bug in them when it slows down upload and downloads drastically and shows ping times above 2000+ ms in the same datacenter.
A fix for this is simply upgrading the kernel to the latest version available (2.6.29) with realtek driver support.
I tried to 'google' they to find the solution, but now i still not find out ... I'll try to reload OS. After reload OS, if i dont have floppy disk, how can i update kernel with no error?
we have one box in hivelocity.net that has been down so many times this month that we were forced to remove links to siteuptime where we were once so proud of having a 99.7% uptime for 3 years in theplanet.
syslog shows that just before crashing, these entries were made:
kernel: kernel BUG at mm/rmap.c:479 kernel: invalid operand:0000 [#1]
dmesg also shows this:
... Brought up 2 CPUs zapping low mappings. checking if image is initramfs... it is Freeing initrd memory: 482k freed NET: Registered protocol family 16 PCI: PCI BIOS revision 2.10 entry at 0xf9f20, last bus=1 PCI: Using configuration type 1 mtrr: v2.0 (20020519) mtrr: your CPUs had inconsistent fixed MTRR settings mtrr: probably your BIOS does not setup all CPUs. mtrr: corrected configuration. ...
i've googled these messages and they point to ram problems.
hivelocity.net claims to have done diagnostics on the box and that there were no problems reported.
they said this is a result of a sys configuration problem made by us.
I'm currently using kernel "2.4.21-27.0.2.EL" on my "Redhat Enterprise Linux - OS ES 3.0" machine, which is running the latest version of cPanel/WHM, and I'd like to update the kernel to the latest stable version that works properly with cPanel.
I'm completely unsure what version to update to, as I've heard the latest kernel doesn't play nice with cPanel...
What is the best antivirus for centos. Control panel used is cPanel by default ClamAV is present, is it good to install another antivirus apart from ClamAV?
Has anyone noticed recently on a fresh cPanel install that named doesn't start by itself on a reboot? I have had to chkconfig named on on every cPanel install I've done on a CentOS box in the last 2 months.
