Discuss

discuss@lists.centos.org

5 participants
34752 discussions

Rsyslog warning
by SternData 20 Dec '18

20 Dec '18

I see this error every day. What should I be looking at to fix it? rsyslogd: sd_journal_get_cursor() failed: 'Cannot assign requested address' [v8.24.0-34.el7] -- -- Steve

1 0

abrt-watch-log -F BUG: WARNING:
by Ilyass Kaouam 20 Dec '18

20 Dec '18

Hi, Please what is this error ? /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch Kernel panic - not syncing: Machine Check Exception: Machine check events logged divide error: bounds: coprocessor segment overrun: invalid TSS: segment not present: invalid opcode: alignment check: stack segment: fpu exception: simd exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops -xtD uname -a 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux CentOS Linux release 7.5.1804 (Core) Thank's --

1 0

kickstart install
by Jerry Geis 20 Dec '18

20 Dec '18

In changing from a 7.5 to 7.6 automated install. 7.6 is not happy and the install process stops and shows the screen where the "Install Source" is not happy. I enter 3 to see what its set for, I select network, I select http and I see my URL that my kickstart file has. It looks right - but its not happy. I tried looking in other consoles (text mode) to see any error and nothing is showing. How do I see what the error is about the install source ? Thanks, Jerry

1 1

Updates in 7.6.1810/os Repository from the CR Announce List
by Johnny Hughes 20 Dec '18

20 Dec '18

As part of the CR process ( https://wiki.centos.org/AdditionalResources/Repositories/CR ), the following updates were done and are included in the CentOS base ( os/ ) repository for CentOS Linux 7.6.1810. https://lists.centos.org/pipermail/centos-cr-announce/2018-November/thread.… https://lists.centos.org/pipermail/centos-cr-announce/2018-December/thread.… There was an issue with the announcement generation scripting that used the errata API to pull information for the announcements (that is now fixed), so some of the announcements happened later than the actual build date and release date of the packages (as an example, the date we created the man-db announcement was December 19th ( https://lists.centos.org/pipermail/centos-cr-announce/2018-December/005800.… ) .. the actual date of the package build was 30 Oct 2018 08:26:54 PM UTC .. and it was signed and then released initially into CR on 12 Nov 2018. We have since generated any missing announcements to the CR announce list and also any updates to the os/ repo (that live in the udpates/ repo) were announced to this centos-announce list. Thanks, Johnny Hughes

1 0

Atomic ISO unavailable
by Eric Lehmann 20 Dec '18

20 Dec '18

Hello The http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7-Install… provided in https://wiki.centos.org/SpecialInterestGroup/Atomic/Download is down. Does anybody know if there is a reason for that? Regards

2 1

A question about why the function "recv" return 0
by yf chu 20 Dec '18

20 Dec '18

I am a website developer. We deploy a Nginx server on centos to provide HTTP services. Recently, some customers of our website were complaining about that occasionally they could not open the webpage, the web browser show that the tcp connection was reset. I checked the Nginx logs and source code and found that the function "recv" return 0 when some customers made HTTP requests. Our customers have confirmed that their network was ok at that time. Now, I could not find any clue about this issue. Is there any solution to find the reason? Does it have something to do with firewall, or ISP? Can we find something from the system log?

3 3

CentOS-announce Digest, Vol 166, Issue 6
by centos-announce-request＠centos.org 20 Dec '18

20 Dec '18

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-2018:3854 Low CentOS 6 ntp Security Update (Johnny Hughes) 2. CEBA-2018:3847 CentOS 7 pacemaker BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 19 Dec 2018 23:46:54 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:3854 Low CentOS 6 ntp Security Update Message-ID: <20181219234654.GA25454(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:3854 Low Upstream details at : https://access.redhat.com/errata/RHSA-2018:3854 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8d4c7f5edb0fb14af55ff6f74ee15349e69f5a8ff180b39b2fbbd01d99c0199a ntp-4.2.6p5-15.el6.centos.i686.rpm a9a5283906f361f4b2d85be307eb8c7574bc749ec6e9d03988831b628e2bd273 ntpdate-4.2.6p5-15.el6.centos.i686.rpm 18edea5cb7d5a13afc34464fd4cef7cbd46e6d6a7b91acbf1a6dd58a9997a411 ntp-doc-4.2.6p5-15.el6.centos.noarch.rpm ba4d8eff03ce5ffdd42025c0aa9e21ca1429f02909e2e0f39a2d838c22e04eae ntp-perl-4.2.6p5-15.el6.centos.i686.rpm x86_64: b6ee6afaf3ff4b90b3a3f0077e111362a9ce6912384799b4798cfba3984a60ec ntp-4.2.6p5-15.el6.centos.x86_64.rpm 0bd3608f6a5a0935529f9e16de6b875ac810e89f25fc03a034e1e11e763b9bf9 ntpdate-4.2.6p5-15.el6.centos.x86_64.rpm 18edea5cb7d5a13afc34464fd4cef7cbd46e6d6a7b91acbf1a6dd58a9997a411 ntp-doc-4.2.6p5-15.el6.centos.noarch.rpm c638a5e57e7895b4c605f63077902c141ada8a26bf2a94272dc0d11f0a35bc30 ntp-perl-4.2.6p5-15.el6.centos.x86_64.rpm Source: b41d310c7c14b58374dfd75e55b5b9b9f7105ca983e0a3ac4cf43be95e47da8b ntp-4.2.6p5-15.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 19 Dec 2018 23:47:22 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2018:3847 CentOS 7 pacemaker BugFix Update Message-ID: <20181219234722.GA25572(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2018:3847 Upstream details at : https://access.redhat.com/errata/RHBA-2018:3847 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 2e35900146ccf77ab81cb32e8a7957c10aa678bae36c55744e9b18f1750a95e8 pacemaker-1.1.19-8.el7_6.2.x86_64.rpm 5b54875eaccb9c93054e5eef35caf5ff46e2f0cfbd2acb859b813cb3f473301f pacemaker-cli-1.1.19-8.el7_6.2.x86_64.rpm e2312c85fc1373cf28748db20cfee3135a390b48b9c0abce874e9939af9377fb pacemaker-cluster-libs-1.1.19-8.el7_6.2.i686.rpm 302e43e36b0262d23fb2cd34f393eb5834c7f82944d79d3e46923f9d6544cb54 pacemaker-cluster-libs-1.1.19-8.el7_6.2.x86_64.rpm a7b495377398e9c514391716bc0a34c66287be8fbad4b47c4d6ff48c9edfa1b0 pacemaker-cts-1.1.19-8.el7_6.2.x86_64.rpm e295d5e858815ad9b39d2498e24de56a7c4aef479f04dedc0e86cee13aaf1727 pacemaker-doc-1.1.19-8.el7_6.2.x86_64.rpm 3d8ca4d2a12878da0d49541b27c8266d6d7e01f8c984b66443f8b1a87b55c004 pacemaker-libs-1.1.19-8.el7_6.2.i686.rpm a19e6555225e34aed04e981aad4925a85c67452b92cece2000e76d03fce500dc pacemaker-libs-1.1.19-8.el7_6.2.x86_64.rpm 65952d9647e01febadc9e68a438e2ca1cf4ab15deaace176761edcbe094ec380 pacemaker-libs-devel-1.1.19-8.el7_6.2.i686.rpm bfa7aa216dab27e96169eb2b63ed0e233eaba1368dd2bbb00e22eaa52348f321 pacemaker-libs-devel-1.1.19-8.el7_6.2.x86_64.rpm db71a78725c41b66642e5ed756d0b7bfeee2ca1230cbf9433ee1cfbc27d245f0 pacemaker-nagios-plugins-metadata-1.1.19-8.el7_6.2.x86_64.rpm 51f9cbc0b8ccf236667e2b6bf057b662a44abdb4633efa58c4961362a9e3bf6a pacemaker-remote-1.1.19-8.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 166, Issue 6 ***********************************************

1 0

VNC question
by isdtor 20 Dec '18

20 Dec '18

We have run into the infamous black screen problem with tigervnc under CentOS7, which prompted me to look into how vnc is configured here. https://access.redhat.com/solutions/966063 Am I reading this correctly - root needs to set up a systemd vnc service for every user and display individually? Compared to e.g. CentOS before 7, or indeed any other Linux/Unix system where vnc is completely under user control?

4 7

how to implement rate-limiting measures on interfaces using IPTables?
by Sean Son 19 Dec '18

19 Dec '18

Hello all I have been tasked to implement rate-limiting measures on interfaces using IPTables in RHEL 7. I know that in order to implement it using FirewallD, I will need to run the following command: firewall-cmd --direct --add-rule ipv4 filter IN_public_allow 0 -p tcp -m limit --limit 25/minute --limit-burst 100 -j ACCEPT How would I do the same using IPtables? Thanks!! Sean

2 1

Cgroups : memory.limit_in_bytes and memory.usage_in_bytes includes file cache?
by valleru＠cbio.mskcc.org 19 Dec '18

19 Dec '18

Hello All, We were under the assumption that Cgroups memory controller, limits memory based on just the RSS size of the process. However, i see that the process is getting killed even when the RSS size is very low compared to the limit in bytes. For example: cat memory.stat cache 85880266752 rss 2441216 rss_huge 0 mapped_file 8192 swap 0 pgpgin 29265847812 pgpgout 29244880354 pgfault 48530374728 pgmajfault 20 inactive_anon 0 active_anon 2441216 inactive_file 85879496704 active_file 770048 unevictable 0 hierarchical_memory_limit 85899345920 hierarchical_memsw_limit 85899345920 total_cache 85880266752 total_rss 2441216 total_rss_huge 0 total_mapped_file 8192 total_swap 0 total_pgpgin 29265847812 total_pgpgout 29244880354 total_pgfault 48530374728 total_pgmajfault 20 total_inactive_anon 0 total_active_anon 2441216 total_inactive_file 85879496704 total_active_file 770048 total_unevictable 0 cat memory.usage_in_bytes 85885800448 cat memory.limit_in_bytes 85899345920 What is confusing is that , why is memory.usage_in_bytes being shown as 85885800448, when the RSS is just 2441216? Is it true that memory.usage_in_bytes/memory.limit_in_bytes takes files cache into consideration when calculating the usage? Regards, Lohit

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