- Discuss - lists.centos.org

Applying changes to route-eth0
by Robert Moskowitz 31 Jan '19

31 Jan '19

I have a series of static routes in route-eth0 Recently I had to made changes and could not find an effective way to get the old routes out and the new routes in. ifdown-route seems to apply the content of route-eth0 to take down the routes listed and ifup-route brings up routes based on route- So what ends up is that the old routes never go away, just new routes added. ifdown eth0; ifup eth0 works, but is a bit heavy-handed for only changing routes. So how do I clear out the routing table and have it rebuilt based on ifcfg-eth0 and route-eth0 without bouncing the interface completely?

2 2

Bacula 9.4.1 Dbdriver issue
by Alessandro Baggi 31 Jan '19

31 Jan '19

Hi list, I created my rpm for Bacula 9.4.1 reading centos srpm spec files. I made a single package and not split in several packages because this is my first rpm so I created my spec file taking a cue from bacula-5.3 spec file. All works as intended, an rpm was created and installed without any not fixable issue. After installing my bacula rpm I run a test to see if all works as expected. After bacula-dir and bacula-sd configuration I run bacula-dir -t to check error in config file and get this message: bacula-dir: dird.c:1206-0 Dbdriver field within director config file "dbi:PostgreSQL" mismatched with the Database argument "PostgreSQL" passed during Bacula compilation. I don't know what it is referring because I don't pass any argument like "PostgreSQL" during configure. The only option about postgresql is --with-postgresql. This is caused by this line in catalog statement: dbdriver = "dbi:postgresql"; I tried also using "dbi:PostgreSQL" but I got the same issue. I searched online but found only one fedora bugreport with the same problem related to fedora29 but for a different bacula version. Over this I tried to run bacula and all works like expected. How I can fix this warning? Hope in help. Thanks in advance. Alessandro.

2 2

C7, mdadm issues
by mark 31 Jan '19

31 Jan '19

I've no idea what happened, but the box I was working on last week has a *second* bad drive. Actually, I'm starting to wonder about that particulare hot-swap bay. Anyway, mdadm --detail shows /dev/sdb1 remove. I've added /dev/sdi1... but see both /dev/sdh1 and /dev/sdi1 as spare, and have yet to find a reliable way to make either one active. Actually, I would have expected the linux RAID to replace a failed one with a spare.... Clues for the poor? I *really* don't want to freak out the user by taking it down, and building yet another array. mark

3 16

kernel boot issues
by RC 31 Jan '19

31 Jan '19

Hello, I run CentOS release 6.10 (Final) on a Dell Inspiron M6700. 2.6.32-754.el6.x86_64 boots, and is whaat I am running now none of these, updated ones, won't boot: 2.6.32-754.3.5.el6.x86_64 2.6.32-754.6.3.el6.x86_64 2.6.32-754.9.1.el6.x86_64 2.6.32-754.10.1.el6.x86_64 They all show the same 'symptom', grub says it is booting that kernel, screen blanks, solid corned in the left-top corner... and that's whee it stays. I know this is vague, but any ideas? thanks, Ron

3 4

SELinux policy vs. static web content
by Nicolas Kovacs 31 Jan '19

31 Jan '19

