Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Re: [CentOS] [CentOS-announce] CESA-2017:2907 Important CentOS 7 wpa_supplicant Security Update
by Yves Bellefeuille 18 Oct '17

18 Oct '17

Johnny Hughes <johnny(a)centos.org> wrote: > CentOS Errata and Security Advisory 2017:2907 Important > > Upstream details at : https://access.redhat.com/errata/RHSA-2017:2907 Will there also be an update for CentOS 6? Or does the problem not exist with CentOS 6? -- Yves Bellefeuille <yan(a)storm.ca>

4 4

Null deference panic in CentOS-6.5
by wuzhouhui 18 Oct '17

18 Oct '17

Hi, I got a panic when running CentOS-6.5: crash> bt PID: 106074 TASK: ffff8839c1e32ae0 CPU: 4 COMMAND: "flushd4[cbd-sd-" #0 [ffff8839c2a91900] machine_kexec at ffffffff81038fa9 #1 [ffff8839c2a91960] crash_kexec at ffffffff810c5992 #2 [ffff8839c2a91a30] oops_end at ffffffff81515c90 #3 [ffff8839c2a91a60] no_context at ffffffff81049f1b #4 [ffff8839c2a91ab0] __bad_area_nosemaphore at ffffffff8104a1a5 #5 [ffff8839c2a91b00] bad_area_nosemaphore at ffffffff8104a273 #6 [ffff8839c2a91b10] __do_page_fault at ffffffff8104a9bf #7 [ffff8839c2a91c30] do_page_fault at ffffffff81517bae #8 [ffff8839c2a91c60] page_fault at ffffffff81514f95 [exception RIP: rb_next+1] RIP: ffffffff81286e21 RSP: ffff8839c2a91d10 RFLAGS: 00010046 RAX: 0000000000000000 RBX: ffff88204b501c00 RCX: 0000000000000000 RDX: ffff88013bc56840 RSI: ffff88013bc568d8 RDI: 0000000000000010 RBP: ffff8839c2a91d60 R8: 0000000000000001 R9: 0000000000000001 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #9 [ffff8839c2a91d18] pick_next_task_fair at ffffffff81068121 #10 [ffff8839c2a91d68] schedule at ffffffff81511e08 #11 [ffff8839c2a91e28] flushd_run at ffffffffa07a2cbd [cbd] #12 [ffff8839c2a91ee8] kthread at ffffffff8109acd6 #13 [ffff8839c2a91f48] kernel_thread at ffffffff8100c20a The [cbd] is a module developed by us, I think this bug has nothing to do with it. And the contents of rq in pick_next_task(struct rq *rq) is (see attachement for full contents of struct rq): struct rq { lock = { raw_lock = { slock = 67109881 } }, nr_running = 2, cpu_load = {0, 5923, 14993, 13888, 9115}, last_load_update_tick = 4365159236, nohz_balance_kick = 0 '\000', skip_clock_update = 0, load = { weight = 2, inv_weight = 0 }, nr_load_updates = 21530842, nr_switches = 148355748, cfs = { load = { weight = 2, inv_weight = 0 }, nr_running = 1, h_nr_running = 2, exec_clock = 3309310258875, min_vruntime = 1181294560093, tasks_timeline = { rb_node = 0x0 }, rb_leftmost = 0x0, tasks = { next = 0xffff88013bc568e8, prev = 0xffff88013bc568e8 }, balance_iterator = 0xffff88013bc568e8, curr = 0xffff88204b501e00, next = 0x0, last = 0x0, skip = 0x0, nr_spread_over = 5, .... We can see that the value if rq->cfs.nr_running is not zero, but rb_leftmost is null. With skip is null, this causes null deference panic in pick_next_entity() of pick_next_task_fair(). Does anyone have encountered same problem or advice? Thanks

5 7

Auth failure messages
by david 18 Oct '17

18 Oct '17

Folks I am using sendmail as my mail server. SELINUX is disabled. I observe messages in Centos 7 (and 6) in /var/log/messages, similar to: saslauthd[2765]: do_auth : auth failure: [user=bettie] [service=smtp] [realm=] [mech=pam] [reason=PAM auth error] I guess that this is because somebody tried to access one of the SMTP ports with a logon attempt. This is understandable; there are crackers out there. I'd like to block SMTP completely from the originating sender (by dropping the IP packets), but don't know how to figure out what the IP address is. I don't see anything in the "maillog" that, for example, has the name "bettie" or some other clue. The only thing I see is a message like sendmail[5452]: v9HIoBox005452: [xxx.xxx.xxx.xxx] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA with a close timestamp, but I'm reluctant to tie the two log entries together. Is there some log, or log setting that might enable me to tie the do_auth error to a specific IP address? I'm very reluctant to change mail servers to postfix or something like that. Thanks David

3 2

gdevilspie on mate
by H 18 Oct '17

18 Oct '17

I just read about gdevilspie on this list the other day and downloaded it for my mate desktop. Although it installed, it complains that python-wnck is not installed. Does anyone know if it is supposed to work on mate? I would have expected it to install python-wnck as a requirement if not already installed?

3 7

Dahdi get latest
by Jerry Geis 18 Oct '17

18 Oct '17

I am trying to use dahdi complete 2.11.1 with a 4.13 kernel. - NOT working for know reasons. I tried applying two patches but still get compile errors. AHHH! How do I just use git to get the latest with the fixes ???? This command did not work - I still get the errors. git clone git://git.asterisk.org/dahdi/linux dahdi-linux Thanks, Jerry

1 1

CentOS-announce Digest, Vol 152, Issue 6
by centos-announce-request＠centos.org 18 Oct '17

18 Oct '17

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-2017:2907 Important CentOS 7 wpa_supplicant Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Oct 2017 21:54:54 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2907 Important CentOS 7 wpa_supplicant Security Update Message-ID: <20171017215454.GA49502(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2907 Important Upstream details at : https://access.redhat.com/errata/RHSA-2017:2907 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: bcb982dc33b01aeb8b0807cee6d6b07bfe0ca020fda96d2b64e34e6912daa698 wpa_supplicant-2.6-5.el7_4.1.x86_64.rpm Source: d19567c0ecc7a639590f1ebd018618a7e061c42c7549fb60070d6f6581efa71b wpa_supplicant-2.6-5.el7_4.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 152, Issue 6 ***********************************************

1 0

AMD epyc/naples
by lejeczek 18 Oct '17

18 Oct '17

do we know if 7.4 is good for new AMD cpus? More specifically for virtualization. Historically there were some issues and things like AMD's IOMMU & similar were not exactly perfectly supported by HW vendors, UEFI/bios <=> kernel. I'm thinking of getting one and I wonder if it might be too soon. I wonder if above things are at least in an acceptable shape of older Opteron platform, and not worse. Any experience? b.w. L.

2 1

lvconvert(split) - raid10 => raid0
by lejeczek 17 Oct '17

17 Oct '17

hi guys, gals do you know if conversion from lvm's raid10 to raid0 is possible? I'm fiddling with --splitmirrors but it gets me nowhere. On "takeover" subject man pages says: "..between striped/raid0 and raid10."" but no details, nowhere I could find documentation, nor a howto. many thanks, L.

2 1

CentOS 7 not shutting down correctly
by Nicolas Kovacs 16 Oct '17

16 Oct '17

Hi, I have CentOS 7 with KDE installed on my workstation. Sometimes - like just now - the system refuses to shutdown correctly. The problem appeared since I installed the OpenVAS vulnerability scanner (the one from EPEL), so I don't know if this is linked. When I try to shutdown the system, I see shutdown messages, and then it stops short on the following message: [ OK ] Stopped logout off all iSCSI sessions on shutdown After this I can wait for hours, nothing happens until I hit the Reset button. Now I'm a bit frustrated because this kind of behavior was the reason I left the Windows world back in 2001, to discover the joys of Slackware and then Red Hat. I also notice this kind of thing never (ever) happened with CentOS versions 5.x and 6.x. Any suggestions? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 3

systemctl reboot -- server not accessible after reboot
by Mike 16 Oct '17

16 Oct '17

Hi, Such a simple problem, but I can't figure out the cause. Supermicro server with a Xeon E3-1200 cpu. 1U entry level item. Using CentOS 7 from ~$root --- systemctl reboot Server disconnects my ssh connection and never comes back up. Go to the server and the power is on but the server is not accessible by ssh. When I connect a monitor and keyboard --- non-responsive. It's like it's in suspend mode. I push and hold the power button until the server fully powers down. Push power again and everything boots, goes to prompt, and all is well. When I try systemctl reboot directly on the server. Same problem --- does not start to login prompt. Manually power down and power up again --- works and all is well. Anyone have this problem before? I've checked all the BIOS options and I can't find anything misconfigured. Thanks for your help. Mike

6 10

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss