Fedora Core 6 for Dedicated and Virtual Dedicated Hosting
GoDaddy now offers the Linux Red Hat Fedora Core 6 operating
system for dedicated and virtual dedicated hosting accounts. The Fedora Core 6
operating system will replace the Fedora Core 4 operating system offering for new
purchases/upgrades.
Customers on Red Hat 9, Red Hat Fedora Core 2 or Red Hat Fedora Core 4 are unaffected at this time, but may upgrade to Red Hat Fedora Core 6, if they choose. We encourage customers to upgrade. There are newer versions of popular packages, such as MySQL 5, a number of performance enhancements, but most importantly, packages are maintained by Red Hat for critical security patches.
Many are already experiencing the benefits of Fedora Core 6. We have full add-on control panel support including Plesk 8.1, cPanel 11 and GoDaddy's own Simple Control Panel. You may find GoDaddy at the forefront with Fedora Core, most competitors are still running Fedora Core 5. Why don't you give it a try? Buy dedicated or virtual dedicated hosting with Fedora Core 6 today.
Dave.
Customers on Red Hat 9, Red Hat Fedora Core 2 or Red Hat Fedora Core 4 are unaffected at this time, but may upgrade to Red Hat Fedora Core 6, if they choose. We encourage customers to upgrade. There are newer versions of popular packages, such as MySQL 5, a number of performance enhancements, but most importantly, packages are maintained by Red Hat for critical security patches.
Many are already experiencing the benefits of Fedora Core 6. We have full add-on control panel support including Plesk 8.1, cPanel 11 and GoDaddy's own Simple Control Panel. You may find GoDaddy at the forefront with Fedora Core, most competitors are still running Fedora Core 5. Why don't you give it a try? Buy dedicated or virtual dedicated hosting with Fedora Core 6 today.
Dave.
1. What kernel did they use (I know kernels beyond 2.6.9 in the regular distribution have broken modules using skge)
2. What happened to your post about IP protection, it seems to have been lost in a void.
3. Could you please ask those people to add serial access to the server, so if we loose our connectivity due to our dumb mistakes we can fix them ourselves instead of overloading the IT's at the datacenters.
4. Can we upgrade from Cent OS 4.4?
Reply to this
We're shipping FC6 with a yum update, so you get the latest kernel from Fedora. Currently, 2.6.20-1.2952.fc6. skge is a network card driver, we've had problems with it in Fedora Core 4. So much so, that we added a "exclude=kernel*" to the yum configuration, because we had to install custom drivers. We actually used a modified sk98lin. This problem is only on some of our server models that have Marvell network cards, we worked around it. With Fedora Core 6, the problem went away. FC6 uses skge for Marvell network cards, but the problems are gone now.
The IP article had a short life of only an hour or so. It was pulled offline, because we decided we didn't want to draw attention to IP theft.
Console access to your dedicated server is a good suggestion. I'd like that too. I'm not sure what the scope would be yet, but I'll look into it.
The reason you're stuck on 4.4 is that we pointed your yum config to our mirrorlist, which is set to 4.4 currently. We'll be moving to 4.5 soon. To upgrade from CentOS 4.4 to 4.5 (or latest), change your /etc/yum.repos.d/CentOS-Base.repo file edit the mirrorlist lines to point back to the centos provided mirrors. For reference here they are:
[base]
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
[update]
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates
[addons]
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=addons
[extras]
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras
[centosplus]
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus
[contrib]
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=contrib
Then, run "yum -y update" and you'll be upgraded to the latest, currently 4.5.
Dave.
Reply to this
Yeah we were making our own skge module, but it seems that since sk98lin was already working, it seemed pointless. Thanks for those updates on the question quickly and promptly.
I had a wierd experience with ip theft, stealing an ip from myself, anyways good work with that anyhow.
That sk98lin driver you were talking about does it ship with the mainstream kernel's? Or is it something I need to get from Godaddy directly?
Reply to this
For FC4, and CentOS4, and RHEL4, we install a package called sk98lin-kmdl, found at atrpms.net, a third party repo.
Dave
Reply to this
thank you for that, in the near future is GoDaddy going to move away from the Marvell chipset?
Reply to this
No immediate plan to move away from Marvell.
Dave.
Reply to this
Okay, I did this, with my CentOS 4.4 system, but I seem to have wiped out my network connectivity because I upgraded the kernel.
What I am wondering, where is this technical information documented? A detailed explanation of how the server is setup when we first log in. I can not seem to find good documentation on the website. If I had known that there was a custom network driver installed I would have made sure to have upgraded that or been more careful on upgrading my kernel.
More and better documentation would be greatly appreciated.
John
Reply to this
John-
Let's get your connectivity restored!
First of all, you can not upgrade your kernel. Instead you will have to roll back to your old kernel.
There are two solutions on how to fix this.
Either you can submit a support ticket through your Manager and explain that you need a technician to access the server and have the grub config file point back to the original kernel or you can re-provision your server with the understanding that this will cause downtime and loss of data.
Reply to this
I don't know how I missed this entry.
I have a FD 4 VS currently running Plesk 8.2, if I upgrade to FD 6 will I need to do anything to my Plesk installation? This is my first time playing with Plesk so I don't know all its quirks yet. Or every thing will work fine after the upgrade?
Reply to this
As you may already know, in order to upgrade to Fedora Core 6 you will need to re-provision your server, keeping in mind that this will cause downtime and loss of data. Once the upgrade is complete you will automatically get Plesk version 8.2.
Reply to this
I have a problems : Fedora core 6 and simple control panel.
The problem found is when we try to create or modify an email account. Appears an error message in the control panel and we are not able to modify/create the email account.
This I have noticed since we have migrated from Fedora Core 4 to Core 6.
-----------------
This is the error when try to create an email account: (from: /var/log/turbopanel/turbopanel.log) :
2007-10-04 21:43:19,570 ERROR LinuxEmailSubsystem: createAccount(): Caught exception
java.io.IOException: Timeout
at com.godaddy.turbopanel.framework.util.ProcessUtils.exec(ProcessUtils.java:85)
at com.godaddy.turbopanel.framework.util.ProcessUtils.exec(ProcessUtils.java:28)
at com.godaddy.turbopanel.framework.systems.email.LinuxEmailSubsystem.mboxAddUser(LinuxEmailSubsystem.java:2239)
at com.godaddy.turbopanel.framework.systems.email.LinuxEmailSubsystem.createAccount(LinuxEmailSubsystem.java:1095)
at com.godaddy.turbopanel.web.actions.domain.ActionDomainAdd$ConfirmDoneHandler.handle(ActionDomainAdd.java:499)
at com.godaddy.turbopanel.web.actions.domain.ActionDomainAdd.process(ActionDomainAdd.java:250)
at com.godaddy.turbopanel.web.actions.AbstractSpringAction.execute(AbstractSpringAction.java:118)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.godaddy.turbopanel.web.filters.AuthorizedResourceFilter.doFilter(AuthorizedResourceFilter.java:38)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.godaddy.turbopanel.web.filters.RequestPopulationFilter.doFilter(RequestPopulationFilter.java:117)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContex
Reply to this
We are aware of this issue and have a planned release, via "yum update", Wednesday of next week.
Reply to this
Thanks, the update works OK.
Reply to this