Hi, Some time ago I wrote an introductory article about SELinux on my blog. I'm currently updating it for my new blog, and I found a curious change in SELinux policy. Here goes. For demonstration purposes, I'm using some static webpages, more exactly the default pages found in /usr/share/httpd/noindex, which I simply copied over to /var/www/html. As a first practical example, I'm copying this stuff over to /tmp/backup and then move it back again. A vaguely similar example has been given by Thomas Cameron in his presentation "SELinux for mere mortals", and I'm reproducing it here with some minor modifications. $ cd /var/www/html/ $ mkdir /tmp/backup $ cp -R * /tmp/backup/ $ rm -rf * $ mv /tmp/backup/* . $ find . -type d -exec chmod 0755 {} \; $ find . -type f -exec chmod 0644 {} \; When I wrote the article back in november 2017, this resulted in a classic "Forbidden" error, since the SELinux context of these files is not httpd_sys_content_t as it should be, but user_tmp_t. But when I try to repeat the experiment now, Apache shows no error. Which seems strange. Any idea what's going on ? Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 2

Re: [CentOS] EPEL repo problem
by Stephen John Smoogen 30 Jan '19

30 Jan '19

On Wed, 30 Jan 2019 at 09:21, Kenneth Porter <shiva(a)sewingwitch.com> wrote: > --On Wednesday, January 30, 2019 6:57 AM -0500 Stephen John Smoogen > <smooge(a)gmail.com> wrote: > > > Can you run the code from: https://github.com/puiterwijk/check_metalink > to > > see if we can pin down the proxy which is the problem (there are 14 and > > our checks are showing they are ok so I need to pin this down somewhere). > > Since I'm seeing the same errors intermittently, I tried to run the > script. > Recall that CentOS still ships with Python 2. First I had to install > rh-python36 from SCL. Then I had to change the script's shebang to > "#!/usr/bin/env python". Now it complains that there's no requests module. > I don't know how to resolve Python3 dependencies for a python installed > from SCL. How far down the rabbit hole will I need to go to get the script > working? ;) > > Yeah.. sorry. I didn't see I had made this one little change to my version: diff --git a/check_metalink b/check_metalink index f2beeb5..380b16d 100755 --- a/check_metalink +++ b/check_metalink @@ -1,4 +1,4 @@ -#!/bin/python3 +#!/bin/python I will see if I can make this work without that pathc. > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Stephen J Smoogen.

1 0

pip on C7
by Jerry Geis 30 Jan '19

30 Jan '19

I am trying to install the python-onvif package on C7. I did: pip install onvif Requirement already satisfied (use --upgrade to upgrade): onvif in /usr/lib/python2.7/site-packages Requirement already satisfied (use --upgrade to upgrade): suds>=0.4 in /usr/lib/python2.7/site-packages (from onvif) Requirement already satisfied (use --upgrade to upgrade): suds-passworddigest in /usr/lib/python2.7/site-packages (from onvif) You are using pip version 8.1.2, however version 19.0.1 is available. You should consider upgrading via the 'pip install --upgrade pip' command. How do I get it to go ahead and install ? Requirements are met. I don't desire to upgrade. Thanks, Jerry

2 3

Signature Pad (Evolis Signotec Sig100)
by Gregory P. Ennis 30 Jan '19

30 Jan '19

Everyone, Please forgive me for being off topic and really off list !!! I am trying to get a Sig100 signature pad to work with Centos 7.6 machine and am not getting much support from the manufacturer. The product is sold as linux compatible, but so far it is not. I have been able to download their software on a microsoft system and see that the unit does work on microsoft. My question to everyone on the list is have any of you had any brand of signature pad work with Centos 7.6? If so I would surely appreciate knowing the brand and how you did it. I have been able to get a HUION H610PRO wacom to easily work with Centos 7.6, but the use of this for a production application for signatures will not really work easily for a user. Any ideas? Thanks ahead for your thoughts!!!! Greg Ennis

3 6

Several tests failing
by Roee Agami 29 Jan '19

29 Jan '19

Hi, I’m attempting to build a 7.63.0 RPM for centos from a spec file I created. I am getting the following tests failures: “These test cases failed: 206 1049 1060 1061 1232 1241 1421” Here is an example of an output for test 206, any help to get insights into it would be greatly appreciated: test 0206...[HTTP proxy CONNECT auth Digest] ../libtool --mode=execute /usr/bin/valgrind --tool=memcheck --quiet --leak-check=yes --suppressions=./valgrind.supp --num-callers=16 --log-file=log/valgrind206 ../src/c url --output log/curl206.out --include --trace-ascii log/trace206 --trace-time http://test.remote.haxx.se.206:6490/path/2060002 --proxy http://127.0.0.1:6490 --proxy-u ser silly:person --proxy-digest --proxytunnel >log/stdout206 2>log/stderr206 2705 CMD (0): ../libtool --mode=execute /usr/bin/valgrind --tool=memcheck --quiet --leak-check=yes --suppressions=./valgrind.supp --num-callers=16 --log-file=log/valgrind206 ../src/curl --output log/curl206.out --include --trace-ascii log/trace206 --trace-time http://test.remote.haxx.se.206:6490/path/2060002 --proxy http://127.0.0.1:6490 --proxy-user silly:person --proxy-digest --proxytunnel >log/stdout206 2>log/stderr206 206: protocol FAILED: --- log/check-expected 2019-01-28 20:44:27.903988339 +0000 +++ log/check-generated 2019-01-28 20:44:27.903988339 +0000 @@ -4,7 +4,7 @@ [CR][LF] CONNECT test.remote.haxx.se.206:6490 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] -Proxy-Authorization: Digest username="silly", realm="weirdorealm", nonce="12345", uri="test.remote.haxx.se.206:6490", response="003e36decb4dbf6366b3ecb9b87c24ec"[CR][L F] +Proxy-Authorization: Digest username="silly", realm="weirdorealm", nonce="12345", uri="test.remote.haxx.se.206:6490", response="e6e133b332307d0e988962837d9e27a1"[CR][L F] Proxy-Connection: Keep-Alive[CR][LF] [CR][LF] GET /path/2060002 HTTP/1.1[CR][LF] == Contents of files in the log/ dir after test 206 === Start of file check-expected CONNECT test.remote.haxx.se.206:6490 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] Proxy-Connection: Keep-Alive[CR][LF] [CR][LF] CONNECT test.remote.haxx.se.206:6490 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] Proxy-Authorization: Digest username="silly", realm="weirdorealm", nonce="12345", uri="test.remote.haxx.se.206:6490", response="003e36decb4dbf6366b3ecb9b87c24ec"[CR][L F] Proxy-Connection: Keep-Alive[CR][LF] [CR][LF] GET /path/2060002 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] Accept: */*[CR][LF] [CR][LF] [DISCONNECT][LF] === End of file check-expected === Start of file check-generated CONNECT test.remote.haxx.se.206:6490 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] Proxy-Connection: Keep-Alive[CR][LF] [CR][LF] CONNECT test.remote.haxx.se.206:6490 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] Proxy-Authorization: Digest username="silly", realm="weirdorealm", nonce="12345", uri="test.remote.haxx.se.206:6490", response="e6e133b332307d0e988962837d9e27a1"[CR][L F] Proxy-Connection: Keep-Alive[CR][LF] [CR][LF] GET /path/2060002 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] Accept: */*[CR][LF] [CR][LF] [DISCONNECT][LF] === End of file check-generated === Start of file curl206.out HTTP/1.1 407 Authorization Required to proxy me my dear Proxy-Authenticate: Digest realm="weirdorealm", nonce="12345" Content-Length: 33 HTTP/1.1 200 OK swsbounce Server: no HTTP/1.1 200 OK Date: Thu, 09 Nov 2010 14:49:00 GMT Content-Length: 7 Connection: close Content-Type: text/html Funny-head: yesyes daniel === End of file curl206.out

1 0

C 7 and gssproxy
by mark 28 Jan '19

28 Jan '19

Ok, folks, I brought this up some time ago, and got no replies. We have a good number of systems - > 100 - and we use sssd. On the C 7 boxen, which is most of them, gssproxy *frequently* (like once a day or so) dies with a SEGV. It restarts fine. Dies again eventually. ARE other people seeing this? If so, I guess we get to file a bug report with upstream. Speaking as an old C programmer, dying with a SEGV? Really? In production? mark

3 2

Re: [CentOS] Centos 7 and backup solution
by Michael Schumacher 28 Jan '19

28 Jan '19

Sunday, January 27, 2019, 5:10:53 PM, you wrote: KP> rsync to a remote site and then BackupPC. (Use the BackupPC version 4 in KP> Software Collections.) I am using BackupPC too, but you don't need to rsync the data first. BackupPC can rsync data natively. I am using independent backup servers that are not accessible from the backup sources. Don't forget safety and integrity of your backed up data these days! Btw., it is not only a nice backup software, it is also very nice in recovering data through its web interface. best regards --- Michael Schumacher

1 0

How to get unrelease kernel, e.g. 3.10.0-341.el7
by wuzhouhui 28 Jan '19

28 Jan '19

Hi, I cloned https://git.centos.org/r/rpms/kernel.git and found that it only contains kernel version that CentOS released. So how do I get the kernel version that CentOS not release officialy, e.g. 3.10.0-341.el7 and 3.10.0-383.el7 (some kernel version I found in kernel.spec's changelog)? Thanks.

2 1

PXEBoot/Diskless client NFS issue
by John Cole 27 Jan '19

27 Jan '19

Hey CentOS list! I've got an oddity with a diskless client setup that I suspect is the result of the initrd.img I'm using, or some parameter I'm unaware -- or I need to build my own initrd image (and could use some assistance on what has to be done in that department) Testbed is defined as: VM A: ip: 192.168.250.10 with dhcp server, tftp server, nfs server VM B: pxeboot VM, with no local disk, bios set to pxe, same internal network as VM A Early on in the boot cycle, it grabs a DHCP address of 192.168.250.100, with correct mask, gw etc from VM A When I start the testbed setup: On the master VM I see log messages with the NIC of the client getting an address, and successfully loading pxelinux.0, pxelinux.cfg/default, vmlinuz and initrd.img. The PXE client on VM B boots up, downloads all the above images, unpacks and executes the inird image. I see drivers load and normal device registration for the nics just fine. After the PXE client VM shows the nic has its link up, this is where things go wrong... * The PXE client (that properly got an address in the 250 space to get its images) sends out a DHCP discover message as would be expected. * VM A responds with an offer of the same 192.168.250.100 address that was used to load * The PXE client comes back with a DHCPREQUEST for 192.168.85.128 * The DHCP server sends a DHCPNAK to the client, and offers the 250 address again. * The client never responds and the image seems to ignore the NAK/OFFER * Eventually the diskless client comes back with a dracut-initqueue message that (as a lease was not ACKed correctly reports) mount.nfs: Network is unreachable IF however, I run the identical configuration I mention above changing the addresses from 192.168.250.x to the 192.168.85.x space to match the initrd image request, everything works fine and the diskless client boots up normally and I get a command prompt. This would seem to indicate that I've got an otherwise working setup. The images I've always used for diskless boot are the ones prebuilt and posted on the centos mirrors site -- http://mirror.centos.org/centos/7/os/x86_64/images/pxeboot/ I've confirmed they and the pxeboot.0 file I'm using are the most recent being distributed. I've also unsuccessfully tried to use the ip parameters on the pxelinux.cfg/default line. As this seems to me as the most relevant config to post, here's what I've got there: label kiosk kernel kiosk/vmlinuz append initrd=kiosk/initrd.img ip=dhcp root=nfs:192.168.250.10:/var/lib/tftpboot/kiosk/root rw selinux=0 If other configs are requested, I'll gladly provide them, but again all works fine if I do this in the 192.168.85.x IP range. Once I've got this particular problem solved, I'm looking to boot up and bond BOTH NICs together, something I know should be possible, but I've not done myself yet. I believe that'd be handled in the append line as well. Any assistance in what I need to do to build a proper initrd image that doesn't suffer the problem of accepting a DHCP offered address, OR pointers to a config parameter I'm missing would be most appreciated. And a breadcrumb to help me with the dual nic once I'm out of the woods would be the "icing on the cake" but that's obviously a secondary concern right now! Thanks jc

2 2

10Gbps network interfaces under KVM
by Carlos Lopez 26 Jan '19

26 Jan '19

Hi all, Anyone knows if exists some plan to support Intel 10Gbps nics like for example 82575, 82576, 82580 or 82598EB Ethernet controllers under KVM for virtual guest like it does with e1000 driver? Regards, C. L. Martinez

2 1

Curl spec file
by Roee Agami 25 Jan '19

25 Jan '19

Hi, I saw this spec file for curl-7.29: https://git.centos.org/blob/rpms!curl.git/c7/SPECS!curl.spec And was wondering if you have one for a later version. And if not, how hard is it to modify the existing one to support later versions. Thanks! Roee.

4 7

CentOS-announce Digest, Vol 167, Issue 5
by centos-announce-request＠centos.org 25 Jan '19

25 Jan '19

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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. CESA-2019:0109 Important CentOS 7 perl Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 24 Jan 2019 15:18:07 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0109 Important CentOS 7 perl Security Update Message-ID: <20190124151807.GA623(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0109 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:0109 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 25fdf4603ff050c99e0733e5c87e956ae4d53958f5cc012c4aef9c96f0db06d7 perl-5.16.3-294.el7_6.x86_64.rpm a5c033d9f07ae7f3e1be74af0efbacba9a28182e49ebb1051e42f401d10df6bd perl-core-5.16.3-294.el7_6.x86_64.rpm d19952d11c7e8a1665de0c25c334a32fbffd15bc86daa5d1d830df8eab234f2e perl-CPAN-1.9800-294.el7_6.noarch.rpm c00e846544d902eea1cd6186e0b0ae97dc8c6e755c324e87f3efb7630aaf4c88 perl-devel-5.16.3-294.el7_6.i686.rpm afd580856968dd1ce74fc7ae4974dd1e0421892524e6fe415cd6300e1959f84e perl-devel-5.16.3-294.el7_6.x86_64.rpm 455397f649b77085744bc3a2e5e256d62d78c21147760b904f0189c21e6c90aa perl-ExtUtils-CBuilder-0.28.2.6-294.el7_6.noarch.rpm 71338d899e335e1fec8e5da0aa24df3400be530758d8380b35d356f07d43cf87 perl-ExtUtils-Embed-1.30-294.el7_6.noarch.rpm aeb5cb697a0edc60d2b4f014cad259620cb435aa0c1b2efead35bc3b60999ee7 perl-ExtUtils-Install-1.58-294.el7_6.noarch.rpm ee21a31de70c64daa1742260fc590203ef3bcb014c881813ada7a3acfb4178b9 perl-IO-Zlib-1.10-294.el7_6.noarch.rpm 2cde9e14351428a33484a57f9e4488ebe3bac607f549187208d0bf169ef85560 perl-libs-5.16.3-294.el7_6.i686.rpm 30bb4e65251eb02ae23fab59cd7833896ca241db385c6f5eea06c489ff00b416 perl-libs-5.16.3-294.el7_6.x86_64.rpm bac35a1f122bcc21c847ee41dc8f660c4a6d52794546eaa557fd036767ef8e8c perl-Locale-Maketext-Simple-0.21-294.el7_6.noarch.rpm a7428d0496b667350f611bbef32237b077e0974e1cff79e4398c0d882e19854a perl-macros-5.16.3-294.el7_6.x86_64.rpm b8f77bf6065bb12cb3fa1f33d0b98b40dabbb231900f41d8b6dbd5bfac7b4acd perl-Module-CoreList-2.76.02-294.el7_6.noarch.rpm 1bfaff78e1bf7696675b2748044beb6ffcd46cbb2a740381c725a617444d9ccb perl-Module-Loaded-0.08-294.el7_6.noarch.rpm 5ab7b507ade62e28bf44e8650b426b8604223314d334fdb7f0d545287086b356 perl-Object-Accessor-0.42-294.el7_6.noarch.rpm 494ab3285e32fd03fe75644fb429ea1250ae442b9cffafbed5a984faf11cffdd perl-Package-Constants-0.02-294.el7_6.noarch.rpm 54e0dadc78699063a7649857f51837a4a2f9299bb410460ad00e9e6c6490c928 perl-Pod-Escapes-1.04-294.el7_6.noarch.rpm 60d7c951435aaf2773a870bc884dbb0509021607f499c2ab06b82e9f3faf76f3 perl-tests-5.16.3-294.el7_6.x86_64.rpm 14342dea55b80183a11e039ca5bd54189467e2b09309717799725bb916dc6d16 perl-Time-Piece-1.20.1-294.el7_6.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 167, Issue 5 ***********************************************

1 0

C7, pulseaudio, multi-user setup
by wwp 24 Jan '19

24 Jan '19

Hello there, I'm on a CentOS7 laptop, in a Mate session w/ my default user, and in that desktop, I run apps from other users using sudo, su. It appears that apps started using sudo or in terminals+su, can't play sound: [pulseaudio] main.c: User-configured server at {f7ac68929370425d82f882c116a21597}unix:/run/user/1000/pulse/native, refusing to start/autospawn. User 1000 is my default user. I've searched and read a lot about this topic, and found many suggestions but none works so far. What's the correct way to allow all users to play sound in my default user's desktop session? Adding them all to the audio group doesn't seem to be enough (at least). Regards, -- wwp

1 0

dhcp-client should send hostname to dhcp/ dns server
by Ralf Prengel 24 Jan '19

24 Jan '19

Hallo, what is the right way in centos7 to configure the dhcp-client so that the system name is send to the dhcp/dns server (windows-domain). I found DHCP_HOSTNAME="Hostname" as entry in the device-config of the network-interface. Thanks for hints Ralf

1 0

C7, and my RAID
by mark 23 Jan '19

23 Jan '19

Ok, I think my only choice at this point is to delete and recreate the RAID, then restore from backup (oy, 7TB). I see that I can do an mdadm --remove /dev/md0, then, the page I see that on, suggests zeroing the superblocks. What would happen if I *don't* zero the superblocks before doing an mdadm --create? Would I just wind up back where I am? mark

1 0

Where is everyone?
by mark 23 Jan '19

23 Jan '19

There's usually a lot more traffic here. Just today, I've started wondering if a lot of folks who are usually here are on furlough, with the US gov't shutdown.... If so, my condolences, folks. mark

1 0

Re: [CentOS] C7 and mdadm - apparently SOLVED
by mark 23 Jan '19

23 Jan '19

Looking around on the Web, what I just tried was to stop the RAID, then do an --assemble --scan, and *that* found everything, put the raid together, and appears to be rebuilding using the new drive. *phew* I do find it interesting that scan works, but explicitly assembling apparently remembers the drive that died, and wouldn't even look at it. mark

2 3

dmarc auth on incoming email
by Fred Smith 23 Jan '19

23 Jan '19

Just reading up on DMARC, toying with setting it up to auth against incoming emails. (but not configure my domain to use dmarc, or at least not yet) ran into an article about opendmarc, which is available on epel. but when I took a look at the opendmarc website and the git pages it doesn't appear to have been updated in several years. while I see that it is still available from epel, I wonder if anyone knows the project status? Is it still active? are there any other viable alternatives? thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- The eyes of the Lord are everywhere, keeping watch on the wicked and the good. ----------------------------- Proverbs 15:3 (niv) -----------------------------

2 1

C7 radeon driver
by mark 23 Jan '19

23 Jan '19

Hi, folks, We've been recently (the last few months) having issues on workstations with the radeon driver. A typical sample is this, from /var/log/messages: Jan 23 11:35:32 <workstation> kernel: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec Jan 23 11:35:32 <workstation> kernel: radeon 0000:03:00.0: GPU lockup (current fence id 0x0000000000000212 last fence id 0x0000000000000213 on ring 0) Jan 23 11:35:33 <workstation> kernel: radeon 0000:03:00.0: Saved 23 dwords of commands on ring 0. Jan 23 11:35:33 <workstation> kernel: radeon 0000:03:00.0: GPU softreset: 0x00000019 Jan 23 11:35:33 <workstation> kernel: radeon 0000:03:00.0: GRBM_STATUS = 0xE5303CA0 Jan 23 11:35:33 <workstation> kernel: radeon 0000:03:00.0: GRBM_STATUS_SE0 = 0xF4000007 Jan 23 11:35:33 <workstation> kernel: radeon 0000:03:00.0: GRBM_STATUS_SE1 = 0x00000007 ... The above system has a Cedar GL [FirePro 2270], while the other two have Radeon HD 8570 / R7 240/340, so it doesn't seem to be limited to one video card. Are other people seeing similar errors? Is this enough for a bug report? mark

1 0

C7 and mdadm
by mark 23 Jan '19

23 Jan '19

A user's system had a hard drive failure over the weekend. Linux RAID 6. I identified the drive, brought the system down (8 drives, and I didn't know the s/n of the bad one. why it was there in the box, rather than where I started looking...) Brought it up, RAID not working. I finally found that I had to do an mdadm --stop /dev/md0, then I could do an assemble, then I could add the new drive. But: it's now cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md0 : active (auto-read-only) raid5 sdg1[8](S) sdh1[7] sdf1[4] sde1[3] sdd1[2] sdc1[1] 23441313792 blocks super 1.2 level 5, 512k chunk, algorithm 2 [7/5] [_UUUU_U] bitmap: 0/30 pages [0KB], 65536KB chunk unused devices: <none> and I can't mount it (it's xfs, btw). *Should* I make it readwrite, or is there something else I should do? mark

3 2

Yum refuses to install kmod-8188eu from elrepo
by Marko Vojinovic 23 Jan '19

23 Jan '19

I am having trouble using the realtek wifi chip in my new tp-link usb wifi dongle. Upon plugging it, the device gets registered by the kernel (in /var/log/messages), but that's about it, no network device is being created (iwconfig does not see it, nothing else works). A few google searches later I found out that this realtek chip is not supported by the kernel and requires a driver, and that the driver is packaged for C7 as kmod-8188eu in elrepo. However, yum install kmod-8188eu refuses to install it (full yum output is here: https://pastebin.com/raw/vvak6FCU ), complaining that the following dependencies cannot be met: --> Processing Dependency: kernel(wireless_send_event) = 0xa02e7e03 for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_submit_urb) = 0x74c6ac58 for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_reset_device) = 0xddd0084e for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_put_dev) = 0xf709107c for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_kill_urb) = 0xa55bf715 for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_get_dev) = 0x372a41af for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_free_urb) = 0x739aecf4 for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_control_msg) = 0xd04e3a9e for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_alloc_urb) = 0x12a4948e for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 I've never seen such output from yum before --- I'm guessing it is asking for a kernel with specific "properties", and failing to find one. What is the best way to resolve this? Is there some kernel package somewhere that matches these properties, or is there some other package that provides these features to an existing kernel, or something else? Or should I just ditch the kmod, and compile the 8188eu driver from source? I'd prefer to avoid this if possible, since I am not a fan of recompiling it every time the kernel is updated in C7. And I might need to use the wifi dongle on multiple machines, anyway. I'd appreciate any suggestions! TIA, :-) Marko

4 8

[Qemu-KVM] Centos 7.0 Guest vm freezing
by Akshar Kanak 22 Jan '19

22 Jan '19

Dear team I am running a centos guest VM which freezes for every few days . The qemu-kvm on shows 100% cpu utilization. Ping to the guest might work or may not work .Please can you tell me what approach can i take to debug it . using "virsh dump" I can dump the core of the guest vm but I am not sure how to analyse it . Guest Centos VM : "Linux GUESTCentOS70 3.10.0-123.4.4.el7.x86_64 #1 SMP Fri Jul 25 05:07:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux" "CentOS Linux release 7.0.1406 (Core)" 1 vcpu and 2 GB ram Host machine : "Linux HOST 3.10.51-1.el6.elrepo.x86_64 #1 SMP Fri Aug 1 13:14:11 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux" "CentOS release 6.5 (Final)" qemu-kvm package used : qemu-kvm-0.12.1.2-2.415.el6_5.10.x86_64 Thanks and regards Akshar

2 1

how to activate the network after an installation
by Ralf Prengel 21 Jan '19

21 Jan '19

Hallo, I can t find the switch to activate the network after an installation without gui. service network start doesn t work and I don t find any other commands. Thanks for a hint. Ralf

4 3

C7 and firewalld and ethernet bridge
by mark 18 Jan '19

18 Jan '19

Does someone have a link to a how-to-do-it with firewalld, not "disable firewalld and use iptables"? mark

3 2

Re: [CentOS] SElinux AVC signull
by Sean 18 Jan '19

18 Jan '19

Hi Leon, I don't have access to a CentOS 6.10 system handy, but it looks like a policy issue. If I take you're ausearch output and pipe it to audit2allow on my CentOS 7.6 system, I get the following: #============= httpd_t ============== #!!!! This avc is allowed in the current policy allow httpd_t httpd_sys_script_t:process signull; Noting that on my 7.6 system with selinux enforcing with selinux policy packages at version 3.13.1-229, it notes that your denial would not happen. If you don't have it installed policycoreutils-python provides the audit2allow and audit2why binaries which can help you generate a policy to avoid this denial if you want. Also, I often find that to truly diagnose the issue, I need to run the following: # semodule --disable_dontaudit --build # setenforce permissive # tail -f /var/log/audit/audit.log | grep denied | tee ~/denials.out ... then reproduce the problem, and kill the tail. The resulting denials.out file will have a lot of unrelated denials, but if you run audit2allow against the entire file, you'll be able to determine which ones are not relevant by the comments produced (much like above where it told us the "avc is allowed"). You can also use this to generate a custom policy module for your system. Sometimes there are denials that are not audited which are relevant to the problem, which seems problematic to me...that there is a default set of things that get denied but do not appear in the audit logs. That's a different conversation though. Anyway, after the data is collected for the denials.out file you can reset to your normal operating stance... # semodule --build # setenforce enforcing From: Leon Fauster <leonfauster(a)googlemail.com> To: CentOS mailing list <centos(a)centos.org> Cc: Bcc: Date: Thu, 17 Jan 2019 18:35:23 +0100 Subject: [CentOS] SElinux AVC signull I have some perl scripts running via CGI to print some monitoring informations out. # cat /etc/redhat-release CentOS release 6.10 (Final) # getenforce Enforcing # LANG=C ausearch -m avc --start today type=SYSCALL msg=audit(1547733474.941:28): arch=c000003e syscall=62 success=no exit=-13 a0=641 a1=0 a2=7f33500079b0 a3=31372f656d6f7268 items=0 ppid=1399 pid=1439 auid=4294967295 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=4294967295 comm="httpd" exe="/opt/rh/httpd24/root/usr/sbin/httpd" subj=system_u:system_r:httpd_t:s0 key=(null) type=AVC msg=audit(1547733474.941:28): avc: denied { signull } for pid=1439 comm="httpd" scontext=system_u:system_r:httpd_t:s0 tcontext=system_u:system_r:httpd_sys_script_t:s0 tclass=process I see a lot of such entries but I don't see any service misbehaviour. All scripts are running fine. Any hints how to classify this AVC; "Denied Signull"?

2 1

C 7.6, radeon
by mark 18 Jan '19

18 Jan '19

Hi, folks, Got a user that's recently(? been having odd things with her workstation video. This morning, in the logs, long before she got in, I saw a ton of errors Jan 18 08:06:50 <workstation> kernel: VM fault (0x04, vmid 1) at page 10, write from CP (48) Jan 18 08:06:50 <workstation> kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x01433014 Jan 18 08:06:50 <workstation> kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0000000A Jan 18 08:06:50 <workstation> kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03030014 I see that radeon.ko is part of the kernel, and there's no updates. She running kernel 3.10.0-957.1.3.el7.x86_64. I see no errors in Xorg.0.log. Anyone got a clue, or see this error? mark

1 0

SElinux AVC signull
by Leon Fauster 17 Jan '19

17 Jan '19

I have some perl scripts running via CGI to print some monitoring informations out. # cat /etc/redhat-release CentOS release 6.10 (Final) # getenforce Enforcing # LANG=C ausearch -m avc --start today type=SYSCALL msg=audit(1547733474.941:28): arch=c000003e syscall=62 success=no exit=-13 a0=641 a1=0 a2=7f33500079b0 a3=31372f656d6f7268 items=0 ppid=1399 pid=1439 auid=4294967295 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=4294967295 comm="httpd" exe="/opt/rh/httpd24/root/usr/sbin/httpd" subj=system_u:system_r:httpd_t:s0 key=(null) type=AVC msg=audit(1547733474.941:28): avc: denied { signull } for pid=1439 comm="httpd" scontext=system_u:system_r:httpd_t:s0 tcontext=system_u:system_r:httpd_sys_script_t:s0 tclass=process I see a lot of such entries but I don't see any service misbehaviour. All scripts are running fine. Any hints how to classify this AVC; "Denied Signull"? -- LF

1 0

CentOS-announce Digest, Vol 167, Issue 4
by centos-announce-request＠centos.org 17 Jan '19

17 Jan '19

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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. CESA-2019:0059 Important CentOS 7 libvncserver Security Update (Johnny Hughes) 2. CEBA-2019:0062 CentOS 6 cups BugFix Update (Johnny Hughes) 3. CEBA-2019:0063 CentOS 6 sssd BugFix Update (Johnny Hughes) 4. CEBA-2019:0064 CentOS 6 kernel BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 16 Jan 2019 16:58:43 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0059 Important CentOS 7 libvncserver Security Update Message-ID: <20190116165843.GA29758(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0059 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:0059 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: f9063672bd316bdb20907ca5477d6f7ee1aa0e057bd8dad70a76bfccd01de635 libvncserver-0.9.9-13.el7_6.i686.rpm 5b91b5ccf0f6dc305174707091e5b95d34c6d81fbaa13efce7041cfce07d7efb libvncserver-0.9.9-13.el7_6.x86_64.rpm 8adaa036f6ea9faba29c3e95e90fc83499a26d6b7b31993903b00d1a6e8f4f63 libvncserver-devel-0.9.9-13.el7_6.i686.rpm d17a31cb27129ad58d1ac49123ff1e2029c052f2f4961608d6b5ef1a6f483cc7 libvncserver-devel-0.9.9-13.el7_6.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 16 Jan 2019 17:00:31 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0062 CentOS 6 cups BugFix Update Message-ID: <20190116170031.GA29910(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0062 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0062 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ae19fac733269fcbd488ea1c9c811883b0cd1f404ece42dd9d01ba479e468146 cups-1.4.2-80.el6_10.i686.rpm 9fbe0535c19671f54c5200871216fff5838e1d891733a780ca395fdb832d5c56 cups-devel-1.4.2-80.el6_10.i686.rpm 08ac58e388403758ffc76f35cd416b445f147956a67769b475a33972e84dbba9 cups-libs-1.4.2-80.el6_10.i686.rpm 232ec808cb65f41f52992350ddf78fc438e9d69f15b92f1751475d24a2d7f3d0 cups-lpd-1.4.2-80.el6_10.i686.rpm 9ddb2dab7f095c1a0f3b350944c429cd71c6d31456491ddeeef980095f3c5099 cups-php-1.4.2-80.el6_10.i686.rpm x86_64: 06d91b4bbea2a7c25090ed85caff95cd179179b2fe353944e2443da5f05342ad cups-1.4.2-80.el6_10.x86_64.rpm 9fbe0535c19671f54c5200871216fff5838e1d891733a780ca395fdb832d5c56 cups-devel-1.4.2-80.el6_10.i686.rpm 50a7345aaab5c79772830dc3d31edbbfa596dd898e925a6bb4c7136488cb044f cups-devel-1.4.2-80.el6_10.x86_64.rpm 08ac58e388403758ffc76f35cd416b445f147956a67769b475a33972e84dbba9 cups-libs-1.4.2-80.el6_10.i686.rpm 7a063ec88b995cbe796b412519e2e06d6d288429785fd8b102c3b87aee74ceae cups-libs-1.4.2-80.el6_10.x86_64.rpm f04c2d5d959a60259d2cb16cceddb4e40e6fdc819c97d3e2fe7adfe590b9ad18 cups-lpd-1.4.2-80.el6_10.x86_64.rpm c4f1c4934cddeeeb13c8efd8375a248fa6a50576753c13a72b06abbad891dfcd cups-php-1.4.2-80.el6_10.x86_64.rpm Source: d49aa1c4abe8c4ddfee1c2a795a4e5f99c329dfa0bb423388d6c6887055172b5 cups-1.4.2-80.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 16 Jan 2019 17:00:46 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0063 CentOS 6 sssd BugFix Update Message-ID: <20190116170046.GA30197(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0063 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0063 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b22a1737a4e5697e44b3151c970a3433097410cf34039258b8fcfbfe8d1dc95b libipa_hbac-1.13.3-60.el6_10.2.i686.rpm 9579917eab870ae298b66132163c3d797a33aff256fa41b91394ca9581963de4 libipa_hbac-devel-1.13.3-60.el6_10.2.i686.rpm d2163b74511864ac8c115e3e45e647435eb99c7496cf182b3f84ad0958959ef0 libsss_idmap-1.13.3-60.el6_10.2.i686.rpm 7654514c0f4e2619b12f96cda69208d26fff1bf8ee49d7d723f7a2b04ac2898d libsss_idmap-devel-1.13.3-60.el6_10.2.i686.rpm 4a72cbcb94f17d7061d3ceec6ad78fb510f35c3c9b948f8c861e3547429324d9 libsss_nss_idmap-1.13.3-60.el6_10.2.i686.rpm 45c7ab78bf30829640762ae059fdfb2e57193fc9de962344ff37826b1d44bcdd libsss_nss_idmap-devel-1.13.3-60.el6_10.2.i686.rpm f35b71e0985e206b50dc63927886864dced1b5f36d1bef7573197808101d50ce libsss_simpleifp-1.13.3-60.el6_10.2.i686.rpm d86ab2a98c13f4c65ef7f9ef37b76c676c704bc30bc550cee8f889aadc950b60 libsss_simpleifp-devel-1.13.3-60.el6_10.2.i686.rpm cce1fa48695645e465a0aedc44f1e30b686c8b8c4ca32b58b4cdcec4a7d28a95 python-libipa_hbac-1.13.3-60.el6_10.2.i686.rpm 167017fa16eb91fa2b9dd702f844d3602d107c25db9f534e66e5a6396419b561 python-libsss_nss_idmap-1.13.3-60.el6_10.2.i686.rpm 47e22d53875a5a68df335b34c97ee3c7c26a62fcac0559730118a0525df2622c python-sss-1.13.3-60.el6_10.2.i686.rpm bfad805da74717748747662b2e40e6a04847737ca6e1ebd86a2f69d93d7af482 python-sssdconfig-1.13.3-60.el6_10.2.noarch.rpm af145bcfbe66b109d95d3583db38097e0f5bfd0fc034d7288e023fab7c86f5fe python-sss-murmur-1.13.3-60.el6_10.2.i686.rpm 6160b35856e1b77f1caa2a667eec9e187b1705ba7e076fc3112118e38d99c4b3 sssd-1.13.3-60.el6_10.2.i686.rpm 4fd8f81c72c5d182acf299fb7969d6468c5970de138bb66f2f516a7297a8cd49 sssd-ad-1.13.3-60.el6_10.2.i686.rpm 6a42040ae3d2ab2494f2c4d03d4b3b15df738a19e0f610083338607ae2791736 sssd-client-1.13.3-60.el6_10.2.i686.rpm 3b1b5c196ca1420669736dbe1bb00be2433f78fba8e592be01a89b845a77dd0c sssd-common-1.13.3-60.el6_10.2.i686.rpm 590c888642a8e7699133436c235d1e3d7cb44e8e4999d3220f9dd9a6457c57ae sssd-common-pac-1.13.3-60.el6_10.2.i686.rpm d4be7a8f81092c513ff5f8306d2fc9e2274f1387877fda51f3acb06b66cd4ec7 sssd-dbus-1.13.3-60.el6_10.2.i686.rpm 02bae49b270443bf5731afaa55ccc7f1fd9b2328438606a3843c26b379cc6820 sssd-ipa-1.13.3-60.el6_10.2.i686.rpm 4f9094c6e0cb3de191ae2966df24276511ec460063f1769872819cbda4ae7010 sssd-krb5-1.13.3-60.el6_10.2.i686.rpm 88b9c420282a5b5d80c8037980d0043bcbf8da1a7401520d73ba1707e292dcef sssd-krb5-common-1.13.3-60.el6_10.2.i686.rpm 9561ed3ec88d7fd79d9b30a7cb9fac45d9dd454f927b12341474b2d03dc7eb32 sssd-ldap-1.13.3-60.el6_10.2.i686.rpm fceb9bf37bb674eb0d50a04399267562b5dd5da8e200054e38c1c3b0fc895cc1 sssd-proxy-1.13.3-60.el6_10.2.i686.rpm 6266373e6038f672c05e0774718148187fa7e10339da25c447cd129c44473634 sssd-tools-1.13.3-60.el6_10.2.i686.rpm x86_64: b22a1737a4e5697e44b3151c970a3433097410cf34039258b8fcfbfe8d1dc95b libipa_hbac-1.13.3-60.el6_10.2.i686.rpm 4b8ba2a2eadd58d4650d33f9025e75d4fa12b5fe3be37cb7ec3bda67ae21eeea libipa_hbac-1.13.3-60.el6_10.2.x86_64.rpm 9579917eab870ae298b66132163c3d797a33aff256fa41b91394ca9581963de4 libipa_hbac-devel-1.13.3-60.el6_10.2.i686.rpm b9e3953546f9b0913615eb7fed07fa94091d41b35ea7fd5651713278626d4f06 libipa_hbac-devel-1.13.3-60.el6_10.2.x86_64.rpm d2163b74511864ac8c115e3e45e647435eb99c7496cf182b3f84ad0958959ef0 libsss_idmap-1.13.3-60.el6_10.2.i686.rpm 0bfc66082d0de5d35aeaf4e8d06ef7e2832d631bd718df6daf2cffd1aacb7061 libsss_idmap-1.13.3-60.el6_10.2.x86_64.rpm 7654514c0f4e2619b12f96cda69208d26fff1bf8ee49d7d723f7a2b04ac2898d libsss_idmap-devel-1.13.3-60.el6_10.2.i686.rpm c2d529420bb8a064b080d16b533838a76a2e54b1163fb07b7d0f2d055898d496 libsss_idmap-devel-1.13.3-60.el6_10.2.x86_64.rpm 4a72cbcb94f17d7061d3ceec6ad78fb510f35c3c9b948f8c861e3547429324d9 libsss_nss_idmap-1.13.3-60.el6_10.2.i686.rpm df7b79efc9d8345436cee514946c840c183ca65b59b7207caef938756d174b48 libsss_nss_idmap-1.13.3-60.el6_10.2.x86_64.rpm 45c7ab78bf30829640762ae059fdfb2e57193fc9de962344ff37826b1d44bcdd libsss_nss_idmap-devel-1.13.3-60.el6_10.2.i686.rpm 0c5b379f5c1c9eda709434e0b0afb079701afd5cd102d1b5898923656a16ceb2 libsss_nss_idmap-devel-1.13.3-60.el6_10.2.x86_64.rpm f35b71e0985e206b50dc63927886864dced1b5f36d1bef7573197808101d50ce libsss_simpleifp-1.13.3-60.el6_10.2.i686.rpm 30feb877eab60348fe8d664ba71e2adb831ffc8da2aa7b95474ff94e57a7cd78 libsss_simpleifp-1.13.3-60.el6_10.2.x86_64.rpm d86ab2a98c13f4c65ef7f9ef37b76c676c704bc30bc550cee8f889aadc950b60 libsss_simpleifp-devel-1.13.3-60.el6_10.2.i686.rpm 332d6c731a5513169a0e0c38c08f2e348b1602690d47386bf9193eecde22a43a libsss_simpleifp-devel-1.13.3-60.el6_10.2.x86_64.rpm c89fb8abb5b40d5408bd228e6b4285c5851298e9e544ab77abe81be793b7da40 python-libipa_hbac-1.13.3-60.el6_10.2.x86_64.rpm acf6a88d4248d90f1fccc20ac2a9c8b824eddb499202fef80b3b5202a0bed4d8 python-libsss_nss_idmap-1.13.3-60.el6_10.2.x86_64.rpm b24caa6e20691e3b8a81b95ef7a0287766bf47a6309c67e4cdd80489cef155b3 python-sss-1.13.3-60.el6_10.2.x86_64.rpm bfad805da74717748747662b2e40e6a04847737ca6e1ebd86a2f69d93d7af482 python-sssdconfig-1.13.3-60.el6_10.2.noarch.rpm a1c6ae6afe50e3499d06bdab308051371b0254fe3121af4c88fa7a806dcc4498 python-sss-murmur-1.13.3-60.el6_10.2.x86_64.rpm c9ff754eb80f31d4d86d8a09fd0566e901aa739b7f847647f93165c6044a82af sssd-1.13.3-60.el6_10.2.x86_64.rpm 07ea734345f5bcaea299c9bd619bc5ab7504f41dc9dab478067a8628e9f53f3c sssd-ad-1.13.3-60.el6_10.2.x86_64.rpm 6a42040ae3d2ab2494f2c4d03d4b3b15df738a19e0f610083338607ae2791736 sssd-client-1.13.3-60.el6_10.2.i686.rpm 17d812177e7be07f73b5efa961c18034de110ba9be1a365bce9dfcc429329663 sssd-client-1.13.3-60.el6_10.2.x86_64.rpm af71933e089e28597ca89984389a83aced948cb1f085b1701f58a59892b40be2 sssd-common-1.13.3-60.el6_10.2.x86_64.rpm 5414043e82746468dcc3dd7653eab24f52c9fce13f5fe64b6c45122e24c0e8ad sssd-common-pac-1.13.3-60.el6_10.2.x86_64.rpm a4ec13b36a5b935fea28430a686e72aade5211f6187da99bfa2f80f077c54dde sssd-dbus-1.13.3-60.el6_10.2.x86_64.rpm 7064499c4abef3ce57c5a57cb4a9bde174d921599d8d2a93715dc26e91f653fd sssd-ipa-1.13.3-60.el6_10.2.x86_64.rpm f31b60af9dd104d17725b0b14a1194a8a17b35697c2a0cf7bd303b24917f8013 sssd-krb5-1.13.3-60.el6_10.2.x86_64.rpm 7055b20e98bd8e937dcccd5923edecaaf1ac97d4ec70e75a43be6d2091b6c656 sssd-krb5-common-1.13.3-60.el6_10.2.x86_64.rpm d867a526e7c28bdda74947414aa9d383355d82a84150b3ceadb4e6d67f2d767e sssd-ldap-1.13.3-60.el6_10.2.x86_64.rpm 24bcc4c6f4ea60d81b7f65208641e324383708bfac2424d3b926ced00b8f5324 sssd-proxy-1.13.3-60.el6_10.2.x86_64.rpm ed2a63b1735c021ebfc5ed14b8b2ae2a338af52dd9bd3f058718f8286886a467 sssd-tools-1.13.3-60.el6_10.2.x86_64.rpm Source: 247b093ae72f99ece4eb1ec36ac48c8daf842a03f08a9fb876e77ffae1236c99 sssd-1.13.3-60.el6_10.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Wed, 16 Jan 2019 17:01:02 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0064 CentOS 6 kernel BugFix Update Message-ID: <20190116170102.GA30359(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0064 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0064 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b9c98cbf953323a56e67a0c28e53634cd6cf6aa600bd8450acde2720ac614075 kernel-2.6.32-754.10.1.el6.i686.rpm cad7a76980dc7d07e5f7533425a6f8b17632c96ce1bf25c92023a042878a6b2d kernel-abi-whitelists-2.6.32-754.10.1.el6.noarch.rpm aa9ca8cce2c5190226a13115b8c7af84128cd01f527d52edd96c1c98a16c7a35 kernel-debug-2.6.32-754.10.1.el6.i686.rpm 1ee4b5feee2525eb5dce2f1892e831dd8a7cde411a24f9b485f915b80c739d7d kernel-debug-devel-2.6.32-754.10.1.el6.i686.rpm 8174c559678952de8b6f41aae2fc347e6907e76ec2789eda52c65ee8aee46804 kernel-devel-2.6.32-754.10.1.el6.i686.rpm fa01abf5c0b25b8e43771abea710a991d721f08a7960c0c1d36ec852734bd11a kernel-doc-2.6.32-754.10.1.el6.noarch.rpm 6db0695340d175e24211a87b64c55ede3326ee32e7d9a226ab00dd075e6b1f8c kernel-firmware-2.6.32-754.10.1.el6.noarch.rpm 247bea5042897bfc78b1e73fc0cd7dfee2c847c8cc710de2a543fbba3e9db62a kernel-headers-2.6.32-754.10.1.el6.i686.rpm 7cab4fd35da0dd1833df81d93e4dd770bc6d0437fa6c0f29f31e5f01be861d50 perf-2.6.32-754.10.1.el6.i686.rpm 8bec1d14dcde36fbeb839f25b3418ec806d452e1108dcbbdbd3779b984ceb33d python-perf-2.6.32-754.10.1.el6.i686.rpm x86_64: 468171ef20cdd72a70bc06715fd76e64d4dafc4cbfd2648c7a3af66e4302b53f kernel-2.6.32-754.10.1.el6.x86_64.rpm cad7a76980dc7d07e5f7533425a6f8b17632c96ce1bf25c92023a042878a6b2d kernel-abi-whitelists-2.6.32-754.10.1.el6.noarch.rpm a22d933669af08e76a87bc55cce266635d907c291e1e662b62030bfc504a2cd0 kernel-debug-2.6.32-754.10.1.el6.x86_64.rpm 1ee4b5feee2525eb5dce2f1892e831dd8a7cde411a24f9b485f915b80c739d7d kernel-debug-devel-2.6.32-754.10.1.el6.i686.rpm 4db33312d3786ec278019f682110edc0cb437e32ce2fe1bac21ca1700483bc7b kernel-debug-devel-2.6.32-754.10.1.el6.x86_64.rpm 51cedf70c96c44256df09ad71bd24519d0b22aa3fcee22330f11378ab98aef37 kernel-devel-2.6.32-754.10.1.el6.x86_64.rpm fa01abf5c0b25b8e43771abea710a991d721f08a7960c0c1d36ec852734bd11a kernel-doc-2.6.32-754.10.1.el6.noarch.rpm 6db0695340d175e24211a87b64c55ede3326ee32e7d9a226ab00dd075e6b1f8c kernel-firmware-2.6.32-754.10.1.el6.noarch.rpm 5e7184f6fc68cd441d2195d1dc9854d2a79d3a260e4e755f118e17cf49576467 kernel-headers-2.6.32-754.10.1.el6.x86_64.rpm 9c8a146d2636171999782d38d5f18160e2bd27f17a9b2ecda74d6b7604a1717d perf-2.6.32-754.10.1.el6.x86_64.rpm 408d8d9b58dab7368191c819425d26b96f7abfed27212e60e5530a1845d231d1 python-perf-2.6.32-754.10.1.el6.x86_64.rpm Source: f65eb1b17c1e1589114aa9796f6c22df00607b850cd7ef6939c2b0836723668b kernel-2.6.32-754.10.1.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 167, Issue 4 ***********************************************

1 0

Inconsistent NIS Client Behavior w/ Centos 7.6
by Capehart, William J 16 Jan '19

16 Jan '19

Hi All. I am working on bringing back a number of Centos 7 rigs in our student computer lab back online. No change was made to the existing server machine [running Scientific Linux 6] Right now there is one remaining thing to resolve: an inconsistency with the rigs' NIS Clients. I have configured rcpbind and ypbind following guidance from Server World ( https://www.server-world.info/en/note?os=CentOS_7&p=nis&f=2 ) identically on all of the client machines. I have done this before with previous installs before this. The last time was this summer. Three are behaving as they are supposed to do. Five, however, are not. In this process I have repeatedly checked that support files .. /etc/sysconfig/network /etc/yp.conf /etc/pam.d/system-auth-ac /etc/pam.d/system-auth /etc/login.defs /etc/sysconfig/authconfig They are identical. IP addresses, Netmasks, Gateways, DNS, etc. are correct and all rigs (Server and Clients) do not conflict on any of the machines or /etc/host files. Disabling firewalls don’t impact the problem. NFS and other services work fine. All other aspects of networking is fine. You can ssh and access the Server rig from the Client rigs and for locally installed accounts on the clients go the other way. Accounts that leverage NIS cannot log into the Client from the Server or any other remote system. rpcbind shows that the ypbind/ypserv services are up and Clients and Server, respectfully (and it works on some of the machines). The rigs that are not working exhibit the following (satisfactory) behavior. * yptest -u [valid nis username] works with no errors. * yppasswd will change a password on the NIS server with no errors and other commands like ypchfn will work as well. * ypwhich, ypcat, ypmap, etc. give the same values we'd see on the NIS server. ...BUT... * You cannot console-login, ssh, or su into the rigs with valid NIS accounts. * (The local ypbind -d "debug mode" shows no response to a login, the "secure" log responds to a valid NIS account login with an "invalid user" a the [preauth] phase) * uids of valid NIS users are not recognized. * With ls -l, we see the uid of a file’s owner and not the username. (gids are explicitly declared locally on all rigs so they’ll match anyway.) * The id command for any valid nis user fails with "no such user" * cd ~[Valid NIS User] responds with "no such directory" even if the home directory exists (and the uid matches the uid on the NIS server). I am totally at a loss here. I cannot see the difference in what I did on the machines that work and the machines that do not work. Is there any test that I am missing or are there any files or setting where the culprit(s) on the errant machines may be? Cheers and Thanks --------------------------------------------------------------------------------------- Dr. Bill Capehart <William.Capehart(a)sdsmt.edu<mailto:William.Capehart@sdsmt.edu>> Director, Atmospheric and Environmental Sciences Program Department of Civil and Environmental Engineering 201 Mineral Industries Building (MWRF) 123 Civil Mechanical Building (T) South Dakota School of Mines and Technology 501 East St Joseph Street Rapid City, SD 57701-3995 USA Ph: +1-605-394-1994 Mobile: +1-605-484-5692

3 3

CentOS 6.X, iptables 1.47 and GeoLite2 Country Database
by Jobst Schmalenbach 16 Jan '19

16 Jan '19

Hi Specs in subject line: CentOS 6.X all latest patches), iptables 1.47, Apache2.2 I use the Geolite legacy databases together with iptables 1.47 to filter traffic for a variety of ports and only allow .AU traffic to have access. Maxmind (https://dev.maxmind.com/geoip/geoip2/geolite2/) changed the default DB to the latest version which is GeoLite2, this leaves all users in need of the old Geolite Legacy database in the dark, they cannot update. If I download a later version of xtables it will complain that it requires iptable>1.6 which I do not think I can get going on CentOS 6.X. Is there a way that I can convert Geolite2 CSV files to Geolite Legacy CSV Files and then compile those into BE/LE? Are there any other ways I can use Geolite2 on a CentOS 6.X system? Does anyone have other ideas how to tackle this? (this made me really sleep well!) thanks Jobst -- "XP: If you are nine years old you are just going to love it. If you're a few years older you'll resent the choking paternalistic atmosphere of vapid gee-whiz kiddie entertainment (babysitting), euphemism and fake-friendly bullying." | |0| | Jobst Schmalenbach, | | |0| Barrett & Sales Essentials |0|0|0| Caulfield South, 3162, Australia

3 6

@reboot only some lines of a script are working (yum install not)
by Ralf Prengel 15 Jan '19

15 Jan '19

Hallo, I m using a script to install docker after a reboot. The script is starting and working. The problem: yum install doesn't work running the script via cron allthough yum remove works. Starting the script manual works fine . Has anyone a hint for me? Thanks Ralf xxx SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root # For details see man 4 crontabs # Example of job definition: # .---------------- minute (0 - 59) # | .------------- hour (0 - 23) # | | .---------- day of month (1 - 31) # | | | .------- month (1 - 12) OR jan,feb,mar,apr ... # | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat # | | | | | # * * * * * user-name command to be executed @reboot root /opt/install_via_pxe/centos_autoinstall/stage01/init_stage01_docker.sh xxx #! /bin/bash echo 'script init_stage01_docker.sh ist gestartet' >> /var/log/comline/autoinst.log /usr/bin/yum install -y cifs-utils systemctl stop packagekit.service systemctl disable packagekit.service yum remove PackageKit -y /usr/bin/yum install -y docker mv /var/lib/docker /mnt/platte02 cd /var/lib ln -s /mnt/platte02/docker docker cp /opt/install_via_pxe/centos_autoinstall/stage01/docker/daemon.json /etc/docker systemctl enable docker systemctl start docker docker run --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher rancher/agent:v1.2.10 http://192.168.242.x.y/v1/scripts/811F51C097F763ABA2E5:1546214400000:Nzpsvk… cp -r /opt/install_via_pxe/centos_autoinstall/stage02/etc/crontab /etc/ echo 'script init_stage01_docker.sh ist gelaufen' >> /var/log/comline/autoinst.log shutdown -r now xxx

3 6

CentOS-announce Digest, Vol 167, Issue 3
by centos-announce-request＠centos.org 15 Jan '19

15 Jan '19

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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. CESA-2019:0049 Important CentOS 7 systemd Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 15 Jan 2019 11:38:56 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0049 Important CentOS 7 systemd Security Update Message-ID: <20190115113856.GA61890(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0049 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:0049 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 649fed4327a416093635b2b80459d00d97ffcfbece08b641b995dbad57fd58ac libgudev1-219-62.el7_6.2.i686.rpm 8e814081fe732ee1a25defc56d00b4c58b25d22ca4772dce34823f97fa6b427b libgudev1-219-62.el7_6.2.x86_64.rpm 1faa7d14cc5a8aa6e547e14cec18a9a6f556d5a2a9f1bbc8711278127358c324 libgudev1-devel-219-62.el7_6.2.i686.rpm 6da8d646dc649d387766110ca7ba495533a14ab47c34b4247c0c639fc0faac37 libgudev1-devel-219-62.el7_6.2.x86_64.rpm a34eedd90269505a11d70d49db2e93b936c670c6dfb439bc6cf68699a5974780 systemd-219-62.el7_6.2.x86_64.rpm 98e49665ffdf214d5dfe711cce125356fdc0348c18fb15eb50b22d6470079467 systemd-devel-219-62.el7_6.2.i686.rpm d67fcdb38a97033c6f3e45e5956f1e5516005567db26fa5b23d328d44f5501ef systemd-devel-219-62.el7_6.2.x86_64.rpm 31421ee8b5a777e3196943b0c232b9f3c29c993b14061b909334c13382826929 systemd-journal-gateway-219-62.el7_6.2.x86_64.rpm 79541a9226cbba215c6ac1c4280e1b428e5e770d5b73870adc5fa0caa37823c7 systemd-libs-219-62.el7_6.2.i686.rpm 2e55da1133e5dcc1892427cd68bf34ee94f7908bb7f39d5a7e6122f8286a70cd systemd-libs-219-62.el7_6.2.x86_64.rpm dac02b0fc760dc1d31266fab4c353821b7d411de644110736b43246686ec0054 systemd-networkd-219-62.el7_6.2.x86_64.rpm ca622a8c3bef58ad6c09b5aab7cb322eff4ff0ace18f3a0a58f598e085453537 systemd-python-219-62.el7_6.2.x86_64.rpm 3f20641ff1ff43a1d562f0b4ba71369b0468ca72d34d0cbedccabc1f58d8ce01 systemd-resolved-219-62.el7_6.2.i686.rpm bd4bf5a9f4339976b00c76b92bd434e36210631f1b43ad0798962de7f159f5a5 systemd-resolved-219-62.el7_6.2.x86_64.rpm e5e0efddb59dd352310097b9a78d00c21248282ae4f9a42f46a102a2fbb7d497 systemd-sysv-219-62.el7_6.2.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 167, Issue 3 ***********************************************

1 0

Re: [CentOS] @reboot only some lines of a script are working (yum install not)
by Ralf Prengel 14 Jan '19

14 Jan '19

Hallo. solved. proxy in yum.conf is working when starting yum in an crontab-environment. Ralf Zitat von Ralf Prengel <ralf.prengel(a)rprengel.de>: > Zitat von Mogens Kjaer <mk(a)lemo.dk>: > >> On 1/10/19 11:32 AM, Ralf Prengel wrote: >>> yum install doesn't work running the script via cron allthough yum >>> remove works. >> >> Is the network up when the script executes? > > > Hallo, > > yes it is up. > Result of 10 pings is fine as first line in the script. > Any other ideas? > > Ralf > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos

1 0

Re: [CentOS] Yum excluding packages I need
by mark 12 Jan '19

12 Jan '19

Stephen Berg (Code 7309) wrote: > On 1/11/19 10:41 AM, mark wrote: > >> C7, and I did a yum update --disableexcludes=all, and yet it's telling >> me [nvidia]: excluding kmod-nvidia-410.66-1.el7_5.elrepo.x86_64 >> [nvidia]: excluding kmod-nvidia-410.73-1.el7_5.elrepo.x86_64 >> [nvidia]: excluding kmod-nvidia-410.73-2.el7_6.elrepo.x86_64 >> [nvidia]: excluding kmod-nvidia-410.78-1.el7_6.elrepo.x86_64 >> [nvidia]: excluding kmod-nvidia-410.93-1.el7_6.elrepo.x86_64 <...> >> Even with a -vvv flag, it doesn't tell me why it's excluding them. >> > Pretty sure that's the yum-plugin-nvidia.noarch doing it's thing to keep > the wrong nvidia drivers from getting installed. Y'all will love this: you *can't* update yum-plugin-nvidia - *it* is excluded by itself. mark

4 5

Help finishing off Centos 7 RAID install
by Gary Stainburn 11 Jan '19

11 Jan '19

I've just finished installing a new Bacula storeage server. Prior to doing the install I did some research and ended up deciding to do the following config. 6x4TB drives /boot/efi efi_fs sda1 /boot/efi_copy efi_fs sdb1 /boot xfs RAID1 sda2 sdb2 VG RAID6 all drives containing SWAP / /home /var/bacula Questions: 1) The big problem with this is that it is dependant on sda for booting. I did find an aritcle on how to set up boot loading on multiple HDD's, including cloning /boot/efi but I now can't find it. Does anyone know of a similar article? 2) is putting SWAP in a RAID a good idea? Will it help, will it cause problems?

5 12

Yum excluding packages I need
by mark 11 Jan '19

11 Jan '19

C7, and I did a yum update --disableexcludes=all, and yet it's telling me [nvidia]: excluding kmod-nvidia-410.66-1.el7_5.elrepo.x86_64 [nvidia]: excluding kmod-nvidia-410.73-1.el7_5.elrepo.x86_64 [nvidia]: excluding kmod-nvidia-410.73-2.el7_6.elrepo.x86_64 [nvidia]: excluding kmod-nvidia-410.78-1.el7_6.elrepo.x86_64 [nvidia]: excluding kmod-nvidia-410.93-1.el7_6.elrepo.x86_64 [nvidia]: excluding nvidia-x11-drv-410.66-1.el7_5.elrepo.x86_64 [nvidia]: excluding nvidia-x11-drv-410.73-1.el7_5.elrepo.x86_64 [nvidia]: excluding nvidia-x11-drv-410.78-1.el7_6.elrepo.x86_64 [nvidia]: excluding nvidia-x11-drv-410.78-2.el7_6.elrepo.x86_64 [nvidia]: excluding nvidia-x11-drv-410.93-1.el7_6.elrepo.x86_64 [nvidia]: excluding nvidia-x11-drv-32bit-410.66-1.el7_5.elrepo.x86_64 [nvidia]: excluding nvidia-x11-drv-32bit-410.73-1.el7_5.elrepo.x86_64 [nvidia]: excluding nvidia-x11-drv-32bit-410.78-1.el7_6.elrepo.x86_64 [nvidia]: excluding nvidia-x11-drv-libs-410.78-2.el7_6.elrepo.i686 [nvidia]: excluding nvidia-x11-drv-libs-410.78-2.el7_6.elrepo.x86_64 [nvidia]: excluding nvidia-x11-drv-libs-410.93-1.el7_6.elrepo.i686 [nvidia]: excluding nvidia-x11-drv-libs-410.93-1.el7_6.elrepo.x86_64 Even with a -vvv flag, it doesn't tell me why it's excluding them. Clues for the poor? mark

2 1

From slashdot, systemd memory corruption bugs
by mark 11 Jan '19

11 Jan '19

Story: Linux systemd Affected by Memory Corruption Vulnerabilities, No Patches Yet (bleepingcomputer.com) 286 Posted by msmash on Thursday January 10, 2019 @01:00PM from the call-the-IT dept. Major Linux distributions are vulnerable to three bugs in systemd, a Linux initialization system and service manager in widespread use, California-based security company Qualys said late yesterday. From a report: The bugs exist in 'journald' service, tasked with collecting and storing log data, and they can be exploited to obtain root privileges on the target machine or to leak information. No patches exist at the moment. Discovered by researchers at Qualys, the flaws are two memory corruption vulnerabilities (stack buffer overflow - CVE-2018-16864, and allocation of memory without limits - CVE-2018-16865) and one out-of-bounds error (CVE-2018-16866). They were able to obtain local root shell on both x86 and x64 machines by exploiting CVE-2018-16865 and CVE-2018-16866. The exploit worked faster on the x86 platform, achieving its purpose in ten minutes; on x64, though, the exploit took 70 minutes to complete. Qualys is planning on publishing the proof-of-concept exploit code in the near future, but they did provide details on how they were able to take advantage of the flaws. -- 30 -- mark "Paging Mr. Poettering...."

1 0

CentOS 7 as a Fibre Channel SAN Target
by Steffan A. Cline 11 Jan '19

11 Jan '19

For quite some time I’ve been using FreeNAS to provide services as a NAS over ethernet and SAN over Fibre Channel to CentOS 7 servers each using their own export, not sharing the same one. It’s time for me to replace my hardware and I have a new R720XD that I’d like to use in the same capacity but configure CentOS 7 as a Fibre Channel target rather than use FreeNAS any further. I’m doing virtualization and this will allow me to have failover from one node to the other since they’ll all be sharing the same export rather than me simply backing up to the FreeNAS server the way I am now. Does anyone know of any really good current articles that explain how to set up CentOS 7 as the target in such a configuration and also setting up CLVMd so they can all share an export over Fibre Channel from CentOS 7? Steffan A. Cline steffan(a)hldns.com 602-793-0014

1 0

IPv6 DUID
by Stephen Berg (Code 7309) 11 Jan '19

11 Jan '19

Does anyone have a utility or method to show the IPv6 DUID for a client system without relying on looking through a DHCP server's logs or waiting until after a request is made? I'd like to determine a client's DUID before I set it up for IPv6, that way I can have it configured in the dhcpd6.conf file for a static assignment before it gets set up. I really don't care if it's an LL, LLT or UUID style as long as I can get it. -- Stephen Berg, IT Specialist, Oceanography Division, Code 7309 Naval Research Laboratory W: (228) 688-5738 DSN: (312) 823-5738 C: (228) 365-0162

1 0

CentOS-announce Digest, Vol 167, Issue 2
by centos-announce-request＠centos.org 11 Jan '19

11 Jan '19

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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-2019:0037 CentOS 6 tzdata BugFix Update (Johnny Hughes) 2. CEBA-2019:0037 CentOS 7 tzdata BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 10 Jan 2019 16:16:58 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0037 CentOS 6 tzdata BugFix Update Message-ID: <20190110161658.GA23833(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0037 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0037 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 2c4d3189531d11d7b6c22a1e38eb09b0f7f385ba27654ff013f819323d4227e4 tzdata-2018i-1.el6.noarch.rpm ee295e8462ac2963c1e4a4acbead61abdd80698fafdfdc4c22aed676e5977931 tzdata-java-2018i-1.el6.noarch.rpm x86_64: 2c4d3189531d11d7b6c22a1e38eb09b0f7f385ba27654ff013f819323d4227e4 tzdata-2018i-1.el6.noarch.rpm ee295e8462ac2963c1e4a4acbead61abdd80698fafdfdc4c22aed676e5977931 tzdata-java-2018i-1.el6.noarch.rpm Source: 02fe5160bae134a6673cabb1547ebcc739596bdeed36d043fce3ccde8765e19e tzdata-2018i-1.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 10 Jan 2019 18:13:13 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0037 CentOS 7 tzdata BugFix Update Message-ID: <20190110181313.GA30216(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0037 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0037 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 080cf6683643fb9af8597fcfe91b2aaaef3ad68d110c334c5d56ca5eb711df5e tzdata-2018i-1.el7.noarch.rpm 14f5d2443eb63d74cc7692658aab8eacc0596e71c3792188a21079514c74a202 tzdata-java-2018i-1.el7.noarch.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 167, Issue 2 ***********************************************

1 0

Re: [CentOS] vsftpd rejects users set to nologin
by Stephen John Smoogen 11 Jan '19

11 Jan '19

On Thu, 10 Jan 2019 at 16:09, Kenneth Porter <shiva(a)sewingwitch.com> wrote: > I updated to CentOS 7.6 and something must have changed in the base OS > setup that prevents vsftpd from allowing logins for accounts with > /sbin/nologin as their shell. I had to add that to /etc/shells so that > such > accounts could FTP again. That file is in the setup package. Did it > include > /sbin/nologin before? I don't have anything in my notes from setting up > the > system last year about changing that. What's the history of shells listed > in /etc/shells? > So I think this is a side effect of a long term argument of the security nature of /sbin/nologin https://serverfault.com/questions/328395/nologin-in-etc-shells-is-dangerous… https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… The second thread goes over me being an idiot in multiple places... > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Stephen J Smoogen.

3 4

vsftpd rejects users set to nologin
by Kenneth Porter 10 Jan '19

10 Jan '19

I updated to CentOS 7.6 and something must have changed in the base OS setup that prevents vsftpd from allowing logins for accounts with /sbin/nologin as their shell. I had to add that to /etc/shells so that such accounts could FTP again. That file is in the setup package. Did it include /sbin/nologin before? I don't have anything in my notes from setting up the system last year about changing that. What's the history of shells listed in /etc/shells?

1 0

Kickstart finishing Installation
by Ralf Prengel 10 Jan '19

10 Jan '19

Hallo, which switch is the right one for Centos 7.6 to finish the installation. Every Installation needs an acknowledgement at the end when the network configuration is shown while installing with grafics. Thanks Ralf Von meinem iPad gesendet

2 2

systemd
by Steve Clark 09 Jan '19

09 Jan '19

Hi List, I am trying to understand what After= means in a unit file. Does it mean after the specified target is up and operational or only that the target has been started? I have something that needs postgres but postgres needs to be operational not just started. Sometimes it can take a bit for postgres to become operational. Thanks, Steve

5 7

high kworker CPU usage in 3.10.0-957 w/ Xorg nouveau driver?
by Sean 09 Jan '19

09 Jan '19

Hi all, I have a number of Gnome/X desktop workstations with NVidia GeForce GT 1030 adapters, dual monitors, Core I7 3770 quad-core hyper-threaded CPUs, with 32GB of RAM. Most (haven't checked them all yet) are exhibiting problems that include significant sluggish-ness with mouse movement and typing as well as screen rendering problems happening since upgrading from kernel 3.10.0-862.14.4.el7.x86_64 to 3.10.0-957.1.3.el7.x86_64. The users have seen this behavior after logging into Gnome, but with out any additional applications running (Chrome/Firefox/LibreOffice, etc.). I can see in top that there are multiple kworker processes consuming a large amount of CPU time and unusually high load averages - like 5-7 range on the 5 minute average, normal load average would be between 1-2 for these users. At one point, while troubleshooting with a user, I was logged in remotely while the user was working on the desktop when it became completely unresponsive. /var/log/messages had nouveau messages like: kernel: nouveau: evo channel stalled kernel: nouveau 0000:01:00.0: disp: chid 1 mthd 0000 data 00000000 10003000 00000000 kernel: nouveau 0000:01:00.0: DRM: base-1: timeout kernel: nouveau 0000:01:00.0: DRM: core notifier timeout Those messages might be meaningless, but they are abundant in the logs. For grins before rebooting, I attempted to stop and start GDM. Both operations seemed successful, I verified all processes owned by the user were gone, and asked him to log in again, but he reported his screens still looked like they did before I restarted GDM and that he didn't have a login screen. Users are currently booting their systems to the 3.10.862 kernel, and this problem does not present itself. I can also add that running the proprietary nvidia driver (from nvidia.com, not elrepo) version 410.78 does not produce this problem. I config manage all these desktops with Puppet and they were all built from by the same kickstart file. The nvidia driver is not purposefully managed by puppet, I just happened to be experimenting with it on my workstation. Before I load the proprietary driver on all the problematic systems, I was hoping someone on the list might have some insight or suggestions. Thanks! --Sean

1 0

NFS deny access
by Thomas Plant 09 Jan '19

09 Jan '19

Hello all, I have an NFS Server where I want give access to a specific address to a specific path. Problem is that I have some other shares active which I do not want the specific IP to not access it. The /etc/exports looks like the following: /nfs/Share1 10.10.*(rw) /nfs/Share2 10.10.*(rw) /kdnbckp/CS21 10.10.193.43(rw) The client on the last line (IP 10.10.193.43) I'd like to exclude from mounting the first two shares. How can I do this? 'man exports' does not give any hint if this is possible. Thanks, Thomas

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss