Discuss September 2015

discuss@lists.centos.org

136 participants
130 discussions

Crash when open a terminal after upgrading from centos5.9 to 5.11
by sunyp_vmd＠sina.com 13 Sep '15

13 Sep '15

Dear all, I had installed Centos 5.9 in my x86_64 system and I installed update yesterday. Just now after I initiated the system, I found it has been upgraded to centos 5.11. But the bad thing is now I cannot open a terminal. When I try to open a terminal, it just gives out a bug buddy window : "The information about the crash has been successfully collected. Please provide some background about what you were doing when the application crashed..." Could anyone help me about this? Thanks in advance. Yeping Sun

1 0

why terminal cannot be open after upgrading?
by sunyp_vmd＠sina.com 13 Sep '15

13 Sep '15

Dear all,

1 0

why terminal cannot be open after upgrading?
by sunyp_vmd＠sina.com 13 Sep '15

13 Sep '15

Dear all,

1 0

flac/sox/etc with mp3 support?
by John R Pierce 13 Sep '15

13 Sep '15

I need to convert a bunch of .flac files to .mp3 files, but the sox and flac command tools thats in the base repo won't do that. EPEL doesn't seem to have much either. I went looking at ATRPMS but am getting database errors from their home page :( I know rpmforge used to have this stuff, but its virtually unmaintained today so I've written it off. any suggestions? I don't really want to have to build this stuff from source. -- john r pierce, recycling bits in santa cruz

3 2

CentOS-announce Digest, Vol 127, Issue 5
by centos-announce-request＠centos.org 12 Sep '15

12 Sep '15

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. Release for CentOS Linux 7 Rolling media Aug 2015 (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Fri, 11 Sep 2015 22:13:43 +0100 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] Release for CentOS Linux 7 Rolling media Aug 2015 Message-ID: <55F34407.8090906(a)centos.org> Content-Type: text/plain; charset=utf-8 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am pleased to announce general availability of the Aug 2015 snapshot for CentOS Linux. This release includes CentOS Linux 7 iso based install media, Generic Cloud images, Atomic Host, Docker containers, Vagrant images, vendor hosted cloud images and live media. CentOS Linux rolling builds are point in time snapshot media rebuild from original release time, to include all updates pushed to mirror.centos.org's repositories. This includes all security, bugfix, enhancement and general updates for CentOS Linux. Machines installed from this media will have all these updates pre-included and will look no different when compared with machines installed with older media that have been yum updated to the same point in time. All rpm/yum repos remain on mirror.centos.org with no changes in either layout or content. - -------- CentOS Linux 7 / x86_64 install media is available at http://buildlogs.centos.org/rolling/7/isos/x86_64/ File: CentOS-7-x86_64-Minimal-1508-01.iso Sha: 58103babe07c1cff0186f91d721dff3a385458f2d49988bf8996e4468d4047dd File: CentOS-7-x86_64-DVD-1508-01.iso Sha: c39bd161830f0edd2ee2f55205f992ed361e1764b0a609ad311d3b19b1c13227 File: CentOS-7-x86_64-Everything-1508-01.iso Sha: 40852e362b8cbc050658270d98ca7dc67e4beea933273b99116afc7fa2ac131e - -------- CentOS Linux 7 / x86_64 Live Media is also available at : http://buildlogs.centos.org/rolling/7/isos/x86_64 File: CentOS-7-x86_64-LiveCD-1508-01.iso Sha: 189f9befe54ce216c21a0a48aa6a6765faeab9331b423e1275fd6ba8fff17159 File: CentOS-7-x86_64-LiveKDE-1508-01.iso Sha: 0882bbd70c6b83e0739b75702fe3a435980bec8c9e50edff485fd0f5e9a75a17 File: CentOS-7-x86_64-GNOME-1508-01.iso Sha: a9d708e0ff62696f0a9220bbbc39cf782087f9307af07a60f89af7bbb7a8c01d - -------- CentOS Linux 7 / x86_64 Cloud Images are available at : http://cloud.centos.org/centos/7/images/ File: CentOS-7-x86_64-GenericCloud-1508.qcow2 Sha: 0952b651a6248998380aef73d9961ccb45af9b1823579bc2b72d28fa5fe5dea7 File: CentOS-7-x86_64-GenericCloud-1508.qcow2c Sha: 8bb46b6619f05d5e58a6fbf929a45abe61b58e87c9a02ae44a0f65e859f3c1b9 File: CentOS-7-x86_64-GenericCloud-1508.qcow2.xz Sha: a8f9e24ad80901cbd6894662c1a20c0173892c002b4f66ec9a935650b34d6461 File: CentOS-7-x86_64-GenericCloud-1508.raw Sha: cd272ea1e07a61cf9a4b080639aa67a35c18ba9c2c59f8f86bfc6be973516ba6 - -------- CentOS Atomic Host was released yesterday, details for the release are available at : http://seven.centos.org/2015/09/announcing-a-new-release-of-centos-atomi c-host/ Images for this release are available at http://cloud.centos.org/centos/7/atomic/images/ File: CentOS-Atomic-Host-7.20150908-GenericCloud.qcow2 Sha: a132d59732e758012029a646c466227f4ecf0c71cc42f0a10d3672908e463c0c File: CentOS-Atomic-Host-7.20150908-GenericCloud.qcow2.gz Sha: aad5d39e0683dc997f34902b068c7373aac3f7dc9b2c962a6ac0fe7394e2aa58 File: CentOS-Atomic-Host-7.20150908-Installer.iso Sha: b222702942d02da2204581de6f877cf93289459a99f9080e29016e3b90328098 File: CentOS-Atomic-Host-7.20150908-Vagrant-Libvirt.box Sha: 5531fa99429b38c6e6c4aca87672bd5990ab90f6445cc0e55c9121ad62229141 File: CentOS-Atomic-Host-7.20150908-Vagrant-Virtualbox.box Sha: bdcf58772117dd3a84100e5902f4f345daeea7c04f057c0ab6e29bfef3c82eab - -------- CentOS Linux 7 / x86_64 Vagrant images are updated at https://vagrantcloud.com/centos/boxes/7 and the backing files can be downloaded for libvirt and virtualbox providers at : Libvirt: http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant- 1508-x86_64-01.LibVirt.box and Virtualbox: http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant- 1508-x86_64-01.box - -------- CentOS Linux 7 / x86_64 in vendor environments, including Amazon web services, are being updated and will be released online working through vendor process's. - -------- CentOS Linux 5 / 6 and 7 docker images are updated at http://index.docker.io/_/centos - -------- We welcome all feedback around these rolling builds and media updates at the centos-devel mailing list ( http://lists.centos.org/ ). enjoy! - -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJV80QHAAoJEI3Oi2Mx7xbtg3wIAJeEKXP3jHufu75dRnl8T0O3 qC+xCYWSbDGrXZ6/RJzqwPoLMIAXqhU1+SgDd5z/DMaXB8+lPRwdjNsvy2NGmF8H NMSlmZH13Tg5WB7mtrdyLY1JjiWPYJDhQDFIbB0PC2BkQJSS/xQjPdE345aUVxoo YANW+f7k3QGC2+xZkQ2d9vtj2EN84tNeCVGZ+4saNo1VL6E42UAtshH5mHqx7Old D3etMaRFdLRr3NN+9OKdaUQh1vHLoIP1K3zPlYbuvuaVv5JKN+C0/WhPZpYRElET Y2uPXnWgjjYnELJJFohhw0kUW/x2GviAEfjE3UPf9rOXhadC3XMfkg3JneKUbck= =dYvx -----END PGP SIGNATURE----- ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 127, Issue 5 ***********************************************

1 0

sshd key exchange security
by Alice Wonder 11 Sep '15

11 Sep '15

I was reading https://weakdh.org/sysadmin.html They also have a very interesting paper as a PDF. Anyway it appears that most ssh servers, when using DHE key exchange, use the 1024-bit Oakley Group 2 and there is suspicion the NSA has done the pre-computations needed to passively decrypt any tls communication using DHE with that particular prime group. They recommend setting the following: KexAlgorithms curve25519-sha256(a)libssh.org I don't even see that directive in my sshd config to set it, I suppose it may be one that is manually added when needed but I want to verify it actually means something in CentOS 7 ssh. Also I'm a little worried that maybe curve25519 is one of the curves that Red Hat (and thus CentOS 7) doesn't support due to patent concerns. If it is, is there a suggestion on what curve should be used instead?

3 3

Cannot open: No space left on device
by reynierpm＠gmail.com 11 Sep '15

11 Sep '15

I have a VBox VM running CentOS 6.7 and I want to extract the content of a 14G tar file. I'm doing as: *tar -xvf www.tar.gz* But I am getting a lot of errors like the ones shown below: html/elclarinweb.dev/wp-content/uploads/2015/03/12-Aura-Ávila-400x320.jpg tar: html/elclarinweb.dev/wp-content/uploads/2015/03/12-Aura-Ávila-400x320.jpg: Cannot open: No space left on device html/elclarinweb.dev/wp-content/uploads/2015/03/Julianne-Moore-11-585x378.jpg tar: html/elclarinweb.dev/wp-content/uploads/2015/03/Julianne-Moore-11-585x378.jpg: Cannot open: No space left on device So, trying to find why the VHDD (Virtual HDD) has left out of space I ran the following command: *df -h* Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_server-lv_root 26G 24G 869M 97% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/sda1 477M 80M 373M 18% /boot And then I've tried to find the conflictive files by running: *du -hsx * | sort -rh | head -10* du: cannot access `proc/3662/task/3662/fd/4': No such file or directory du: cannot access `proc/3662/task/3662/fdinfo/4': No such file or directory du: cannot access `proc/3662/fd/4': No such file or directory du: cannot access `proc/3662/fdinfo/4': No such file or directory 14G var 1.8G usr 278M lib 77M boot 31M etc 27M lib64 15M sbin 7.8M bin 188K dev 112K root Why *df -h* is reporting 24G used? Where the space did go? How I can fix this?

5 9

CPU Scheduling allocates more time for few threads
by Radha krishna 11 Sep '15

11 Sep '15

Hi I have a Virtual Machine with CentOS 7 64-bit having 6 CPUs (intel). I have a process with 10 threads. two threads of the process pinned to two CPU's using affinity. These threads processes lot of network messages via Sockets. Other threads wait for other events using pthread condition wait. When two threads CPU reaches 75 to 80% then the schedular, schedules most of the time for those two threads, even though remaining 4 CPU's are ideal. Due to this other threads event processing is delayed a lot. Is it mostly do to more signal's from kernel space to user space tor those threads ? Is there a way to avoid this issue? RegardsRadha

2 1

Re: [CentOS] rsync question
by C Linus Hicks 11 Sep '15

11 Sep '15

On 09/10/15, Robert Moskowitz wrote: --------------- Quoted text ------------------ SSh is not parsing the port the way http does, it seems: $ rsync -ah --stats root@192.168.129.2:613:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp ssh: connect to host 192.168.129.2 port 22: No route to host rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1] The reason why I change my SSH port is a simple way to keep port knocker robots away. Different hosts use different ports... ------------------ End quote -------------------- Oh, right, so you either need to put that in your .ssh/config file or use -e 'ssh -p 613' on the rsync command. The config file should look like this: Host 192.168.129.2 Port 613

3 3

Rebuilding a Centos 6.2 netinstall initrd with an updated driver?
by Rory Falloon 11 Sep '15

11 Sep '15

Hi all, It seems that with the release of the X99 motherboards, a lot of vendors are shifting away from using Realtek ethernet on board NICs and using Intel. Our main distro. on the floor is Centos 6.2 for numerous reasons. Efforts are being made toward 7.1, but not there yet. Anyway, the new Intel NICs are recognised by Centos 6.6 netinstall ISO when booting, but not Centos 6.2. I have had the idea of unpacking the initrd and using the e1000/e1000e drivers from 6.6, and updating the 6.2 initrd. This has not worked so far, but I'm hoping I've missed a step. I have: 1) unpacked both initrd's 2) updated modules.* from the 6.2 initrd to match 6.6 for the relevant modules/dependent modules 3) updated the pci.ids file 4) chrooted, run `depmod -a -v` 5) rebuilt the initrd 6.2 still fails to see the NIC. Is there a step I've missed here? Do I have to concern myself with the kernel(vmlinuz) file too?

3 3

← Newer
1
...
5
6
7
8
9
10
11
12
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss September 2015