Re: [CentOS] 10 Gbps adapter recommendation

[Karanbir Singh]

On 11/11/2014 11:51 AM, Nux! wrote:
> Thanks Gotz,
> 
> I'll definitely do some storage on them, Gluster/DRBD/ISCSI, but also general 
> traffic; I just want to replace 1 Gbps as much as possible, budgets allows.
> 

lots of infiniband stuff, 20gbps grade, exceptionally cheap off ebay.


-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Network menu doesn't appear on system menu on CentOS 6.6

[John Doe]

From: Gilbert Sebenste 

> On Mon, 10 Nov 2014, Frank Cox wrote:
>>  yum install nm-connection-editor
> Yeah, I'm having a tough day, THAT is where it should be found,
> but isn't, under Gnome, on this one machine. Typing what you did above
> gave me an error of "no such package". I then tried yum install
> *connection* and yum install *editor* and nothing came up that matches
> what I need.

# rpm -qf /usr/bin/nm-connection-editor
NetworkManager-gnome-0.8.1-75.el6.x86_64

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

[CentOS] CentOS-announce Digest, Vol 117, Issue 6

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CEBA-2014:1830 CentOS 6 389-ds-base BugFix Update (Johnny Hughes)
   2. CESA-2014:1826 Moderate CentOS 6 libvncserver Security Update
  (Johnny Hughes)
   3. CESA-2014:1843 Important CentOS 6 kernel Security Update
  (Johnny Hughes)
   4. CEBA-2014:1828  CentOS 7 ipa BugFix Update (Johnny Hughes)
   5. CEBA-2014:1838 CentOS 7 resource-agents BugFixUpdate
  (Johnny Hughes)
   6. CEEA-2014:1839 CentOS 7 hpsa Enhancement Update (Johnny Hughes)
   7. CEBA-2014:1840  CentOS 7 corosync BugFix Update (Johnny Hughes)
   8. CESA-2014:1827 Moderate CentOS 7 kdenetwork   Security Update
  (Johnny Hughes)
   9. CEEA-2014:1839 CentOS 7 hpsa Enhancement Update (Johnny Hughes)


--

Message: 1
Date: Tue, 11 Nov 2014 18:35:53 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CEBA-2014:1830 CentOS 6 389-ds-base BugFix
Update
Message-ID: <2014183553.ga2...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2014:1830 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1830.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
598b9c7bcdd7d03a53c8899dce8971f572fbef57aa354cd3c6c48bf2b1d6cbe5  
389-ds-base-1.2.11.15-48.el6_6.i686.rpm
5dba5b47c36830686f1d7514cf3c45fdce59775bf20323dfc6624926f7e039c8  
389-ds-base-devel-1.2.11.15-48.el6_6.i686.rpm
d0a6aa276bcbeb90a532c63043d60965ed44a95ce06b52f8b77987fa674ff8f7  
389-ds-base-libs-1.2.11.15-48.el6_6.i686.rpm

x86_64:
70b26cfa45e124b5e9c365df809137b2311dd778b472fa27a605ed0f03d2de98  
389-ds-base-1.2.11.15-48.el6_6.x86_64.rpm
5dba5b47c36830686f1d7514cf3c45fdce59775bf20323dfc6624926f7e039c8  
389-ds-base-devel-1.2.11.15-48.el6_6.i686.rpm
392a5802599973ebb2438d406d1fc164ab45877895e20ccfa0866b900b6c01f3  
389-ds-base-devel-1.2.11.15-48.el6_6.x86_64.rpm
d0a6aa276bcbeb90a532c63043d60965ed44a95ce06b52f8b77987fa674ff8f7  
389-ds-base-libs-1.2.11.15-48.el6_6.i686.rpm
f0f1c4306530146674c7f0cc80f80d96ab58410cd911678d7ddab8006559f353  
389-ds-base-libs-1.2.11.15-48.el6_6.x86_64.rpm

Source:
49d58c1b04e66ff35d3070e8f071a5fc0d59857fead6db4840245e61ba779103  
389-ds-base-1.2.11.15-48.el6_6.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 2
Date: Tue, 11 Nov 2014 18:36:28 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2014:1826 Moderate CentOS 6
libvncserverSecurity Update
Message-ID: <2014183628.ga2...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2014:1826 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1826.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
0716f57168140f6062b8cdb0efc7c601ffa3fe81855f759d3e2733d5b7d7a355  
libvncserver-0.9.7-7.el6_6.1.i686.rpm
266355a2ec31bea7285f3a530991345604875e1662bcbcfd200be9d8876f4e7d  
libvncserver-devel-0.9.7-7.el6_6.1.i686.rpm

x86_64:
0716f57168140f6062b8cdb0efc7c601ffa3fe81855f759d3e2733d5b7d7a355  
libvncserver-0.9.7-7.el6_6.1.i686.rpm
2c8f243f3b7de8151b420b84178764b8f19bd64c510dec6f6d95c8f7b8838086  
libvncserver-0.9.7-7.el6_6.1.x86_64.rpm
266355a2ec31bea7285f3a530991345604875e1662bcbcfd200be9d8876f4e7d  
libvncserver-devel-0.9.7-7.el6_6.1.i686.rpm
5134ca78f7182719b16a45f8a33b576d108dee4f4b4de10ddc92e10e8e73cafe  
libvncserver-devel-0.9.7-7.el6_6.1.x86_64.rpm

Source:
7d83f556540cd4df5e71bc1be7f4106483c604c95da62af25f4dc0c3894d060a  
libvncserver-0.9.7-7.el6_6.1.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 3
Date: Tue, 11 Nov 2014 19:31:00 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2014:1843 Important CentOS 6 kernel
SecurityUpdate
Message-ID: <2014193100.ga4...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2014:1843 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1843.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filen

Re: [CentOS] Network menu doesn't appear on system menu on CentOS 6.6

[Nicolas Thierry-Mieg]

On 11/12/2014 12:10 PM, John Doe wrote:

From: Gilbert Sebenste 


On Mon, 10 Nov 2014, Frank Cox wrote:

  yum install nm-connection-editor

Yeah, I'm having a tough day, THAT is where it should be found,
but isn't, under Gnome, on this one machine. Typing what you did above
gave me an error of "no such package". I then tried yum install
*connection* and yum install *editor* and nothing came up that matches
what I need.


# rpm -qf /usr/bin/nm-connection-editor
NetworkManager-gnome-0.8.1-75.el6.x86_64


or if you don't have it installed somewhere, you can:
yum whatprovides '*/nm-connection-editor'
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Keepalived - spurious failovers

[John Horne]

Hello,

We are using CentOS 6.6 and keepalived 1.2.13 on two servers for
failover, no load-balancing. Failover is governed by the NIC being
present, and the Apache and Tomcat processes being present. Both servers
are configured as 'EQUAL' (not master/backup). An initial priority of
100 is set, and if a process or NIC fails, then this is reduced by 60 -
causing a lower priority to be seen and failover to take place.
Generally this works well. If we stop the network or one of the
processes, this is logged (to /var/log/messages) and failover happens
within a few seconds.

However, we have had failovers occur during the night several times. It
happened last night, and the night before. Nothing was logged in the
messages file about the NIC being down, or the Apache/Tomcat processes
being unavailable. Nothing was logged by the Apache or Tomcat processes
in their own log files. The failovers have happened at 03:56 on both
nights.

The most obvious suspect causing this would be some nighttime process
such as log rotation or automatic updates. However, I can see nothing
obvious occurring during the night that would cause the keepalived
virtual interface to failover.

The messages log file typically shows:

On the previous master, now slave server...
===
Nov 12 03:56:40 bill Keepalived_vrrp[27279]: VRRP_Instance(Shib_srvrs)
Transition to MASTER STATE
Nov 12 03:56:43 bill Keepalived_vrrp[27279]: VRRP_Instance(Shib_srvrs)
Entering MASTER STATE
Nov 12 03:56:43 bill Keepalived_vrrp[27279]: VRRP_Instance(Shib_srvrs)
setting protocol VIPs.
Nov 12 03:56:43 bill Keepalived_vrrp[27279]: VRRP_Instance(Shib_srvrs)
Sending gratuitous ARPs on eth0 for xxx.xxx.xxx.xxx
Nov 12 03:56:48 bill Keepalived_vrrp[27279]: VRRP_Instance(Shib_srvrs)
Sending gratuitous ARPs on eth0 for xxx.xxx.xxx.xxx
Nov 12 03:56:51 bill Keepalived_vrrp[27279]: VRRP_Instance(Shib_srvrs)
Received higher prio advert
Nov 12 03:56:51 bill Keepalived_vrrp[27279]: VRRP_Instance(Shib_srvrs)
Entering BACKUP STATE
Nov 12 03:56:51 bill Keepalived_vrrp[27279]: VRRP_Instance(Shib_srvrs)
removing protocol VIPs.
==

On the previous slave, now master server, there is nothing logged at (or
around) this time at all.

As the previous master log shows it 'Received higher prio advert'. But
that implies that the priority on the server is lower, and no indication
why.

Has anyone seen this themselves? Or have any idea why it may be
occurring? As said, some nighttime process seems to be the cause, but I
cannot think or find anything that would cause it.



Thanks,

John.

-- 
John Horne   Tel: +44 (0)1752 587287
Plymouth University, UK

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

Re: [CentOS] To James B. Byrne

[James B. Byrne]

On Tue, November 11, 2014 13:05, Alexander Farber wrote:
> And ignore the Chrome people getting
> the certificate warning at https://harte-lyne.ca too ;-)
>

We operate our own CA.  If you 'TRUST' us then you can add the the root cert
for our CA by visiting  http://ca.harte-lyne.ca/CA_HLL_ISSUER_01/ca.crt and
accepting the cert (presumably after reading the CP and CPS statements).  Then
the warning will disappear.  If not then you can leave or proceed, accepting
the exception permanently or not,  as your inclination dictates.

That web site is ancient and was designed for straight http access. It is in
the process of revision but that is not in my hands and given past events I
have no expectation of anything changing soon.  We have since gone to "https
everywhere" and thus the certificate is now an issue.  Most of our sites are
blocked to outside access or require authentication in any case.

That said, the issue of Trusted certificates is problematic. In my opinion,
the present state of the PKI CA's is in such disarray that anyone that is
counting on the 'Trusted' CA's that come pre-installed in browser packages is
living in blissful ignorance of the underlying risks presented thereby. Users
are rarely aware, or realise the implications, of the fact that any 'Trusted'
CA can issue a valid certificate for ANY domain. Any browser that 'Trusts'
that CA will accept any site presenting said certificate as legitimate.  This
is the singular weakness of imposing a hierarchical requirement on top of a
distributed solution.  DNSSEC is representative of the alternative approach
that I believe eventually will be adopted for all forms of network identities,
including email.

Our company policy at the moment does not properly address the Trusted CA
issue either;  Other than we have set up and exclusively use our own CA for
our own use.  I am pushing to have all default trusted roots removed from all
user's browsers and only approved roots added back.  This is not feasible at
the present time because of the lack of any automated tool (of which I am
aware and that is FLOSS) to enforce it.

For that matter, we are still waiting for our registrar to support DNSSEC, for
which we have been ready since early 2012 and the .ca. registrar since 2013.


-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@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

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

Re: [CentOS] To James B. Byrne

[James B. Byrne]

On Tue, November 11, 2014 19:33, Igor Zubkov wrote:
> On Tue, Nov 11, 2014 at 6:16 PM, Alexander Farber wrote:
>> Dear James,
>>
>> everyday I look into my Gmail SPAM folder and your mails (sent to
>> Centos list) are there. Noone else is there but you.
>>
>> Please finally fix your MX records or whatever is needed. No offence
>
> I bit a tired of this too.
>
> James, be the Man and fix your mail server. Or what else.
>
>> Greetings from Germany
>> Alex
>
> Greetins from Ukraine (Donetsk).
>

But, the mail server is not broken.  It is entirely to RFC specifications. 
Google decides how to treat the resulting confusion respecting mail forwarded
by the CentOS list. Yahoo I understand simply drops it into the bit bucket and
the recipient never knows.

Your complaint would be better directed at the consortium of Email providers,
including Google and Yahoo, who forced DMARC on the IETF; or rather entirely
by-passed the IETF and put this Rube Goldberg hack into play regardless.  The
people who run mailing lists screamed blue murder but it happened nonetheless.

In any case the fix to this for Mailman already exists.  It just needs to be
accepted by RedHat and rolled out as an update.  I tried to build it myself
and succeeded in getting a working version on CentOS6.  But, the source
package layout does not fit the HFS used by RedHat and I could not deploy it
for that reason.  Nor could I figure out the patches necessary to restructure
the project layout into something resembling HFS.  Nor could I figure out the
interim changes between the current Mailman version and that shipped with
CentOS to back-port the fixes in a systematic way.

I apologise for the number of messages presently originating from me.  This
one included.  Once I get past my ignorance with CentOS7 and can manage on my
own I will stop annoying the list with questions and replies.

-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@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

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

Re: [CentOS] To James B. Byrne

[Valeri Galtsev]

On Wed, November 12, 2014 8:26 am, James B. Byrne wrote:
>
> On Tue, November 11, 2014 13:05, Alexander Farber wrote:
>> And ignore the Chrome people getting
>> the certificate warning at https://harte-lyne.ca too ;-)
>>
>
> We operate our own CA.

Yes, that is what I was doing for years too (till we got access to Certs
paid by central university IT office). Mostly those who are harassing you
on this list seem to have much less knowledge on each of the subjects than
you do. It is just my observation. Not that I'm saying everybody using
gmail, but, of course, knowledgeable ones do not make any noise. It
somehow comes to my mind what I've heard once (not intended to offend
anyone but if you think about it it carries some wisdom, - for me at
least): "Never argue with the fool, or others will not notice any
difference between you two".

Valeri

> If you 'TRUST' us then you can add the the root
> cert
> for our CA by visiting  http://ca.harte-lyne.ca/CA_HLL_ISSUER_01/ca.crt
> and
> accepting the cert (presumably after reading the CP and CPS statements).
> Then
> the warning will disappear.  If not then you can leave or proceed,
> accepting
> the exception permanently or not,  as your inclination dictates.
>
> That web site is ancient and was designed for straight http access. It is
> in
> the process of revision but that is not in my hands and given past events
> I
> have no expectation of anything changing soon.  We have since gone to
> "https
> everywhere" and thus the certificate is now an issue.  Most of our sites
> are
> blocked to outside access or require authentication in any case.
>
> That said, the issue of Trusted certificates is problematic. In my
> opinion,
> the present state of the PKI CA's is in such disarray that anyone that is
> counting on the 'Trusted' CA's that come pre-installed in browser packages
> is
> living in blissful ignorance of the underlying risks presented thereby.
> Users
> are rarely aware, or realise the implications, of the fact that any
> 'Trusted'
> CA can issue a valid certificate for ANY domain. Any browser that 'Trusts'
> that CA will accept any site presenting said certificate as legitimate.
> This
> is the singular weakness of imposing a hierarchical requirement on top of
> a
> distributed solution.  DNSSEC is representative of the alternative
> approach
> that I believe eventually will be adopted for all forms of network
> identities,
> including email.
>
> Our company policy at the moment does not properly address the Trusted CA
> issue either;  Other than we have set up and exclusively use our own CA
> for
> our own use.  I am pushing to have all default trusted roots removed from
> all
> user's browsers and only approved roots added back.  This is not feasible
> at
> the present time because of the lack of any automated tool (of which I am
> aware and that is FLOSS) to enforce it.
>
> For that matter, we are still waiting for our registrar to support DNSSEC,
> for
> which we have been ready since early 2012 and the .ca. registrar since
> 2013.
>
>
> --
> ***  E-Mail is NOT a SECURE channel  ***
> James B. Byrnemailto:byrn...@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
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://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
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] To James B. Byrne

[Valeri Galtsev]

On Wed, November 12, 2014 8:50 am, James B. Byrne wrote:
>
> On Tue, November 11, 2014 19:33, Igor Zubkov wrote:
>> On Tue, Nov 11, 2014 at 6:16 PM, Alexander Farber wrote:
>>> Dear James,
>>>
>>> everyday I look into my Gmail SPAM folder and your mails (sent to
>>> Centos list) are there. Noone else is there but you.
>>>
>>> Please finally fix your MX records or whatever is needed. No offence
>>
>> I bit a tired of this too.
>>
>> James, be the Man and fix your mail server. Or what else.
>>
>>> Greetings from Germany
>>> Alex
>>
>> Greetins from Ukraine (Donetsk).
>>

As I said, James, don't argue with the ones who have no idea what they are
talking about (sorry for posting above your reply to him). This particular
one did set me off, and the only thing that held me from answering him was
the "wisdom" I mentioned in another reply.

Valeri

>
> But, the mail server is not broken.  It is entirely to RFC specifications.
> Google decides how to treat the resulting confusion respecting mail
> forwarded
> by the CentOS list. Yahoo I understand simply drops it into the bit bucket
> and
> the recipient never knows.
>
> Your complaint would be better directed at the consortium of Email
> providers,
> including Google and Yahoo, who forced DMARC on the IETF; or rather
> entirely
> by-passed the IETF and put this Rube Goldberg hack into play regardless.
> The
> people who run mailing lists screamed blue murder but it happened
> nonetheless.
>
> In any case the fix to this for Mailman already exists.  It just needs to
> be
> accepted by RedHat and rolled out as an update.  I tried to build it
> myself
> and succeeded in getting a working version on CentOS6.  But, the source
> package layout does not fit the HFS used by RedHat and I could not deploy
> it
> for that reason.  Nor could I figure out the patches necessary to
> restructure
> the project layout into something resembling HFS.  Nor could I figure out
> the
> interim changes between the current Mailman version and that shipped with
> CentOS to back-port the fixes in a systematic way.
>
> I apologise for the number of messages presently originating from me.
> This
> one included.  Once I get past my ignorance with CentOS7 and can manage on
> my
> own I will stop annoying the list with questions and replies.
>
> --
> ***  E-Mail is NOT a SECURE channel  ***
> James B. Byrnemailto:byrn...@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
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://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
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Keepalived - spurious failovers

[John Horne]

On Wed, 2014-11-12 at 10:27 -0500, m.r...@5-cent.us wrote:
> John Horne wrote:
> >
> > We are using CentOS 6.6 and keepalived 1.2.13 on two servers for
> > failover, no load-balancing. Failover is governed by the NIC being
> > present, and the Apache and Tomcat processes being present. Both servers
> > are configured as 'EQUAL' (not master/backup). An initial priority of
> > 100 is set, and if a process or NIC fails, then this is reduced by 60 -
> > causing a lower priority to be seen and failover to take place.
> > Generally this works well. If we stop the network or one of the
> > processes, this is logged (to /var/log/messages) and failover happens
> > within a few seconds.
> >
> > However, we have had failovers occur during the night several times. It
> > happened last night, and the night before. Nothing was logged in the
> > messages file about the NIC being down, or the Apache/Tomcat processes
> > being unavailable. Nothing was logged by the Apache or Tomcat processes
> > in their own log files. The failovers have happened at 03:56 on both
> > nights.
> >
> > The most obvious suspect causing this would be some nighttime process
> > such as log rotation or automatic updates. However, I can see nothing
> > obvious occurring during the night that would cause the keepalived
> > virtual interface to failover.
> 
> I trust you've looked at the crontab, and /etc/cron.daily, etc.
>
Yes. Nothing obvious that would cause a problem to apache/tomcat or the
network.

> The other option: have you looked *outside* the systems? Do you have a
> cable between the two, or is it over the network? Is there a network
> thing going on? For example, are the servers on a UPS, and the switch
> they're on not on one?
> 
They are both virtual servers - so no UPS. Failover communication is
over the network.



John.

-- 
John Horne   Tel: +44 (0)1752 587287
Plymouth University, UK

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

Re: [CentOS] Keepalived - spurious failovers

[Richard Mann]

+1 to your logrotate thought; I'd dig deeper there.

check /var/lib/logrotate.status; see if it doesn't match up with days the 
failover happens, that different httpd logs are rotating.  


-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of 
John Horne
Sent: Wednesday, November 12, 2014 10:36 AM
To: CentOS mailing list
Subject: Re: [CentOS] Keepalived - spurious failovers

On Wed, 2014-11-12 at 10:27 -0500, m.r...@5-cent.us wrote:
> John Horne wrote:
> >
> > We are using CentOS 6.6 and keepalived 1.2.13 on two servers for
> > failover, no load-balancing. Failover is governed by the NIC being
> > present, and the Apache and Tomcat processes being present. Both servers
> > are configured as 'EQUAL' (not master/backup). An initial priority of
> > 100 is set, and if a process or NIC fails, then this is reduced by 60 -
> > causing a lower priority to be seen and failover to take place.
> > Generally this works well. If we stop the network or one of the
> > processes, this is logged (to /var/log/messages) and failover happens
> > within a few seconds.
> >
> > However, we have had failovers occur during the night several times. It
> > happened last night, and the night before. Nothing was logged in the
> > messages file about the NIC being down, or the Apache/Tomcat processes
> > being unavailable. Nothing was logged by the Apache or Tomcat processes
> > in their own log files. The failovers have happened at 03:56 on both
> > nights.
> >
> > The most obvious suspect causing this would be some nighttime process
> > such as log rotation or automatic updates. However, I can see nothing
> > obvious occurring during the night that would cause the keepalived
> > virtual interface to failover.
> 
> I trust you've looked at the crontab, and /etc/cron.daily, etc.
>
Yes. Nothing obvious that would cause a problem to apache/tomcat or the
network.

> The other option: have you looked *outside* the systems? Do you have a
> cable between the two, or is it over the network? Is there a network
> thing going on? For example, are the servers on a UPS, and the switch
> they're on not on one?
> 
They are both virtual servers - so no UPS. Failover communication is
over the network.



John.

-- 
John Horne   Tel: +44 (0)1752 587287
Plymouth University, UK

___
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] To James B. Byrne

[Les Mikesell]

On Wed, Nov 12, 2014 at 8:50 AM, James B. Byrne  wrote:
>
> But, the mail server is not broken.  It is entirely to RFC specifications.
> Google decides how to treat the resulting confusion respecting mail forwarded
> by the CentOS list. Yahoo I understand simply drops it into the bit bucket and
> the recipient never knows.
>
> Your complaint would be better directed at the consortium of Email providers,
> including Google and Yahoo, who forced DMARC on the IETF; or rather entirely
> by-passed the IETF and put this Rube Goldberg hack into play regardless.  The
> people who run mailing lists screamed blue murder but it happened nonetheless.

If this is something caused by google and not your own server settings
that indicate how to treat forwarders, why doesn't email originating
from gmail have the same issue?

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Not To James B. Byrne

[Kai Schaetzl]

That's ridiculous, you don't even know what's wrong or if it's wrong at 
all or what you want him to do but you have to cry it out loud to the list 
to put social pressure on him. Please move this to private mail and 
understand that Gmail is *not* what rules email best practice and also try 
to understand what Gmail is telling *you* before you ask others to do 
something.


Kai


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

Re: [CentOS] Not To James B. Byrne

[Valeri Galtsev]

On Wed, November 12, 2014 9:46 am, Kai Schaetzl wrote:
> That's ridiculous, you don't even know what's wrong or if it's wrong at
> all or what you want him to do but you have to cry it out loud to the list
> to put social pressure on him. Please move this to private mail and
> understand that Gmail is *not* what rules email best practice and also try
> to understand what Gmail is telling *you* before you ask others to do
> something.
>
>
> Kai

+1
Bravo.

Valeri


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
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Not To James B. Byrne

[Les Mikesell]

On Wed, Nov 12, 2014 at 9:46 AM, Kai Schaetzl  wrote:
> That's ridiculous, you don't even know what's wrong or if it's wrong at
> all or what you want him to do but you have to cry it out loud to the list
> to put social pressure on him.

Well, no.  Per the headers:

Authentication-Results: mx.google.com;
   spf=neutral (google.com: centos-boun...@centos.org does not
designate permitted sender hosts) smtp.mail=centos-boun...@centos.org;
   dkim=neutral (body hash did not verify) header.i=@;
   dmarc=fail (p=QUARANTINE dis=NONE) header.from=harte-lyne.ca


The p=quarantine setting from his server explicitly requests that the
message be marked as spam if it s not sent from an authorized server,
which don't include the centos list server. So it is accepted and
dropped in the spam folder as requested.

And at the moment, he is the only list member that posts regularly
from a server with this setting.  (We don't even see ones with
p=reject, they'll bounce and get kicked off the list).

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Keepalived - spurious failovers

[John Horne]

On Wed, 2014-11-12 at 11:12 -0500, m.r...@5-cent.us wrote:
> John Horne wrote:

> >>
> > They are both virtual servers - so no UPS. Failover communication is
> > over the network.
> 
> Um, bingo: are the host systems on UPS's? What happens on the *host*
> systems at 03:56? They don't, perhaps, take snapshots of the guests then?
> 
No, no snapshots are taken. As said this is a spurious event which has
happened at 03:56 for the past two nights. However, we ran for a few
days before then with no problems. Before that it happened at something
like 5AM. It does not happen every night, nor at the same time
(usually).

I have set up a couple of cronjobs to check ifconfig and ping the
interface every few seconds. I also have a job that will monitor the
main interface for VRRP traffic since that should show what the priority
value is when a server claims to have received a higher priority from
another server.




John.

-- 
John Horne   Tel: +44 (0)1752 587287
Plymouth University, UK

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

Re: [CentOS] To James B. Byrne

[John Hoe]

On Wed, Nov 12, 2014 at 11:44 PM, Les Mikesell 
wrote:

> On Wed, Nov 12, 2014 at 8:50 AM, James B. Byrne 
> wrote:
> >
> > But, the mail server is not broken.  It is entirely to RFC
> specifications.
> > Google decides how to treat the resulting confusion respecting mail
> forwarded
> > by the CentOS list. Yahoo I understand simply drops it into the bit
> bucket and
> > the recipient never knows.
> >
> > Your complaint would be better directed at the consortium of Email
> providers,
> > including Google and Yahoo, who forced DMARC on the IETF; or rather
> entirely
> > by-passed the IETF and put this Rube Goldberg hack into play
> regardless.  The
> > people who run mailing lists screamed blue murder but it happened
> nonetheless.
>
> If this is something caused by google and not your own server settings
> that indicate how to treat forwarders, why doesn't email originating
> from gmail have the same issue?
>
> --
>Les Mikesell
>  lesmikes...@gmail.com
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>

​I guess the upside to all these  feedback is I learnt something about
standards, and how futile they can be sometimes.

Yeah we've followed the RFCs, yes there's DMARC serving its own purposes,
yes there's some mangling and yes there's a fix for it, but if the main
party (RH in this case) refuses to budge, shit remains broken. I'm not
pointing fingers at anyone but I'm not surprised why we haven't colonised
mars yet.

​I personally find it annoying that James is getting stuffed into spam box
_all_ the time, but with all these explanations I've gotten I think I got
the better end of the bargain.




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

Re: [CentOS] Not To James B. Byrne

[Les Mikesell]

On Wed, Nov 12, 2014 at 10:13 AM, Les Mikesell  wrote:
> On Wed, Nov 12, 2014 at 9:46 AM, Kai Schaetzl  wrote:
>> That's ridiculous, you don't even know what's wrong or if it's wrong at
>> all or what you want him to do but you have to cry it out loud to the list
>> to put social pressure on him.
>
> Well, no.  Per the headers:
>
> Authentication-Results: mx.google.com;
>spf=neutral (google.com: centos-boun...@centos.org does not
> designate permitted sender hosts) smtp.mail=centos-boun...@centos.org;
>dkim=neutral (body hash did not verify) header.i=@;
>dmarc=fail (p=QUARANTINE dis=NONE) header.from=harte-lyne.ca
>
>
> The p=quarantine setting from his server explicitly requests that the
> message be marked as spam if it s not sent from an authorized server,
> which don't include the centos list server. So it is accepted and
> dropped in the spam folder as requested.
>
> And at the moment, he is the only list member that posts regularly
> from a server with this setting.  (We don't even see ones with
> p=reject, they'll bounce and get kicked off the list).
>

I guess that last part isn't true.  Apparently forwarded yahoo senders
also go to spam instead of bouncing:

Authentication-Results: mx.google.com;
   spf=neutral (google.com: centos-boun...@centos.org does not
designate permitted sender hosts) smtp.mail=centos-boun...@centos.org;
   dkim=neutral (body hash did not verify) header.i=@;
   dmarc=fail (p=REJECT dis=NONE) header.from=yahoo.com

Anyway, you can see a domain's dmarc setting with:
nslookup -type=txt _dmarc.domain.com
and see the p= meanings at http://www.dmarc.org/faq.html
In particular, see http://www.dmarc.org/faq.html#r_2 for the effect on
mail lists.
   "If the domain in the From: header is from an organization that
publishes a DMARC record, the email is likely to not be delivered."

-- 
   Les Mikesell
  lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Not To James B. Byrne

[Kai Schaetzl]

Les Mikesell wrote on Wed, 12 Nov 2014 10:13:07 -0600:

> Well, no.

Well, *yes*. It's not business to be carried out on the list nor does the 
guy who moans about it seem to know why. And if you are the second from 
Gmail then please move it off-list as well. It's really not anyone's 
problem on this list what Gmail does.


Kai


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

Re: [CentOS] Not To James B. Byrne

[Les Mikesell]

On Wed, Nov 12, 2014 at 11:31 AM, Kai Schaetzl  wrote:
> Les Mikesell wrote on Wed, 12 Nov 2014 10:13:07 -0600:
>
>> Well, no.
>
> Well, *yes*. It's not business to be carried out on the list nor does the
> guy who moans about it seem to know why. And if you are the second from
> Gmail then please move it off-list as well. It's really not anyone's
> problem on this list what Gmail does.

Gmail isn't making this up, it is doing what the sender's domain
explicitly tells it to do with mail with a From: address in that
domain when it is (re)sent by a non-permitted host.  So yes it is
relevant to the list that if you don't want your mail to end up in
spam folders you shouldn't use a From: address in a domain that sets
p=quarantine or p=reject in its dmarc record, because that is exactly
what those say to do per the faq from www.dmarc.org.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Not To James B. Byrne

[Chris Adams]

Once upon a time, Kai Schaetzl  said:
> Well, *yes*. It's not business to be carried out on the list nor does the 
> guy who moans about it seem to know why. And if you are the second from 
> Gmail then please move it off-list as well. It's really not anyone's 
> problem on this list what Gmail does.

No, it isn't just "what Gmail does."  Yahoo and AOL are other major
handlers that do the same/similar thing (and there are other
not-as-major email handlers doing it too).  As has happened many times
in the past, the "rules" for email handling have changed.  The biggest
group of legitimate email handlers affected by this change is mailing
list handlers; they need to adapt or get blocked/sidelined/etc.

Is it annoying?  Yep.  Is what these providers are doing a good idea?
That's debatable.  Is it here to stay?  Most likely.
-- 
Chris Adams 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Not To James B. Byrne

[Les Mikesell]

On Wed, Nov 12, 2014 at 12:29 PM, Chris Adams  wrote:
> Once upon a time, Kai Schaetzl  said:
>> Well, *yes*. It's not business to be carried out on the list nor does the
>> guy who moans about it seem to know why. And if you are the second from
>> Gmail then please move it off-list as well. It's really not anyone's
>> problem on this list what Gmail does.
>
> No, it isn't just "what Gmail does."  Yahoo and AOL are other major
> handlers that do the same/similar thing (and there are other
> not-as-major email handlers doing it too).  As has happened many times
> in the past, the "rules" for email handling have changed.  The biggest
> group of legitimate email handlers affected by this change is mailing
> list handlers; they need to adapt or get blocked/sidelined/etc.
>
> Is it annoying?  Yep.  Is what these providers are doing a good idea?
> That's debatable.  Is it here to stay?  Most likely.

So in practice I think this really boils down to the common problem of
ancient software shipped by RHEL and the bug-for-bug compatibility in
CentOS with the list system eating its own dog food.  That is, there
is a fix for mailman, but not in the CentOS version. Sometimes
stability is good, sometimes you need the updates.

There is still something of a philosophical issue in changing the
apparent authorship (From: ) of the message...


Here's an interesting bug report filed 5/7/2014 by, ummm, James Byrne:
https://bugzilla.redhat.com/show_bug.cgi?id=1095359
with the apparent resolution being that you need a support contract to
discuss problems.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Not To James B. Byrne

[g]

On 11/12/2014 10:13 AM, Les Mikesell wrote:
> On Wed, Nov 12, 2014 at 9:46 AM, Kai Schaetzl
>  wrote:
>> That's ridiculous, you don't even know what's wrong or if it's
>> wrong at all or what you want him to do but you have to cry it out
>> loud to the list to put social pressure on him.

very good point Kai.

>
> Well, no.  Per the headers:
>
> Authentication-Results: mx.google.com; spf=neutral (google.com:
> centos-boun...@centos.org does not designate permitted sender hosts)
> smtp.mail=centos-boun...@centos.org; dkim=neutral (body hash did not
> verify) header.i=@; dmarc=fail (p=QUARANTINE dis=NONE)
> header.from=harte-lyne.ca
>
> The p=quarantine setting from his server explicitly requests that
> the message be marked as spam if it s not sent from an authorized
> server, which don't include the centos list server. So it is accepted
> and dropped in the spam folder as requested.
>
> And at the moment, he is the only list member that posts regularly 
> from a server with this setting.  (We don't even see ones with 
> p=reject, they'll bounce and get kicked off the list).

Les,

i believe problems are on your end, and not with server for James.

i do not see "dmarc=fail" or "p=QUARANTINE" in *any* of his email
headers.

therefore, i suggest that it is problem that _you_need_to_correct_.

because you are pulling emails from your server and if your email
client is thunderbird, simply create a filter for James where the
actions is;

   Set Junk Status to   Not Junk

then you can stop loading this list with needless *junk* rants
about *your* problem.

thank you.


-- 

peace out.

in a world with out fences, who needs gates.

tc,hago.

g
.

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

Re: [CentOS] Keepalived - spurious failovers

[John Horne]

On Wed, 2014-11-12 at 15:44 +, Richard Mann wrote:
> 
> +1 to your logrotate thought; I'd dig deeper there.
> 
> check /var/lib/logrotate.status; see if it doesn't match up with days
> the failover happens, that different httpd logs are rotating.  
>
Given that failover only occurs if Apache, Tomcat or the NIC fail, I
can't find anything in log rotation that could cause this effect. For
failover to occur the Apache/Tomcat process must be non-existent (in our
case keepalived checks for them using pgrep). We have secondary
monitoring of these processes (Xymon using checks of 'ps'), and that
shows no such failure. Simply logging into the servers and running ps
shows that they are running. I would hope that something would be logged
by either process in the appropriate log file, but nothing is seen. Of
course it could be something dire that simply kills the process dead,
but again we do not see that at all (ps shows they are present). So that
leaves the NIC. Again, I cannot think of any process (day or night) that
would cause the NIC to fail (or restart) - that would be a serious
problem. Secondly, keepalived should log the fact and put itself into a
FAULT state. I tested this on a test server, and it worked as described.
We, however, see no such fault state or log messages on our live
servers.

So, I am very much stumped as to the problem. I'm hoping that if
keepalived fails over tonight, then the cron jobs I have set up may give
a clue.




John.

-- 

John Horne   Tel: +44 (0)1752 587287
Plymouth University, UK

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

Re: [CentOS] Chromium browser for C6

[Phelps, Matthew]

I concur. Enter key, ^M, etc. has no effect in the browser. Same for number
keys.

On Mon, Nov 10, 2014 at 10:57 AM, Cian Mc Govern 
wrote:

> On 8 November 2014 13:52, Johnny Hughes  wrote:
>
> > On 11/07/2014 02:41 PM, Greg Bailey wrote:
> > > On 11/07/2014 01:20 PM, Robert Arkiletian wrote:
> > >> On Thu, Nov 6, 2014 at 2:11 PM, Johnny Hughes 
> > wrote:
> > >>
> > >>> On 11/06/2014 02:30 PM, Phelps, Matthew wrote:
> >  On Thu, Nov 6, 2014 at 3:00 PM, Robert Arkiletian  >
> > >>> wrote:
> > > On Thu, Nov 6, 2014 at 6:17 AM, Leon Fauster <
> > >>> leonfaus...@googlemail.com>
> > > wrote:
> > >
> > >> BTW:
> > >>
> > >>>
> >
> http://install.linux.ncsu.edu/pub/yum/itecs/public/chromium/rhel6/x86_64/
> > >>>
> > >>
> > > Are there any differences between how these rpms were built vs the
> > >>> official
> > > "supplementary" ones from RH?
> > >
> > > In other words, were they built with the same libs, patches,
> > >>> environment,
> > > etc... ?
> > >>> Yes, those use the Developer Tool Set .. the ones from Red Hat do
> not.
> > >>>
> > >>> I can not get the Sources for the Red Hat supplemental channel
> because
> > >>> they do distribute the pepperflash component.
> > >>>
> > >>> I am sorry, but Google is not interested in supporting CentOS.
> > >>>
> > >>>
> > >> Am I correct in interpreting, that even if RH wanted to release the
> > >> supplemental package for Chromium to CentOS they would not be able to
> > >> because it contains the pepperflash component.
> > >>
> > >
> > > The "chromium-browser" RPM from the supplemental channel doesn't appear
> > > to have pepperflash included in it:
> > >
> > > $ rpm -qilv chromium-browser|grep -i flash
> > >
> > > As opposed to "google-chrome-stable":
> > >
> > > $ rpm -qilv google-chrome-stable | grep -i flash
> > > drwxr-xr-x2 rootroot0 Oct 21 18:53
> > > /opt/google/chrome/PepperFlash
> > > -rw-r--r--1 rootroot 17350240 Oct 21 18:53
> > > /opt/google/chrome/PepperFlash/libpepflashplayer.so
> > > -rw-r--r--1 rootroot 2045 Oct 21 18:53
> > > /opt/google/chrome/PepperFlash/manifest.json
> > >
> > > The .spec file for chromium-browser does have conditionals in it, such
> > as:
> > >
> > > %define flash 0
> > >
> > > Looks like pepperflash is added from google-chrome-stable if flash is
> > > defined...
> >
> > OK new version posted.
> >
> > This uses the centos-6 testing key and is available here:
> >
> > http://people.centos.org/hughesjr/chromium/6/
> >
> > The repo file is here:
> >
> > http://people.centos.org/hughesjr/chromium/6/chromium-el6.repo
> >
> > This version is now called chromium-browser and not chromium, so if you
> > have the older version, you will need to:
> >
> > yum remove chromium
> >
> > then
> >
> > yum install chromium-browser
> >
> > Later updates should happen with yum update and the name chromium-browser
> >
> >
> > Thanks,
> > Johnny Hughes
> >
> >
> >
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > http://lists.centos.org/mailman/listinfo/centos
> >
> >
> Thanks for this Johnny. I'm seeing some strange input related issues with
> it however:
>
> 1. It doesn't detect anything typed on the keypad when NumLock is enabled.
> 2. It's not detecting the return key ie. entering text in a search field
> and hitting return results in nothing whereas before it would invoke the
> search.
>
> I'd be happy to provide more information if required.
>
> Thanks,
> Cian
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>



-- 
Matt Phelps
System Administrator, Computation Facility
Harvard - Smithsonian Center for Astrophysics
mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Not To James B. Byrne

[Les Mikesell]

On Wed, Nov 12, 2014 at 2:50 PM, g  wrote:
>
>> Authentication-Results: mx.google.com; spf=neutral (google.com:
>> centos-boun...@centos.org does not designate permitted sender hosts)
>> smtp.mail=centos-boun...@centos.org; dkim=neutral (body hash did not
>> verify) header.i=@; dmarc=fail (p=QUARANTINE dis=NONE)
>> header.from=harte-lyne.ca
>
> Les,
>
> i believe problems are on your end, and not with server for James.
>
> i do not see "dmarc=fail" or "p=QUARANTINE" in *any* of his email
> headers.

They are not 'in' his headers.  They are the settings in his domain's
DNS dmarc record.

Do:
nslookup -type=txt _dmarc.harte-lyne.ca
to see the record, and you'll see the 'p=quarantine' which says that
mail with 'From: ' addresses claiming to be some...@harte-lyne.ca that
is not sent from their approved hosts should be quarantined.

> therefore, i suggest that it is problem that _you_need_to_correct_.
>
> because you are pulling emails from your server and if your email
> client is thunderbird, simply create a filter for James where the
> actions is;
>
>Set Junk Status to   Not Junk

I'm not pulling emails from a server, I'm using gmail's web interface
because it is much more convenient to use from multiple systems.  And
even if I used imap to sync, I think it would already appear in the
spam folder.

>
> then you can stop loading this list with needless *junk* rants
> about *your* problem.

It's not my problem, it is what his domain says should be done with
mail claiming to be from there but isn't..  Your mail system may
simply ignore the request, but that doesn't mean it always will or
that it is the right thing to do.   And on a more practical note,
shouldn't be left as each recipient's problem.   And particularly
since it affects mail from yahoo.com and aol.com senders, the long
term fix will have to be in the list software (and already is, in the
current version).   Meanwhile, the workaround is to not send with a
From: address where the domain requests that it not be forwarded.

-- 
  Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Anyone have any experience with Epson EasyMP projectors?

[Fred Smith]

The folks at my office have acquired a new Epson EasyMP wireless projector,
which requires a windows/MacOS plugin to use. Of course, they don't provide
one for Linux.

Here's their web page on it:

http://www.epson.com/cgi-bin/Store/support/supDetail.jsp?BV_UseBVCookie=yes&infoType=Overview&oid=35942&prodoid=36528570

Do any of you folks out there know of any way to use Linux with one of
those devices?

Thanks!

Fred
-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us 
Do you not know? Have you not heard? 
The LORD is the everlasting God, the Creator of the ends of the earth. 
  He will not grow tired or weary, and his understanding no one can fathom.
- Isaiah 40:28 (niv) -
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Keepalived - spurious failovers

[John Horne]

On Wed, 2014-11-12 at 16:45 -0500, m.r...@5-cent.us wrote:
> John Horne wrote:
> 
> > Given that failover only occurs if Apache, Tomcat or the NIC fail, I
> > can't find anything in log rotation that could cause this effect. For
> > failover to occur the Apache/Tomcat process must be non-existent (in our
> > case keepalived checks for them using pgrep). We have secondary
> > monitoring of these processes (Xymon using checks of 'ps'), and that
> > shows no such failure. Simply logging into the servers and running ps
> > shows that they are running. I would hope that something would be logged
> 
> I don't suppose there was anything in dmesg, either on the guests or the
> host?
> 
Nope.



John.

-- 

John Horne   Tel: +44 (0)1752 587287
Plymouth University, UK

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

Re: [CentOS] Not To James B. Byrne

[Darr247]

On 12 November 2014 @20:50 zulu, g wrote:
i believe problems are on your end, and not with server for James. i 
do not see "dmarc=fail" or "p=QUARANTINE" in *any* of his email headers.


I think you're not seeing the full headers, then.

e.g. most of the headers of a recent message in here from James, and 
both those criteria appear about 5 lines down:


Received-SPF: none (google.com: centos-boun...@centos.org does not designate 
permitted sender hosts) client-ip=72.26.200.203;
Authentication-Results: mx.google.com;
   spf=neutral (google.com: centos-boun...@centos.org does not designate 
permitted sender hosts) smtp.mail=centos-boun...@centos.org;
   dkim=neutral (body hash did not verify) header.i=@;
   dmarc=fail (p=QUARANTINE dis=NONE) header.from=harte-lyne.ca
Received: from mail.centos.org (localhost [127.0.0.1])
by mail.centos.org (Postfix) with ESMTP id 1CE62A00713;
Tue, 11 Nov 2014 17:34:07 + (UTC)
X-Original-To: centos@centos.org
Delivered-To: centos@centos.org
Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca
[216.185.71.28])
by mail.centos.org (Postfix) with ESMTP id 67F77A002CA
for ; Tue, 11 Nov 2014 17:34:04 + (UTC)
Received: from localhost (localhost [127.0.0.1])
by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id B436E6043B
for ; Tue, 11 Nov 2014 12:34:04 -0500 (EST)
X-Virus-Scanned: amavisd-new at harte-lyne.ca
Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1])
by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new,
port 10024) with ESMTP id by9zNScqFHCh for ;
Tue, 11 Nov 2014 12:34:01 -0500 (EST)
Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca
[216.185.71.24])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPSA id 41849602AC
for ; Tue, 11 Nov 2014 12:34:00 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=harte-lyne.ca;
s=dkim_hll; t=1415727240;
bh=bSzYYms7jOodBs74U9LvZAeQZVdsPPxt1/o9XNYXuR8=;
h=In-Reply-To:References:Date:Subject:From:To:Reply-To;
b=w1KDyK3Rm7K3CZzoP2ZdIAYwMZ1ZPANhjAn69iRCUvu+ggGgI/j7XBwmXRvYxFC5B
GMNJQG6nuEEzhemHim3w5NsmPf2UL/n8LDBPzHvhLYwg3P+2L7GjaWG7tDhG3UDM+H
u1v1AS75zKzrf5yznmW91ctz1+jm0Oprn/STmdOYolBeKeiKbNO7sWPfnnHIGk8ml6
tRg4r/WrnwlgxoNc4n6U/r9aLpIkaygm51yzDDPscVz0dWyoP1FCcwCqRKzFy6qF5C
L+uCbolF2JlYG1dN10v0t1v3GcMX5un9m73jGHW+fGFfMXSOy9uWBh6D25NLW0T/Gw
UuiAj65wERRBA==
Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb)
by webmail.harte-lyne.ca with HTTP; Tue, 11 Nov 2014 12:34:00 -0500
Message-ID: 
In-Reply-To: 
References: 
Date: Tue, 11 Nov 2014 12:34:00 -0500
From: "James B. Byrne" 
To: "CentOS mailing list" 
User-Agent: SquirrelMail/1.4.22-4.el6
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
Subject: Re: [CentOS] Non-Gnome desktop
X-BeenThere: centos@centos.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: CentOS mailing list 
List-Id: CentOS mailing list 
List-Unsubscribe: ,

List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: ,

Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: centos-boun...@centos.org



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

Re: [CentOS] Not To James B. Byrne

[Les Mikesell]

On Wed, Nov 12, 2014 at 4:47 PM, Darr247  wrote:
> On 12 November 2014 @20:50 zulu, g wrote:
>>
>> i believe problems are on your end, and not with server for James. i do
>> not see "dmarc=fail" or "p=QUARANTINE" in *any* of his email headers.
>
>
> I think you're not seeing the full headers, then.
>
> e.g. most of the headers of a recent message in here from James, and both
> those criteria appear about 5 lines down:
>
> Received-SPF: none (google.com: centos-boun...@centos.org does not designate
> permitted sender hosts) client-ip=72.26.200.203;
> Authentication-Results: mx.google.com;
>spf=neutral (google.com: centos-boun...@centos.org does not designate
> permitted sender hosts) smtp.mail=centos-boun...@centos.org;
>dkim=neutral (body hash did not verify) header.i=@;
>dmarc=fail (p=QUARANTINE dis=NONE) header.from=harte-lyne.ca

These are added by the receiving google server as a trace for how it
processed the spf/dkim/dmarc options.   They wouldn't be present on a
receiving system that ignores them - and probably wouldn't match that
format in any case.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Not To James B. Byrne

[Darr247]

On 12 November 2014 @22:47 zulu, Darr247 wrote:

On 12 November 2014 @20:50 zulu, g wrote:
i believe problems are on your end, and not with server for James. i 
do not see "dmarc=fail" or "p=QUARANTINE" in *any* of his email headers.


I think you're not seeing the full headers, then.

e.g. most of the headers of a recent message in here from James, and 
both those criteria appear about 5 lines down:


And here are headers from a yahoo.com sender, which I also dug out of my 
spam folder (I was pretty sure James was *not* the only one, but I 
hadn't seen any from other senders since this thread started)... note 
the "dmarc=fail (p=REJECT dis=NONE)" line:


Received-SPF: none (google.com: centos-boun...@centos.org does not 
designate permitted sender hosts) client-ip=72.26.200.203;

Authentication-Results: mx.google.com;
   spf=neutral (google.com: centos-boun...@centos.org does not 
designate permitted sender hosts) smtp.mail=centos-boun...@centos.org;

   dkim=neutral (body hash did not verify) header.i=@;
   dmarc=fail (p=REJECT dis=NONE) header.from=yahoo.com
Received: from mail.centos.org (localhost [127.0.0.1])
by mail.centos.org (Postfix) with ESMTP id CEB02A00361;
Wed, 12 Nov 2014 11:13:55 + (UTC)
X-Original-To: centos@centos.org
Delivered-To: centos@centos.org
Received: from nm33-vm5.bullet.mail.ne1.yahoo.com
(nm33-vm5.bullet.mail.ne1.yahoo.com [98.138.229.69])
by mail.centos.org (Postfix) with ESMTP id 949F3A001C1
for ; Wed, 12 Nov 2014 11:13:53 + (UTC)
Received: from [127.0.0.1] by nm33.bullet.mail.ne1.yahoo.com with NNFMP;
12 Nov 2014 11:13:53 -
Received: from [98.138.226.180] by nm33.bullet.mail.ne1.yahoo.com with 
NNFMP;

12 Nov 2014 11:10:59 -
Received: from [98.138.89.160] by tm15.bullet.mail.ne1.yahoo.com with 
NNFMP;

12 Nov 2014 11:10:59 -
Received: from [127.0.0.1] by omp1016.mail.ne1.yahoo.com with NNFMP;
12 Nov 2014 11:10:59 -
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 659555.68554...@omp1016.mail.ne1.yahoo.com
Received: (qmail 89140 invoked by uid 60001); 12 Nov 2014 11:10:59 -
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024;
t=1415790659; bh=7qbieqBFb43LfAQpJtw5KO2xm6Rn/EkDckMX7LV8vb4=;

h=References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type;

b=jF9IP9S5JEqueyNjk3NCheNshejVdJ1Vx+Y69HnA570xRpMI72NND3yiGzHQiBIyhjhOZA37xc65I+4Bt0Mczl3+ohjPFgt9m/kCD+21sL2KkpHmrg0XdNc9OC+K7q89MVSHUi1wZJAZGjPFE/Qz622n+VCHKn9w8A1lGojk7b4=
X-YMail-OSG: qLXo8CgVM1n0YUBxJOr0lEPeaR8mb1G44c0HNETr4aSfPMs
rGnO0UgO3zcyVAEz9zgmftvHOq64olujwnboH7dL6n3OeNeaRjNwln07ewmj
E3vPdG0l.zipsTBWyHuWBUv8SlbMmS7pNSNkTnoYQbPeTEGNJmzIu4s11INb
rYUTKC1r6OgKlaOXh7moiXRxoQdL9nHKHZUz.DogQN5Qiz38hchKBJ0JgXC4
ty_xkUJA_OVNxRwCe4rz_rGVAuanVAY5J45ZXqK7W5_x0yrpPae03UWokpHs
I1.zs9DuUskb4zjFDFh3T2I9rqKGqARLzrT8SplNLd.qBVGAyx1NpK3GhHP1
_4agMu1d0iWqyz46vYN8KVIkAyuJCCJ.OTo0wUFmkCUO5DstvK8wFhpYCH7q
MXxoXL4kouNV_dpR0wcGPialrFjoltpR4heBkH7cOrCY.2lSJYoNFg3p8G6.
dpLPf8gIAOpjBVTfyo2XUW2DOUZNohfs9ITYmvGjNxGNVGPtkBhtvshMISFr
nN4tGR_M6KjhvQcEM9J3PFlpe1EHWRZLxS9n2DHJ9y_VjmYMXOqhvKq5fBgo
hzXEQu4W7y29eiHY8VQ--
Received: from [109.190.51.179] by web126105.mail.ne1.yahoo.com via HTTP;
Wed, 12 Nov 2014 03:10:59 PST
X-Rocket-MIMEInfo: 002.001,

RnJvbTogR2lsYmVydCBTZWJlbnN0ZSA8c2ViZW5zdGVAd2VhdGhlci5hZG1pbi5uaXUuZWR1PgoKPiBPbiBNb24sIDEwIE5vdiAyMDE0LCBGcmFuayBDb3ggd3JvdGU6Cj4.ICB5dW0gaW5zdGFsbCBubS1jb25uZWN0aW9uLWVkaXRvcgo.IFllYWgsIEknbSBoYXZpbmcgYSB0b3VnaCBkYXksIFRIQVQgaXMgd2hlcmUgaXQgc2hvdWxkIGJlIGZvdW5kLAo.IGJ1dCBpc24ndCwgdW5kZXIgR25vbWUsIG9uIHRoaXMgb25lIG1hY2hpbmUuIFR5cGluZyB3aGF0IHlvdSBkaWQgYWJvdmUKPiBnYXZlIG1lIGFuIGVycm8BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.203.733
References:  
 
<20141110153844.573b95e1e53439551f4f2...@melvilletheatre.com>


Message-ID: <1415790659.59608.yahoomail...@web126105.mail.ne1.yahoo.com>
Date: Wed, 12 Nov 2014 03:10:59 -0800
From: John Doe 
To: CentOS mailing list 
In-Reply-To: 
MIME-Version: 1.0
Subject: Re: [CentOS] Network menu doesn't appear on system menu on CentOS
6.6
X-BeenThere: centos@centos.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: CentOS mailing list 
List-Id: CentOS mailing list 
List-Unsubscribe: ,

List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: ,

Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: centos-boun...@centos.org



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

[CentOS] Anyone have a Brother multifunction working on Centos 7?

[Negative]

I have a Brother MFC 7360N, and it is refusing to print.

Given a job, the printer state shows, "Sending data to printer"; the file
is in the spool dir; the job queue is empty, and nothing more happens.

I had used the Brother driver installer, and ran into a 32-bit problem. The
rpm runs braddprinter, which fails looking for /lib/ld-linux.so.2. I don't
know what braddprinter does, but I then tried setting up the printer
through the system printer config. Everything seems to go ok. A driver is
in /usr/share/cups.

I tried to install glibc.i686, but it wants glibc-common. I have the 64-bit
glibc-common package but do not see a i686 one available.

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

Re: [CentOS] Anyone have a Brother multifunction working on Centos 7?

[Fred Smith]

On Wed, Nov 12, 2014 at 06:10:44PM -0500, Negative wrote:
> I have a Brother MFC 7360N, and it is refusing to print.
> 
> Given a job, the printer state shows, "Sending data to printer"; the file
> is in the spool dir; the job queue is empty, and nothing more happens.
> 
> I had used the Brother driver installer, and ran into a 32-bit problem. The
> rpm runs braddprinter, which fails looking for /lib/ld-linux.so.2. I don't
> know what braddprinter does, but I then tried setting up the printer
> through the system printer config. Everything seems to go ok. A driver is
> in /usr/share/cups.
> 
> I tried to install glibc.i686, but it wants glibc-common. I have the 64-bit
> glibc-common package but do not see a i686 one available.
> 
> Thanks in adv.

I've got a Brother DCP7065DN here, and I was able to get it working
on CentOS 7 using the Brother installation program:
linux-brprinter-installer-2.0.0.1

It's been a few weeks since I did it, and I didn't take notes. I recall
having to fool with it a while to make it work. The one I have now that
does work is using the IPP interface, so the Device URI is:

ipp://192.168.2.97/ipp

I seem to recall fooling around with various choices here, before
finally settling on that one (because it worked).

I don't THINK I had to hack at anything else to make it work...

good luck!

-- 
---
 .Fred Smith   /  
( /__  ,__.   __   __ /  __   : / 
 //  /   /__) /  /  /__) .+'   Home: fre...@fcshome.stoneham.ma.us 
//  (__ (___ (__(_ (___ / :__ 781-438-5471 
 Jude 1:24,25 -
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Anyone have a Brother multifunction working on Centos 7?

[Peter]

On 11/13/2014 12:10 PM, Negative wrote:
> I have a Brother MFC 7360N, and it is refusing to print.

I have a DCP-540CN which is a similar but I think older network printer.
 I haven't tried it on CentOS 7 yet, but got it to work with Fedora 18
and 19 which are very similar.  I do recall having to create an selinux
policy to get it to work, so that may very well be your issue.


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

[CentOS] Slow access from Windows 7 to samba share on CentOS 6.6 after upgrade

[Sorin Srbu]

Hi all,

Did anybody notice a really slow access from Windows 7 (especially from the MS 
Office suite) when trying to open a Word-doc for example, that sits on a  samba 
share on a computer recently upgraded to CentOS 6.6?
It can take up to two-three minutes to open a 20 kB Word-doc...

I tested with the latest available LibreOffice for Windows on the same 
Word-docs, but this one doesn't show this sluggishness.

Also opening PDF-documents on the samba share with Adobe Reader from Win7 gives 
this problem.

Opening e.g. jpegs and regular plain text files with Irfanview and Notepad++ 
respectively is just fine.

Pre-CentOS 6.6 opening any file on the samba share from Windows was 
lightning-fast.

I'm not too sure where to start trouble-shooting. I've tried disabling the TCP 
autotune on Windows for starters, which a small improvement, but what next?

Hints would be appreciated. Thanks.

-- 
BW,
Sorin
---
# Sorin Srbu, Sysadmin
# Uppsala University
# Dept of Medicinal Chemistry
# Div of Org Pharm Chem
# Box 574
# SE-75123 Uppsala
# Sweden
#
# Phone: +46 (0)18-4714482
# Visit: BMC, Husargatan 3, D5:512b
# Web: http://www.orgfarm.uu.se
---
# ()  ASCII ribbon campaign - Against html E-mail 
# /\
#
# This message was not sent from an iProduct!
#
# MotD follows:
# If it jams, force it. If it breaks, it needed replacing anyway.

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