Discuss

discuss@lists.centos.org

3 participants
34748 discussions

Question on booting other kernel
by adrian＠pa0rda.nl 14 Jan '16

14 Jan '16

Hi, In CentOS6 I do: echo "savedefault --default=0 --once" | grub --batch My question is how do I do the same on CentOS7? Any ideas? Adrian -- Adri P. van Bloois Antonlaan 104 email: adrian(a)pa0rda.nl 3701 VG Zeist voice: +31-(0)-30-6912741 The Netherlands fax: NONE 52 05'15.77"N 5 4'44.56"E QTH-locater JO 22 OC "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

2 1

CentOS 7, missing tools
by m.roth＠5-cent.us 14 Jan '16

14 Jan '16

I'm trying to resolve an issue where a back is taking a *long* time. The data's being pulled from a CentOS 6 box by a CentOS 7 box. I went to use netstat, and iostat and sar... and they're not there. Should I install sysstat, or are there replacement tools I'm expected to use? mark

2 1

Re: [CentOS] Fwd: Heads up: OpenSSH users
by Timo Schöler 14 Jan '16

14 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 01/14/2016 06:05 PM, Timo Schöler wrote: > On 01/14/2016 05:34 PM, m.roth(a)5-cent.us wrote: >> Michael H wrote: >>> Probably worth a read... >>> >>> http://www.openssh.com/txt/release-7.1p2 >>> >>>> Important SSH patch coming soon. For now, everyone on all >>>> operating systems, please do the following: >>>> >>>> Add undocumented "UseRoaming no" to ssh_config or use >>>> "-oUseRoaming=no" to prevent upcoming #openssh client bug >>>> CVE-2016-0777. More later. >>> >>> echo "UseRoaming no" >> /etc/ssh/ssh_config > >> Please clarify - will the update add *Roam* to >> /etc/ssh/ssh_config? > > It will fix the bug. > >> I've just checked on two systems that are CentOS 7, a server, and >> a workstation that I literally built yesterday, and grep -i on >> both reports "no, not here". > > Yes, as it's undocumented, but enabled since about 2010. FYI: https://github.com/openssh/openssh-portable/search?q=AppGate+Network+Sec urity+AB > Even OpenBSD 5.9 (pre-release, it's going to be released on May > 1st, 2016) does not mention it. > > Timo > >> mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlaX2IIACgkQuSPmkPhAW0rh0AD+Kje8MZE5xlnK1YQlH1H7oFgK M6JOfkgiWt3gvdzOjewA/RgopaQKm7YkdIgiiVRCVoKtUaRVieBr6xz/SccrISFR =94uA -----END PGP SIGNATURE-----

1 0

systemd: SIGPWR handler for Centos 7.2?
by Harald Dunkel 14 Jan '16

14 Jan '16

Hi folks, it seems that sigpwr.target is just a dummy. Something like kill -PWR 1 or systemctl isolate sigpwr.target is visible in the journal, but it does not power down the host. This breaks a clean shutdown of LXContainers setup with Centos 7.2. I would guess there are problems with UPS monitors, too. Is there a workaround? Every helpful comment is highly appreciated Harri

1 0

CentOS-announce Digest, Vol 131, Issue 4
by centos-announce-request＠centos.org 14 Jan '16

14 Jan '16

1 0

Balsa problem
by Fred Smith 13 Jan '16

13 Jan '16

Wondering if anyone here has built Balsa for Centos-7. I've used it on Centos 5 and 6 for years, though I had to compile it myself. It compiles cleanly on c7, but when run I keep getting error messages that say "Failure to sync mailbox xxxx" that seem to happen when I try to view a mailbox that has new/unread mail, or perhaps it happens when a mailbox receives new mail whilei Balsa is open, not certain which. I can't find anything in the Balsa mailing list(s) that helps, and Google isn't my friend in searching for any help on this. Anybody got any thoughts? -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- But God demonstrates his own love for us in this: While we were still sinners, Christ died for us. ------------------------------- Romans 5:8 (niv) ------------------------------

2 1

Slow to reboot
by Jerry Geis 13 Jan '16

13 Jan '16

I have CentOS 7.2 installed and when I issue a reboot I get a message about "A stop job is running" and its my process I start with a service file. My service file just runs a script. Type=forking ExecStart=/path/to/myscript What do I add so the reboot process goes faster ? My process does not need to stop anything before allowing the reboot. No databases are open or anything... Thanks, Jerry

1 0

Getting a boost patch into RHEL 7
by Alice Wonder 13 Jan '16

13 Jan '16

There is a patch to boost that should get into both CentOS and RHEL 7. I already sent an e-mail to the person who last modified the rpm spec file but I have no idea if he will even see the e-mail. The small patch - https://github.com/boostorg/asio/pull/23/files The problem it fixes - boost assumes that the TLS supports SSLv3 which the OpenSSL currently in RHEL / CentOS 7 does. However SSLv3 is incredibly old and is no longer considered to be secure and should not be used, so some alternative TLS implementations do not even include support for it. LibreSSL is one such example, and some distributions (e.g. Debian) have removed SSLv3 support from the OpenSSL library they ship. Given how old and insecure SSLv3 is and given the incredibly long support cycle of RHEL 7 it would not surprise me at all if removal of SSLv3 from the OpenSSL library in RHEL 7 is going to happen at some point in the next few years. As such getting this patch into boost will be necessary. The patch does not have any impact on boost when using TLS libraries that do support SSLv3 so it will not do any harm to get it into the packaging now. Getting it into the packaging now means boost is ready when the change is made, and it also makes life a lot easier for people like me who have to use an alternate TLS implementation because we need the EC stuff that RHEL removed from OpenSSL due to potential patent reasons that the lawyers were afraid of. I'm hoping someone on this list with some influence understands the issue. Filing a bug report with CentOS I suppose is also an option, but given that the patch doesn't solve a problem with any *current* CentOS packages, I doubt that would result in the bug trickling up to RHEL and they are the ones that have to apply the patch for it to make it into CentOS. Thank you for your time

2 4

CentOS-announce Digest, Vol 131, Issue 3
by centos-announce-request＠centos.org 13 Jan '16

