Received
-----Original Message-----
From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On Behalf Of centos-request@xxxxxxxxxx
Sent: Saturday, December 27, 2014 6:00 AM
To: centos@xxxxxxxxxx
Subject: CentOS Digest, Vol 119, Issue 26 - Email found in subject
Send CentOS mailing list submissions to
centos@xxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos
or, via email, send a message with subject or body 'help' to
centos-request@xxxxxxxxxx
You can reach the person managing the list at
centos-owner@xxxxxxxxxx
When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS digest..."
Today's Topics:
1. Re: (py)curl error 7 (Mateusz Guz)
2. Fail2ban mail failures ??? (Robert G. (Doc) Savage)
3. Re: Fail2ban mail failures ??? (Mike Burger)
4. Re: Fail2ban mail failures ??? (Mike Burger)
5. Re: Fail2ban mail failures ??? (????????? ????????)
6. Re: Fail2ban mail failures ??? (Robert G. (Doc) Savage)
7. Re: CentOS 7 boot network problem (Greg Lindahl)
8. Re: Fail2ban mail failures ??? (????????? ????????)
----------------------------------------------------------------------
Message: 1
Date: Fri, 26 Dec 2014 14:04:08 +0000
From: Mateusz Guz <Mateusz.Guz@xxxxxxxxxx>
To: CentOS mailing list <centos@xxxxxxxxxx>
Subject: Re: (py)curl error 7
Message-ID: <6c9b32de4e744a0c859a3c943b4466e1@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Added:
"OPTIONS=-4 -named" to /etc/sysconfig/named, disabled ipv6 per interface, created /etc/modprobe.d/ipv6_disable.conf file with alias net-pf-10 off alias ipv6 off options ipv6 disable=1
but still getting the same error message.
Maybe it just needs a reboot (which im trying to avoid)
-----Original Message-----
From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On Behalf Of Mateusz Guz
Sent: Thursday, December 25, 2014 3:16 PM
To: CentOS mailing list
Subject: Re: (py)curl error 7
Tried that :D
yum is still trying to connect via ipv6
(ip_resolve=4 in config file)
-----Original Message-----
From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On Behalf Of Alikhan Damirov
Sent: Thursday, December 25, 2014 11:59 AM
To: CentOS mailing list
Subject: Re: (py)curl error 7
Hi,
from man yum.conf:
ip_resolve Determines how yum resolves host names.
`4' or `IPv4': resolve to IPv4 addresses only.
`6' or `IPv6': resolve to IPv6 addresses only.
On 25 December 2014 at 11:53, Mateusz Guz <Mateusz.Guz@xxxxxxxxxx> wrote:
> Hi,
>
> Disabled ipv6 (using sysctl, disabled ip6tables, no reboot, no proxy
> present) and still get the message as below.
>
> Centos 6.3 (i know its old)
> Kernel : 2.6.32-279.14.1.el6.x86_64 (I know its old) Standard
> /etc/yum.conf (no changes) Standard repos (centos base), enabled
>
> Cleaned cache: yum metadata (didn't work)
> Then: yum clean all (didn't work)
> Then yum makecache (didn't work)
>
> Yum repolist
> Could not retrieve mirrorlist
> http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os error was
> 14: PYCURL ERROR 7 - "Failed to connect to
> 2a02:2498:1:3d:5054:ff:fed3:e91a: Network is unreachable"
>
> Ping on mirrorlist.centos.org is OK
> Curl mirrrorlist.centos.org NOT_OK
>
> Message started to occur suddenly, I didn't even update any package.
> Any suggestions ?
>
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
------------------------------
Message: 2
Date: Fri, 26 Dec 2014 11:39:32 -0600
From: "Robert G. (Doc) Savage" <dsavage@xxxxxxxxxxx>
To: centos@xxxxxxxxxx
Subject: Fail2ban mail failures ???
Message-ID: <1419615572.4484.6.camel@xxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="UTF-8"
I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's alerts sent to root's mail to be rejected. Here's a clip from one of the error messages:
Message 48:
From MAILER-DAEMON@xxxxxxxxxxxxxxxxxx Sun Dec 21 03:09:20 2014
Return-Path: <MAILER-DAEMON@xxxxxxxxxxxxxxxxxx>
Date: Sun, 21 Dec 2014 03:09:19 -0600
From: Mail Delivery Subsystem <MAILER-DAEMON@xxxxxxxxxxxxxxxxxx>
To: postmaster@xxxxxxxxxxxxxxxxxx
Content-Type: multipart/report; report-type=delivery-status;
boundary="sBL97EKS003880.1419152959/lion.protogeek.org"
Subject: Postmaster notify: see transcript for details
Auto-Submitted: auto-generated (postmaster-notification)
Status: R
Part 1:
The original message was received at Tue, 16 Dec 2014 03:09:17
-0600
from localhost
with id sBG97E83025627
----- The following addresses had permanent fatal errors
-----
<fail2ban@xxxxxxxxxxx>
----- Transcript of session follows -----
<fail2ban@xxxxxxxxxxx>... Deferred: Connection timed out with
example.com.
Message could not be delivered for 5 days
Message will be deleted from queue
..........
I used to get the messages that are now being deleted after five days.
Any suggestions?
--Doc Savage
Fairview Heights, IL
------------------------------
Message: 3
Date: Fri, 26 Dec 2014 12:59:10 -0500
From: Mike Burger <mburger@xxxxxxxxxxxxxxxxx>
To: CentOS mailing list <centos@xxxxxxxxxx>
Subject: Re: Fail2ban mail failures ???
Message-ID: <ea1a2849d9364fe8cbf306dd40a2a978@xxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=US-ASCII; format=flowed
On 2014-12-26 12:39 pm, Robert G. (Doc) Savage wrote:
> I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's
> alerts sent to root's mail to be rejected. Here's a clip from one of
> the error messages:
>
>
> Message 48:
> From MAILER-DAEMON@xxxxxxxxxxxxxxxxxx Sun Dec 21 03:09:20 2014
> Return-Path: <MAILER-DAEMON@xxxxxxxxxxxxxxxxxx>
> Date: Sun, 21 Dec 2014 03:09:19 -0600
> From: Mail Delivery Subsystem
> <MAILER-DAEMON@xxxxxxxxxxxxxxxxxx>
> To: postmaster@xxxxxxxxxxxxxxxxxx
> Content-Type: multipart/report; report-type=delivery-status;
> boundary="sBL97EKS003880.1419152959/lion.protogeek.org"
> Subject: Postmaster notify: see transcript for details
> Auto-Submitted: auto-generated (postmaster-notification)
> Status: R
>
> Part 1:
>
> The original message was received at Tue, 16 Dec 2014 03:09:17
> -0600
> from localhost
> with id sBG97E83025627
>
> ----- The following addresses had permanent fatal errors
> -----
> <fail2ban@xxxxxxxxxxx>
>
> ----- Transcript of session follows -----
> <fail2ban@xxxxxxxxxxx>... Deferred: Connection timed out with
> example.com.
> Message could not be delivered for 5 days
> Message will be deleted from queue
> ..........
>
>
>
> I used to get the messages that are now being deleted after five days.
> Any suggestions?
I would suggest looking at the mailer daemon logs on both the sending and receiving systems. It would appear that the sending system is having difficulties at the receiving system end.
You will likely find the root of your issues in the log entries for that message (or those messages) that occurred over the 5 days in question.
--
Mike Burger
http://www.bubbanfriends.org
"It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
------------------------------
Message: 4
Date: Fri, 26 Dec 2014 13:05:21 -0500
From: Mike Burger <mburger@xxxxxxxxxxxxxxxxx>
To: CentOS mailing list <centos@xxxxxxxxxx>
Subject: Re: Fail2ban mail failures ???
Message-ID: <09ef054be1244426578ae9b115c3431c@xxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=US-ASCII; format=flowed
On 2014-12-26 12:59 pm, Mike Burger wrote:
> On 2014-12-26 12:39 pm, Robert G. (Doc) Savage wrote:
>> I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's
>> alerts sent to root's mail to be rejected. Here's a clip from one of
>> the
>> error messages:
>>
>>
>> Message 48:
>> From MAILER-DAEMON@xxxxxxxxxxxxxxxxxx Sun Dec 21 03:09:20
>> 2014
>> Return-Path: <MAILER-DAEMON@xxxxxxxxxxxxxxxxxx>
>> Date: Sun, 21 Dec 2014 03:09:19 -0600
>> From: Mail Delivery Subsystem
>> <MAILER-DAEMON@xxxxxxxxxxxxxxxxxx>
>> To: postmaster@xxxxxxxxxxxxxxxxxx
>> Content-Type: multipart/report; report-type=delivery-status;
>> boundary="sBL97EKS003880.1419152959/lion.protogeek.org"
>> Subject: Postmaster notify: see transcript for details
>> Auto-Submitted: auto-generated (postmaster-notification)
>> Status: R
>>
>> Part 1:
>>
>> The original message was received at Tue, 16 Dec 2014 03:09:17
>> -0600
>> from localhost
>> with id sBG97E83025627
>>
>> ----- The following addresses had permanent fatal errors
>> -----
>> <fail2ban@xxxxxxxxxxx>
>>
>> ----- Transcript of session follows -----
>> <fail2ban@xxxxxxxxxxx>... Deferred: Connection timed out with
>> example.com.
>> Message could not be delivered for 5 days
>> Message will be deleted from queue
>> ..........
>>
>>
>>
>> I used to get the messages that are now being deleted after five days.
>> Any suggestions?
>
> I would suggest looking at the mailer daemon logs on both the sending
> and receiving systems. It would appear that the sending system is
> having difficulties at the receiving system end.
>
> You will likely find the root of your issues in the log entries for
> that message (or those messages) that occurred over the 5 days in
> question.
PS: "Connection timed out with example.com" is the first thing I'd look
at.
--
Mike Burger
http://www.bubbanfriends.org
"It's always suicide-mission this, save-the-planet that. No one ever
just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
------------------------------
Message: 5
Date: Fri, 26 Dec 2014 21:30:39 +0300
From: ????????? ???????? <nevis2us@xxxxxxxxxxx>
To: CentOS mailing list <centos@xxxxxxxxxx>
Subject: Re: Fail2ban mail failures ???
Message-ID: <fd36bb75c1f5fc608b87419adeef4243@localhost>
Content-Type: text/plain; charset=UTF-8; format=flowed
Robert G. (Doc) Savage ????? 2014-12-26 20:39:
> I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's
> alerts sent to root's mail to be rejected. Here's a clip from one of
> the
> error messages:
>
>
> Message 48:
> From MAILER-DAEMON@xxxxxxxxxxxxxxxxxx Sun Dec 21 03:09:20 2014
> Return-Path: <MAILER-DAEMON@xxxxxxxxxxxxxxxxxx>
> Date: Sun, 21 Dec 2014 03:09:19 -0600
> From: Mail Delivery Subsystem
> <MAILER-DAEMON@xxxxxxxxxxxxxxxxxx>
> To: postmaster@xxxxxxxxxxxxxxxxxx
> Content-Type: multipart/report; report-type=delivery-status;
> boundary="sBL97EKS003880.1419152959/lion.protogeek.org"
> Subject: Postmaster notify: see transcript for details
> Auto-Submitted: auto-generated (postmaster-notification)
> Status: R
>
> Part 1:
>
> The original message was received at Tue, 16 Dec 2014 03:09:17
> -0600
> from localhost
> with id sBG97E83025627
>
> ----- The following addresses had permanent fatal errors
> -----
> <fail2ban@xxxxxxxxxxx>
>
> ----- Transcript of session follows -----
> <fail2ban@xxxxxxxxxxx>... Deferred: Connection timed out with
> example.com.
> Message could not be delivered for 5 days
> Message will be deleted from queue
> ..........
>
>
>
> I used to get the messages that are now being deleted after five days.
> Any suggestions?
Check your /etc/fail2ban/jail.local /etc/fail2ban/jail.conf.
You have to provide valid email addresses for dest= and sender=
parameters in sendmail-whois or mail-whois actions for enabled jails.
------------------------------
Message: 6
Date: Fri, 26 Dec 2014 19:00:01 -0600
From: "Robert G. (Doc) Savage" <dsavage@xxxxxxxxxxx>
To: centos@xxxxxxxxxx
Subject: Re: Fail2ban mail failures ???
Message-ID: <1419642001.4484.11.camel@xxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="UTF-8"
-----Original Message-----
From: ????????? ???????? <nevis2us@xxxxxxxxxxx>
Reply-to: CentOS mailing list <centos@xxxxxxxxxx>
To: CentOS mailing list <centos@xxxxxxxxxx>
Subject: Re: Fail2ban mail failures ???
Date: Fri, 26 Dec 2014 21:30:39 +0300
Robert G. (Doc) Savage ????? 2014-12-26 20:39:
> I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's
> alerts sent to root's mail to be rejected. Here's a clip from one of
> the
> error messages:
>
>
> Message 48:
> From MAILER-DAEMON@xxxxxxxxxxxxxxxxxx Sun Dec 21 03:09:20 2014
> Return-Path: <MAILER-DAEMON@xxxxxxxxxxxxxxxxxx>
> Date: Sun, 21 Dec 2014 03:09:19 -0600
> From: Mail Delivery Subsystem
> <MAILER-DAEMON@xxxxxxxxxxxxxxxxxx>
> To: postmaster@xxxxxxxxxxxxxxxxxx
> Content-Type: multipart/report; report-type=delivery-status;
> boundary="sBL97EKS003880.1419152959/lion.protogeek.org"
> Subject: Postmaster notify: see transcript for details
> Auto-Submitted: auto-generated (postmaster-notification)
> Status: R
>
> Part 1:
>
> The original message was received at Tue, 16 Dec 2014 03:09:17
> -0600
> from localhost
> with id sBG97E83025627
>
> ----- The following addresses had permanent fatal errors
> -----
> <fail2ban@xxxxxxxxxxx>
>
> ----- Transcript of session follows -----
> <fail2ban@xxxxxxxxxxx>... Deferred: Connection timed out with
> example.com.
> Message could not be delivered for 5 days
> Message will be deleted from queue
> ..........
>
>
>
> I used to get the messages that are now being deleted after five days.
> Any suggestions?
Check your /etc/fail2ban/jail.local /etc/fail2ban/jail.conf.
You have to provide valid email addresses for dest= and sender=
parameters in sendmail-whois or mail-whois actions for enabled jails.
os.org/mailman/listinfo/centos
????????? ????????,
I should have made it clear that this is all on one machine. The
jail.conf file is the default from the fail2ban package. It used to work
perfectly, but now has the mail problem. All I've had to do for years is
install the fail2ban package, start it, and make it autostart whenever I
reboot. Now it's misbehaving in a way that puzzles me.
--Doc Savage
Fairview Heights, IL
------------------------------
Message: 7
Date: Fri, 26 Dec 2014 22:17:39 -0800
From: Greg Lindahl <lindahl@xxxxxxx>
To: CentOS mailing list <centos@xxxxxxxxxx>
Subject: Re: CentOS 7 boot network problem
Message-ID: <20141227061739.GA1973@xxxxxxx>
Content-Type: text/plain; charset=us-ascii
>From reading
http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
it seems that this is a common problem, and that
systemctl enable NetworkManager-wait-online.service
might be a solution. I have a bunch of IP aliases on the same
network interface, is that what's caused my problem?
On Sat, Dec 20, 2014 at 01:05:01PM -0800, Greg Lindahl wrote:
> I rebooted a new CentOS 7 host and it attempted to start postfix and
> apache before the network came up. Needless to say both complained
> that they couldn't bind to the requested IP address and "entered the
> failed state."
>
> Did I miss an option somewhere? The network config is a manual one,
> and I see from the generated file in /etc/sysconfig/network-scripts
> that ONBOOT="yes"...
>
> -- greg
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
------------------------------
Message: 8
Date: Sat, 27 Dec 2014 12:24:19 +0300
From: ????????? ???????? <nevis2us@xxxxxxxxxxx>
To: CentOS mailing list <centos@xxxxxxxxxx>
Subject: Re: Fail2ban mail failures ???
Message-ID: <d0ba95645f021fb68d4cff013c7d5bf3@localhost>
Content-Type: text/plain; charset=UTF-8; format=flowed
>> I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's
>> alerts sent to root's mail to be rejected. Here's a clip from one of
>> the
>> error messages:
>>
>>
>> Message 48:
>> From MAILER-DAEMON@xxxxxxxxxxxxxxxxxx Sun Dec 21 03:09:20
>> 2014
>> Return-Path: <MAILER-DAEMON@xxxxxxxxxxxxxxxxxx>
>> Date: Sun, 21 Dec 2014 03:09:19 -0600
>> From: Mail Delivery Subsystem
>> <MAILER-DAEMON@xxxxxxxxxxxxxxxxxx>
>> To: postmaster@xxxxxxxxxxxxxxxxxx
>> Content-Type: multipart/report; report-type=delivery-status;
>> boundary="sBL97EKS003880.1419152959/lion.protogeek.org"
>> Subject: Postmaster notify: see transcript for details
>> Auto-Submitted: auto-generated (postmaster-notification)
>> Status: R
>>
>> Part 1:
>>
>> The original message was received at Tue, 16 Dec 2014 03:09:17
>> -0600
>> from localhost
>> with id sBG97E83025627
>>
>> ----- The following addresses had permanent fatal errors
>> -----
>> <fail2ban@xxxxxxxxxxx>
>>
>> ----- Transcript of session follows -----
>> <fail2ban@xxxxxxxxxxx>... Deferred: Connection timed out with
>> example.com.
>> Message could not be delivered for 5 days
>> Message will be deleted from queue
>> ..........
>>
>>
>>
>> I used to get the messages that are now being deleted after five days.
>> Any suggestions?
>
> Check your /etc/fail2ban/jail.local /etc/fail2ban/jail.conf.
> You have to provide valid email addresses for dest= and sender=
> parameters in sendmail-whois or mail-whois actions for enabled jails.
> os.org/mailman/listinfo/centos
>
>
> ????????? ????????,
>
> I should have made it clear that this is all on one machine. The
> jail.conf file is the default from the fail2ban package. It used to
> work
> perfectly, but now has the mail problem. All I've had to do for years
> is
> install the fail2ban package, start it, and make it autostart whenever
> I
> reboot. Now it's misbehaving in a way that puzzles me.
Robert,
If you never changed fail2ban defaults you probably had email aliases
defined somewhere in your configurations. Whatever you had it was
incorrect and it's not worth the effort to figure out why it ever worked
if at all. The "right" way is to use email addresses in (at least
locally) routable domains.
Alexander
------------------------------
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
End of CentOS Digest, Vol 119, Issue 26
***************************************
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
