I'm trying to disable TCP Segmentation offloading across the board in our datacenter to improve performance. Reading the history in the CentOS Bugzilla and the upstream's Bugzilla, they recommend doing this within the udev rules. See:[URL].. So, I created a new udev rules file that looks like this, as filename /etc/udev/rules.d/50-eth_tso.rules:
Can anyone out there figure out just what I'm doing wrong - I've been struggling with this for about 2 hours trying to make it work, and simply can not figure it out - and would like to not resort to hacking the problem and adding the ethtool commands to /etc/rc.d/rc.local!
I'm trying to arrange my 4 NIC's on CentOS 5. Two of them are build-in motherboard nic's and the others are PCI-E Dual Intel card. I'm wondering if someone succeed with udev renaming rule based on BUS location like ID=="0000:03:00.0" ... etc
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..
I had a problem with my laptop which is dell studio 1569 wireless card is as shown above intel centrino advanced n-6200. I had ubuntu before and it worked very well but with centos and oracle enterprise linux (not unbreakable) it does not work at all? And also the graphics card not fully configured I knew that when I tried an opengl apps?
I have 2 WD20EARS hard drives on the way (2 TB green WD disks with 4k sectors) and I'll be installing Centos 5.5 in RAID1 on them (2 partitions, one 16 GB / at the beginning and the rest in its own partition). I read the following thread: [URL]
and it seems that I might be having problems with the 4k sectors (Advanced Drive Format in WD lingo). I'm confused as to what exactly to do. I was thinking of downloading Fedora 14 Live CD and partitioning there and then switching to Centos 5.5 to install. Will that work? Seems I want the md 0.9 metadata because it doesn't have the space limit for me (2 TB) and it's stored at the end of the partition so it avoids alignment issues. Will I be able to make that happen with Fedora 14?
I have three network interfaces on my box. Lets call them A, B and C.
I want to place my box in-line within our corporate network, so that traffic from LAN goes into interface A and is directed out again through B. So essentially making a Switch. And the last interface is for management of the box it self.
Is this possible?
LAN ---> [[ int . A -- int . B ]] --------> Firewall --> Internet
Could i configure the interfaces so that you basically make a software based TAP? Or on other words "Cut the cable" and putting my box in the middle....
I did a Yum update last Friday. It was done before 5.6 was released so I still have 5.5 + various updates. Yum is now giving me a segmentation fault when I try to run it. I believe it has to do with an improperly synchronized version of sqlite which was updated and then Yum stopped working. I'm guessing that installing the latest Yum RPM will fix the dependency issues. Will this throw me out of sync with for instance updating to 5.6?
I have a centos server running nagios for monitoring. I restarted the machine, it is actually a console server anyway. After getting to the login screen, I typed in my user name but it never propt for my password. I can't even ssh into the system. So I tried to use the installation cd and enter into rescue mode where I typed chroot and was able to enter into the root environment. I was able to configure a network interface in the rescue mode and can ping the machine at this point, though can ssh still. In the root environment, I tried running couple commands. like try to restart the sshd. When I typed /etc/init.d/sshd restart, I got an error saying:
766 segmentation fault.
when I vi any thing I get error:
how can I solve this problem? What is causes this. Even in the event of restarting the machine, I see so many fails with segmentation fault.
I have a problem while trying to get rpm fixed I removed it then it removed yum also. I was able to get rpm installed and tried to install yum there was a bunch of depency files i had to install. After that then every command results in Segmentation fault some commands work like pwd does but not ls, rpm, vi and most other ones ive tried. server is still up and running.
Recently I noticed that on my Centos 5.4 system, yum no longer works and is giving segmentation faults. I can run "yum --help" and it works, but if I try to run something like "yum upgrade php" it will fault. I also noticed that other things are seg faulting as well, like /usr/sbin/logrotate and /usr/bin/certwatch.
I am guessing there is some sort of common library that needs fixing, but I have no idea what. I've read other posts about the yum segmentation fault and have tried various steps provided but so far no luck in getting it to work again. It used to work, and I rarely change this system so I'm not sure what could have caused it.
Have just installed 5.4 64 bit on an AMD64 x2 system with 4 GB ram running ESXi4.Text based install went fine, but on reboot starting up it gets as far as 'Starting udev' and just hangs. Checking the performance in ESXi it appears to be using 100% cpu.I have left it for half an hour and it does not progress and the only thing to do is to power cycle the VM.I have searched and found a few suggestions for kernel parameters but they did not make any difference. I can't even get in to a command line as it doesn't boot up far enough.I have reinstalled it several times and also checked the MD5 of the downloaded file and all appears Ok.
I have built a CentOS 5.6 kernel with the Preemption Model changed from Voluntary to Preemptible Kernel. Everything works fine except for gdb. When attempting to debug a binary using start or run there is a segmentation fault. If I attach to a running process everything works fine. I expect that I need to make an additional change to the kernel config file, but don't know what it might be. I'm using menuconfig to make the changes: Processor type and features --->Preemption Model ---> [x] Preemptible Kernel (Low-Latency Desktop).
gdb /bin/true (gdb) run Starting program: /bin/true During startup program terminated with signal SIGSEGV, Segmentation Fault.
I haven't updated my centos box for almost about a year, my theory is if it ain't broke don't fix it.These last two weeks I've been replacing hardware, a motherboard, memory, processor, and a hard-disk. Everything worked fine with the current 2.6.18-128.1.10, but I decided that I should upgrade to the latest along with all the new packages. But in doing so I would need to recompile the driver module for the raid controllers, rr1740. So I recompiled them using the 2.6.18-164.1 build while I was in kernel 128. When I was done, I restarted the machine and when it booted to the new 164 kernel, it came back very long error messages but here's what I can remember off the top of my head.
My centos linux mailserver has crushed and does not allow any login form any user including root. I have managed to start it in single user mode but using vi editor, df command gives segmentation fault. I suspect the /var/* is full but I can neither remove any file/folder/mail/logs nor copy these to make a backup.Attempt to do this as single user/root is met with readonly files yet I have given full permissions to the files and the folders.
I'm hoping someone knows about this one... I'm running the latest CentOS 5.4 with kernel 2.6.18-164.15.1.el5 (x86_64).When I boot the machine, it gets to the udev starting bit, hangs for like 5 minutes, then prints a message "Failed, will continue in the background." Then it boots OK after that.I tried booting again with the kernel option (from grub) "udevdebug", and what I saw when it tried again was a million messages saying it was waiting for "/sbin/pam_console_apply" to return, but I guess it wasn't returning... ;) Again, after 5 minutes, it gave up and finished booting.Now, this host is an LDAP client.
I figured that may have something to do with it as it is likely that pam_console_apply tries to make an LDAP lookup, which is wrong, because networking hasn't even started yet. If I disable LDAP (by removing ldap lookups in nsswitch.conf), I get no pam_console_apply errors from udev and it boots quickly. But that's a bummer, I need LDAP on this box, and I don't want my boot time to be 7-8 minutes. ;)Presumably before, when LDAP was enabled and it waited 5 minutes and then notified me that it will "continue in the background", that it was eventually successful after networking started. LDAP otherwise works fine on this box, just like all the other servers we have.This is new behavior, I've not seen it with CentOS 5.3 and below. Has anyone seen this? Any hints on what I can do to avoid it? It seems like a pam bug or something, but I don't know for sure.
I've been told to setup a first ubuntu sw development pc in my office. Our network domain server is Windows 2000 Advanced. Are there any issues or limitations that would prevent this marriage? Will it be apparent when I crack open ubuntu? Maybe a link to this procedure? Is joining a workgroup equally simple?
I have a Raid5 software partitioned using LVM (at centos 5.2 installation). Actually the raid is composed by 3 320Gb HDD. I would like to replace them with 3 2T hdd, but I'm worried about the alignment issues of the upgrade. I know it is easy to align the raid partition URL But what will happen to the LVM partition? Reformat and install everything is not an option
I'm trying to set my network interfaces so that they don't get random every boot.(eg assign eth0 to a network interface with a given MAC addr, and eth1 to the other one)I trew in a udev rule (in fact just modified the rules that was automatically generated and set the ethX in it) but the system ignores my udev rule.What am I missing ?Here is all the info :
Code: $cat /etc/udev/rules.d/70-persistent-net.rules # This file maintains persistent names for network interfaces.
For some reason, Ubuntu keeps assigning my network interface wrong MAC address. This happens only after fresh boot (I have dual boot with WinXP, if I start Windows first and then restart to Ubuntu without switching computer off, the MAC is correct). Contents of /etc/udev/rules.d/70-persistent-net.rules: