Discuss May 2014

discuss@lists.centos.org

165 participants
148 discussions

Ulimit problem - CentOS 5.10
by Nathan Duehr 05 May '14

05 May '14

Running across some curious stuff with ulimit on CentOS 5.10. We have a non CentOS packaged version of Asterisk (using their packages) that we start at boot time with a typical RC script. Recently it started whining that it couldn't open enough file handles. As we dug further into this, it appears that at boot time, it inherits ulimit from init, which is pretty low: 1024. We've set /etc/security/limits.conf and sysctl significantly higher both for root/system wide and also for the user Asterisk runs under, to no avail. If we log in via ssh as root (or sudo) the correct root/system-wide ulimit of 8192 is set. Looking in /proc/[PID]/limits shows the lower ulimit only if the package is started from init (standard rc3.d type sysV stuff...). If we restart it via console, remote ssh, anything else, the limit bumps to 8196. Attempting to force the ulimit up inside the RC script has no effect, since the package is running as a non-root user. It fails to raise the limit. Right now, we're not totally against just taking it out of the startup and starting it manually anyway, since we really don't want the Asterisk platform coming up after a crash/reboot anyway, and any other reboots there will always be a human involved, but the way init is handling ulimit seems utterly retarded and broken. Some indication (different engineer found it, I haven't seen the RHEL case number) appears to indicate that folks wanted init ulimited heavily in case of startup DDoS type stuff, but we haven't figured out a semi-sane unix-conventional type way AROUND this when it's needed that if we were hit by the proverbial bus, a "normal" unix guy would find. Perhaps we're missing something. Thoughts? -- Nate Duehr denverpilot(a)me.com

5 10

Re: [CentOS] Disappearing Network Manager config scripts
by Les Mikesell 05 May '14

05 May '14

On Thu, May 1, 2014 at 5:54 AM, Steve Clark <sclark(a)netwolves.com> wrote: > On 04/30/2014 02:41 PM, Les Mikesell wrote: > > On Wed, Apr 30, 2014 at 1:28 PM, Steve Clark <sclark(a)netwolves.com> wrote: > > So, have you ever had to deal with a CentOS box and multiple NICs. > Especially one where you've cloned it or moved a disk to a new > chassis? Apparently there is just not a good way to identify > interfaces. > > Yep, do it all the time - first two thing I do are: > rm -f /etc/udev/rules.d/70-persistent-net.rules > rm -r /etc/sysconfig/network-scripts/ifcfg-eth* > and then reboot. > > So, now you've got 6 NICs connected to 6 different switches. Which > name is which? This is a really fun exercise when the box is remote > and you are trying to tell someone used to configuring windows systems > how to get it to a point where you can ssh in. > > I guess I am confused, you haven't ever worked with the hardware you are > installing the cloned > drive in? If that is true then I guess you have a problem. > "Working with it" doesn't matter. And network manager or not doesn't matter. Interfaces get named in a random order unless it is a Dell with the netbios naming scheme and probably then only for the motherboard NICs. Our servers generally have on-board Broadcomm and Intel cards and the names within a set may stay ordered, but the cards and motherboards will flip randomly if there are not already matching items with the correct MAC addresses in the udev rulss file (in 6.x, in 5.x having a matching MAC in the ifcfg-eth? file was enough to rename the device to match). This is just a response to your comment about windows names being difficult to know, (and a long-standing problem on its own) and doesn't relate much to the NetworkManager discussion. If you only have one (or maybe even a pair on the motherboard or a single card) you might always see the same ordering - if so consider yourself lucky because that is not the general case. We usually have to run through a drill like 'ip link ls' to get a list of interface names, then iterate through them with 'ifconfig up' and use ethtool to see which has link up, connecting one at a time. So, in my opinion, there are problems with the old system that need to be fixed, but they aren't the things that networkmanager does. A way to restore a backup to an identical machine and have the same NICs in the same positions get the old configurations would be nice. Or at least to know the names of the NICs in the same positions. (And if you go back to CentOS3 they did - detection was single threaded back then and would always probe in the same order). -- Les Mikesell lesmikesell(a)gmail.com

5 8

Ordering of disks in laptop
by H 05 May '14

05 May '14

I have a Lenovo laptop where I recently replaced the harddisk with a Intel 530 240 Gb SSD (SATA III) on which I then installed Centos 6.5 which runs just fine albeit at SATA II speed. I then replaced the DVD-drive in the Ultrabay with an identical Intel SSD, the Ultrabay-adapter apparently uses a PATA-SATA bridge so this drive would only run at PATA speed. Being a Centos newbie, I am not sure why Centos calls the first SSD sdb and the second one in the Ultrabay sda? It would seem to me that the first one, the one replacing the original harddisk, should be the main one and be called sda but clearly there is something I don't understand. In the BIOS the SSD replacing the harddisk has a higher boot order priority then the SSD replacing the DVD-drive. Suggestions? Thanks.

3 2

Opendkim and SELinux
by James B. Byrne 05 May '14

05 May '14

CentOS-6.5 OpenDKIM-2.9.0 (epel) Postfix-2.6.6 (updates) I am trying to get opendkim working with our mailing lists. In the course of that endeavour I note that these messages are appearing in our syslog: May 4 20:50:02 inet08 setroubleshoot: SELinux is preventing /usr/sbin/opendkim from using the signull access on a process. For complete SELinux messages. run sealert -l 442cb257-3db2-488c-a92e-bfc936e16a0c May 4 20:55:25 inet08 setroubleshoot: SELinux is preventing /usr/sbin/opendkim from using the dac_override capability. For complete SELinux messages. run sealert -l c7c1199d-008d-4ae5-b61f-71a11edb0aa3 May 5 04:03:57 inet08 setroubleshoot: SELinux is preventing /usr/sbin/opendkim from search access on the directory /sys. For complete SELinux messages. run sealert -l 800523d5-0420-4038-9c7d-c2ec47c3bb6a Anyone have any guidance to e on as to what this means and how I get rid of it, besides generating a custom policy I mean. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

3 2

Re: [CentOS] Disappearing Network Manager config scripts
by Les Mikesell 05 May '14

05 May '14

On Wed, Apr 30, 2014 at 1:28 PM, Steve Clark <sclark(a)netwolves.com> wrote: >> > So, have you ever had to deal with a CentOS box and multiple NICs. > Especially one where you've cloned it or moved a disk to a new > chassis? Apparently there is just not a good way to identify > interfaces. > > Yep, do it all the time - first two thing I do are: > rm -f /etc/udev/rules.d/70-persistent-net.rules > rm -r /etc/sysconfig/network-scripts/ifcfg-eth* > and then reboot. > So, now you've got 6 NICs connected to 6 different switches. Which name is which? This is a really fun exercise when the box is remote and you are trying to tell someone used to configuring windows systems how to get it to a point where you can ssh in. -- Les Mikesell lesmikesell(a)gmail.com

11 16

Re: [CentOS] BIND Log file entries
by James B. Byrne 02 May '14

02 May '14

On Fri, May 2, 2014 02:30, Andrew Holway wrote: > Hi James, > > Gmail sees your email as spam. You might want to take a look at it. > > ta > > Andrew I think that you will receive the directly addressed message without any indication of spam. The one routed through the Mailing list will probably be flagged unless you have white-listed me. The CentOS list uses Mailman (2.1.12) and as another has pointed out, recent changes to DMARC enforcement at Yahoo, AOL, and now apparently Google, causes DKIM signed email forwarded though mailman to fail the authentication checks relating to DKIM. This is either treated as suspicious (as is apparently the case with Google) or rejected outright, as is the case with Yahoo and AOL. We really need Mailman 2.1.18 as this fixes a lot of bugs with DKIM handling still present in 2.1.16/17 but .18 is only at the RC3 stage of release. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

3 2

plug in USB device no longer noticed by system
by Fred Smith 01 May '14

01 May '14

Hi all! My C6 box seems to have developed this problem somewhere during recent weeks. not quite sure when, but I've noticed it several times lately. Whenever I plug in a USB device, be it a camera or a HD or a mouse, nothing happens. I mean nothing. /var/log/messages doesn't show any activity, lsusb does not show the new device. Back at the start of Feb I did move the raid1 pair of HDs to a new motherboard, so I suppose it could go back that far. I did try to make sure everything was working at that time, and I can't remember if I verified that USB autodiscovery was working. But it for sure isn't now. I use a USB keyboard and USB mouse, but they seem to be discovered at boot time and work fine thereafter. but adding any other devices after boot isn't working. I'd appreciate thoughts on how to troubleshoot/fix this. thanks! -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- "Not everyone who says to me, 'Lord, Lord,' will enter the kingdom of heaven, but only he who does the will of my Father who is in heaven." ------------------------------ Matthew 7:21 (niv) -----------------------------

1 1

nvidia-related messages in /var/log/messages
by Fred Smith 01 May '14

01 May '14

Just discovered these messages in /var/log/messages, while looking at the USB problem I just posted about, separately. Apr 27 20:23:16 fcshome kernel: NVRM: API mismatch: the client has the version 331.67, but Apr 27 20:23:16 fcshome kernel: NVRM: this kernel module has the version 331.49. Please Apr 27 20:23:16 fcshome kernel: NVRM: make sure that this kernel module and all NVIDIA driver Apr 27 20:23:16 fcshome kernel: NVRM: components have the same version. Apr 27 20:23:16 fcshome kernel: NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22 Apr 29 19:22:30 fcshome kernel: NVRM: API mismatch: the client has the version 331.67, but Apr 29 19:22:30 fcshome kernel: NVRM: this kernel module has the version 331.49. Please Apr 29 19:22:30 fcshome kernel: NVRM: make sure that this kernel module and all NVIDIA driver but I cannot find anything relating to Nvidia that has a 331.49 version number. "yum list installed | grep 331.49" returns no hits "yum list installed | grep 331.[0-9]" returns ONLY hits on 331.67. "find 331" finds lots of things, but none of them is 331.49. So, I'd be appreciative if someone could shine a light on this for me. thanks! -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- Show me your ways, O LORD, teach me your paths; Guide me in your truth and teach me, for you are God my Savior, And my hope is in you all day long. -------------------------- Psalm 25:4-5 (NIV) --------------------------------

2 2

Re: [CentOS] Disappearing Network Manager config scripts
by Les Mikesell 01 May '14

01 May '14

On Thu, May 1, 2014 at 1:55 PM, Steve Clark <sclark(a)netwolves.com> wrote: > > Yep, do it all the time - first two thing I do are: > rm -f /etc/udev/rules.d/70-persistent-net.rules > rm -r /etc/sysconfig/network-scripts/ifcfg-eth* > and then reboot. > > The above makes them be rediscovered on the reboot. > > The lan ports are numbered on the back of the unit and I have never had them > not come up in the correct order - In fact it would cause us untold grief it > they did. > > > I forgot to add this is over 750 systems. They must all appear on the same motherboard/card location. Mine stay the same order within a card but the cards motherboard sets jump around. And yes, it causes grief. -- Les Mikesell lesmikesell(a)gmail.com

1 0

Disappearing Network Manager config scripts
by Evan Rowley 01 May '14

01 May '14

Is anyone frustrated by Network Manager? I wish CentOS just used the basic configuration files like the ones on BSD-style OSes. Those are so simple in comparison. Each time I reboot, it seems like the configuration file I create for Network Manager gets destroyed and replaced with a default file. Nothing in the default file would actually make sense on my network, so I'm not even really sure how this machine is still connected to the network after a reboot destroys my previous configuration. The only way I seem to be able to keep my proper DNS settings is through the GUI interface to Network Manager. I have to enter the configuration in each time I reboot. At the very least, I just want to stop Network Manager from wiping out my perfectly fine /etc/resolv.conf. There has to be a better way. -- - EJR

18 75

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss May 2014