Discuss December 2014

discuss@lists.centos.org

164 participants
167 discussions

Re: [CentOS] CentOS 7 KVM guests no longer get keystrokes after yum update [solved]
by Charles Polisher 29 Dec '14

29 Dec '14

Fixed. I had installed a preview repository from Red Hat for some not-yet-released libguestfs features (libguestfs-RHEL-7.1-preview). There were evidently changes to some release packages in the updates repository that were incompatible with the candidate packages in the preview repository cited above. I disabled the preview repo in /etc/yum.repos.d/..., uninstalled each of its packages, and re-installed the relevant packages (libvirt qemu-kvm qemu-kvm-tools virt-* spice-gtk spice-gtk-python spice-gtk-tools spice-gtk3-vala spice-xpi). Lesson learned: When you install 3rd party repositories you should reserve time for hand-holding your package management system. -- Charles Polisher

1 0

Re: [CentOS] Fetchmail multiple instances increasing load average
by Anshul Chauhan 29 Dec '14

29 Dec '14

Kindly suggest is this right way to start the cronjob with lock if i've not mis understood. */5 * * * * /usr/bin/flock -n */etc/webmin/fetchmail/check.pl <http://check.pl> *>* --file /var/log/fetchmaillog* Warm Regards, Anshul Chauhan

1 0

Re: [CentOS] Fetchmail multiple instances increasing load average
by Anshul Chauhan 29 Dec '14

29 Dec '14

Kindly suggest is this right way to start the cronjob with lock if i've not mis undestood. */5 * * * * /usr/bin/flock -n */etc/webmin/fetchmail/check.pl <http://check.pl> *>* --file /var/log/fetchmaillog* Warm Regards, Anshul Chauhan

1 0

Re: [CentOS] OT: Bittorrent clients
by Alexandru Chiscan 29 Dec '14

29 Dec '14

>Hey, ktorrent looks pretty good! >Thanks for the hint! Maybe it's time to give KDE a second look :) LEC

3 3

OT: Bittorrent clients
by Sorin Srbu 29 Dec '14

29 Dec '14

Hi all, Just switched my home computer from Windows 7 to CentOS 6.6 and I'm having a slight bit of trouble with the bittorrent-clients. * Transmission is fine but lacks "a bit" in features. * Vuze is my preferred bt-client but gives me horrendous gfx-artifacts, like not showing the torrent name (it's white text on a white background or some such...). * Deluge is better, and what I'm using now, but I'm having trouble finding a repo that has the updated versions available for install with yum. I installed v1.3.5 a few days ago and already it's telling me that version is way outdated. Would anybody have any hints as to how and where to get the latest Deluge for CentOS? Or maybe even suggest a better torrent-client? All I'm getting from the Deluge site is some kind of source packages that is of no use for me. 8-/ Thanks in advance for any hints, tips and tricks. -- /Sorin

4 7

Re: [CentOS] OT: Bittorrent clients
by Alexandru Chiscan 28 Dec '14

28 Dec '14

>Isn't that a KDE-specific program? Yes, it's from kde. >Works with Gnome as well? All kde programs work in all desktop managers provided that you install the required libraries. The same is true for gnome programs. LEC ----- Reply message ----- From: "Sorin Srbu" <Sorin.Srbu(a)orgfarm.uu.se> To: "Centos" <centos(a)centos.org> Subject: [CentOS] OT: Bittorrent clients Date: Sun, Dec 28, 2014 13:14 Isn't that a KDE-specific program? Works with Gnome as well? //Sorin Sent from my tablet, please excuse the brevity. Alexandru Chiscan <lec(a)easterng.ro> wrote: ktorrent Lec _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

2 1

Re: [CentOS] OT: Bittorrent clients
by Alexandru Chiscan 28 Dec '14

28 Dec '14

ktorrent Lec

3 8

CentOS 7 KVM guests no longer get keystrokes after yum update
by Charles Polisher 28 Dec '14

28 Dec '14

Dear all, After "yum update" and reboot on a CentOS 7 server running kvm, all VM guests fail to receive keyboard input. Even sending ctrl-alt-delete from the virt-manager "Send Key" menu is inoperative. Most guests are set up as spice + QXL, and viewed on remote X sessions using virt-manager. Extensive browsing for a solution has turned up only dead ends. I tried reverting to the earlier kernel but there was no joy. Possibly I made some config change or installed (or removed) something that didn't take effect until I rebooted, but searching the host's command history has been unhelpful. Has anyone here run into this? Connecting to a CentOS 6 guest with virt-viewer writes some messages to the console, but what little I found in a web search was unhelpful. BTW, I hadn't messed with any guest keymaps, all stock installs with en_US. $ virt-viewer irc.foo.peecee3.com (virt-viewer:6016): GSpice-WARNING **: Warning no automount- inhibiting implementation available (virt-viewer:6016): vnc-keymap-WARNING **: Unknown keycode mapping '(null)'. Please report to gtk-vnc-list(a)gnome.org including the following information: - Operating system - GDK build - X11 Server - xprop -root - xdpyinfo Every attempted keystroke on the guest produces one of these messages: (virt-viewer:6016): GSpice-CRITICAL **: send_key: assertion `scancode != 0' failed What I think is relevant, running on the most recent kernel, all commands run from the host: $ libvirtd --version libvirtd (libvirt) 1.2.8 $ uname -a Linux mencius.peecee3.com 3.10.0-123.13.2.el7.x86_64 #1 SMP Thu Dec 18 14:09:13 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/redhat-release CentOS Linux release 7.0.1406 (Core) $ systemctl --no-pager list-unit-files 2>&1| egrep -i 'spice|agent|virt|qxl|qemu|kvm' | grep -v '\.socket' machine-qemu\x2dirc.foo.peecee3.com.scope static libvirt-guests.service disabled libvirtd.service enabled virt-who.service disabled virtlockd.service static $ localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: us X11 Layout: us $ rpm -qa | egrep -i 'spice|agent|virt|qxl|qemu|kvm' | sort ipxe-roms-qemu-20130517-5.gitc4bce43.el7.noarch libgovirt-0.1.0-3.el7.x86_64 libvirt-1.2.8-9.el7.x86_64 libvirt-client-1.2.8-9.el7.x86_64 libvirt-daemon-1.2.8-9.el7.x86_64 libvirt-daemon-config-network-1.2.8-9.el7.x86_64 libvirt-daemon-config-nwfilter-1.2.8-9.el7.x86_64 libvirt-daemon-driver-interface-1.2.8-9.el7.x86_64 libvirt-daemon-driver-lxc-1.2.8-9.el7.x86_64 libvirt-daemon-driver-network-1.2.8-9.el7.x86_64 libvirt-daemon-driver-nodedev-1.2.8-9.el7.x86_64 libvirt-daemon-driver-nwfilter-1.2.8-9.el7.x86_64 libvirt-daemon-driver-qemu-1.2.8-9.el7.x86_64 libvirt-daemon-driver-secret-1.2.8-9.el7.x86_64 libvirt-daemon-driver-storage-1.2.8-9.el7.x86_64 libvirt-daemon-kvm-1.2.8-9.el7.x86_64 libvirt-glib-0.1.7-3.el7.x86_64 libvirt-python-1.2.8-5.el7.x86_64 perl-Sys-Virt-1.1.1-5.el7.x86_64 qemu-img-rhev-2.1.2-13.el7.x86_64 qemu-kvm-common-rhev-2.1.2-13.el7.x86_64 qemu-kvm-rhev-2.1.2-13.el7.x86_64 qemu-kvm-tools-rhev-2.1.2-13.el7.x86_64 spice-glib-0.20-8.el7.x86_64 spice-gtk3-0.20-8.el7.x86_64 spice-protocol-0.12.6-2.el7.noarch spice-server-0.12.4-5.el7_0.1.x86_64 virt-install-1.0.1-1.el7.centos.noarch virt-manager-1.0.1-1.el7.centos.noarch virt-manager-common-1.0.1-1.el7.centos.noarch virt-top-1.0.8-7.el7.x86_64 virt-viewer-0.5.7-7.el7.x86_64 virt-what-1.13-5.el7.x86_64 virt-who-0.8-15.el7_0.noarch Ordinarily selinux run on the host, but I temporarily disabled it to facilitate problem solving: $ getenforce Disabled The qemu logs for the guests are unremarkable, and nothing much shows up in /var/log/messages. Thanks, -- Charles Polisher

1 0

Re: [CentOS] CentOS Digest, Vol 119, Issue 26 - Email found in subject
by David Docherty 27 Dec '14

27 Dec '14

Received -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of centos-request(a)centos.org Sent: Saturday, December 27, 2014 6:00 AM To: centos(a)centos.org Subject: CentOS Digest, Vol 119, Issue 26 - Email found in subject Send CentOS mailing list submissions to centos(a)centos.org 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(a)centos.org You can reach the person managing the list at centos-owner(a)centos.org 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(a)itworks.pl> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] (py)curl error 7 Message-ID: <6c9b32de4e744a0c859a3c943b4466e1(a)KAEXC.itworks.pl> 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(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Mateusz Guz Sent: Thursday, December 25, 2014 3:16 PM To: CentOS mailing list Subject: Re: [CentOS] (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(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Alikhan Damirov Sent: Thursday, December 25, 2014 11:59 AM To: CentOS mailing list Subject: Re: [CentOS] (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(a)itworks.pl> 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(a)centos.org > http://lists.centos.org/mailman/listinfo/centos > _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos ------------------------------ Message: 2 Date: Fri, 26 Dec 2014 11:39:32 -0600 From: "Robert G. (Doc) Savage" <dsavage(a)peaknet.net> To: centos(a)centos.org Subject: [CentOS] Fail2ban mail failures ??? Message-ID: <1419615572.4484.6.camel(a)lion.protogeek.org> 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(a)lion.protogeek.org Sun Dec 21 03:09:20 2014 Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> Date: Sun, 21 Dec 2014 03:09:19 -0600 From: Mail Delivery Subsystem <MAILER-DAEMON(a)lion.protogeek.org> To: postmaster(a)lion.protogeek.org 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(a)example.com> ----- Transcript of session follows ----- <fail2ban(a)example.com>... 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(a)bubbanfriends.org> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Fail2ban mail failures ??? Message-ID: <ea1a2849d9364fe8cbf306dd40a2a978(a)bubbanfriends.org> 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(a)lion.protogeek.org Sun Dec 21 03:09:20 2014 > Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> > Date: Sun, 21 Dec 2014 03:09:19 -0600 > From: Mail Delivery Subsystem > <MAILER-DAEMON(a)lion.protogeek.org> > To: postmaster(a)lion.protogeek.org > 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(a)example.com> > > ----- Transcript of session follows ----- > <fail2ban(a)example.com>... 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(a)bubbanfriends.org> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Fail2ban mail failures ??? Message-ID: <09ef054be1244426578ae9b115c3431c(a)bubbanfriends.org> 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(a)lion.protogeek.org Sun Dec 21 03:09:20 >> 2014 >> Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> >> Date: Sun, 21 Dec 2014 03:09:19 -0600 >> From: Mail Delivery Subsystem >> <MAILER-DAEMON(a)lion.protogeek.org> >> To: postmaster(a)lion.protogeek.org >> 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(a)example.com> >> >> ----- Transcript of session follows ----- >> <fail2ban(a)example.com>... 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(a)infoline.su> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] 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(a)lion.protogeek.org Sun Dec 21 03:09:20 2014 > Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> > Date: Sun, 21 Dec 2014 03:09:19 -0600 > From: Mail Delivery Subsystem > <MAILER-DAEMON(a)lion.protogeek.org> > To: postmaster(a)lion.protogeek.org > 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(a)example.com> > > ----- Transcript of session follows ----- > <fail2ban(a)example.com>... 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(a)peaknet.net> To: centos(a)centos.org Subject: Re: [CentOS] Fail2ban mail failures ??? Message-ID: <1419642001.4484.11.camel(a)lion.protogeek.org> Content-Type: text/plain; charset="UTF-8" -----Original Message----- From: ????????? ???????? <nevis2us(a)infoline.su> Reply-to: CentOS mailing list <centos(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] 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(a)lion.protogeek.org Sun Dec 21 03:09:20 2014 > Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> > Date: Sun, 21 Dec 2014 03:09:19 -0600 > From: Mail Delivery Subsystem > <MAILER-DAEMON(a)lion.protogeek.org> > To: postmaster(a)lion.protogeek.org > 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(a)example.com> > > ----- Transcript of session follows ----- > <fail2ban(a)example.com>... 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(a)pbm.com> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] CentOS 7 boot network problem Message-ID: <20141227061739.GA1973(a)bx9.net> 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(a)centos.org > http://lists.centos.org/mailman/listinfo/centos ------------------------------ Message: 8 Date: Sat, 27 Dec 2014 12:24:19 +0300 From: ????????? ???????? <nevis2us(a)infoline.su> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] 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(a)lion.protogeek.org Sun Dec 21 03:09:20 >> 2014 >> Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> >> Date: Sun, 21 Dec 2014 03:09:19 -0600 >> From: Mail Delivery Subsystem >> <MAILER-DAEMON(a)lion.protogeek.org> >> To: postmaster(a)lion.protogeek.org >> 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(a)example.com> >> >> ----- Transcript of session follows ----- >> <fail2ban(a)example.com>... 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(a)centos.org http://lists.centos.org/mailman/listinfo/centos End of CentOS Digest, Vol 119, Issue 26 ***************************************

1 0

Re: [CentOS] Fail2ban mail failures ???
by James B. Byrne 27 Dec '14

27 Dec '14

On Fri, December 26, 2014 12:59, 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(a)lion.protogeek.org Sun Dec 21 03:09:20 2014 >> Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> >> Date: Sun, 21 Dec 2014 03:09:19 -0600 >> From: Mail Delivery Subsystem >> <MAILER-DAEMON(a)lion.protogeek.org> >> To: postmaster(a)lion.protogeek.org >> 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(a)example.com> >> >> ----- Transcript of session follows ----- >> <fail2ban(a)example.com>... 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. > Just checking the obvious but can you confirm that you are not actually sending messages to example.com? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

← Newer
1
2
3
4
5
6
7
...
17
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss December 2014