Discuss

discuss@lists.centos.org

34758 discussions

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 23 Aug '14

23 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 23 Aug '14

23 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

color is not known to server "FOREGROUND"
by Frank Cox 23 Aug '14

23 Aug '14

I asked about this a while back with no response, but now have a bit more information. Still no idea how to fix it. I am occasionally seeing the above error when running various programs. Originally, I discovered it when running the "display" command from ImageMagick. $display picture.jpg display: color is not known to server `FOREGROUND': No such file or directory @ error/xwindow.c/XGetPixelPacket/3064. No picture is displayed. GraphicsMagick does the same thing, but it shows the picture: $ gm display picture.jpg gm display: Unable to load font (-*-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1) [Resource temporarily unavailable]. gm display: Color is not known to server (FOREGROUND) [No such file or directory]. gm display: Color is not known to server (BACKGROUND) [No such file or directory]. I have now discovered a tcl/tk program that appears to have the same issue: $ ./Mobi_Unpack.pyw Traceback (most recent call last): File "./Mobi_Unpack.pyw", line 211, in <module> sys.exit(main()) File "./Mobi_Unpack.pyw", line 202, in main root = Tkinter.Tk() File "/usr/lib64/python2.7/lib-tk/Tkinter.py", line 1745, in __init__ self.tk = _tkinter.create(screenName, baseName, className, interactive, wantobjects, useTk, sync, use) _tkinter.TclError: unknown color name "BACKGROUND" My reading indicates that this may be due to an issue with the xorg rgbpath declaration, but I don't know how to check what xorg is actually using (since the rgbpath declaration doesn't appear in any of the files in the xorg.conf.d subdirectory). /usr/share/X11/rgb.txt is present, though. Where and how is FOREGROUND and BACKGROUND defined for this purpose? -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

1 0

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

23 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:C001 CentOS 7 libguestfs BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 22 Aug 2014 17:27:26 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:C001 CentOS 7 libguestfs BugFix Update To: centos-announce(a)centos.org Message-ID: <20140822172726.GA9960(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and BugFix Advisory 2014:C001 Upstream details at : http://bugs.centos.org/view.php?id=7364 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a2b5ece4065075c7b11e9ce59d6281bebc9b9b98b3076160f388f3eb1e965fc2 libguestfs-1.22.6-22.el7.centos.0.1.x86_64.rpm 6fdac768fd7cc557c32e01e49eead7c6901a609aa1b46ba91b52f16b195635f6 libguestfs-devel-1.22.6-22.el7.centos.0.1.x86_64.rpm bb0dbe3b121fa58851f1efcf6ac77f98f4ceb93d599328231e245e5e8f7b8462 libguestfs-gobject-1.22.6-22.el7.centos.0.1.x86_64.rpm 38b332740586a141be3253621c7fdb906989e6e3888204a989ed317ae4128b16 libguestfs-gobject-devel-1.22.6-22.el7.centos.0.1.x86_64.rpm cd1e202eaee0eefaea4c7a7b12fb8f147ba552429fd32055defa98b5f10219ce libguestfs-gobject-doc-1.22.6-22.el7.centos.0.1.noarch.rpm 2c3081e6044ca3464770804cf24de23b6a12137b16530aee0232a646b04214fd libguestfs-java-1.22.6-22.el7.centos.0.1.x86_64.rpm d5e4132f8e185bffcfb5b51d910ec254e966c4b7c931b0165969b6b541ac4fd5 libguestfs-java-devel-1.22.6-22.el7.centos.0.1.x86_64.rpm f5b1888a82a4f53d24e6a9af34bd9ab397a7ef2691da5ff7e5c51be6cac4d855 libguestfs-javadoc-1.22.6-22.el7.centos.0.1.noarch.rpm f53dfe84dadd58c0a5abebcf6c4b8fd14c6b747c10376092555a5c501e202b30 libguestfs-man-pages-ja-1.22.6-22.el7.centos.0.1.noarch.rpm 715601b5e1e597127d3b4793ba000364f0afff4eed59f5238f88d68964bd6008 libguestfs-man-pages-uk-1.22.6-22.el7.centos.0.1.noarch.rpm 205774376743bcbb4b91dfcad5c754272de9475afc47cf161986391108d18541 libguestfs-tools-1.22.6-22.el7.centos.0.1.noarch.rpm 65347ba1c5cd9e35bacecdaca62e6b8b7f821f8dab4f965758135f3cc6346b5c libguestfs-tools-c-1.22.6-22.el7.centos.0.1.x86_64.rpm f8d44ca2d182e044dd065c1bcc08b061e9fb06065738b30beb1fe776d0c27169 lua-guestfs-1.22.6-22.el7.centos.0.1.x86_64.rpm 6b3b2704b73b2a2630e19f52341670b818cd14c40a3a1172e66ce30a81e1db21 ocaml-libguestfs-1.22.6-22.el7.centos.0.1.x86_64.rpm 9d91d4755184c056b8e3f4610bd25d4205a587f5b29f70f1ad17486399088f7a ocaml-libguestfs-devel-1.22.6-22.el7.centos.0.1.x86_64.rpm 410da626e570af05b224dc513a66cad96f6d66ac280e25e44a27dece647fae9d perl-Sys-Guestfs-1.22.6-22.el7.centos.0.1.x86_64.rpm 095f5a74533068091558bcc743ffb067b170dd805788f5ff5098b972a4b1667b python-libguestfs-1.22.6-22.el7.centos.0.1.x86_64.rpm 47d61af9a0533ff357c45034dd26ef1d3f482c6ca1ffba12a7afb9e29941c005 ruby-libguestfs-1.22.6-22.el7.centos.0.1.x86_64.rpm Source: 9d8b5596e405ba7a9b452adedd46a614c242bbc1a9b9e203d8b03d169c7402a5 libguestfs-1.22.6-22.el7.centos.0.1.src.rpm NOTE: This is a rebuild of the libguestfs SRPM to fix CentOS bug 7364 ... there is no modification to the actual source code, just needed to be built against a new centos-release file. -- 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 12 ************************************************

1 0

Re: [CentOS] Upgrade to m7.0 retaining some existing partitions
by Tony Molloy 23 Aug '14

23 Aug '14

On Friday 22 August 2014 14:00:45 you wrote: > Le 19.08.2014 08:44, Tony Molloy a écrit : > > I want to install 7.0 replacing an existing 6.5 installation. > > > > When I choose custom partitioning I can delete the old 6.5 > > partitions and create new partitions 7.0 but there doesn't appear > > to be any way to retain an existing partition, say /home for > > instance, over the installation. > > > > Am I just missing something obvious or any ideas on what the > > magic is. > > Hi Tony > > Did you receive an answer to your question ? I didn't see anything > on the list ! I'm interested too. > > Thank you No but I sorted it out myself. I just took a chance, it was on a test server anyway ;-) In the disk partitioning screen you will see the old 6.5 installation. Clicking on it will bring up the existing 6.5 partitions. Then select each of the existing partitions and a configuration menu comes up which allows you to reformat the partition if required. So just don't reformat the partitions you want to keep .They then become part of the new 7.0 installation. Hope this helps. Regards, Tony -- Linux nogs.tonyshome.ie 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

1 0

php-fpm on centos 6
by Александр Кириллов 23 Aug '14

23 Aug '14

What's the story with php-fpm on centos 6? There's a php-fpm rpm for centos 6 in epel but other essential mods like mod_fastcgi or mod_proxy_fcgi seem to be missing from the repos I'm usually using. Need a push in right direction. Thanks.

4 11

Centos 6.6 changes
by Ted Miller 23 Aug '14

23 Aug '14

What are the significant changes in Centos 6.6 (as released so far)? Ted Miller Elkhart, IN, USA

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss