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.
(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!
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?
ive got a one of my personal sites - (a fairly mysql heavy chat community that works on mobile phones aswell) and its running on a cheap dedicated server
the specs of the server at the moment are -
celeron 2.0GHz 512mb ram 120gb ide disk 1500gb bandwidth linux centos 4 no control panel
now i never come close to using my bandwidth so thats fine. but ive noticed when i had around 30 members online last night the server load spiked at about 3.5 so im wondering if anyone can suggest what would be the best thing to upgrade to reduce load.
im currently running apache serving the dynamic files and lighttpd hosting images on a different port. using php 4.4.7 with eaccellerator. mod_gzip is enabled in apache due to a need to reduce the size of pages as much as possible.
BURSTNET Network Maintenance Advisory - Saturday, September 20th, 2008 - 2AM-4AM EST WINDOW
BurstNET™ Network Engineering will be performing maintenance in our Scranton facility during the hours of 2AM and 4AM EST on Saturday, September 20th, 2008. At this time, BurstNET™ Network Engineering will be performing a significant upgrade/replacement of our existing network infrastructure. This upgrade will involve removing/replacing our older/out-dated core Cisco™ GSR & Extreme Summit™ routing/switching equipment, with newer state-of-the-art Cisco™ 6500-series routing/switching equipment, and implementing a new network design---allowing for easier upgrade, higher fault-tolerance, additional capacity, and extra redundancy.
This maintenance will be service affecting, however, we expect the overall network downtime to be 30 minutes or less, during the 2-hour maintenance window, with the majority of that occurring at the start of the work...as equipment and cabling is changed. There will also be momentary periods of higher than normal latency while circuits are re-routed, BGP updated/reloaded, and cabling switched, throughout the 2-hour maintenance window. Proper planning, configuration, and testing has been completed in advance of this maintenance period, in order to minimize as much as possible the overall time that will be service affecting.
This maintenance is necessary in order for further growth of the BurstNET™ network, as well as to implement additional redundancy into the network. This should also help resolve any latency and packet loss issues our clientele may have been experiencing in recent weeks. BurstNET™ has recently hired new Network Engineering staff, and this is the first step in several upgrades/modifications they will be making to the BurstNET™ network over the next 60-90 days, to expand reliability, increase capacity, install further redundancy, and increase performance network-wide.
We thank you for your patience and understanding with this necessary maintenance, as well as for your continued business!
Sounds like a pretty major upgrade (they've been upgrading a lot recently). Here's to more uptime and redundancy at BurstNET!
Lastly, a quick point to the army of Burst-haters out there: go check outages, BurstNET has had two great months for us (99.9%+ uptime). Stop hating .
On used equipment (for example, 6509s), is there any possibility of getting IOS upgrades from Cisco? Is there any sort of re-certification process? My only concern with used equipment is that often times the firmware is years old.
What are the benefits of moving to faster uplink speeds? I'm considering upgrading from 10 to 100 Mbps. Does it only mean being able to send information faster or are response times improved as well?
it looks like FDC is taking more pain than usual in terms of network upgrade, i see the network seems unstable till 5am and even now the sessions are getting lost, once in a while like once a hr, anyway this is not the reason i am writing this, but when did comcast become transit provider, i did a trace to UK for example and i see trace going through comcast and then hopping onto tiscali/level3, it looks to me like, comcast could be trying to even out (1:1) it;s carriers so that they get all inbound for free sort of and it;s upstream selling as a transit make money there. sort of, just a surprise to me at this point
2 <1 ms <1 ms <1 ms 66.90.127.141 [66.90.127.141] 3 1 ms 1 ms 1 ms be-10-604-cr01.chicago.il.ibone.comcast.net [68. 6.89.49] 4 37 ms 40 ms 36 ms pos-1-14-0-0-cr01.newyork.ny.ibone.comcast.net [ 8.86.85.105] 5 42 ms 42 ms 42 ms pos-1-15-0-0-cr01.mclean.va.ibone.comcast.net [6 .86.85.89] 6 30 ms 30 ms 31 ms xe-3-1-0.was11.ip.tiscali.net [213.200.84.117] 7 122 ms 115 ms 113 ms xe-2-1-0.par70.ip.tiscali.net [89.149.186.165] 8 119 ms 119 ms 119 ms kpn-eurorings-gw.ip.tiscali.net [213.200.85.238]
9 120 ms 120 ms 123 ms asd2-rou-1021.NL.eurorings.net [134.222.231.177]
10 119 ms 119 ms 167 ms obl-rou-1021.NL.eurorings.net [134.222.231.130]
I've decided to move from my current provider (which I have praised many times on this forum before) because I'm just not getting the service I expect.
I'm specifically interested in a provider who is able to upgrade a VPS quickly, efficiently and on time, with no excuses and without "forgetting" things.
If you have experienced more than one upgrade with a provider which has been handled exceptionally well, please point me in the right direction.
I am a host reseller and the parent company is upgrading their servers to PHP5. This may break some of my clients' sites (OSCommerce, Zen). Should we fix those sites for free or should my clients pay for the upgrade?
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...
Simple... new Plesk 12 includes this fancy feature to tell me which Wordpress plugins and themes need updating (because I obviously can't do this myself). But maybe I don't want to update some plugins (because they've been customized and changed)... how do I....
STOP Plesk 12 from sending me Wordpress update notification emails EVERY DAY!???? The auto-update is off... and EVERY day is sends me (and all of those clients) an ugly email about their Wordpress installations. How do I turn this OFF?