13 Jan '16

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-2016:0020 CentOS 6 logwatch FASTTRACK BugFix Update (Johnny Hughes) 2. CEBA-2016:0021 CentOS 6 freeipmi FASTTRACK BugFix Update (Johnny Hughes) 3. CEBA-2016:0022 CentOS 6 libcanberra FASTTRACK BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 12 Jan 2016 14:15:16 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:0020 CentOS 6 logwatch FASTTRACK BugFix Update Message-ID: <20160112141516.GA49681(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:0020 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0020.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: cb9758c76a0ad8ee1ab12b5a6ffc27c72be8f88dc01359e3cb97c1754a2467d0 logwatch-7.3.6-54.el6.noarch.rpm x86_64: cb9758c76a0ad8ee1ab12b5a6ffc27c72be8f88dc01359e3cb97c1754a2467d0 logwatch-7.3.6-54.el6.noarch.rpm Source: f22084a0f4f5114cb4d38722d95ee8df3a36adf1fd0f7bae5bea88566ffc43b2 logwatch-7.3.6-54.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 12 Jan 2016 14:15:50 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:0021 CentOS 6 freeipmi FASTTRACK BugFix Update Message-ID: <20160112141550.GA49960(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:0021 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0021.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: bf1215c882abdfa6ebac45dbb0d701996afad41c7a35016c2d2bfc80ac8892ca freeipmi-1.2.1-7.el6.i686.rpm eb3dd2b37a3e4d29cb8e5645c4f235d3295a1e1ef74475189c1e9991889d594e freeipmi-bmc-watchdog-1.2.1-7.el6.i686.rpm 808666d9c36024a3c74754de809f27506f71d458073d51470ae1944b2d2d5740 freeipmi-devel-1.2.1-7.el6.i686.rpm 6297ec7d60e56d61613aa1752f557bbbcbf31b8f50a98f2859ea4a48bd10a837 freeipmi-ipmidetectd-1.2.1-7.el6.i686.rpm x86_64: bf1215c882abdfa6ebac45dbb0d701996afad41c7a35016c2d2bfc80ac8892ca freeipmi-1.2.1-7.el6.i686.rpm 12f33eb38f25269d76b841bf5621cd481d2f42a19ef26602dea632ccd57dab41 freeipmi-1.2.1-7.el6.x86_64.rpm baf1dfd1df735026492784bd572f7bfe7fe207e745ba9c865ed535e4b4bf47af freeipmi-bmc-watchdog-1.2.1-7.el6.x86_64.rpm 808666d9c36024a3c74754de809f27506f71d458073d51470ae1944b2d2d5740 freeipmi-devel-1.2.1-7.el6.i686.rpm 9e8e2f1fce93ea91b8c28503006f73b13bcf39a666df311da6dbff382b055ce7 freeipmi-devel-1.2.1-7.el6.x86_64.rpm a73a6523500070a91da712beb15cbcd5adfad5a3562ea8bb5012209b09f27d7b freeipmi-ipmidetectd-1.2.1-7.el6.x86_64.rpm Source: a11ff9f0fe520f17096ce63f774596d12f39346bfbb1eb7ac0aebbdce2a10193 freeipmi-1.2.1-7.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 12 Jan 2016 14:16:18 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:0022 CentOS 6 libcanberra FASTTRACK BugFix Update Message-ID: <20160112141618.GA50216(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:0022 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0022.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1d46b8216b0321300d9e849ef6638cce1502e291a76cc8946a15c6f29ec49d6d libcanberra-0.22-3.el6.i686.rpm e141de513daf28e63f332218a6bad7ca87e79835dda17cc06d19c923d5e0d7b0 libcanberra-devel-0.22-3.el6.i686.rpm 744deaeb955bb2fd3c7dcb448520e59b572b8c9523e5c24666809d418e697699 libcanberra-gtk2-0.22-3.el6.i686.rpm x86_64: 1d46b8216b0321300d9e849ef6638cce1502e291a76cc8946a15c6f29ec49d6d libcanberra-0.22-3.el6.i686.rpm 2f4030352f08891a3f43b26b0c4aa78817f1cdd5cdbb1e5afcf1d5bbe7701783 libcanberra-0.22-3.el6.x86_64.rpm e141de513daf28e63f332218a6bad7ca87e79835dda17cc06d19c923d5e0d7b0 libcanberra-devel-0.22-3.el6.i686.rpm 8651ac9eb23fd345ccb1847cec52bd1767bc8f4819dc986778b133c71c649b49 libcanberra-devel-0.22-3.el6.x86_64.rpm 744deaeb955bb2fd3c7dcb448520e59b572b8c9523e5c24666809d418e697699 libcanberra-gtk2-0.22-3.el6.i686.rpm 85665af03e46af9550800d312e81446de9559bd287ee3ea57dc731d45cfdea1c libcanberra-gtk2-0.22-3.el6.x86_64.rpm Source: 6a8d5306caa39c8e272551ecbbedfaf26046890f0b93ad9ee08e7029e55ad8ef libcanberra-0.22-3.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 131, Issue 3 ***********************************************

1 0

Centos 7 guest - long delay on mounting /boot with host disk write cache off
by Andrzej Szymanski 12 Jan '16

12 Jan '16

Hello, I've noticed a strange delay while booting a CentOS 7 guest on a CentOS 7 host with slow disks (7200RPM) with write cache off. The guest and host are freshly installed Centos 7 (host was fully patched before guest install). Guest is installed on an lvm pool residing on an md raid1 with two SATA 7200 RPM drives with their write caches off. The delay is on mounting /boot, the dmesg on the guest says: [ 23.491857] XFS (vda1): Mounting V4 Filesystem [ 46.668396] XFS (vda1): Ending clean mount [ 46.668404] SELinux: initialized (dev vda1, type xfs), uses xattr Subsequent mounts by hand on a running system last even longer - dmesg records: [ 96.442544] XFS (vda1): Unmounting Filesystem [ 100.086741] XFS (vda1): Mounting V4 Filesystem [ 146.098703] XFS (vda1): Ending clean mount [ 146.098721] SELinux: initialized (dev vda1, type xfs), uses xattr mounting "-o ro" doesn't help - dmesg records: [ 205.552778] XFS (vda1): Unmounting Filesystem [ 212.452724] XFS (vda1): Mounting V4 Filesystem [ 258.537459] XFS (vda1): Ending clean mount [ 258.537477] SELinux: initialized (dev vda1, type xfs), uses xattr but mounting with "-o ro,norecovery" does help - dmesg records: [ 263.795813] XFS (vda1): Unmounting Filesystem [ 271.973701] XFS (vda1): Mounting V4 filesystem in no-recovery mode. Filesystem will be inconsistent. [ 272.003618] SELinux: initialized (dev vda1, type xfs), uses xattr xfs_logprint -t /dev/vda1 says that the device is clean: xfs_logprint: data device: 0xfc01 log device: 0xfc01 daddr: 512032 length: 6824 log tail: 3447 head: 3447 state: <CLEAN> however the full xfs log contains a lot of entries xfs_logprint /dev/vda1 results in ~23000 lines of text. Permanent help is from xfs_repair which zeroes the log - a subsequent mount is fast, and subsequent reboots are fast. [ 411.290031] XFS (vda1): Mounting V4 Filesystem [ 411.456661] XFS (vda1): Ending clean mount [ 411.456676] SELinux: initialized (dev vda1, type xfs), uses xattr During the problematic mounts the host reports a lot of small disk writes with queue depth ~1. Also, when I move the problematic filesystem using dd to an lvm volume, mount -o ro, unmount, make snapshot, mount -o ro again, then the contents of the original volume are the same as the snapshot but the snapshot usage increases from 0 to ~2MB - so something writes to the original volume in a ro mode - possibly a log replay. Is is normal for the xfs mount to replay a log after a clean unmount? With best regards, Andrzej -- Andrzej Szymański, Ph.D. tel. +48 12 6174035 fax. +48 12 6342372 e-mail: szymans(a)agh.edu.pl AGH University of Science and Technology Department of Telecommunications Al. Mickiewicza 30 30-059 Kraków POLAND

2 2

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