Discuss

discuss@lists.centos.org

1 participants
34753 discussions

Spacewalk 2.9 Sync Status bar not showing progress
by Laurence Rosen 01 Nov '19

01 Nov '19

Is this a known bug? I cannot get the Snc Status to show progress on the Channel Repositories -> sync page. I must tail -f the logfile to monitor progress which is ok but the status bar works on my 2.8 server. LR -- ******************************************************************************* This e-mail and any of its attachments may contain Interactions LLC proprietary information, which is privileged, confidential, or subject to copyright belonging to the Interactions LLC. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. *******************************************************************************

1 0

CentOS-announce Digest, Vol 177, Issue 1
by centos-announce-request＠centos.org 01 Nov '19

01 Nov '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:3193 Critical CentOS 7 firefox Security Update (Johnny Hughes) 2. CESA-2019:3210 Important CentOS 7 thunderbird Security Update (Johnny Hughes) 3. CESA-2019:3197 Important CentOS 7 sudo Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 31 Oct 2019 14:47:55 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:3193 Critical CentOS 7 firefox Security Update Message-ID: <20191031144755.GA14371(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:3193 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2019:3193 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: f623427e75a11624765bf76950a1e27a6176b06216e1d88a2fca4161a2d5d43f firefox-68.2.0-1.el7.centos.i686.rpm 6cb2fc6d8ca2606f2056b058a902cb4f2bb49e1c1ed85eaf45404bf3b50f0944 firefox-68.2.0-1.el7.centos.x86_64.rpm Source: 77808d14ad945553e17146efbf969ae8059c0a88a20259a0792312cebf80114e firefox-68.2.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 31 Oct 2019 14:48:49 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:3210 Important CentOS 7 thunderbird Security Update Message-ID: <20191031144839.GA14504(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:3210 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:3210 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4e0b083ad2cf304b4b3cc49e4cf6ba35f4f0845b279fffe77f4a5f647a18e9c4 thunderbird-68.2.0-1.el7.centos.x86_64.rpm Source: f4370d730dc220cbfe085587821fd05365005b4316c8ae91992dd30cc07335bd thunderbird-68.2.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Thu, 31 Oct 2019 14:50:12 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:3197 Important CentOS 7 sudo Security Update Message-ID: <20191031145012.GA14672(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:3197 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:3197 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 51bef6c9700b2222adbfab925c0859b1f53835237cfecf4e7d4f4645e3832b1b sudo-1.8.23-4.el7_7.1.x86_64.rpm 175dbcd940f43918e139a89cb19e420fdaa2dbe516ec0da192094c2b3f97af1f sudo-devel-1.8.23-4.el7_7.1.i686.rpm 317ab59b373fee0a9527429d600e57a58023726b1cbb425978b4584c3ae7e98f sudo-devel-1.8.23-4.el7_7.1.x86_64.rpm Source: 3a1a41999d8973d8a8ec358e67f076070e59c3c908e57eaef877d2111a1907d9 sudo-1.8.23-4.el7_7.1.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 177, Issue 1 ***********************************************

1 0

Re: [CentOS] NFS shutdown issue
by Darby Vicker 01 Nov '19

01 Nov '19

> I disagree. This is probably part of the NFS server, to catch when > systems are being shut down and cleanly notifying and disconnecting > clients. Interesting - thanks for the info. I can understand that behavior in a shutdown situation. But I'm surprised that unmounting (either cleanly or uncleanly) one of two exported filesystems triggers the NFS service to shutdown completely. Is this consistent with other peoples experiences?

2 1

Help with CentOS 7 and nvidia
by Jerry Geis 01 Nov '19

01 Nov '19

Hello my hardware has: 03:00.0 VGA compatible controller: NVIDIA Corporation GT218 [ION] (rev a2) rpm -qa | grep nvidia nvidia-detect-410.78-1.el7.elrepo.x86_64 kmod-nvidia-340xx-340.107-2.el7_6.elrepo.x86_64 nvidia-x11-drv-340xx-340.107-1.el7.elrepo.x86_64 rpm -qa | grep libva libva-vdpau-driver-0.7.4-19.el7.x86_64 libva-utils-1.8.3-4.el7.x86_64 libva-devel-1.8.3-1.el7.x86_64 libva-1.8.3-1.el7.x86_64 rpm -qa | grep vdpau libva-vdpau-driver-0.7.4-19.el7.x86_64 libvdpau-1.1.1-3.el7.x86_64 vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 0.7.4 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG4Simple : VAEntrypointVLD VAProfileMPEG4AdvancedSimple : VAEntrypointVLD VAProfileH264Main : VAEntrypointVLD VAProfileH264High : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD grep Driver /var/log/Xorg.0.log [ 43.069] X.Org Video Driver: 24.0 [ 45.744] Module class: X.Org Video Driver [ 45.744] (II) NVIDIA dlloader X Driver 340.107 Thu May 24 21:18:05 PDT 2018 [ 45.744] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 47.328] Module class: X.Org XInput Driver grep -i vdpau /var/log/Xorg.0.log [ 46.978] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia So to me all looks good - but there is no hardware acceleration??? When I play the video with totem its taking way too much CPU. I removed the ~/.cache/gstreamer* . What have I missed ? Jerry

3 2

HA tools from clusterlabs.org
by lejeczek 31 Oct '19

31 Oct '19

hi everybody, would you know if 8 version is going to have HA solutions from clusterlabs.org available, just like Centos7 has? (from Centos' own repos/streams) many thanks, L.

2 2

Limit user password by time
by Gestió Servidors 31 Oct '19

31 Oct '19

Hello, I would like to know if it is possible to configure a password that expires, once user has logged, after 2 hours, for example. Thanks.

2 1

udev on CEntOS7 - can't get a match, looking for tips...
by John H Nyhuis 30 Oct '19

30 Oct '19

The mtx binary requires my tape library to be assigned a sg# driver, but the kernel periodically renumbers the sg devices. Normally, we would write a udev rule to manually assign a persistent name, but it looks like things have changed as I can't seem to get a match on CEntOS7. I'd appreciate any feedback or pointers to help me get my rule working. My two attempts are below. cat /etc/udev/rules.d/90-local.rules KERNEL=="sg[0-9]*", SUBSYSTEM=="scsi_generic", \ ENV{ID_SERIAL}=="1QUANTUM_D0H0112430_LLA", SYMLINK+="sg8" SUBSYSTEM=="scsi", SUBSYSTEMS=="scsi_genric", \ ATTRS{model}=="Scalar i40-i80 ", SYMLINK:="sg8" Neither rule above generates a match with udev, so I still have something wrong. Right now the assignment is sg7 (but it's had other names in the past. udevadm info --query=all --name=/dev/sg7 P: /devices/pci0000:00/0000:00:07.0/0000:04:00.0/0000:05:00.0/0000:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1/scsi_generic/sg7 N: sg7 S: tape/by-id/scsi-1QUANTUM_D0H0112430_LLA E: DEVLINKS=/dev/tape/by-id/scsi-1QUANTUM_D0H0112430_LLA E: DEVNAME=/dev/sg7 E: DEVPATH=/devices/pci0000:00/0000:00:07.0/0000:04:00.0/0000:05:00.0/0000:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1/scsi_generic/sg7 E: ID_MODEL=Scalar_i40-i80 E: ID_MODEL_ENC=Scalar\x20i40-i80\x20\x20 E: ID_REVISION=190G E: ID_SCSI=1 E: ID_SCSI_SERIAL=QUANTUMD0H0112430_LLA E: ID_SERIAL=1QUANTUM_D0H0112430_LLA E: ID_SERIAL_SHORT=QUANTUM_D0H0112430_LLA E: ID_TYPE=generic E: ID_VENDOR=QUANTUM E: ID_VENDOR_ENC=QUANTUM\x20 E: MAJOR=21 E: MINOR=7 E: SUBSYSTEM=scsi_generic E: USEC_INITIALIZED=28815292891 Assigned and parent device listed below: udevadm info -a -p `udevadm info -q path -n /dev/sg7` looking at device '/devices/pci0000:00/0000:00:07.0/0000:04:00.0/0000:05:00.0/0000:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1/scsi_generic/sg7': KERNEL=="sg7" SUBSYSTEM=="scsi_generic" DRIVER=="" looking at parent device '/devices/pci0000:00/0000:00:07.0/0000:04:00.0/0000:05:00.0/0000:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1': KERNELS=="8:0:0:1" SUBSYSTEMS=="scsi" DRIVERS=="ch" ATTRS{rev}=="190G" ATTRS{type}=="8" ATTRS{scsi_level}=="4" ATTRS{model}=="Scalar i40-i80 " ATTRS{state}=="running" ATTRS{unpriv_sgio}=="0" ATTRS{queue_type}=="none" ATTRS{iodone_cnt}=="0xe2" ATTRS{iorequest_cnt}=="0xe2" ATTRS{queue_ramp_up_period}=="120000" ATTRS{device_busy}=="0" ATTRS{evt_capacity_change_reported}=="0" ATTRS{timeout}=="0" ATTRS{evt_media_change}=="0" ATTRS{ioerr_cnt}=="0x7" ATTRS{queue_depth}=="30" ATTRS{vendor}=="QUANTUM " ATTRS{evt_soft_threshold_reached}=="0" ATTRS{device_blocked}=="0" ATTRS{evt_mode_parameter_change_reported}=="0" ATTRS{evt_lun_change_reported}=="0" ATTRS{evt_inquiry_change_reported}=="0" ATTRS{dh_state}=="detached" ATTRS{iocounterbits}=="32" ATTRS{eh_timeout}=="10" Would anyone mind pointing out the error in my udev rule or proposing a better way of getting a persistent sg device name? -- Thanks in advance, John H. Nyhuis Desk: (206)-685-8334 jnyhuis(a)uw.edu Box 359461, 15th floor, 106

4 6

No IrDA Support with CentOS anymore?
by andreas.reschke＠mahle.com 30 Oct '19

30 Oct '19

Hi there, I've a laptop with CentOS 8 and a PC with CentOS 7. After 3 years of break I was Scuba Diving last 3 weeks. Back at home I wish to download all dive logs from my divecomputer connext via IrDA to my PC. But no kernel modul for IrDA was found. [root@rechner1 ~]# modprobe ircomm modprobe: FATAL: Module ircomm not found in directory /lib/modules/4.18.0-147.6.el8.x86_64 [root@rechner1 ~]# modprobe ircomm_tty modprobe: FATAL: Module ircomm_tty not found in directory /lib/modules/4.18.0-147.6.el8.x86_64 [root@destn40768 ~]# [root@rechner1 ~]# lsusb | grep -i irda Bus 002 Device 011: ID 9710:7780 MosChip Semiconductor MCS7780 4Mbps Fast IrDA Adapter [root@rechner1 ~]# Same with CentOS7 How do I get IrDA support? Mit freundlichen Grüßen / Kind regards Andreas Reschke MAHLE International GmbH Unix/Linux-Administration (FIE4.1) Pragstr. 26 - 46, 70376 Stuttgart, Germany Phone: +49 711 501-475 98 Mobile: +49 173 3197397 andreas.reschke(a)mahle.com, https://www.mahle.com MAHLE International GmbH, Location: Stuttgart, Registered: Amtsgericht Stuttgart HRB 16413 Management Board: Dr. Jörg Stratmann, Michael Frick, Michael Glowatzki, Martin Wellhöffer

2 2

Security Policies
by JEFFREY MC DANIELS 29 Oct '19

29 Oct '19

Hello, I just started working with CentOS and I want to say it's a great OS. The only issue is that I no longer see the lists of Security polices during the installation and I would like to know how to install them in Centos 8

3 2

NFS shutdown issue
by Darby Vicker 29 Oct '19

29 Oct '19

Hi all, I have an odd interaction on a CentOS 7 file server. The basic setup is a minimal 7.x install. I have 4 internal drives (/dev/sd[a-d]) configured in a RAID5 and mounted locally on /data. This is exported via NFS to ~12 workstations which use the exported file systems for /home. I have an external drive connected via USB (/dev/sde) and mounted on /rsnapshot. I use rsnapshot to back up the RAID5 to the external drive periodically. I also export /rsnapshot (read only) to the workstations so users can grab a backup copy of /home data if needed. These two mounts (/data and /rsnapshot) should be independent of each other. However, a couple of times now I've had somebody accidentally unplug my backup drive (sde), which causes NFS to shut down. Here are the messages entries when this happens. Oct 28 16:34:12 linux-fs01 kernel: xhci_hcd 0000:00:14.0: Cannot set link state. Oct 28 16:34:12 linux-fs01 kernel: usb usb4-port2: cannot disable (err = -32) Oct 28 16:34:12 linux-fs01 kernel: usb 4-2: USB disconnect, device number 2 Oct 28 16:34:17 linux-fs01 systemd: Stopping NFS server and services... Oct 28 16:34:17 linux-fs01 systemd: Stopped NFS server and services. Oct 28 16:34:17 linux-fs01 systemd: Stopping NFSv4 ID-name mapping service... Oct 28 16:34:17 linux-fs01 systemd: Stopping NFS Mount Daemon... Oct 28 16:34:17 linux-fs01 systemd: Stopped NFSv4 ID-name mapping service. Oct 28 16:34:17 linux-fs01 rpc.mountd[10570]: Caught signal 15, un-registering and exiting. Oct 28 16:34:17 linux-fs01 systemd: Stopped NFS Mount Daemon. Oct 28 16:34:17 linux-fs01 systemd: Stopped target Local File Systems. Oct 28 16:34:17 linux-fs01 systemd: Unmounting /rsnapshot... Oct 28 16:34:17 linux-fs01 kernel: XFS (sde1): Unmounting Filesystem Oct 28 16:34:19 linux-fs01 kernel: XFS (sde1): metadata I/O error: block 0x2800ccac8 ("xlog_iodone") error 5 numblks 64 Oct 28 16:34:19 linux-fs01 kernel: XFS (sde1): xfs_do_force_shutdown(0x2) called from line 1221 of file fs/xfs/xfs_log.c. Return address = 0xffffffffc06cec30 Oct 28 16:34:19 linux-fs01 kernel: XFS (sde1): Log I/O Error Detected. Shutting down filesystem Oct 28 16:34:19 linux-fs01 kernel: XFS (sde1): Please umount the filesystem and rectify the problem(s) Oct 28 16:34:19 linux-fs01 kernel: XFS (sde1): Unable to update superblock counters. Freespace may not be correct on next mount. Oct 28 16:34:20 linux-fs01 systemd: Unmounted /rsnapshot. Oct 28 16:34:20 linux-fs01 kernel: nfsd: last server has exited, flushing export cache Should it be expected that NFS stops when one of the exports is unmounted? I don't think so. Below is some more info on the setup. Getting another eye on this would be much appreciated. Darby /etc/fstab entries /dev/md/Storage /data xfs defaults 0 0 LABEL=rsnapshot /rsnapshot xfs defaults 0 0 /etc/exports /data 10.0.223.0/22(rw,async,no_root_squash) /rsnapshot 10.0.223.0/22(ro,sync,no_root_squash) mdrad info [root@linux-fs01 ~]# cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md125 : active raid5 sda[3] sdb[2] sdc[1] sdd[0] 134217728 blocks super external:/md127/0 level 5, 64k chunk, algorithm 0 [4/4] [UUUU] md126 : active raid5 sda[3] sdb[2] sdc[1] sdd[0] 5440012288 blocks super external:/md127/1 level 5, 64k chunk, algorithm 0 [4/4] [UUUU] md127 : inactive sda[3](S) sdb[2](S) sdd[1](S) sdc[0](S) 20804 blocks super external:imsm unused devices: <none> [root@linux-fs01 ~]# mdadm -D /dev/md/System /dev/md/System: Container : /dev/md/imsm0, member 0 Raid Level : raid5 Array Size : 134217728 (128.00 GiB 137.44 GB) Used Dev Size : 44739328 (42.67 GiB 45.81 GB) Raid Devices : 4 Total Devices : 4 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-asymmetric Chunk Size : 64K Consistency Policy : resync UUID : b359c1f9:04655baa:52b3ed0c:5aa3c9b6 Number Major Minor RaidDevice State 3 8 0 0 active sync /dev/sda 2 8 16 1 active sync /dev/sdb 1 8 32 2 active sync /dev/sdc 0 8 48 3 active sync /dev/sdd [root@linux-fs01 ~]#

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss