Discuss August 2014

discuss@lists.centos.org

173 participants
168 discussions

OT: Linksys router misbehaviour
by Timothy Murphy 26 Aug '14

26 Aug '14

I'm running a Linksys WRT54GL router from my CentOS-7 home server. Every now and then (maybe once every 2 days) the router's WiFi cuts out, and I've found no way to solve this except to disconnect the power from the router, wait 10 seconds and then re-connect. This always works. The router is running under dd-wrt. My question is - which makes it a tiny bit CentOS-related - does anyone with such a router know of a way to wake the router up in such a case through the computer? I wouldn't have dared to ask this question here or anywhere until recently, as I assumed my ancient Linksys routers were obsolete. But I've been reading posts recently saying that there hasn't really been a Linux router to replace the WRT54GL, and in particular Linksys's recent 11n replacement is not as good as the old model in many ways. Anyway, if anyone has an answer to my query I should be very grateful. I have a couple of IP cameras working by WiFi on the computer, which I can look at remotely. I've connected one by TP-Link through the router, and this doesn't cut out, but it is not wholly satisfactory. But this shows that the router is alive and well, only its WiFi side is failing. -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

5 6

CentOS-announce Digest, Vol 114, Issue 13
by centos-announce-request＠centos.org 26 Aug '14

26 Aug '14

Send CentOS-announce mailing list submissions to centos-announce(a)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-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)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:1085 CentOS 7 gtk2 BugFix Update (Johnny Hughes) 2. CESA-2014:1091 Important CentOS 7 mod_wsgi Security Update (Johnny Hughes) 3. CEBA-2014:1092 CentOS 7 seabios BugFix Update (Johnny Hughes) 4. CEBA-2014:C002 CentOS 7 centos-release BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 25 Aug 2014 12:17:44 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:1085 CentOS 7 gtk2 BugFix Update To: centos-announce(a)centos.org Message-ID: <20140825121744.GA8742(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:1085 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1085.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e41482da9da676331e8a11fb920597ab986a9754971fccf15701a797bba67703 gtk2-2.24.22-5.el7_0.1.i686.rpm 2aa0aa568bc2a522e7d658868eb5ab861572105681453fdf655f523cd09e9b31 gtk2-2.24.22-5.el7_0.1.x86_64.rpm 0926f208326f29ed7e6f706b955907f44d081dacb5328e58714f6665dcd6015b gtk2-devel-2.24.22-5.el7_0.1.i686.rpm 15e292d3e30fb79b1cade0b6993af02f2ad6679a2e5dcc5ae89066756f2652b8 gtk2-devel-2.24.22-5.el7_0.1.x86_64.rpm 2e49736c64b8424aa63f742c6dab39fca8d17c45eb86ab05ac6090e0b02db72b gtk2-devel-docs-2.24.22-5.el7_0.1.x86_64.rpm e3f0ae3abcb359491c9894e0bef465e397ccc4a55913a4c0ea40c4e89b1986cd gtk2-immodules-2.24.22-5.el7_0.1.i686.rpm 57e7b5123d49d9727a9275012bb0162593e795e83ebe442f667f1c64fa464763 gtk2-immodules-2.24.22-5.el7_0.1.x86_64.rpm b39d8c232d3c0fc9beade3821273f7ed40bb4cd66f06e9ed6092a3d83c271ceb gtk2-immodule-xim-2.24.22-5.el7_0.1.i686.rpm 54943d7dbf75a1cfef3084c1c60cdb701f25d521c09846618bf5d36217e02cff gtk2-immodule-xim-2.24.22-5.el7_0.1.x86_64.rpm Source: 3499b681c2678c5272c91bc96947b4d9d4a044b519853e57a6e846aade8c3871 gtk2-2.24.22-5.el7_0.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Mon, 25 Aug 2014 12:17:55 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:1091 Important CentOS 7 mod_wsgi Security Update To: centos-announce(a)centos.org Message-ID: <20140825121755.GA8814(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:1091 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1091.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: f738fd103039a582ad48700fb180ccbc48011c5a70b3f99687eb2885fe19f0e4 mod_wsgi-3.4-12.el7_0.x86_64.rpm Source: 73eee7148a40507f7093229df2e58dca4e6d3d4afd683c195507bf18390000ca mod_wsgi-3.4-12.el7_0.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Mon, 25 Aug 2014 12:18:05 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:1092 CentOS 7 seabios BugFix Update To: centos-announce(a)centos.org Message-ID: <20140825121805.GA8876(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:1092 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1092.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 66eb91e24851a9226f723b40815b23e736083eccb421f04f6c0feffee261a715 seabios-1.7.2.2-12.el7_0.1.x86_64.rpm 8076a8cb80bb06e260293e6032ba42265f478d766ceeca38cfed16be9a141a6f seabios-bin-1.7.2.2-12.el7_0.1.x86_64.rpm fdc88be2d5264ffdeec3f50ad2d77a5a6ad6e3a5303bf2e436bff600e5b9970c seavgabios-bin-1.7.2.2-12.el7_0.1.x86_64.rpm Source: 90e66cd5133c7ccbc8cf593c2eca45f798322d2909e47e0c467054d986776a78 seabios-1.7.2.2-12.el7_0.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Mon, 25 Aug 2014 12:28:16 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:C002 CentOS 7 centos-release BugFix Update To: centos-announce(a)centos.org Message-ID: <20140825122816.GA9020(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and BugFix Advisory 2014:C002 Details at : http://bugs.centos.org/view.php?id=7516 http://bugs.centos.org/view.php?id=7497 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ef6a842d6442453376896d5d1a8f37704ce2bd9d9f791f00cec2a1f2d43ef860 centos-release-7-0.1406.el7.centos.2.5.x86_64.rpm Source: fa92c9d0ea4ed641fe82947d3e0b5f904411675905d39bc4784d2fa6426065ef centos-release-7-0.1406.el7.centos.2.5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos at irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 114, Issue 13 ************************************************

1 0

ipset module loaded at startup on CentOS 6.5
by Rob Townley 26 Aug '14

26 Aug '14

Anybody on here successfully get ipset iptables sets to work _after_ a reboot? My question on StackExchange http://unix.stackexchange.com/questions/149536/upon-bootup-all-iptables-are… Some of the things that need to be in place, otherwise iptables does not load: 1.) The kernel module ip_set needs to be loaded. 2.) The "sets" need to be created. 3.) Only after 1 and 2 succeed, dare start up iptables.

3 3

Port scanning from MicroSoft?
by James B. Byrne 26 Aug '14

26 Aug '14

This mornings activity log shows this: . . . From 23.102.132.99 - 2 packets to tcp(3389) From 23.102.133.164 - 1 packet to tcp(3389) From 23.102.134.239 - 2 packets to tcp(3389) From 23.102.136.210 - 3 packets to tcp(3389) From 23.102.136.222 - 2 packets to tcp(3389) From 23.102.137.62 - 3 packets to tcp(3389) From 23.102.137.101 - 2 packets to tcp(3389) From 23.102.138.184 - 1 packet to tcp(3389) From 23.102.138.216 - 1 packet to tcp(3389) From 23.102.139.11 - 2 packets to tcp(3389) From 23.102.139.27 - 5 packets to tcp(3389) From 23.102.140.90 - 2 packets to tcp(3389) From 23.102.140.158 - 3 packets to tcp(3389) From 23.102.161.114 - 1 packet to tcp(3389) From 23.102.170.1 - 2 packets to tcp(3389) From 23.102.170.48 - 4 packets to tcp(3389) From 23.102.171.49 - 2 packets to tcp(3389) From 23.102.172.233 - 2 packets to tcp(3389) From 23.102.173.124 - 2 packets to tcp(3389) . . . These are either mostly or entirely MicroSoft.com addresses. Any ideas as to what legitimate use this probing might have? I know that 3389 is MS-RDP. My question is why would a 'reputable' firm be scanning my systems for open connections on that port? -- *** 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

4 3

Postfix setup
by Timothy Murphy 26 Aug '14

26 Aug '14

I'm trying to clarify the various ways in which I could set up Postfix + Dovecot + SpamAssassin under CentOS-7, and I'd welcome any comments on the following remarks. As far as I can see there are 3 standard ways of setting this up: 1. Use amavisd 2. Use dovecot + pigeonhole/sieve 3. Use spamass-milter At present I'm following (2), but am thinking of going over to (1), since this seems simpler. (Amavisd wasn't available when I set up CentOS-7, so I didn't consider it then.) It seems to me that (2) is using dovecot in a slightly odd way, since as far as I can see dovecot normally takes email from ~/Maildir/cur/ and then moves marked spam. I'm not quite sure if (3) is a genuine alternative, or if it is why it is not the standard since it seems very simple? -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

2 1

Hardware raid health?
by Les Mikesell 25 Aug '14

25 Aug '14

I just had an IBM in a remote location with a hardware raid1 have both drives go bad. With local machines I probably would have caught it from the drive light before the 2nd one died... What is the state of the art in linux software monitoring for this? Long ago when that box was set up I think the best I could have done was a Java GUI tool that IBM had for their servers - and that seemed like overkill for a simple monitor. Is there anything more lightweight that knows about the underlying drives in a hardware raid set on IBM's - and also recent HP servers? -- Les Mikesell lesmikesell(a)gmail.com

5 6

Re: [CentOS] NetworkManager
by Marcelo Ricardo Leitner 25 Aug '14

25 Aug '14

Em 23-08-2014 19:30, Steve Clark escreveu: > On 08/22/2014 07:42 PM, Digimer wrote: >> On 22/08/14 07:07 PM, Les Mikesell wrote: >>> On Fri, Aug 22, 2014 at 5:46 PM, Digimer <lists(a)alteeve.ca> wrote: >>>> To continue your analogy, should car companies have stopped changing >>>> after the 20s? I mean, the cars then got you were you needed to go, right? >>> The point is to abstract an interface so you can make changes behind >>> it without breaking the things already built around it. You can >>> always add things without breaking anything that already worked for >>> your community of users. If you didn't care about that yourself, >>> you'd be recompiling a gentoo weekly instead of being here. >> To echo John, this is a major release. It's where, when needed, things >> can change and break backwards compatibility. If a change like this >> happened as a y-stream release, sure, I'll grab my pitch fork along with >> you. >> >> It's not realistic to expect backwards compatibility to last forever. >> The sysv init stuff had a good long run, but it was time to change. Now, >> you're welcome to disagree with me (and the archives are littered >> already with this argument), but in the end, it changed. A major version >> was the right place to do it, and now it is done. >> >> So this brings me back to my original point... Unless you plan to wage a >> war against things like Network Manager, systemd or what have you in the >> faint home of reverting in the next major release, you don't have a lot >> of viable long term options. >> >> Learn the new ways or fade from relevance. >> >> I say this without passing judgment on the merits of the new or old >> ways, simply as a fact of life. Even if you did hold out hope for, say, >> RHEL 8 to return to the old ways, you will have a hard time avoiding >> EL7. It will almost certainly be adopted wide-scale and that will >> provide inertia. >> > NetworkManager is the window's world way of doing things for people that don't really understand > what is going on. I see no use for it immediately disable it. But it pains me to have to take the time. TBH, I also had some pain on learning it, but now that we also have nmcli (command line tool), I actually feel it's easier than the old ifcfg- files. It's better script-able than before. Marcelo

2 1

Compiling modules in kernel source but not included in distro.
by Andrew Stringer 25 Aug '14

25 Aug '14

Hi, I've been trying to compile some kernel modules for centos 6.5, specifically fore_200e atm driver (although I also have hardware to try nicstar and he ). This module is not included in the centos kernel or modules but is included in the stock kernel source. Lots of articles on compiling or patching modules in general or compiling code not included in the kernel source, but not much on creating a module in the source but not included in a distro. After reading some of the centos wiki articles on why I don't need the kernel source, I tried just compiling the module source on it's own, but when I tried to modprobe / insmod it, I get this error:- insmod: error inserting '/lib/modules/2.6.32-431.20.5.el6.x86_64/extra/fore_200e.ko': -1 Invalid module format Google suggests this is because I am trying to compile against the wrong headers but as far as I can see, there is only one kernel and kernel headers on the system. This is my os:- Linux localhost.localdomain 2.6.32-431.20.5.el6.x86_64 #1 SMP Fri Jul 25 08:34:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux It's a vm used just for compiling the code, so obviously there isn't some real PCI bus hardware present but this should not cause the above error. As a different track, I tried to compile a new kernel and modules. This is on a real machine, with a 32bit kernel, 2.6.32-431.20.5.el6.i686 #1 SMP, although the hardware is 64 bits. I thought to avoid any possible issues with either non-64 bit clean code or trying to compile 32 bit code on a 64 bit machine initially, I installed a 32 bit os. With make menuconfig I could select the extra modules to compile. This seems to have worked ok, but the resulting kernel is kernel-2.6.32-1.i386.rpm, the src package is kernel-2.6.32-1.src.rpm but the running kernel is 2.6.32-431.20.5 Trying to install it gives:- [root@neptune ~]# rpm -ivh /home/andrew/rpmbuild/RPMS/i386/kernel-2.6.32-1.i386.rpm Preparing... ########################################### [100%] package kernel-2.6.32-71.el6.i686 (which is newer than kernel-2.6.32-1.i386) is already installed package kernel-2.6.32-431.20.5.el6.i686 (which is newer than kernel-2.6.32-1.i386) is already installed [root@neptune ~]# I'm not sure why the new kernel isn't a later number. I downloaded the latest centos source so the major numbers match, but I'm not sure why the minor numbers are 2.6.32-1 not 2.6.32-431.20.5 and note importantly, how to fix it. I'm still not convinced that recompling the whole kernel just to get some new modules is the right way to go. My feeling is that my initial approach is the right way to go. Any clues on the best direction to proceed? Regards, Andrew. -- Windows, for life without walls. Linux, for life without Windows.

3 4

Re: [CentOS] NetworkManager
by Keith Keller 24 Aug '14

24 Aug '14

On 2014-08-23, Steve Clark <sclark(a)netwolves.com> wrote: > NetworkManager is the window's world way of doing things for people that don't really understand > what is going on. I see no use for it immediately disable it. But it pains me to have to take the time. If you do it often enough, you should probably create a kickstart file, install image (e.g., Docker/KVM), or similar, which already has it disabled. I already do this for my OpenVZ images, which are preconfigured for my desires. And if that's too much work then it's probably not too often that you need to manually disable it. :) --keith -- kkeller(a)wombat.san-francisco.ca.us

1 0

NetworkManager
by Christof Stocker 24 Aug '14

24 Aug '14

So I noticed that the minimal installation of CentOS 7 comes - in contrary to minimal CentOS 6.5 - preinstalled with the NetworkManager. I somewhat understand its usefulness, especially for wlan / desktops, and its not like it really bothers me.. That being said, it seems to me with my naive linux understanding that it kinda goes against the definition of a "minimal" installation. Does anyone know why this decision was made / a good idea?

12 20

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss August 2014