CentOS 5 :: Prevent Automatic Upgrade From 5.2 To 5.3
Jul 2, 2009
I installed CentOS 5.2 because I want to install the latest VMWare Server (2.0.1).The release notes of vmware server say: "Support for CentOS 5.2".But after installing CentOS 5.2 and updating the packages marked for update,the Version of the system is 5.3. I know from Debian that if you do not explicitly want to do a system version upgrade,only bug fixes and security fixes are installed. That seems to be different with CentOS/RHEL?
Is there any way (or what ist the right way) to prevent automatic upgrade from one release to another? I don't want VMWare Server to stop working because of some upgrade from 5.x to 5.y.
The server runs# uname -r2.6.18-128.4.1.el5However, today I executed yum update kernel*due to security advisory. I was just about to reboot the system when I realized that it runs VMWare Server Instance that will most likely fail to restart after kernel upgrade (I had a hard time fixing it after previous kernel update). Now I want to keep 2.6.18-128.4.1.el5 after reboot.I see that new kernel is scheduled for booting:
when I am doing a "yum update" I receive now a long list (~94MB) because of the latest CentOS 5.4 release.I am running CentOS 5.3 on a virtual machine (virtuozzo) and had already problems to install 5.3 before. To not lose the installation I do not want to update to 5.4 but of course I want to get all updates for 5.3.How can I configure my CentOS 5.3 to update the server only with 5.3 patches/releases and how to prevent it to update to 5.4?
I have installed CentOS 5.5 successfully and I have VNC working. This server will be a headless box that will reside in a server rack. I intend to perform any necessary maintenance on the machine remotely though my desktop computer. My problem is that when CentOS is on the login screen, I cannot connect with VNC. Once I have logged into a user account, then I can connect.
I would like the server to automatically login to one of my users each time it boots so that the VNC connection will be opened. Currently I have two users, root and Zachary. I would like the server to automatically login to the user Zachary.
In the CentOS Gnome GUI, when I go into System > Administration > Login Screen, and then click on the Security tab there is an option to "Enable Automatic Login." If you check this box a select form field becomes active; however, there are no user accounts showing in that select field. I tried typing in the user name that I wanted to automatically login, but after closing the screen it clears that username. What am I missing?
I've just built a fresh Centos 5.4 install on a 533 MHz P3. This machine is going to be used as a thick client on a LAN. I'm trying to implement automatic logons to the KDE desktop but the automatic logon implementation isn't working as expected. I'm hoping that someone can tell me what I've done wrong. Here's what I've done so far:
1. Created a non-root user account named "bob". "bob" has generic low-level privileges on the machine.
2. I've tried to enable automatic logons using the following GUI menu selections:
Control Center > System Administration > Login Manager > Administrator Mode > Convenience Tab
i am not familialized with Linux i installed recently a TACACS+ server under CentOS 5.5 and it is working well but my boss asked me to make a weekly backup of the tacacs.log file to check who was connected at any time the problem is that i don't know how tp make this backup and how to make it automatic and also he asked me to change the default port of tacacs from 49 to another port does someone knows how to make it?
How can I prevent users from changing their own password? I was surprisingly unsuccessfull in finding a solution for this on google. Lots of stuff about hardening ssh access or dealing with password aging using "chage" but nowhere could I find an answer for my question.
After replacing all of the memory, the error remained, so we tried updating to the latest kernel. (Currently having to use centos-plus because we are using XFS)
After the kernel update the error disappeared fro 5 days (previously UNHEARD of - would often repeat several times a day), it appeared again and hasn't appeared since.
It does not seem like any real damage is done here - and I would like to suppress this error somehow. Optimally I would like it to only be forwarded to the log files - and NOT be displayed on the console.
Could someone point me to an easy way to set that up?
I am trying to prevent the dm_mod and friends from loading during install.I am installing by PXE boot with NFS and kickstart files over http. This works fine for other machines.Ok, I have a Dell PowerEdge 2900 III with 8gig ram, PERC 6/i raid controller.The raid has 8 1TB drives in it, so the total size of the device is >2TB.There is also an SATA drive, which is NOT on the raid controller.
The problem is, I want to install CentOS on the SATA drive. The SATA drive comes up as a device-mapper drive, with a big crazy device name.This is ok, but the problem is, when the system goes to boot, it just says 'missing operating system'.I can't boot from the raid because it is large enough to require a GPT partition, and CentOS says it can't boot from a GPT partition.The SATA drive would work FINE if I could just prevent the damn device mapper from loading, so that I could install on the SATA drive in ordinary SATA mode.
I have tried re-squashing the stage2.img with /etc/modprobe.conf with alias dm_mod off and such, no luck.I also tried adding an /etc/modprobe.d/blacklist file, that did not work either.I also tried putting blacklist= dm_mod in the kickstart file, but that seems to be a fedora-only option and it kills my install. any ideas on preventing the dm_mod et. al. from loading at install time??
I run a few dozen dedicated web servers all running CentOS 5.5. A long time ago when one server was apparently compromised, I was urgently advised to sign in to the server and run "yum update" at least once a week to ensure that everything which I had installed using "yum", would get updated with any recently available updates, including security fixes, and that one reason I might have been hacked before was because I hadn't been doing that.
So, I'm still not sure if that would have prevented the original break-in, or how much this has reduced my chances of being hacked, but I've been faithfully signing in to each server every week for the past few months and running "yum udpate". Most times, this results in a lot of patches being downloaded and applied, so it's clear the machines are not doing it automatically. I figure it's about time to learn how to make the machines do this on their own. Is there a standard way to make "yum update" run automatically, every day, or every week? Yes, I'm sure there are many ways to do it, but is there a single way used by the majority of webmasters of CentOS sites who have automatic updates set up? Googling a bit for "make yum updates automatic" turned up some threads like:
in which people describe writing their own custom scripts to do yum update automatically. This seems odd. It seems like the kind of thing that there would be a standard way to turn on. Also, is there a reason that virtually every newly provisioned dedicated server does not have "yum update" set up to recur automatically? If it's true that people break into websites using exploits that have been found in older versions of webservers and other software, and that sometimes these breakins would have been prevented by the newest patches, wouldn't it reduce the number of websites being compromised if the OS had yum updates turned on automatically by default?
I'm trying to make my system automatically shutdown once the battery level is low, but still without success. I've tried kpowersave, gnome-power-manager, kpower, klaptop but none of these worked for me. Well, I can't imagine I would be that stupid, but simply it doesn't work. In all cases mentioned above (kpower, klaptop, gnome-power-manager) I've tried to setup the laptop to shutdown once the defined level is reached, but the laptop never actually switched off unless all the battery was drained.
Btw. I think all the above mentioned apps only work once the user is logged in. But I'd like the solution to work also when the PC is on without anyone logged in. I thought I could write a bash script based on parsing of acpitools output and define it as a service, which would monitor the battery level, but I simply don't believe there isn't any functional solution to this.
Next week we will get a new Server for rent with a preinstalled Debian. If we download the Networkinstaller and put it in Grub, it is possible to set some settings with a script or commandline? We need SSH and the Network haves to run. So we have to set up the Networkadress , Gateway and Netmasq. So if the Networkinstaller is booting that we get direcly access with SSH to install CentOS. It is possible?
Today I upgraded my 10.10 to 11.04. Since the last step of upgrading, when it was restarted, I get stucked in consola where it is checking, and there is written fail at stopping automatic crash report generation. How can I repair it. I tried to do
I have an intel DP35DP motherboard - ICH9 southbridge - set to AHCI mode. Working fine under 5.2. Yesterday I updated to centos 5.3, and got kernel 2.6.18-128.1.16 and now it can't boot. It hangs trying to read sata1 with DRDY errors and exceptions.So then I installed 5.3 from a DVD onto a new drive, and got kernel 2.6.18-128. This worked, most of the time, but occasionally gave me this error. I then updated my BIOS, and the error went away.Then I updated this new working drive to the latest kernel (yum update again) and got kernel 2.6.18-128.1.16, and now it wont boot again, with the same message.
have all ways been hiding in the background read not say a thinglets start well i look after 2 dell poweredge 2650 with 12 gig ram installed servers has been running fine onwell i though it was time to upgrade to 5 all went fine till reboot Memory for crash kernel (0x to 0x) not within permissible range ! well what i have been reading this is the norm for now What is mean by ignore it? LoLwell so i did the system keeps boot till i get to this linesbin/mingetty: /sbin/mingetty: cannot execute binary file alot, and it shows. INIT: Id "5" respawning too fast: disabled for 5 minutes ...so maybe its a memory issue so took 8 gig out left 4 in the system now it reboot alls good with only 4 gig of ram installed so is there a way to fix it to use all the ram can i get the system boot on 4 gig and then add the 8gig later on
I make upgrade from CentOS 5.4 to CentOS 5.5. Architecture is historical i386. On first boot my system was freezed by disabled earlier but not removed manualy writed xdm service. I disable it. But not found network. I see hardware address of card fe:ff:ff:ff:ff:ff. This address is not normal. But how to restore eeprom of this network adapter?
I don't think its trouble of new CentOS. I think this is random incident.Configuration of computer is Intel D510MO motherboard with integrated atom processor and realtek 8111dl nic. I know some trics about fix mac address in centos, but how to fix this address in bios?
I have encountered the same problem as indicated in this post: "udev hang after upgrade from 5.3 to 5.4"[URL]... I'm testing the upgrade path to centos 5.4 on several virtual machines prior to upgrading our production systems. I have upgraded centos 5.2 --> centos 5.4 and centos 5.3 to centos 5.4. In both cases udev hangs after the upgrade. The following message is displayed on the console: "Starting udev: Wait timeout. Will continue in the background [FAILED]"
I found another related post: "udev hangs on boot for a long time, suspect pam_console_apply"[URL]..So, I booted by VMs using the "udevdebug" option to grub and received the same error message - "udevd-event [###]: run_program: Waiting ## seconds for output of '/sbin/pam_console_apply /dev/..."
In my /etc/ldap.conf file "bind_policy hard" is commented out. I added a line "bind_policy soft" as described in the post and my VMs booted fine. NOTE: This problem is not encountered with a fresh install of CentOS 5.4 and the "bind_policy hard" option in the /etc/ldap.conf is commented out as in the upgraded systems. What is really causing this problem and how do I get it addressed? I have a couple hundred systems to update from various releases of CentOS 5 to the latest current version 5.4. It would be nice to get this bug squashed..
there is a bug on the quad core B2 opteron cpu there is a beta patch available , but only for for 2.6.24 kernel i am very happy with my centos, and i would upgrade the kernel to try this patch i am new on linux, so i need a precise tutoriral to upgrade and keep the actual configuration of the kernel
Last nights upgrade of java-1.6.0-openjdk-18.104.22.168-22.214.171.124.fc13.i686 and java-1.6.0-openjdk-plugin-126.96.36.199-188.8.131.52.fc13.i686 prevent the loading of Ameritrades Command Center.Downgrading to version 184.108.40.206-37 fixes the problem. I'll post the bugzilla number as soon as I get the chance to file it.
I've been living too long in apt-land, that's for sure. One of my servers is for an application the vendor indicates "isn't supported under 5.3". Nevertheless, I'm urged to upgrade from 5.2 with 178 packages ready to go when I log in. And for most hosts, that would be a fine thing.
However, for this particular host, I don't want to do that. I do want to upgrade any essential packages (i.e., security), of course, because I don't have a choice there, really. I can certainly look at the security emails from the project, and just upgrade those. Is there an easier way to do this?
I have a server currently running 5.2. The developers have asked me (the SysAdmin) to upgrade the server to 5.3 -- but not all the way to 5.4, as they haven't tested the app on 5.4 yet.I believe a simple `yum upgrade` will move me all the way to 5.4 -- at least, `yum check-update` shows a whole bunch of 5.4 packages.