Re: [CentOS] Centos 6.3 Network bnx2 Problem on HP DL360

[Woehrle Hartmut SBB CFF FFS (Extern)]

Hello Svavar

This was the first time that this problem occurred - with 60 Servers and about 
half a year of Centos 6 (5 before).
But because the interfaces have a permanent load - really 24x7 - problems with 
power management would be a disaster.
I will try to switch off.

Thanks
Hartmut

> How often are you getting these crashes ?
>
>I had simular problem on my HP DL380 G7 server.
>
>I disabled Active State PowerManagement on the PCI-E express.
>
>Try it.
>
>Add pcie_aspm=off as optional boot option.
>
>
>Best regards,
>
>Svavar O
>Reykjavik - Iceland



> On 19.3.2013, at 15:32, Woehrle Hartmut SBB CFF FFS (Extern) wrote:
>
> Hello Mailing List
> 
> I got a severe network error message at a HP DL360 Server.
> The kernel log says:
> 
> --- /var/log/messages 
> -
> Mar 19 15:45:06 server kernel: do_IRQ: 2.168 No irq handler for vector 
> (irq -1) Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: 
> DEBUG: intr_sem[0] PCI_CMD[00100446] Mar 19 15:45:17 server kernel: 
> bnx2 :02:00.1: eth1: DEBUG: PCI_PM[19002108] 
> PCI_MISC_CFG[9288] Mar 19 15:45:17 server kernel: bnx2 
> :02:00.1: eth1: DEBUG: EMAC_TX_STATUS[0008] 
> EMAC_RX_STATUS[0006] Mar 19 15:45:17 server kernel: bnx2 
> :02:00.1: eth1: DEBUG: RPM_MGMT_PKT_CTRL[4088] Mar 19 15:45:17 
> server kernel: bnx2 :02:00.1: eth1: DEBUG: 
> HC_STATS_INTERRUPT_STATUS[017f0080]
> Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
> PBA[] Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: 
> <--- start MCP states dump ---> Mar 19 15:45:17 server kernel: bnx2 
> :02:00.1: eth1: DEBUG: MCP_STATE_P0[0003610e] 
> MCP_STATE_P1[0003610e] Mar 19 15:45:17 server kernel: bnx2 
> :02:00.1: eth1: DEBUG: MCP mode[b880] state[80008000] 
> evt_mask[0500] Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: 
> DEBUG: pc[0800adec] pc[0800aeb0] instr[8fb10014] Mar 19 15:45:17 server 
> kernel: bnx2 :02:00.1: eth1: DEBUG: shmem states:
> Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
> drv_mb[0103000f] fw_mb[000f] link_status[006f] 
> drv_pulse_mb[432b] Mar 19 15:45:17 server kernel: bnx2 
> :02:00.1: eth1: DEBUG: dev_info_signature[44564903] 
> reset_type[01005254] condition[0003610e] Mar 19 15:45:17 server 
> kernel: bnx2 :02:00.1: eth1: DEBUG: 03cc:   
>  0a3c Mar 19 15:45:17 server kernel: bnx2 :02:00.1: 
> eth1: DEBUG: 03dc: 0ffe    Mar 19 
> 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03ec: 
>    0002 Mar 19 15:45:17 server kernel: 
> bnx2 :02:00.1: eth1: DEBUG: 0x3fc[] Mar 19 15:45:17 server 
> kernel: bnx2 :02:00.1: eth1: <--- end MCP states dump ---> Mar 19 
> 15:45:17 server kernel: bnx2 :02:00.1: eth1: NIC Copper Link is 
> Down Mar 19 15:45:20 server kernel: bnx2 :02:00.1: eth1: NIC 
> Copper Link is Up, 1000 Mbps full duplex
> --
> -
> 
> Does anyone know that problem?
> 
> System is Centos 6.3 Kernel
> Linux server 2.6.32-279.5.2.el6.centos.plus.x86_64 #1 SMP Fri Aug 24 
> 00:25:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> 
> 
> Thanks
> Hartmut
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Centos 6.3 Network bnx2 Problem on HP DL360

[Svavar Örn Eysteinsson]

After you have tried the pcie_aspm boot option, also try :

echo performance > /sys/module/pcie_aspm/parameters/policy
This will disable ASPM on PCIe and operate with maximum performance.

This is what I use today on the DL380 G7.




On 25.3.2013, at 09:06, Woehrle Hartmut SBB CFF FFS (Extern) wrote:

> Hello Svavar
> 
> This was the first time that this problem occurred - with 60 Servers and 
> about half a year of Centos 6 (5 before).
> But because the interfaces have a permanent load - really 24x7 - problems 
> with power management would be a disaster.
> I will try to switch off.
> 
> Thanks
> Hartmut
> 
>> How often are you getting these crashes ?
>> 
>> I had simular problem on my HP DL380 G7 server.
>> 
>> I disabled Active State PowerManagement on the PCI-E express.
>> 
>> Try it.
>> 
>> Add pcie_aspm=off as optional boot option.
>> 
>> 
>> Best regards,
>> 
>> Svavar O
>> Reykjavik - Iceland
> 
> 
> 
>> On 19.3.2013, at 15:32, Woehrle Hartmut SBB CFF FFS (Extern) wrote:
>> 
>> Hello Mailing List
>> 
>> I got a severe network error message at a HP DL360 Server.
>> The kernel log says:
>> 
>> --- /var/log/messages 
>> -
>> Mar 19 15:45:06 server kernel: do_IRQ: 2.168 No irq handler for vector 
>> (irq -1) Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: 
>> DEBUG: intr_sem[0] PCI_CMD[00100446] Mar 19 15:45:17 server kernel: 
>> bnx2 :02:00.1: eth1: DEBUG: PCI_PM[19002108] 
>> PCI_MISC_CFG[9288] Mar 19 15:45:17 server kernel: bnx2 
>> :02:00.1: eth1: DEBUG: EMAC_TX_STATUS[0008] 
>> EMAC_RX_STATUS[0006] Mar 19 15:45:17 server kernel: bnx2 
>> :02:00.1: eth1: DEBUG: RPM_MGMT_PKT_CTRL[4088] Mar 19 15:45:17 
>> server kernel: bnx2 :02:00.1: eth1: DEBUG: 
>> HC_STATS_INTERRUPT_STATUS[017f0080]
>> Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
>> PBA[] Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: 
>> <--- start MCP states dump ---> Mar 19 15:45:17 server kernel: bnx2 
>> :02:00.1: eth1: DEBUG: MCP_STATE_P0[0003610e] 
>> MCP_STATE_P1[0003610e] Mar 19 15:45:17 server kernel: bnx2 
>> :02:00.1: eth1: DEBUG: MCP mode[b880] state[80008000] 
>> evt_mask[0500] Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: 
>> DEBUG: pc[0800adec] pc[0800aeb0] instr[8fb10014] Mar 19 15:45:17 server 
>> kernel: bnx2 :02:00.1: eth1: DEBUG: shmem states:
>> Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
>> drv_mb[0103000f] fw_mb[000f] link_status[006f] 
>> drv_pulse_mb[432b] Mar 19 15:45:17 server kernel: bnx2 
>> :02:00.1: eth1: DEBUG: dev_info_signature[44564903] 
>> reset_type[01005254] condition[0003610e] Mar 19 15:45:17 server 
>> kernel: bnx2 :02:00.1: eth1: DEBUG: 03cc:   
>>  0a3c Mar 19 15:45:17 server kernel: bnx2 :02:00.1: 
>> eth1: DEBUG: 03dc: 0ffe    Mar 19 
>> 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03ec: 
>>    0002 Mar 19 15:45:17 server kernel: 
>> bnx2 :02:00.1: eth1: DEBUG: 0x3fc[] Mar 19 15:45:17 server 
>> kernel: bnx2 :02:00.1: eth1: <--- end MCP states dump ---> Mar 19 
>> 15:45:17 server kernel: bnx2 :02:00.1: eth1: NIC Copper Link is 
>> Down Mar 19 15:45:20 server kernel: bnx2 :02:00.1: eth1: NIC 
>> Copper Link is Up, 1000 Mbps full duplex
>> --
>> -
>> 
>> Does anyone know that problem?
>> 
>> System is Centos 6.3 Kernel
>> Linux server 2.6.32-279.5.2.el6.centos.plus.x86_64 #1 SMP Fri Aug 24 
>> 00:25:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>> 
>> 
>> Thanks
>> Hartmut
>> 
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
> 
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] maintaining patches across releases

[James Pearson]

Keith Keller wrote:
> I was looking at this bug which my machines are currently experiencing:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=883905
> 
> The proposed patch is literally one new line in the XFS codebase.  So
> since the patch is so straightforward, I had a crazy idea that I would
> build my own kernel with this patch, and test it out to see if it
> worked.  (It's been many years since I built my own kernel, so that
> would be an adventure in and of itself.)

Looks like this problem will be fix in kernel-2.6.32-358.5.1.el6 - see 


James Pearson
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Bonded interfaces - testing

[Dermot]

Hi,

I have 2 servers running CentOS 6.3. Each has four 1gb Ethernet ports. I
have bonded all four ports on each server and patched them to the same
switch (following the instructions at
http://wiki.centos.org/TipsAndTricks/BondingInterfaces). I have created
aggregated trunks for the servers respective ports on the switch. The
switch reports that the ports are up and that the Link Aggregation is
enabled.

I was under the impression, perhaps falsely, that I would see an
improvement in the throughput. I am not sure that I am. I used a utility
call nuttcp before the trunking and after to test the throughput. I am
seeing miniscule differences in the Mbps. I am not sure that I am testing
correctly. Perhaps the speed will not change but the available bandwidth
has increased. Is there some way to demonstrate that I am able to transfer
data from these two servers at a rate of 4,000Mbs?

Does anyone have any thoughts? I pasted some details below increase they
have a bearing.
Thanks in advance
Dermot.


./nuttcp otherserver
1125.6573 MB /  10.03 sec =  941.4967 Mbps 10 %TX 47 %RX


cat /proc/net/bonding/bond0

Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: slow
Aggregator selection policy (ad_select): stable
Active Aggregator Info:
Aggregator ID: 2
Number of ports: 4
Actor Key: 17
Partner Key: 420
Partner Mac Address: 10:0d:7f:4c:16:ca

Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 2c:76:8a:5d:28:1c
Aggregator ID: 2
Slave queue ID: 0

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 2c:76:8a:5d:28:1d
Aggregator ID: 2
Slave queue ID: 0

Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 2c:76:8a:5d:28:1e
Aggregator ID: 2
Slave queue ID: 0

Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 2c:76:8a:5d:28:1f
Aggregator ID: 2
Slave queue ID: 0
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Bonded interfaces - testing

[James Hogarth]

> Does anyone have any thoughts? I pasted some details below increase they
> have a bearing.
>


Remember that LACP (802.3ad) uses a hash algorithm (configurable on how
it's carried out and whether you use mac addresses, dst/src IPs and ports
will vary quite often for optimisation) to pick a physical connection for
the TCP flow ... and that will stay over the physical connection.

As such for any one given flow you'll see up to the speed of the physical
interface the data is going over... the speed increases come with multiple
systems communicating with that server and with the right pick of hashing
function having those connections go over differing interfaces.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Bonded interfaces - testing

[Dermot]

In which case, an appropriate test would be to have several servers push
data to one the server while it's interface is un-bonded. We'd anticipate
that the results would be under 1000Mbps. Then do the same with the bonded
interface and the results would hopefully be more consistently around
1000Mpbs. So I should not expect fastest throughput, simply a fatter pipe?

If it matters these are the hashing options available on the switch:

Thanks,
Dermot

Src MAC, VLAN, EType, incoming port

Dest MAC, VLAN, EType, incoming port

Src/Dest MAC, VLAN, EType, incoming port

Src IP and Src TCP/UDP Port fields

Dest IP and Dest TCP/UDP Port fields

Src/Dest IP and TCP/UDP Port fields
Enhanced hashing mode



On 25 March 2013 14:56, James Hogarth  wrote:

> > Does anyone have any thoughts? I pasted some details below increase they
> > have a bearing.
> >
>
>
> Remember that LACP (802.3ad) uses a hash algorithm (configurable on how
> it's carried out and whether you use mac addresses, dst/src IPs and ports
> will vary quite often for optimisation) to pick a physical connection for
> the TCP flow ... and that will stay over the physical connection.
>
> As such for any one given flow you'll see up to the speed of the physical
> interface the data is going over... the speed increases come with multiple
> systems communicating with that server and with the right pick of hashing
> function having those connections go over differing interfaces.
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] nscd

[m . roth]

Has anyone had problems accessing random websites since going up to 6.4?

Since about the day after I got partly upgraded, if I try to access
nytimes.com, or orbitz.com, I get server not found.

With a lot of work, I, my manager, and the other admin, found that setting
options edns0 in /etc/resolv.conf fixed it - I suspect that the network
folks updated their internal nameservers (which are M$) about that time...
but... we got this Thurs. Friday, I went to look, lunchtime, at a story,
and back to the same. Later, and I think I was playing around, it came
back.

Just now, over lunch, it failed... until I restarted nscd. My manager
tells me it's caching... but it seems to be caching momentary failures.

So: has anyone else seen oddness that might be related to nscd?

mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] nscd

[m . roth]

m.r...@5-cent.us wrote:
> Has anyone had problems accessing random websites since going up to 6.4?
>
> Since about the day after I got partly upgraded, if I try to access
> nytimes.com, or orbitz.com, I get server not found.
>
> With a lot of work, I, my manager, and the other admin, found that setting
> options edns0 in /etc/resolv.conf fixed it - I suspect that the network
> folks updated their internal nameservers (which are M$) about that time...
> but... we got this Thurs. Friday, I went to look, lunchtime, at a story,
> and back to the same. Later, and I think I was playing around, it came
> back.
>
> Just now, over lunch, it failed... until I restarted nscd. My manager
> tells me it's caching... but it seems to be caching momentary failures.
>
> So: has anyone else seen oddness that might be related to nscd?

A quick followup of myself to provide more info: I see, in /etc/nscd.conf,
that all the negative ttl's appear to be 20 sec, but I'm resonably sure
that once I lose it, it's > 20 sec before go back to try again, and it's
still not gone.

  mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] [Partially Solved] -Re: PHP Questions on move from CentOS 5.x to CentOS 6.x

[Max Pyziur]

On Sun, 24 Mar 2013, Johnny Hughes wrote:

> On 03/24/2013 10:45 AM, Max Pyziur wrote:

[...]

>> Apache's log files show a 503 (for postgresql) and 500 (for mysql) errors
>>
>> I'm troubleshooting this through obvious channels (looking at logfiles,
>> searching google, sdiff'ing configuration files).
>>
>> However, if someone has suggestions or answers, please do speak up!
>
> The php versions in CentOS-5 and CentOS-6 are different.  You don't say
> what version you are using and what version you moved to WRT php.
>
> However, if you were running the default, the versions of software that
> run on CentOS-5 might have to be upgraded to run on the newer php in
> CentOS-6. (from php-5.1.6 to php-5.3.3)
>
> You might also need to follow the upgrade procedures when moving from
> the older version of mysql and postgresql in CentOS-5 to the newer
> versions in CentOS-6.  (mysql-5.0.95 to mysql-5.1.67, postgresql-8.1.23
> to postgresql-8.4.13)
>
> Upgrading for major versions (ie, from CentOS-5.x to CentOS-6.x) is a
> major undertaking and data/configuration files usually have to upgraded.
>
> This is unlike moving between point releases within the same major
> version (ie, moving from 5.8 to 5.9 or 6.3 to 6.4).  This is because
> "minor version" upgrades are designed to just work because of
> backporting and freezing ABI/API changes inside the Major version ...
> whereas changing Major versions is a major upgrade and should be planned
> and testing accordingly.


The problems are separated here (divide and conquer). The PHP/Mysql 
websites now function.

The issue was a default directive in /etc/php.ini; the directive is 
short_open_tag. On CentOS 5 it is on; on CentOS 6 is off. Dropping the 
following into relevant .htaccess files:
php_value short_open_tag 1

fixed the problem.

On the PostgreSQL/Drupal/PHP side: I installed four minor releases of 
Drupal (6.14 -> 6.28), creating new test sites. Each works as designed.

So the PHP/PostgreSQL stack isn't the problem.

Existing websites (using Drupal releases ranging from 6.14-> 6.22) are 
where the errors are occuring. One person suggested deleting cache* 
content and session* content in relevant tables. That hasn't restored 
things; but the hunch now is that it is somewhere in the data.

fyi,

MP
p...@brama.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] nscd

[Cliff Pratt]

On Tue, Mar 26, 2013 at 6:26 AM,   wrote:
> Has anyone had problems accessing random websites since going up to 6.4?
>
> Since about the day after I got partly upgraded, if I try to access
> nytimes.com, or orbitz.com, I get server not found.
>
> With a lot of work, I, my manager, and the other admin, found that setting
> options edns0 in /etc/resolv.conf fixed it - I suspect that the network
> folks updated their internal nameservers (which are M$) about that time...
> but... we got this Thurs. Friday, I went to look, lunchtime, at a story,
> and back to the same. Later, and I think I was playing around, it came
> back.
>
> Just now, over lunch, it failed... until I restarted nscd. My manager
> tells me it's caching... but it seems to be caching momentary failures.
>
> So: has anyone else seen oddness that might be related to nscd?
>
Do you want the whole book? 'nscd' is a synonym for weird. I've had
many strange DNS issues which have been solved by either bouncing nscd
or purging its cache entries.

However, you appear to be using nscd on your machine to cache DNS and
using the internal MS DSN servers to do the actual lookups. Am I
correct? In which case, the MS DNS server should be caching the DNS
lookups anyway, so you probably don't derive a lot of benefit from the
nscd unless you do a lot of repeated DNS lookups.

Cheers,

Cliff
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] nscd

[Gary Greene]

On Tuesday, Cliff Pratt wrote:
> On Tue, Mar 26, 2013 at 6:26 AM,   wrote:
>> Has anyone had problems accessing random websites since going up to 6.4?
>>
>> Since about the day after I got partly upgraded, if I try to access
>> nytimes.com, or orbitz.com, I get server not found.
>>
>> With a lot of work, I, my manager, and the other admin, found that setting
>> options edns0 in /etc/resolv.conf fixed it - I suspect that the network
>> folks updated their internal nameservers (which are M$) about that time...
>> but... we got this Thurs. Friday, I went to look, lunchtime, at a story,
>> and back to the same. Later, and I think I was playing around, it came
>> back.
>>
>> Just now, over lunch, it failed... until I restarted nscd. My manager
>> tells me it's caching... but it seems to be caching momentary failures.
>>
>> So: has anyone else seen oddness that might be related to nscd?
>>
>Do you want the whole book? 'nscd' is a synonym for weird. I've had
>many strange DNS issues which have been solved by either bouncing nscd
>or purging its cache entries.
>
> However, you appear to be using nscd on your machine to cache DNS and
> using the internal MS DSN servers to do the actual lookups. Am I
> correct? In which case, the MS DNS server should be caching the DNS
> lookups anyway, so you probably don't derive a lot of benefit from the
> nscd unless you do a lot of repeated DNS lookups.
> 
> Cheers,
> 
> Cliff

NSCD is also necessary if you're running an LDAP or NIS environment, so don't 
just turn it off if you're using external authentication services. In a Winbind 
environment, NSCD is unnecessary however.

--
Gary L. Greene, Jr.
Sr. Systems Administrator
IT Operations
Minerva Networks, Inc.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] nscd

[Stephen Harris]

On Mon, Mar 25, 2013 at 11:06:31PM +, Gary Greene wrote:
> NSCD is also necessary if you're running an LDAP or NIS environment,

Not necessary in a NIS environment on a LAN 'cos NIS is UDP based and
very very fast to respond.  LDAP, however, pretty much needs nscd (or
sssd) in order to be halfway near performant.

-- 

rgds
Stephen
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How to make a network interface come up automatically on link up?

[Joakim Ziegler]

On 24/03/13 4:01, Nux! wrote:
> On 24.03.2013 02:27, Joakim Ziegler wrote:
>> I have a recently installed Mellanox VPI interface in my server. This
>> is
>> an InfiniBand interface, which, through the use of adapters, can also
>> do
>> 10GbE over fiber. I have one of the adapter's two ports configured for
>> 10GbE in this way, with a point to point link to a Mac workstation
>> with
>> a Myricom 10GbE card.

>> I've configured this interface on the Linux box (eth2) using
>> /etc/sysconfig/network-scripts/ifcfg-eth2 , setting its IP address,
>> MTU,
>> subnet, etc.

> Try adding HOTPLUG=yes in the cfg file.

Neither HOTPLUG=yes or MANAGED=no seems to make this interface come back
up when the cable is unplugged and then plugged, unfortunately. For
instance, before unplugging anything, ifconfig says:

eth2  Link encap:Ethernet  HWaddr 00:02:C9:29:64:8F
 inet addr:10.10.0.1  Bcast:10.10.255.255  Mask:255.255.0.0
 inet6 addr: fe80::2:c900:129:648f/64 Scope:Link
 UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
 RX packets:47 errors:0 dropped:0 overruns:0 frame:0
 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1000
 RX bytes:14924 (14.5 KiB)  TX bytes:3940 (3.8 KiB)

Then I unplug the cable, which, in dmesg, gives me:

mlx4_en: eth2: Link Down

And in /var/log/messages:

Mar 25 11:36:24 resolve02 ntpd[4819]: Deleting interface #14 eth2,
10.10.0.1#123, interface stats: received=0, sent=0, dropped=0,
active_time=163 secs

(Which I guess is just ntpd reacting)

And then I plug the cable back in, and in dmesg, I have:

mlx4_en: eth2: Link Up

Mar 25 11:38:09 resolve02 kernel: mlx4_en: eth2: Link Up
Mar 25 11:38:09 resolve02 NetworkManager[4429]:  (eth2): carrier
now ON (device state 2)
Mar 25 11:38:09 resolve02 NetworkManager[4429]:  (eth2): device
state change: 2 -> 3 (reason 40)

But ifconfig gives me:

eth2  Link encap:Ethernet  HWaddr 00:02:C9:29:64:8F
 inet6 addr: fe80::2:c900:129:648f/64 Scope:Link
 UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
 RX packets:104 errors:0 dropped:0 overruns:0 frame:0
 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1000
 RX bytes:25567 (24.9 KiB)  TX bytes:3940 (3.8 KiB)

So no IP address, and no joy. ifup eth2 brings me back to:

eth2  Link encap:Ethernet  HWaddr 00:02:C9:29:64:8F
 inet addr:10.10.0.1  Bcast:10.10.255.255  Mask:255.255.0.0
 inet6 addr: fe80::2:c900:129:648f/64 Scope:Link
 UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
 RX packets:104 errors:0 dropped:0 overruns:0 frame:0
 TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1000
 RX bytes:25567 (24.9 KiB)  TX bytes:6493 (6.3 KiB)

Ideas?

-- 
Joakim Ziegler  -  Supervisor de postproducción  -  Terminal
joa...@terminalmx.com   -   044 55 2971 8514   -   5264 0864
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] nscd

[Gordon Messmer]

On 03/25/2013 10:26 AM, m.r...@5-cent.us wrote:
> Just now, over lunch, it failed... until I restarted nscd. My manager
> tells me it's caching... but it seems to be caching momentary failures.

That could be coincidence.  As far as I know, Firefox will not use nscd 
for hostname lookups.  I confirmed Firefox using strace, but not others.

If edns0 changed your system's behavior, I would suspect that someone 
recently turned on DNSSEC, and it's not working correctly.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] nscd

[Gordon Messmer]

On 03/25/2013 04:06 PM, Gary Greene wrote:
> NSCD is also necessary if you're running an LDAP or NIS environment,
> so don't just turn it off if you're using external authentication
> services. In a Winbind environment, NSCD is unnecessary however.

I would advise all users to migrate to sssd from nscd.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] LVM filters not working?

[Dennis Jacobfeuerborn]

Hi,
I'm trying to set up a redundant DRBD system but I'm running into 
trouble when I try to define a volume group. The physical backing device 
for the drbd resource /dev/drbd0 is /dev/vdb1. The problem is that when 
I do a "pvs" on the command line the physical volume is shown as 
/dev/vdb1. So I tried the following filter in /etc/lvm/lvm.conf:

filter = [ "r|/dev/vdb.*|", "a/.*/"

But this doesn't seem to haven any effect at all. The system still sees 
the volumen group on /dev/vdb1. Also various how-to's on the net say I 
should pay attention to deleting /etc/lvm/cache/.cache which makes sense 
but this file is never created.

Any ideas what might be going on here? I'm trying all of this on CentOS 6.

Regards,
   Dennis
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] "Can't find root device" with lvm root after moving drive on CentOS 6.3

[Joakim Ziegler]

Hi, Gordon, this was indeed a very good idea. I'm attaching that file 
here, as it's a bit large. Thanks in advance for help and ideas.


--
Joakim Ziegler  -  Supervisor de postproducción  -  Terminal
joa...@terminalmx.com   -   044 55 2971 8514   -   5264 0864

On 25/03/13 0:21, Gordon Messmer wrote:

On 03/24/2013 10:43 PM, Joakim Ziegler wrote:

I haven't actually tried writing anywhere in the rescue shell before
vgchange and mount. I'll give it a try, that would simplify things.


If nothing else, you probably can fit most or all of that in the shell's
environment.  In case it's ever useful:

# debug=$(lvm pvdisplay; lvm vgdisplay; lvm lvdisplay; blkid; dmesg)
# vgchange -a y
# mount ...
# echo "$debug" > /mnt/sysroot/root/debug

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] "Can't find root device" with lvm root after moving drive on CentOS 6.3

[Joakim Ziegler]

On 25/03/13 19:26, Joakim Ziegler wrote:
> Hi, Gordon, this was indeed a very good idea. I'm attaching that file
> here, as it's a bit large. Thanks in advance for help and ideas.

Hm, it seems the list strips attachments, and just pasting it makes the 
mail too big to go through, so, pastebin to the rescue:

http://pastebin.com/x4wqzHyc

That's the output of, like you suggested:

  lvm pvdisplay; lvm vgdisplay; lvm lvdisplay; blkid; dmesg

In that order.

-- 
Joakim Ziegler  -  Supervisor de postproducción  -  Terminal
joa...@terminalmx.com   -   044 55 2971 8514   -   5264 0864
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How to make a network interface come up automatically on link up?

[Earl Ramirez]

On Mon, 2013-03-25 at 18:09 -0600, Joakim Ziegler wrote:
> On 24/03/13 4:01, Nux! wrote:
> > On 24.03.2013 02:27, Joakim Ziegler wrote:
> >> I have a recently installed Mellanox VPI interface in my server. This
> >> is
> >> an InfiniBand interface, which, through the use of adapters, can also
> >> do
> >> 10GbE over fiber. I have one of the adapter's two ports configured for
> >> 10GbE in this way, with a point to point link to a Mac workstation
> >> with
> >> a Myricom 10GbE card.
> 
> >> I've configured this interface on the Linux box (eth2) using
> >> /etc/sysconfig/network-scripts/ifcfg-eth2 , setting its IP address,
> >> MTU,
> >> subnet, etc.
> 
> > Try adding HOTPLUG=yes in the cfg file.
> 
> Neither HOTPLUG=yes or MANAGED=no seems to make this interface come back
> up when the cable is unplugged and then plugged, unfortunately. For
> instance, before unplugging anything, ifconfig says:
> 
> eth2  Link encap:Ethernet  HWaddr 00:02:C9:29:64:8F
>  inet addr:10.10.0.1  Bcast:10.10.255.255  Mask:255.255.0.0
>  inet6 addr: fe80::2:c900:129:648f/64 Scope:Link
>  UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
>  RX packets:47 errors:0 dropped:0 overruns:0 frame:0
>  TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
>  collisions:0 txqueuelen:1000
>  RX bytes:14924 (14.5 KiB)  TX bytes:3940 (3.8 KiB)
> 
> Then I unplug the cable, which, in dmesg, gives me:
> 
> mlx4_en: eth2: Link Down
> 
> And in /var/log/messages:
> 
> Mar 25 11:36:24 resolve02 ntpd[4819]: Deleting interface #14 eth2,
> 10.10.0.1#123, interface stats: received=0, sent=0, dropped=0,
> active_time=163 secs
> 
> (Which I guess is just ntpd reacting)
> 
> And then I plug the cable back in, and in dmesg, I have:
> 
> mlx4_en: eth2: Link Up
> 
> Mar 25 11:38:09 resolve02 kernel: mlx4_en: eth2: Link Up
> Mar 25 11:38:09 resolve02 NetworkManager[4429]:  (eth2): carrier
> now ON (device state 2)
> Mar 25 11:38:09 resolve02 NetworkManager[4429]:  (eth2): device
> state change: 2 -> 3 (reason 40)
> 
> But ifconfig gives me:
> 
> eth2  Link encap:Ethernet  HWaddr 00:02:C9:29:64:8F
>  inet6 addr: fe80::2:c900:129:648f/64 Scope:Link
>  UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
>  RX packets:104 errors:0 dropped:0 overruns:0 frame:0
>  TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
>  collisions:0 txqueuelen:1000
>  RX bytes:25567 (24.9 KiB)  TX bytes:3940 (3.8 KiB)
> 
> So no IP address, and no joy. ifup eth2 brings me back to:
> 
> eth2  Link encap:Ethernet  HWaddr 00:02:C9:29:64:8F
>  inet addr:10.10.0.1  Bcast:10.10.255.255  Mask:255.255.0.0
>  inet6 addr: fe80::2:c900:129:648f/64 Scope:Link
>  UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
>  RX packets:104 errors:0 dropped:0 overruns:0 frame:0
>  TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
>  collisions:0 txqueuelen:1000
>  RX bytes:25567 (24.9 KiB)  TX bytes:6493 (6.3 KiB)
> 
> Ideas?
> 

I am just shooting in the dark what happen if you have NM_CONTROLLED=yes
in the eth2 network script?
-- 


Kind Regards
Earl Ramirez
GPG Key: http://trinipino.com/PublicKey.asc


signature.asc
Description: This is a digitally signed message part
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] nscd

[Cliff Pratt]

On Tue, Mar 26, 2013 at 12:06 PM, Gary Greene
 wrote:
> On Tuesday, Cliff Pratt wrote:
>> On Tue, Mar 26, 2013 at 6:26 AM,   wrote:
>>> Has anyone had problems accessing random websites since going up to 6.4?
>>>
>>> Since about the day after I got partly upgraded, if I try to access
>>> nytimes.com, or orbitz.com, I get server not found.
>>>
>>> With a lot of work, I, my manager, and the other admin, found that setting
>>> options edns0 in /etc/resolv.conf fixed it - I suspect that the network
>>> folks updated their internal nameservers (which are M$) about that time...
>>> but... we got this Thurs. Friday, I went to look, lunchtime, at a story,
>>> and back to the same. Later, and I think I was playing around, it came
>>> back.
>>>
>>> Just now, over lunch, it failed... until I restarted nscd. My manager
>>> tells me it's caching... but it seems to be caching momentary failures.
>>>
>>> So: has anyone else seen oddness that might be related to nscd?
>>>
>>Do you want the whole book? 'nscd' is a synonym for weird. I've had
>>many strange DNS issues which have been solved by either bouncing nscd
>>or purging its cache entries.
>>
>> However, you appear to be using nscd on your machine to cache DNS and
>> using the internal MS DSN servers to do the actual lookups. Am I
>> correct? In which case, the MS DNS server should be caching the DNS
>> lookups anyway, so you probably don't derive a lot of benefit from the
>> nscd unless you do a lot of repeated DNS lookups.
>>
>> Cheers,
>>
>> Cliff
>
> NSCD is also necessary if you're running an LDAP or NIS environment,
> so don't just turn it off if you're using external authentication services. In
> a Winbind environment, NSCD is unnecessary however.
>
Ah, yes, indeed. Thanks Gary,

Cliff
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How to make a network interface come up automatically on link up?

[Eero Volotinen]

> Mar 25 11:38:09 resolve02 kernel: mlx4_en: eth2: Link Up
> Mar 25 11:38:09 resolve02 NetworkManager[4429]:  (eth2): carrier
> now ON (device state 2)
> Mar 25 11:38:09 resolve02 NetworkManager[4429]:  (eth2): device
> state change: 2 -> 3 (reason 40)

Is the network manager REALLY disabled on that interface?

--
Eero
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How to make a network interface come up automatically on link up?

[Joakim Ziegler]

Well, /etc/sysconfig/network-scripts/ifcfg-eth2 looks like this:

DEVICE=eth2
BOOTPROTO=none
ONBOOT=yes
NETWORK=10.10.0.0
NETMASK=255.255.0.0
IPADDR=10.10.0.1
USERCTL=no
MTU=9000
HOTPLUG=yes
NM_MANAGED=no

-- 
Joakim Ziegler  -  Supervisor de postproducción  -  Terminal
joa...@terminalmx.com   -   044 55 2971 8514   -   5264 0864

On 24/03/13 7:38, Patrick Lists wrote:
> On 24-03-13 08:03, Joakim Ziegler wrote:
>> How do I do that? I've not used network manager to set it up, I just
>> made the ifcfg-eth2 file from scratch.
>
> Besides the other two suggestions you may also want to set a proper
> SELinux label on the ifcfg-eth2 file with something like:
> /sbin/restorecon -v -F /etc/sysconfig/network-scripts/ifcfg-eth2
>
> The SELinux label I have on my ifcfg-eth0 is:
> -rw-r--r--. root root system_u:object_r:net_conf_t:s0  ifcfg-eth0
>
> Regards,
> Patrick
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How to make a network interface come up automatically on link up?

[Eero Volotinen]

2013/3/26 Joakim Ziegler :
> Well, /etc/sysconfig/network-scripts/ifcfg-eth2 looks like this:
>
> DEVICE=eth2
> BOOTPROTO=none
> ONBOOT=yes
> NETWORK=10.10.0.0
> NETMASK=255.255.0.0
> IPADDR=10.10.0.1
> USERCTL=no
> MTU=9000
> HOTPLUG=yes
> NM_MANAGED=no

try changing BOOTPROTO=static, instead of none.

--
Eero
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How to make a network interface come up automatically on link up?

[Eero Volotinen]

2013/3/26 Eero Volotinen :
> 2013/3/26 Joakim Ziegler :
>> Well, /etc/sysconfig/network-scripts/ifcfg-eth2 looks like this:
>>
>> DEVICE=eth2
>> BOOTPROTO=none
>> ONBOOT=yes
>> NETWORK=10.10.0.0
>> NETMASK=255.255.0.0
>> IPADDR=10.10.0.1
>> USERCTL=no
>> MTU=9000
>> HOTPLUG=yes
>> NM_MANAGED=no
>
> try changing BOOTPROTO=static, instead of none.

some documentation also like NM_CONTROLLED=no :
http://wiki.centos.org/FAQ/CentOS6

--
Eero
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] "Can't find root device" with lvm root after moving drive on CentOS 6.3

[Gordon Messmer]

On 03/25/2013 06:35 PM, Joakim Ziegler wrote:
> That's the output of, like you suggested:

And you ran that before you ran "vgchange -a y"?  That doesn't make any 
sense.  The commands show the volume group active.  I can't see any 
reason why the system wouldn't boot.

I hate for you to keep rebooting your server, but do the device nodes 
look correct in both /dev/mapper and /dev/vg_resolve02 at that point?

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] "Can't find root device" with lvm root after moving drive on CentOS 6.3

[Joakim Ziegler]

Yes, I ran that immediately after getting dropped to the shell. I can 
take a look at the device nodes tomorrow, but if I remember correctly, 
/dev/mapper contained only the file "control" before running vgchange 
-ay, that is, there was no "vg_resolve02-lv_root" device there. That 
device only shows up after I run vgchange -ay.

I did not check whether /dev/vg_resolve02 exists, I can do that tomorrow.

-- 
Joakim Ziegler  -  Supervisor de postproducción  -  Terminal
joa...@terminalmx.com   -   044 55 2971 8514   -   5264 0864

On 25/03/13 23:26, Gordon Messmer wrote:
> On 03/25/2013 06:35 PM, Joakim Ziegler wrote:
>> That's the output of, like you suggested:
>
> And you ran that before you ran "vgchange -a y"?  That doesn't make any
> sense.  The commands show the volume group active.  I can't see any
> reason why the system wouldn't boot.
>
> I hate for you to keep rebooting your server, but do the device nodes
> look correct in both /dev/mapper and /dev/vg_resolve02 at that point?
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos