Discuss

discuss@lists.centos.org

3 participants
34748 discussions

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

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