Re: [CentOS] [Fwd: The CentOS list]

[Valeri Galtsev]

On Mon, January 30, 2017 9:12 pm, John R. Dennison wrote:
> On Mon, Jan 30, 2017 at 06:53:41PM -0800, Keith Keller wrote:
>>
>> It's a bit unproductive to trouble list members about list problems.
>
> Not that I disagree but lists.centos.org and mail.centos.org are the
> same box; it is likely that if someone is having issues getting a post
> to the list they will have similar problems mailing f...@centos.org as
> well.
>

Thanks John.

Moreover, I didn't intend to ask help with access to list, what I asked
was to look into technical problem the person has on his machine which he
himself was not able to pass over to the list. This ours is the only list
of technical mail lists I am being bashed on for merely sending to list
someone's e-mail with non-trivial _technical_ _question_ which he is
unable to send to list himself.

Valeri

>   John
> --
> The ability to focus attention on important things is a defining
> characteristic of intelligence.
>
> -- Robert J. Shiller (1946-), American economist, academic, and author,
>Irrational Exuberance (2006)
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

Re: [CentOS] [Fwd: The CentOS list]

[Valeri Galtsev]

On Mon, January 30, 2017 8:53 pm, Keith Keller wrote:
> On 2017-01-30, Valeri Galtsev  wrote:
>>
>> Mark has problem sending mail to centos@centos.org list
>
> Isn't there an email address for the list admins?
>
> https://lists.centos.org/mailman/listinfo/centos
>
> centos-ow...@centos.org
>
> It's a bit unproductive to trouble list members about list problems.

This phrase you quote was mere explanation why I forwarded somebody's else
message, and by no means intended to be request about the list, to the
contrary, about some software on CentOS system.

Creative editing is bad when one pills some phrase totally out of the
message context like you did ;-( So we are both bad about list etiquette
(even though I doubt I am ;-)

Valeri

>
> --keith
>
> --
> kkel...@wombat.san-francisco.ca.us
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

Re: [CentOS] [Fwd: The CentOS list]

[John R. Dennison]

On Mon, Jan 30, 2017 at 06:53:41PM -0800, Keith Keller wrote:
> 
> It's a bit unproductive to trouble list members about list problems.

Not that I disagree but lists.centos.org and mail.centos.org are the
same box; it is likely that if someone is having issues getting a post
to the list they will have similar problems mailing f...@centos.org as
well.







John
-- 
The ability to focus attention on important things is a defining
characteristic of intelligence.

-- Robert J. Shiller (1946-), American economist, academic, and author,
   Irrational Exuberance (2006)


signature.asc
Description: PGP signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [Fwd: The CentOS list]

[Keith Keller]

On 2017-01-30, Valeri Galtsev  wrote:
>
> Mark has problem sending mail to centos@centos.org list

Isn't there an email address for the list admins?

https://lists.centos.org/mailman/listinfo/centos

centos-ow...@centos.org

It's a bit unproductive to trouble list members about list problems.

--keith

-- 
kkel...@wombat.san-francisco.ca.us


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

Re: [CentOS] CentOS 6, flash-plugin crashing

[Richard]

> Date: Monday, January 30, 2017 13:56:24 -0500
> From: m.r...@5-cent.us
>
> Anyone else seeing this? I'm playing streaming media, and after
> about 10 or 15 min, flash-plugin crashes. I've had this happen
> today on streams from two separate radio stations.
> 
>mark


Care to provide any specifics?

   - URL(s) of content that is causing the crashes
   - flash plugin release number
   - firefox version
   - OS version


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

[CentOS] Question about 7.3

[TE Dukes]

I haven't done a fresh install in years. I've always gone the upgrade route.
Seemed to have always worked for me.

I moved to 7.3 since it supports the latest versions of some programs I want
to use to implement as a backup server/RAID/NAS for 3 machines here at home
and a remote laptop at work.

So, the question is, is there something different in 7.3 than the previous 7
versions?

The reason I ask is I was running a lesser version of 7, I think 7.1, as a
VM on 6.8. I remember I chose not to install the most recent version at the
time. Never had these issues. Not really issues but everything just worked
without a lot of expertise involved.

One thing I could never figure out is that on 6.8, I have the zoneminder
repo installed and when I did a yum update on the 7.1 VM, it was also
accessing the zmrepo which wasn't installed. Just thought it was odd.

Anyway, I really appreciate the help and keep paying it forward!!

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

Re: [CentOS-virt] NIC Stability Problems Under Xen 4.4 / CentOS 6 / Linux 3.18

[Kevin Stange]

On 01/30/2017 06:12 PM, Adi Pircalabu wrote:
> On 31/01/17 10:49, Kevin Stange wrote:
>> You said 3.x kernels specifically. The kernel on Xen Made Easy now is a
>> 4.4 kernel.  Any chance you have tested with that one?
> 
> Not yet, however the future Xen nodes we'll deploy will run CentOS 7 and
> Xen with kernel 4.4.

I'll keep you (and others here) posted on my own experiences with that
4.4 build over the next few weeks to report on any issues.  I'm hoping
something happened between 3.18 and 4.4 that fixed underlying problems.

>> Did you ever try without MTU=9000 (default 1500 instead)?
> 
> Yes, also with all sorts of configuration combinations like LACP rate
> slow/fast, "options ixgbe LRO=0,0" and so on. No improvement.

Alright, I'll assume that probably won't help then.  I tried it on one
box which hasn't had the issue again yet, but that doesn't guarantee
anything.

>> I am having certain issues on certain hardware where there's no shutting
>> down the affected NICs.  Trying to do so or unload the igb module hangs
>> the entire box.  But in that case they're throwing AER errors instead of
>> just unit hangs:
>>
>> pcieport :00:03.0: AER: Uncorrected (Non-Fatal) error received:
>> id=
>> igb :04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
>> type=Transaction Layer, id=0401(Requester ID)
>> igb :04:00.1:   device [8086:10a7] error
>> status/mask=4000/
>> igb :04:00.1:[14] Completion Timeout (First)
>> igb :04:00.1: broadcast error_detected message
>> igb :04:00.1: broadcast slot_reset message
>> igb :04:00.1: broadcast resume message
>> igb :04:00.1: AER: Device recovery successful
> 
> This is interesting. We've never had any problems with the 1Gb NICs, but
> we're only using 10Gb for the storage network. Could it be a common
> problem with either the adapters, or the drivers which only replicate
> running the Xen enabled kernel?

Since I've never run the 3.18 kernel on a box of this type without
running in a dom0 and since I can't reproduce this kind of issue without
a fair amount of NIC load over a tremendous period of time, it's
impossible to test if it's tied to Xen.

However, I know this hardware works well under 2.6.32-*.el6 and
3.10.0-*.el7 kernels without stability problems, as it did with
2.6.18-*.el5xen (Xen 3.4.4).

I suspect the above errors are actually due to something PCIe related,
and I have a subset of boxes which are actually being impacted by two
distinct problems with equivalent impact, which increases the likelihood
that the boxes will die.  Another set of boxes only ever sees the unit
hangs which seem unrecoverable even unloading/reloading the driver.  A
third set has random recoverable unit hangs only.  With so much
diversity, it's even harder to pin any specific causes to the problems.

The fact we're both pushing NFS and iSCSI traffic over these links makes
me wonder if there's something about that kind of traffic that increases
the chances of causing these issues.  When I put VM network traffic over
the same NICs, they seem a lot less prone to failures, but also end up
pushing less traffic in general.

>> Switching to Broadcom would be a possibility, though it's tricky because
>> two of the NICs are onboard, so we'd need to replace the dual-port 1G
>> card with a quad-port 1G card.  Since you're saying you're all 10G,
>> maybe you don't know, but if you have any specific Broadcom 1G cards
>> you've had good fortune with, I'd be interested in knowing which models.
>>   Broadcom cards are rarely labeled as such which makes finding them a
>> bit more difficult than Intel ones.
> 
> We've purchased a number of servers with Broadcom BCM957810A1008G, sold
> by Dell as QLogic 57810 dual 10Gb Base-T adapters, none of them going up
> & down like a yo-yo so far.
> 
>> So far the one hypervisor with pci=nomsi has been quiet but that doesn't
>> mean it's fixed.  I need to give it 6 weeks or so. :)
> 
> It'd be more like 6-9 months for us, making it terrible to debug it :-/

I had a bunch of these on relatively light VM load for 3 months for
"burn in" with no issues but they've been pretty aggressively failing
since I started to try to put real loads on them.  Still, it's odd
because some of the boxes with identical hardware and similar VM loads
have not yet blown up after 3 or more weeks, and maybe they won't for
several months.

-- 
Kevin Stange
Chief Technology Officer
Steadfast | Managed Infrastructure, Datacenter and Cloud Services
800 S Wells, Suite 190 | Chicago, IL 60607
312.602.2689 X203 | Fax: 312.602.2688
ke...@steadfast.net | www.steadfast.net
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] Mail issues

[John R Pierce]

On 1/30/2017 4:13 PM, TE Dukes wrote:

This is a fresh install, I haven't changed anything except adding
mail_location = maildir:~/Maildir in /etc/dovecot/conf.d/10-mail.conf


the mail transfer agent (postfix) needs a mail delivery agent for 
locally delivered mail, in traditional email systems this was often 
procmail or fetchmail. dovecot is a mail client, although it contains an 
optional local delivery agent.  a bit of googling found 
http://wiki.dovecot.org/LDA/Postfix



--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS] Mail issues

[TE Dukes]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of John R.
> Dennison
> Sent: Monday, January 30, 2017 7:05 PM
> To: CentOS mailing list
> Subject: Re: [CentOS] Mail issues
> 
> On Mon, Jan 30, 2017 at 06:50:13PM -0500, TE Dukes wrote:
> >
> > to=, orig_to=, relay=local,
> > delay=0.1, delays=0.07/0.01/0/0.03, dsn=2.0.0, status=sent (delivered
> > to mailbox)
> >
> > Do I need to install additional packages that move mail to the user's
> > /Maildir?
> 
> This is indicative of misconfiguration with mail being delivered to
> /var/mail/whatever instead of /home/whatever/Maildir.  Check your
> configuration again to ensure it's delivering as you wish.
> Alternatively, post _all_ content from /etc/postfix/{main,master}.cf for
> review.
> 
> 
>   John


This is a fresh install, I haven't changed anything except adding
mail_location = maildir:~/Maildir in /etc/dovecot/conf.d/10-mail.conf

Output from postconf -n:

alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd
$daemon_directory/$process_name $process_id & sleep 5
html_directory = no
inet_interfaces = localhost
inet_protocols = all
mail_owner = postfix
mailq_path = /usr/bin/mailq.postfix
manpage_directory = /usr/share/man
mydestination = $myhostname, localhost.$mydomain, localhost
newaliases_path = /usr/bin/newaliases.postfix
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES
sample_directory = /usr/share/doc/postfix-2.10.1/samples
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
unknown_local_recipient_reject_code = 550

Thanks!!

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

Re: [CentOS-virt] NIC Stability Problems Under Xen 4.4 / CentOS 6 / Linux 3.18

[Adi Pircalabu]

On 31/01/17 10:49, Kevin Stange wrote:

You said 3.x kernels specifically. The kernel on Xen Made Easy now is a
4.4 kernel.  Any chance you have tested with that one?


Not yet, however the future Xen nodes we'll deploy will run CentOS 7 and 
Xen with kernel 4.4.



Did you ever try without MTU=9000 (default 1500 instead)?


Yes, also with all sorts of configuration combinations like LACP rate 
slow/fast, "options ixgbe LRO=0,0" and so on. No improvement.



I am having certain issues on certain hardware where there's no shutting
down the affected NICs.  Trying to do so or unload the igb module hangs
the entire box.  But in that case they're throwing AER errors instead of
just unit hangs:

pcieport :00:03.0: AER: Uncorrected (Non-Fatal) error received: id=
igb :04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
type=Transaction Layer, id=0401(Requester ID)
igb :04:00.1:   device [8086:10a7] error status/mask=4000/
igb :04:00.1:[14] Completion Timeout (First)
igb :04:00.1: broadcast error_detected message
igb :04:00.1: broadcast slot_reset message
igb :04:00.1: broadcast resume message
igb :04:00.1: AER: Device recovery successful


This is interesting. We've never had any problems with the 1Gb NICs, but 
we're only using 10Gb for the storage network. Could it be a common 
problem with either the adapters, or the drivers which only replicate 
running the Xen enabled kernel?



Switching to Broadcom would be a possibility, though it's tricky because
two of the NICs are onboard, so we'd need to replace the dual-port 1G
card with a quad-port 1G card.  Since you're saying you're all 10G,
maybe you don't know, but if you have any specific Broadcom 1G cards
you've had good fortune with, I'd be interested in knowing which models.
  Broadcom cards are rarely labeled as such which makes finding them a
bit more difficult than Intel ones.


We've purchased a number of servers with Broadcom BCM957810A1008G, sold 
by Dell as QLogic 57810 dual 10Gb Base-T adapters, none of them going up 
& down like a yo-yo so far.



So far the one hypervisor with pci=nomsi has been quiet but that doesn't
mean it's fixed.  I need to give it 6 weeks or so. :)


It'd be more like 6-9 months for us, making it terrible to debug it :-/

Adi Pircalabu
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] Mail issues

[John R. Dennison]

On Mon, Jan 30, 2017 at 06:50:13PM -0500, TE Dukes wrote:
>
> to=, orig_to=, relay=local, 
> delay=0.1, delays=0.07/0.01/0/0.03, dsn=2.0.0, status=sent (delivered to 
> mailbox)
> 
> Do I need to install additional packages that move mail to the user's
> /Maildir?

This is indicative of misconfiguration with mail being delivered to
/var/mail/whatever instead of /home/whatever/Maildir.  Check your
configuration again to ensure it's delivering as you wish.
Alternatively, post _all_ content from /etc/postfix/{main,master}.cf for
review.


John
-- 
One original thought is worth a thousand mindless quotings.

-- Diogenes of Sinope (412 BC - 323 BC), Cynic philosopher of ancient Greece


signature.asc
Description: PGP signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 6, flash-plugin crashing

[m . roth]

Anyone else seeing this? I'm playing streaming media, and after about 10
or 15 min, flash-plugin crashes. I've had this happen today on streams
from two separate radio stations.

   mark

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

[CentOS] Mail issues

[TE Dukes]

I know I'm wearing you guys out.

I thought I had mail working. It is but it isn't.

Mail is stuck in /var/spool/mail.

This is a fresh install of dovecot and postfix. I have uninstalled
mailscanner as well until I can figure out what's wrong.

I sent a test mail from root to tdukes but its not being delivered to
~/Maildir

Here's the clip from maillog:

Jan 30 18:40:42 ts130 postfix/pickup[4828]: 2DF2D82CA5B9: uid=0 from=
Jan 30 18:40:42 ts130 postfix/cleanup[6070]: 2DF2D82CA5B9:
message-id=<20170130234042.2df2d82ca...@ts130.palmettodomains.com>
Jan 30 18:40:42 ts130 postfix/qmgr[4829]: 2DF2D82CA5B9:
from=, size=480, nrcpt=1 (queue active)
Jan 30 18:40:42 ts130 postfix/local[6071]: 2DF2D82CA5B9:
to=, orig_to=, relay=local,
delay=0.1, delays=0.07/0.01/0/0.03, dsn=2.0.0, status=sent (delivered to
mailbox)
Jan 30 18:40:42 ts130 postfix/qmgr[4829]: 2DF2D82CA5B9: removed
Jan 30 18:40:49 ts130 dovecot: imap-login: Login: user=,
method=PLAIN, rip=::1, lip=::1, mpid=6078, secured,
session=
Jan 30 18:40:49 ts130 dovecot: imap(tdukes): Disconnected: Logged out in=82
out=495

Do I need to install additional packages that move mail to the user's
/Maildir?

TIA

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

Re: [CentOS-virt] NIC Stability Problems Under Xen 4.4 / CentOS 6 / Linux 3.18

[Kevin Stange]

On 01/30/2017 04:17 PM, Adi Pircalabu wrote:
> On 28/01/17 05:21, Kevin Stange wrote:
>> On 01/27/2017 06:08 AM, Karel Hendrych wrote:
>>> Have you tried to eliminate all power management features all over?
>>
>> I've been trying to find and disable all power management features but
>> having relatively little luck with that solving the problems.  Stabbing
>> the the dark I've tried different ACPI settings, including completely
>> disabling it, disabling CPU frequency scaling, and setting pcie_aspm=off
>> on the kernel command line.  Are there other kernel options that might
>> be useful to try?
> 
> May I chip in here? In our environment we're randomly seeing:

Welcome.  It's a relief to know someone else has been having a similar
nightmare!  Perhaps that's not encouraging...

> Jan 17 23:40:14 xen01 kernel: ixgbe :04:00.1 eth6: Detected Tx Unit
> Hang
> Jan 17 23:40:14 xen01 kernel:  Tx Queue <0>
> Jan 17 23:40:14 xen01 kernel:  TDH, TDT <9a>, <127>
> Jan 17 23:40:14 xen01 kernel:  next_to_use  <127>
> Jan 17 23:40:14 xen01 kernel:  next_to_clean<98>
> Jan 17 23:40:14 xen01 kernel: ixgbe :04:00.1 eth6:
> tx_buffer_info[next_to_clean]
> Jan 17 23:40:14 xen01 kernel:  time_stamp   <218443db3>
> Jan 17 23:40:14 xen01 kernel:  jiffies  <218445368>
> Jan 17 23:40:14 xen01 kernel: ixgbe :04:00.1 eth6: tx hang 1
> detected on queue 0, resetting adapter
> Jan 17 23:40:14 xen01 kernel: ixgbe :04:00.1 eth6: Reset adapter
> Jan 17 23:40:15 xen01 kernel: ixgbe :04:00.1 eth6: PCIe transaction
> pending bit also did not clear.
> Jan 17 23:40:15 xen01 kernel: ixgbe :04:00.1: master disable timed out
> Jan 17 23:40:15 xen01 kernel: bonding: bond1: link status down for
> interface eth6, disabling it in 200 ms.
> Jan 17 23:40:15 xen01 kernel: bonding: bond1: link status definitely
> down for interface eth6, disabling it
> [...] repeated every second or so.
> 
>>> Are the devices connected to the same network infrastructure?
>>
>> There are two onboard NICs and two NICs on a dual-port card in each
>> server.  All devices connect to a cisco switch pair in VSS and the links
>> are paired in LACP.
> 
> We've been experienced ixgbe stability issues on CentOS 6.x with various
> 3.x kernels for years with different ixgbe driver versions and, to date,
> the only way to completely get rid of the issue was to switch from Intel
> to Broadcom. Just like in your case, the problem pops up randomly and
> the only reliable temporary fix is to reboot the affected Xen node.
> Another temporary fix that worked several times but not always was to
> migrate / shutdown the domUs, deactivate the volume groups, log out of
> all the iSCSI targets, "ifdown bond1" and "modprobe -r ixgbe" followed
> by "ifup bond1".
> 
> The set up is:
> - Intel Dual 10Gb Ethernet - either X520-T2 or X540-T2
> - Tried Xen kernels from both xen.crc.id.au and CentoS 6 Xen repos
> - LACP bonding to connect to the NFS & iSCSI storage using Brocade
> VDX6740T fabric. MTU=9000

You said 3.x kernels specifically. The kernel on Xen Made Easy now is a
4.4 kernel.  Any chance you have tested with that one?

Did you ever try without MTU=9000 (default 1500 instead)?

I am having certain issues on certain hardware where there's no shutting
down the affected NICs.  Trying to do so or unload the igb module hangs
the entire box.  But in that case they're throwing AER errors instead of
just unit hangs:

pcieport :00:03.0: AER: Uncorrected (Non-Fatal) error received: id=
igb :04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
type=Transaction Layer, id=0401(Requester ID)
igb :04:00.1:   device [8086:10a7] error status/mask=4000/
igb :04:00.1:[14] Completion Timeout (First)
igb :04:00.1: broadcast error_detected message
igb :04:00.1: broadcast slot_reset message
igb :04:00.1: broadcast resume message
igb :04:00.1: AER: Device recovery successful

Spammed continuously.

Switching to Broadcom would be a possibility, though it's tricky because
two of the NICs are onboard, so we'd need to replace the dual-port 1G
card with a quad-port 1G card.  Since you're saying you're all 10G,
maybe you don't know, but if you have any specific Broadcom 1G cards
you've had good fortune with, I'd be interested in knowing which models.
 Broadcom cards are rarely labeled as such which makes finding them a
bit more difficult than Intel ones.

>>> There has to be something common.
>>
>> The NICs having issues are running a native VLAN, a tagged VLAN, iSCSI
>> and NFS traffic, as well as some basic management stuff over SSH, and
>> they are configured with an MTU of 9000 on the native VLAN.  It's a lot
>> of features, but I can't really turn them off and then actually have
>> enough load on the NICs to reproduce the issue.  Several of these
>> servers were installed and being burned in for 3 months without ever
>> having an issue, but suddenly collapsed when I 

[CentOS] [Fwd: The CentOS list]

[Valeri Galtsev]

Dear All,

Mark has problem sending mail to centos@centos.org list... He has trouble
with flash plugin on CentOS 6, please, take a look at his e-mail below.
I'll try to see what I can do to help, but what I can do definitely is no
match to Experts on this list.

Thanks in advance!

Valeri

 Original Message 
Subject: The CentOS list
From:m.r...@5-cent.us
Date:Mon, January 30, 2017 3:11 pm
To:  "Valeri Galtsev" 
--

Hi, Valeri,

   I've tried, twice, to post to the list today, and they neither show up,
*nor* do I get a blocked message - they just go to /dev/null.

   The second was just a test, the first was asking if anyone else was
seeing, with CentOS 6 (updated) flash-plugin crashing every 10-15 min.
And there's no downgrade for it.

   mark



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

Re: [CentOS-virt] NIC Stability Problems Under Xen 4.4 / CentOS 6 / Linux 3.18

[Kevin Stange]

On 01/30/2017 02:15 PM, Johnny Hughes wrote:
> On 01/30/2017 12:59 PM, Kevin Stange wrote:
>> On 01/30/2017 03:18 AM, Jinesh Choksi wrote:
 Are there other kernel options that might be useful to try?
>>>
>>> pci=nomsi
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/13
>>
>> Incidentally, already found that one and I'm trying it currently on one
>> of the boxes.  So far there's been no issues, but it's only been since
>> Friday.
>>
>> Also, I found this:
>>
>> https://xen.crc.id.au/support/guides/install/
>>
>> There's a 4.4 kernel here built for Xen Dom0, which I'm giving a whirl
>> to see how stable it is, also only since Friday.  I'm not using anything
>> else he's packaged from his repo.
>>
>> On a related note, does the SIG have plans to replace the 3.18 kernel
>> which is marked as projected EOL of January 2017
>> (https://www.kernel.org/category/releases.html)?
>>
> 
> I am currently working on a 4.4 kernel as a replacement for the 3.18
> kernel.  I have it working well no el7, but not yet working well on el6.
>  I hope to have something to release in the first 2 weeks of Feb. for
> testing.

What kind of issues are you having with 4.4?  Since I'm testing that
"Xen Made Easy" build of 4.4, are there any things I should watch out
for?  Might be worth looking at what he did for his builds to see if
that helps get yours working better.

http://au1.mirror.crc.id.au/repo/el6/SRPM/

-- 
Kevin Stange
Chief Technology Officer
Steadfast | Managed Infrastructure, Datacenter and Cloud Services
800 S Wells, Suite 190 | Chicago, IL 60607
312.602.2689 X203 | Fax: 312.602.2688
ke...@steadfast.net | www.steadfast.net
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] NIC Stability Problems Under Xen 4.4 / CentOS 6 / Linux 3.18

[Johnny Hughes]

On 01/30/2017 12:59 PM, Kevin Stange wrote:
> On 01/30/2017 03:18 AM, Jinesh Choksi wrote:
>>> Are there other kernel options that might be useful to try?
>>
>> pci=nomsi
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/13
> 
> Incidentally, already found that one and I'm trying it currently on one
> of the boxes.  So far there's been no issues, but it's only been since
> Friday.
> 
> Also, I found this:
> 
> https://xen.crc.id.au/support/guides/install/
> 
> There's a 4.4 kernel here built for Xen Dom0, which I'm giving a whirl
> to see how stable it is, also only since Friday.  I'm not using anything
> else he's packaged from his repo.
> 
> On a related note, does the SIG have plans to replace the 3.18 kernel
> which is marked as projected EOL of January 2017
> (https://www.kernel.org/category/releases.html)?
> 

I am currently working on a 4.4 kernel as a replacement for the 3.18
kernel.  I have it working well no el7, but not yet working well on el6.
 I hope to have something to release in the first 2 weeks of Feb. for
testing.



signature.asc
Description: OpenPGP digital signature
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] NIC Stability Problems Under Xen 4.4 / CentOS 6 / Linux 3.18

[Kevin Stange]

On 01/30/2017 03:18 AM, Jinesh Choksi wrote:
>>Are there other kernel options that might be useful to try?
> 
> pci=nomsi
> 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/13

Incidentally, already found that one and I'm trying it currently on one
of the boxes.  So far there's been no issues, but it's only been since
Friday.

Also, I found this:

https://xen.crc.id.au/support/guides/install/

There's a 4.4 kernel here built for Xen Dom0, which I'm giving a whirl
to see how stable it is, also only since Friday.  I'm not using anything
else he's packaged from his repo.

On a related note, does the SIG have plans to replace the 3.18 kernel
which is marked as projected EOL of January 2017
(https://www.kernel.org/category/releases.html)?

-- 
Kevin Stange
Chief Technology Officer
Steadfast | Managed Infrastructure, Datacenter and Cloud Services
800 S Wells, Suite 190 | Chicago, IL 60607
312.602.2689 X203 | Fax: 312.602.2688
ke...@steadfast.net | www.steadfast.net
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] tor and selinux

[Gordon Messmer]

On 01/29/2017 10:32 PM, Mark wrote:

That's strange, because I started the tor process simply with
sudo systemctl start tor



Yes, it looks like that package runs the service as "root".  That 
doesn't seem like a good default, and it could be a packaging bug.  Try 
adding "User toranon" to the configuration file and see if things work.  
If so, file a bug so that the maintainer can change the default.


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

[CentOS] Strange ABRT error when I try to switch to su

[Sean Son]

Hello all

One of my VMs, running RHEL 7, has been giving me the following ABRT error
when I try to login as su Ive seen this error the past three times that
Ive logged in. I know that the VM is using Red Hat,but seeing that
RHEL/CentOS are pretty much the same thing, I figured I should ask the
CentOS mailing list for help. Here is the error:

$ su
Password:
ABRT has detected 1 problem(s). For more info run: abrt-cli list --since
1485781

# abrt-cli list --since 1485781
id b35dcbc9f05781fab04cdd9aca28bbe86a93eace
reason: php-fpm killed by SIGSEGV
time:   Wed 25 Jan 2017 07:44:07 PM EST
cmdline:'php-fpm: pool www' '' '' '' '' '' '' '' '' '' '' '' '' ''
'' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' ''
package:rh-php56-php-fpm-5.6.5-9.el7
uid:48 (apache)
count:  4
Directory:  /var/spool/abrt/ccpp-2017-01-25-19:44:07-47637
Run 'abrt-cli report /var/spool/abrt/ccpp-2017-01-25-19:44:07-47637' for
creating a case in Red Hat Customer Portal

id 27190e6535600b6fc4bc97de457b302a10698b95
reason: WARNING: at lib/vsprintf.c:1734 vsnprintf+0x691/0x6a0()
time:   Mon 01 Aug 2016 09:14:44 AM EDT
cmdline:BOOT_IMAGE=/vmlinuz-3.10.0-327.22.2.el7.x86_64
root=/dev/mapper/VolGroup00-LogVol00 ro rd.lvm.lv=VolGroup00/LogVol00
vconsole.keymap=us vconsole.font=latarcyrheb-sun16 crashkernel=auto audit=1
rhgb quiet biosdevname=0 net.ifnames=0 LANG=en_US.UTF-8
package:kernel
uid:0 (root)
count:  1
Directory:  /var/spool/abrt/oops-2016-08-01-09:14:44-8775-0
Reported:   cannot be reported



What is this error trying to say and how do I fix the issue?


All help is greatly appreciated!


Thank you

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

[CentOS] Centos 7 as a Hyper-V guest and Integration Services

[Adrian Jenzer]

Dear all

I'm running a Centos 7.3 as a Hyper-V guest on Windows Server 2012R2. Actually 
everything works fine but I'm still wondering if I do everything right 
regarding Linux Integration Services.

When I installed Centos 7 I didn't installed any LIS package or so as I 
understood it's built-in.
How are you handling this?
Is it recommended to install/update to the latest LIS from Microsoft provided 
as ISO or do I need to install the hyperv-daemons?


Currently my system reports:
[root@share ~]# lsmod | grep hv
hv_utils   24418  2
hv_storvsc 18032  6
hv_netvsc  40261  0
hv_vmbus  397185  6 
hyperv_keyboard,hv_netvsc,hid_hyperv,hv_utils,hyperv_fb,hv_storvsc

and I think this time shifts on rebbots are related to missing LIS (?):
[root@share ~]# last
root pts/0172.16.4.103   Mon 
Jan 30 12:14   still logged in
(unknown :0   :0
Sun Jan 29 03:59   still logged in
reboot   system boot  3.10.0-514.6.1.eFri Feb  3 15:55 - 
12:14 (-4+-3:-41)
root pts/0172.16.4.128   Fri 
Jan 27 15:24 - 15:57  (00:33)
root pts/0172.16.4.128   Fri 
Jan 27 12:22 - 12:49  (00:27)
root pts/0172.16.4.128   Mon 
Jan 23 13:53 - 14:00  (00:07)
(unknown :0   :0
Mon Jan 23 13:53 - 02:00 (5+12:06)
reboot   system boot  3.10.0-514.6.1.eTue Jan 24 23:41 - 
02:00 (4+02:18)
root pts/0172.16.4.128   Mon 
Jan 23 13:36 - down   (00:15)
administ pts/0172.16.4.128  Mon Jan 23 
12:44 - 13:00  (00:15)
(unknown :0   :0
Sun Jan 22 03:56 - 13:52 (1+09:55)
reboot   system boot  3.10.0-514.2.2.eFri Jan 27 17:31 - 
13:52 (-4+-3:-38)
root pts/1172.16.4.117   Mon 
Jan 16 12:20 - 13:28  (01:07)

Do you also get this Warnings in Hyper-V Event Viewer?:

Device 'Microsoft Synthetic Display Controller' in 'SHARE' is loaded but has a 
different version from the server.  Server version 3.3 Client version 3.2 
(Virtual machine ID C2D0C208-BC00-4E73-8AF1-DA595FE6ECE7). The device will 
work, but this is an unsupported configuration. This means that technical 
support will not be provided until this problem is resolved. To fix this 
problem, upgrade the integration services. To upgrade, connect to the virtual 
machine and select Insert Integration Services Setup Disk from the Action menu.


Thanks
best
Adrian

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

Re: [CentOS-virt] Selinux Problem

[George Dunlap]

On Thu, Jan 26, 2017 at 8:08 PM, Günther J. Niederwimmer
 wrote:
> Hello,
>
> Am Donnerstag, 26. Januar 2017, 10:54:20 CET schrieb Johnny Hughes:
>> On 01/26/2017 10:06 AM, Günther J. Niederwimmer wrote:
>> > Hello,
>> >
>> > CentOS 7.(3) Xen 4.4,
>> >
>> > Can I find any Doc for selinux with XEN, I found many Problems with
>> > selinux on Dom0 ?
>> >
>> > Or have I to disable selinux when I install XEN.
>> >
>> > Thank's for a answer.
>>
>> We have not tried to make xen work with selinux on Dom0 .. in fact our
>> documentation:
>>
>> https://wiki.centos.org/Manuals/ReleaseNotes/Xen4-01
>>
>>  says:
>>
>> SELinux support is disabled, and you might need to disable SELinux on
>> the dom0 for some operations; primarily when using qemu-xen and blktap
>> backed storage.
>
> This is not the best Situation, but when I have no other way I have to disable
> selinux :-(.

I think that comment may be a little old.  I do try to support SELinux
-- the smoke tests I use before pushing changes have it enabled by
default, and they use both qemu-xen and blktap.

But it's difficult to help debug problems when you haven't even said
what problem(s) you're having. :-)

Please be sure to include the output of `dmesg`, `xl dmesg`, your
xl.cfg, and /var/log/audit/audit.log.

Thanks,
 -George
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] NIC Stability Problems Under Xen 4.4 / CentOS 6 / Linux 3.18

[Jinesh Choksi]

>Are there other kernel options that might be useful to try?

pci=nomsi

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/13



On 27 January 2017 at 18:21, Kevin Stange  wrote:

> On 01/27/2017 06:08 AM, Karel Hendrych wrote:
> > Have you tried to eliminate all power management features all over?
>
> I've been trying to find and disable all power management features but
> having relatively little luck with that solving the problems.  Stabbing
> the the dark I've tried different ACPI settings, including completely
> disabling it, disabling CPU frequency scaling, and setting pcie_aspm=off
> on the kernel command line.  Are there other kernel options that might
> be useful to try?
>
> > Are the devices connected to the same network infrastructure?
>
> There are two onboard NICs and two NICs on a dual-port card in each
> server.  All devices connect to a cisco switch pair in VSS and the links
> are paired in LACP.
>
> > There has to be something common.
>
> The NICs having issues are running a native VLAN, a tagged VLAN, iSCSI
> and NFS traffic, as well as some basic management stuff over SSH, and
> they are configured with an MTU of 9000 on the native VLAN.  It's a lot
> of features, but I can't really turn them off and then actually have
> enough load on the NICs to reproduce the issue.  Several of these
> servers were installed and being burned in for 3 months without ever
> having an issue, but suddenly collapsed when I tried to bring 20 or so
> real-world VMs up on them.
>
> The other NICs in the system that are connected don't exhibit issues and
> run only VM network interfaces.  They are also in LACP and running VLAN
> tags, but normal 1500 MTU.
>
> So far it seems to correlate with NICs on the expansion cards, but it's
> a coincidence that these cards are the ones with the storage and
> management traffic.  I'm trying to swap some of this load to the onboard
> NICs to see if the issues migrate over with it, or if they stay with the
> expansion cards.
>
> If the issue exists on both NIC types, then it rules out the specific
> NIC chipset as the culprit.  It could point to the driver, but upgrading
> it to a newer version did not help and actually appeared to make
> everything worse.  This issue might actually be more to do with the PCIe
> bridge than the NICs, but these are still different motherboards with
> different PCIe bridges (5520 vs C600) experiencing the same issues.
>
> > I've been using Intel NICs with Xen/CentOS for ages with no issues.
>
> I figured that must be so.  Everyone uses Intel NICs.  If this was a
> common issue, it would probably be causing a lot of people a lot of
> trouble.
>
> --
> Kevin Stange
> Chief Technology Officer
> Steadfast | Managed Infrastructure, Datacenter and Cloud Services
> 800 S Wells, Suite 190 | Chicago, IL 60607
> 312.602.2689 X203 | Fax: 312.602.2688
> ke...@steadfast.net | www.steadfast.net
> ___
> CentOS-virt mailing list
> CentOS-virt@centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
>
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt