Discuss

discuss@lists.centos.org

3 participants
34748 discussions

Latest version of kate editor
by H 07 Mar '16

07 Mar '16

I have installed the kate editor on Centos 6.7 but it seems to be a very old version, 3.3.4, installed as part of kdesdk. On Centos 7 I can simply run 'yum install kate' but, alas, not on Centos 6. What is the recommended way of updating kate on Centos 6? Thank you.

11 36

Re: [CentOS] 6.7 netinstall fails at insert cd to continue
by Richard 07 Mar '16

07 Mar '16

> Date: Sunday, March 06, 2016 22:25:55 -0600 > From: g <geleem(a)bellsouth.net> > > On 03/06/16 22:15, Richard wrote: > <<>> > >> "shell" is a yum command, invoked as shown below. I don't believe >> there is any program called "yum-shell" (even though that is the >> man page reference). >> >> shell Is used to enter the 'yum shell', when a filename is >> specified the contents of that file is executed in >> yum shell mode. See yum-shell(8) for more info. >> >> SYNOPSIS >> yum shell [filename] >> >> The contents of the file need to be standard yum-acceptable lines. >> I.e., the lines of a package list would need to be edited to >> include "install " and/or input continuation characters, etc. >> > -- > > ok. so how about; > > yum shell install < pkginstalllist.file I suspect not. However, yum shell pkginstalllist.file where you have prepended "install " to each line (and I believe added "run" at the end) of that file would seem to be likely to work. A simple vi or perl search/replace edit/one-line script should get you the input file you need. Since you have an interest in this I'll let you read the man page and do the experimenting.

1 0

C-Media CM8828 [CentOS 7]
by Alice Wonder 07 Mar '16

07 Mar '16

Basically I will be needing a low profile PCIe sound card with optical out. There isn't a hell of a lot of selection, seems the assumption is if you need sound it is on the motherboard. That one has PCIe and a low profile bracket, but it uses the C-Media CM8828 chipset. My understanding that chipset is only supported in 3.17+ kernels, CentOS 7 uses 3.10.x A) By any chance, has the been back-ported in CentOS kernel? B) If not, does anyone know of a 3rd party repo that has it as a kernel module built against CentOS kernel? I suspect B is no because it looks like the patches were to ALSA driver itself and not a new module. I'd prefer not to have to run a custom kernel because of updates. Anyone know the status of that chipset in CentOS 7?

1 0

trying to get amavid to work on centos 7
by Jason Welsh 06 Mar '16

06 Mar '16

hey folks, trying to migrate my faithful old centos6 server over to centos 7 and as part of my email server, I have amavisd, clamd, postfix, etc.. The amavisd seems to be failing with some funky (systemd) error.. Mar 6 11:39:03 monster-new systemd: amavisd.service failed. Mar 6 11:39:03 monster-new systemd: amavisd.service holdoff time over, scheduling restart. Mar 6 11:39:03 monster-new systemd: Cannot add dependency job for unit firewalld.service, ignoring: Unit firewalld.service is masked. Mar 6 11:39:03 monster-new systemd: Starting Amavisd-new is an interface between MTA and content checkers.... Mar 6 11:39:03 monster-new amavisd: Error reading config file "/etc/amavisd/amavisd.conf": Permission denied at /usr/sbin/amavisd line 2163. Mar 6 11:39:03 monster-new systemd: amavisd.service: control process exited, code=exited status=13 Mar 6 11:39:03 monster-new systemd: Failed to start Amavisd-new is an interface between MTA and content checkers.. Mar 6 11:39:03 monster-new systemd: Unit amavisd.service entered failed state. yes, I did shut off the new-fangled firewalld so that I can use iptables the way I'm to.. sooo what should I do to make amavisd behave? Jason

2 2

logrotate script error
by Tim Dunphy 06 Mar '16

06 Mar '16

Hey guys, I'm trying to rotate a logstash log that can grow pretty large. 3.4GB last I saw! And that's because the logrotate script I came up with didn't work. The error I get on a syntax check is this: #logrotate -f logstash size: '100M': No such file size: '100M': No such file size: '100M': No such file size: '100M': No such file size: '100M': No such file size: '100M': No such file size: '100M': No such file size: '100M': No such file And this is the logstash rotate script: #cat /etc/logrotate.d/logstash /var/log/logstash/* { daily rotate 7 copytruncate compress delaycompress missingok notifempty postrotate size 100M /bin/kill -HUP `cat /var/run/logstash.pid 2>/dev/null` 2> /dev/null || true endscript } I can't find the error there. Can I have a suggestion as to what's wrong and how to correct it? Thanks, Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

2 2

wpa_supplicant service script marked executable
by Luigi Rosa 05 Mar '16

05 Mar '16

I just installed a fresh CentOS 7 with "minimal" setup. Upon restart of systemd I get this warning: Configuration file /usr/lib/systemd/system/wpa_supplicant.service is marked executable. Please remove executable permission bits. Proceeding anyway. Probably the exec bit is no longer needed. -- Ciao, luigi / +--[Luigi Rosa]-- \ Draco dormiens nunquam titillandos.

1 0

kernel parm question: MPS? pcie_bus_safe
by m.roth＠5-cent.us 04 Mar '16

04 Mar '16

I'm fighting a long-standing problem: we've got a Dell PE R720 with a BT878 card in it, running four surveillance cameras (it's a secure room). Since I put the card in, within 20-30 min, the box's little LCD screen goes orange, and complains "bus error" on the slot the card's in; I've moved it to different slot, no joy. Note that the same card in an older Penguin (rebranded Supermicro) has no issues. Where it's been serious is for the last six or so months, if we use the 2.6.32-431.20.3.el6.x86_64 kernel, it pretty much stays up; every single newer kernel, and it will start rebooting, a number of times per day. So, I'm hoping to find a runtime kernel parm I can set, or it might be something I can set using ipmitool. However, in googling, I found one or two folks setting pcie_bus_safe to resolve what I see with ipmitool sel list. What I cannot find is what MPS is an acronym off... I've seen references to metal performance shaders, and to an LSI fusion driver. Can someone set me straight on this? Any suggestions would also be very appreciated. mark

1 0

Sharing virtualizing physical Server 2008R2 experience on CentOS 7
by Emmanuel Noobadmin 04 Mar '16

04 Mar '16

Not as smooth an experience as I had assumed it would be after a test run with a clean install worked perfectly. So figured I would share the experience in case anybody else runs into similar situation since not all information are consolidated in a single place. Physical machine in question is a 4yr W2008R2 server (non-raided!) running custom app from defunct developer which is why I am virtualizing the failing server instead of doing a fresh/newer Windows setup. Too many articles online saying can't just dd/clone a Windows drives and expect it to run. So opted to go with the "new" Bare Metal Restore functionality added in 2008R2. https://blogs.technet.microsoft.com/askcore/2011/05/12/bare-metal-restore/ BMR caveats ========== - It can only restore from BIOS to BIOS and UEFI to UEFI (virt-manager in C7 doesn't appear to do UEFI, see below) - It can only restore to a disk of same or larger size. - It doesn't appear to be possible to trick it using a sparse qcow2 disk file to fit it into a smaller disk (500GB HDD to 250GB SSD in my case) UEFI ==== - current version of libvirt/virt-manager in C7 doesn't appear come with UEFI firmware/loader - got it done thanks to http://www.nbalonso.com/centos-7-uefi-boot-kvm/ - Summary: - install ovmf from https://www.kraxel.org/repos/ - using virsh edit, add to the <arch> section: <loader>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> - sidenote: with the UEFI BIOS, warm reboot of the VM often ends up in an UEFI shell instead of booting directly, and sometimes the shell doesn't see attached drives. A "cold" reboot of the VM will fix this. Registry changes before booting ======================= After using the S2008R2 installation ISO to do a BMR restore, the restored S2008R2 won't boot. - need to boot into recovery mode with the CD again to run regedit to change some registry keys ( http://tech-stuff.org/migrate-windows-2008-server-from-physical-to-virtual-… ) - specifically for S2008R2 - select HKLM then open the File menu to 'Load Hive' from \restored drive\Windows\system32\config\SYSTEM. Give it a name e.g. 'restored_HLKM' - navigate through the restored HKLM tree to \ControlSet001\services and set the following for KVM - intelide > start = 0 - lsi_sas > start = 4 - msahci > start = 0 - pciide > start = 4 - the actual value in my registry are 3 instead of 4 but the changes appear to work regardless. - Note: I'm using IDE not virtio mode to avoid any added complications. Multi-core issue ============ For some reason, the restored VM won't boot if more than 1 core is assigned. There are plenty of hits on this issue but unfortunately mostly related to attempts to do PCI VGA passthrough. Trying out the various suggestions such as emulating core2duo, requiring nx and such did not really helped. What worked in the end is - single core - remove <hyperv> section in the guest xml - core2duo (might not be necessary) - require nx (might not be necessary) Resizing drives =========== In my situation, the server barely used 60GB on the old drive across two partitions. So 250GB SSDs was assumed to be enough until I hit the BMR restore issue. Ended up using a temporary 1TB spare drive to install before trying to shrink it down to fit onto a 250GB SSD. - Windows Disk Manager won't resize boot partition below 1/2 of original - Do NOT use Aomei partition assistant (thought it was easier and safer to use a Windows-based tool for this but...) - gparted livecd won't boot properly in KVM with UEFI/OVMF so better to just use it on a raw disk on the virtualization host directly. - Before repartitioning, from here https://wiki.archlinux.org/index.php/GParted (although says it's for WinXP) - Delete the registry key HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices - randomly gparted will get errors: - about unable to read data on the ntfs partition, fixed by mounting the partition before running gparted. - or abort a resize/move operation because it can't find the device in /etc/mtab. It doesn't quite make sense to me because the partition seems to appear only in /etc/mtab if I mount it in the host. But if I mount the drive, gparted will indicate it is mounted and needs to be unmounted. Fixed by rebooting the host machine everytime it happens. - Windows still won't boot after partition changes despite deleting the registry key. Fixed by manually running chkdsk /f in Windows rescue/repair command prompt. No errors found but for some reason this makes Windows happy. Transferring to smaller drive ==================== The web is full of warnings about trying to clone a bigger drive into a smaller drive using dd. Especially since GPT puts a spare table at the end of the drive. However, I figured it can't hurt to try since I will still have the working 1TB to fall back on. - did a dd if=/dev/vg/lv_temp of=/dev/vg_ssd/lv_ssd1 BS=32M conv=notrunc,sync - appears to work as Windows booted without complains. I'm still left with the unable to assign more than 1 core issue but so far the virtualized server appears to be working. Making a backup image before I mess around with it further. Hope this helps anybody else who might find themselves in a similar situation.

1 0

CentOS-announce Digest, Vol 133, Issue 2
by centos-announce-request＠centos.org 03 Mar '16

03 Mar '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. CESA-2016:0347 Important CentOS 6 postgresql Security Update (Johnny Hughes) 2. CESA-2016:0346 Important CentOS 7 postgresql Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 2 Mar 2016 17:36:01 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0347 Important CentOS 6 postgresql Security Update Message-ID: <20160302173601.GA50734(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0347 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0347.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 28887eb490932c082e1b7b1265d02162825dc1441e4a3a42bb5512b7f4640c22 postgresql-8.4.20-5.el6_7.i686.rpm 21b0002c1e9c222562e1983daa806617ef41aaac55a0c2e69fc10775b2afda04 postgresql-contrib-8.4.20-5.el6_7.i686.rpm ae7607f18010b13d047dea7824218ff37e3ffed61e613079c8f2bc5a86e7d7e2 postgresql-devel-8.4.20-5.el6_7.i686.rpm c2d3da027a5532c8776da45a58d8d3ea1cc45c62b32b852f4d025b055a60f14d postgresql-docs-8.4.20-5.el6_7.i686.rpm ab8d3a2bec35fef0477a62dc8aad01af0ce9cb4207392b402620b4a87ba55d16 postgresql-libs-8.4.20-5.el6_7.i686.rpm 3b97c7a7a81ff2e8ce6235b01337bd5267496491599f5621a8e958f77fe33aba postgresql-plperl-8.4.20-5.el6_7.i686.rpm b215251545d709136b8491aadfeebd68336d65855f68292d1ff849ddd6282f22 postgresql-plpython-8.4.20-5.el6_7.i686.rpm 4a29d7cdfcb7db337a96919a83c266e8a8f65c5b31beecbb6cb022ca66ff371f postgresql-pltcl-8.4.20-5.el6_7.i686.rpm fe69ec2c0a5be8820d4d6732a79f25011356d95e4cb8c9c3c00353b524794c20 postgresql-server-8.4.20-5.el6_7.i686.rpm ee3bcd8a1b0f602d62c3dcc66d4dfba7c1c07dfc0b0325655fdb1089e795917e postgresql-test-8.4.20-5.el6_7.i686.rpm x86_64: 28887eb490932c082e1b7b1265d02162825dc1441e4a3a42bb5512b7f4640c22 postgresql-8.4.20-5.el6_7.i686.rpm c7cd7d3d73f7881040d5e76f4602f9b3c99051eeb66bfb16d614fc0e92bb6a72 postgresql-8.4.20-5.el6_7.x86_64.rpm 0f5d90c73d67b5d75b1d18e38f55cab7a7f14634a44aa5246a8b902a08499e2a postgresql-contrib-8.4.20-5.el6_7.x86_64.rpm ae7607f18010b13d047dea7824218ff37e3ffed61e613079c8f2bc5a86e7d7e2 postgresql-devel-8.4.20-5.el6_7.i686.rpm d5138d6cf2d30936b11d07e0f6405edef3b16da393d1b10f19571dc3da67c99b postgresql-devel-8.4.20-5.el6_7.x86_64.rpm 787b50591dc468e74ccb804e5a36afc30923e3a416bd5b0711db4ff863d765f6 postgresql-docs-8.4.20-5.el6_7.x86_64.rpm ab8d3a2bec35fef0477a62dc8aad01af0ce9cb4207392b402620b4a87ba55d16 postgresql-libs-8.4.20-5.el6_7.i686.rpm fc4a053f7f71071c0559d6718e06c7f0eca8026d8df595deaa2ee15b060aa745 postgresql-libs-8.4.20-5.el6_7.x86_64.rpm 894f0de472b5ce8bac0507f5c3f9c03b1f7c2c7f365f6d78b78084924fe2d2bc postgresql-plperl-8.4.20-5.el6_7.x86_64.rpm 4a30da101c89de17815d3428a28f40a2c0abad82ab95ee2bcb5c32bfec373367 postgresql-plpython-8.4.20-5.el6_7.x86_64.rpm fef0d25e31d54df816279e46671ad715335705b12af73d63b8f3cc1420d02bb4 postgresql-pltcl-8.4.20-5.el6_7.x86_64.rpm 02b4bd3d5b2df30694e57e6e35e51437c17f4665c5b0d79abf123efdcd7b7d9f postgresql-server-8.4.20-5.el6_7.x86_64.rpm b7bd6d7f6d4fc310e6eaed09b8f0078037f4631d3c99257610d7e3ef432c3edd postgresql-test-8.4.20-5.el6_7.x86_64.rpm Source: 1d25cec7562ac152fbf1be84b28cd1ec2b57d46e031457188db1f565e02812f8 postgresql-8.4.20-5.el6_7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 2 Mar 2016 18:17:48 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0346 Important CentOS 7 postgresql Security Update Message-ID: <20160302181748.GA4394(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0346 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0346.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 5c458f42b2ef11fcc4b62d7f69c7dc1e033957c471387d65a6d49c0d7df6f128 postgresql-9.2.15-1.el7_2.i686.rpm 2434cedad6cd2fd921d499c57864e69e8db4ec7166d0f390c055074d50ddd2a7 postgresql-9.2.15-1.el7_2.x86_64.rpm f7484385c8df8fa144de7fea6e3fb64f657a3325608e3d25dd5d6e68f32fa7ea postgresql-contrib-9.2.15-1.el7_2.x86_64.rpm 1eeabfd3110ad851ad61b68271e2594d2807241617e395427a83f89f1e662d6f postgresql-devel-9.2.15-1.el7_2.i686.rpm 62790ddfbb18ad771af372509b674b62284d8d47c390dc397269f71c9fef8df3 postgresql-devel-9.2.15-1.el7_2.x86_64.rpm 0e787b99e9fddde0900c8dbf2014025ec8ce1c578c684e5ce51c532b52f1abb4 postgresql-docs-9.2.15-1.el7_2.x86_64.rpm 51c0e1cc0983e2139d11ea212f23f1ce60b6ed25a071743f360515688898aaa5 postgresql-libs-9.2.15-1.el7_2.i686.rpm 53f4bed4816944cdfd1b896ad6933c799f3429b221d2146d91d462e5c608fae3 postgresql-libs-9.2.15-1.el7_2.x86_64.rpm 2c9e04943c318f89e8c94d8104e01cbeb1c9dcbf868dee434c3e65505384cb03 postgresql-plperl-9.2.15-1.el7_2.x86_64.rpm 36021f26db1f2addf89e15707348cc611b34f0b9fe385df77e1f50994c978fa6 postgresql-plpython-9.2.15-1.el7_2.x86_64.rpm a9d8728e1b5a7c34ce94b1c339c3017691da43458afcec07f6be207c96877795 postgresql-pltcl-9.2.15-1.el7_2.x86_64.rpm 5be958fcca92e4b44dcfcae4f50bb16c05386c06b31ddcd36b5cf6c4ffd01af4 postgresql-server-9.2.15-1.el7_2.x86_64.rpm 8afce69552067b932036be540522b0db2d4c245cedb1fad8eb4762b02586a83d postgresql-test-9.2.15-1.el7_2.x86_64.rpm 1e7aa4a53e7cee01fdd305e69bc2e7927f85d97682dd925b3adb0b12e75a9872 postgresql-upgrade-9.2.15-1.el7_2.x86_64.rpm Source: 2e7e14805236939e21dd3bb2b293c205206c7cb76c0beb42317a4073aeb9aab0 postgresql-9.2.15-1.el7_2.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 133, Issue 2 ***********************************************

1 0

Problems with CentOS 7 and X w/ nvidia
by m.roth＠5-cent.us 03 Mar '16

03 Mar '16

Ok, here's a bit more on the issues: I see in Xorg.0.log that it appears to have loaded the NVidia drivers I built from proprietary. But, and this may, or may not be significant, the user's home directory is, of course, NFS mounted. And his old machine that dies was running CentOS 5. Is it possible that some of the gnome settings are breaking things with CentOS 7's default gnome? If so, what kinds of things should I be looking for? mark

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