Discuss

discuss@lists.centos.org

12 participants
34747 discussions

Start a nNew thread

Download Centos 7.2 64 bit
by JEYARAJ 02 Nov '16

02 Nov '16

Hi All, How to download the Centos 7.2 64 bit.. If you see anyone please send me the link. Urgent. Regards, Jeyaraj. M

3 3

how to install amule in CertOS 7?
by Zhao Xiaoqi 01 Nov '16

01 Nov '16

I could find the amule package in CertOS7, is anyone know this? Thanks. Xiaoqi

1 0

Airprint to old printer using Centos server
by Gary Stainburn 31 Oct '16

31 Oct '16

Hi folks, I've found a number of articles on setting up a Linux / CUPS / Avahi server to allow airprinting, but they all seem to be quite old. Two questions: 1) Does anyone have a link for a more recent article, hopefully specifically for Centos7. 2) I'm on a structured, VLAN network. Will I have to put a WIFI card into my Centos server to give it a presence on the WIFI before this will work? Gary

4 4

Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel
by Paul R. Ganci 31 Oct '16

31 Oct '16

I have something very strange that occurred. After updating the kernel on my host CentOS 7 Dell 2950iii I have found that one of my CentOS 7 guest VMs will no longer boot... it just stops at the grub prompt (a second VM functions just fine). I have no idea why this problem occurred and have been unable to fix it. On google I have found several suggestions as to how to repair grub but so far none have worked. What I have found so far is this: grub> ls (hd0) (hd0,msdos2) (hd0,msdos1) grub> ls -l (hd0,1) (hd0,msdos2) (hd0,msdos1) Partition hd0,1: Filesystem type xfs, UUID 250008ab-9fde-4892-a8b7-a38882b1a1448 - Partition start at 1024KiB - Total size 512000Kib Partition hd0,msdos2: No known filesystem detected - Partition start at 513024KiB - Total size 12069888KiB Partition hd0,msdos1: Filesystem type xfs, UUID 250008ab-9fde-4892-a8b7-a38882b1a1448 - Partition start at 1024KiB - Total size 512000Kib So it appears that (hd0,1) and (hd0,msdos1) are the same partition containing the boot directory contents grub> set root=(hd0,1) grub> ls -l / DIR 20151002231139 grub/ DIR 20161013022100 grub2/ 10190975 20151219235512 initrd-plymouth.img 40655493 20150403032637 initramfs-0-rescue-6494b5d98adc4f66b0cf4c19a0f6ab66.img 4902656 20150403032703 vmlinuz0-rescue-6494b5d98adc4f66b0cf4c19a0f6ab66 252739 20161010232025 symvers-3.10.0-327.36.2.el7.x86_64.gz 29666884 20161013012551 initramfs-3.10.0-327.36.2.el7.x86_64.img 2965270 20161010231818 System.map-3.10.0-327.36.2.el7.x86_64 126431 20161010231818 config-3.10.0-327.36.2.el7.x86_64 5157936 20161010231819 vmlinuz-3.10.0-327.36.2.el7.x86_64 18119089 20161013022032 initramfs-3.10.0-327.36.2.el7.x86_64kdump.img Is that (hd0,msdos2) the root partition? If is, has it become corrupted somehow? Can I get this system to boot somehow so that I might fix the grub configuration? So far I have tried something along these lines with out success: grub> set root=(hd0,msdos2) grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 root=(hd0,msdos2)/ grub> initrd initrd-plymouth.img grub> boot I just get this error: [ 2.128131] No filesystem could mount root, tried: [ 2.129038] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) [ 2.130537] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.0-327.36.2.el7.x86_64 #1 [ 2.132017] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 {remainder of stack dump} Does anyone have any ideas as to 1.) How to fix the problem? 2.) Why the problem occurred in the first place? 3.) How to go about debugging the problem? I would really like to know how this problem could have occurred on the 1 VM but the Host and 2nd Guest are just fine? Thanks for your help. -- Paul (ganci(a)nurdog.com) Cell: (303)257-5208

4 10

Disk near failure
by Alessandro Baggi 30 Oct '16

30 Oct '16

Hi list, on my workstation I've a md raid (mirror) for / on md1. This raid has 2 ssd as members (each corsair GT force 120GB MLC). This disks are ~ 5 years old. Today I've checked my ssds smart status and I get: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 050 Pre-fail Always - 0/4754882 5 Retired_Block_Count 0x0033 100 100 003 Pre-fail Always - 0 9 Power_On_Hours_and_Msec 0x0032 000 000 000 Old_age Always - 17337h+11m+24.440s 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 1965 171 Program_Fail_Count 0x0032 000 000 000 Old_age Always - 0 172 Erase_Fail_Count 0x0032 000 000 000 Old_age Always - 0 174 Unexpect_Power_Loss_Ct 0x0030 000 000 000 Old_age Offline - 780 177 Wear_Range_Delta 0x0000 000 000 000 Old_age Offline - 3 181 Program_Fail_Count 0x0032 000 000 000 Old_age Always - 0 182 Erase_Fail_Count 0x0032 000 000 000 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 194 Temperature_Celsius 0x0022 033 042 000 Old_age Always - 33 (Min/Max 15/42) 195 ECC_Uncorr_Error_Count 0x001c 120 120 000 Old_age Offline - 0/4754882 196 Reallocated_Event_Count 0x0033 100 100 003 Pre-fail Always - 0 201 Unc_Soft_Read_Err_Rate 0x001c 120 120 000 Old_age Offline - 0/4754882 204 Soft_ECC_Correct_Rate 0x001c 120 120 000 Old_age Offline - 0/4754882 230 Life_Curve_Status 0x0013 100 100 000 Pre-fail Always - 100 231 SSD_Life_Left 0x0013 100 100 010 Pre-fail Always - 0 233 SandForce_Internal 0x0000 000 000 000 Old_age Offline - 6585 234 SandForce_Internal 0x0032 000 000 000 Old_age Always - 6885 241 Lifetime_Writes_GiB 0x0032 000 000 000 Old_age Always - 6885 242 Lifetime_Reads_GiB 0x0032 000 000 000 Old_age Always - 6244 The second ssd has very similar values. SSD_Life_Left is 0 since ~ 1years ago for each ssd. Today these disks are working without problems: # hdparm -tT /dev/md1 /dev/md1: Timing cached reads: 26322 MB in 2.00 seconds = 13181.10 MB/sec Timing buffered disk reads: 1048 MB in 3.00 seconds = 349.00 MB/sec # hdparm -tT /dev/sda /dev/sda: Timing cached reads: 26604 MB in 2.00 seconds = 13322.82 MB/sec Timing buffered disk reads: 1140 MB in 3.00 seconds = 379.87 MB/sec # hdparm -tT /dev/sdb /dev/sdb: Timing cached reads: 26258 MB in 2.00 seconds = 13148.38 MB/sec Timing buffered disk reads: 1140 MB in 3.00 seconds = 379.70 MB/sec # dd if=/dev/zero of=file count=2000000 2000000+0 record in 2000000+0 record out 1024000000 byte (1,0 GB) copied, 2,36335 s, 433 MB/s My ssds are failing? Thanks in advance.

8 22

Stupid vim question
by Alice Wonder 30 Oct '16

30 Oct '16

on very large files, vim will condense display - e.g. +-- 8 lines: static inline void php_openssl_rand_add_timeval() -------------------------------------------------------------------------------------------------------------------------------------------------- #endif +-- 29 lines: static int php_openssl_load_rand_file(const char * file, int *egdsocket, int *seeded) --------------------------------------------------------------------------------------------------------------- +-- 22 lines: static int php_openssl_write_rand_file(const char * file, int egdsocket, int seeded) ---------------------------------------------------------------------------------------------------------------- +-- 45 lines: static EVP_MD * php_openssl_get_evp_md_from_algo(zend_long algo) { ---------------------------------------------------------------------------------------------------------------------------------- +-- 42 lines: static const EVP_CIPHER * php_openssl_get_evp_cipher_from_algo(zend_long algo) { -------------------------------------------------------------------------------------------------------------------- How do I get it to stop doing that? It didn't use to do that as far as I remember, seems to be new to me in CentOS 7 - either that or I previously had something in me .vimrc that prevented it and I just forgot. I have tried searching but I just can't seem to get the proper search term to produce relevant results. using it in a terminal shell, the only way I ever use it.

3 6

Squid question
by paul.greene.va 29 Oct '16

29 Oct '16

I'm having issues getting squid to send traffic through a specific upstream gateway. I need for a MS WSUS server and a Symantec Endpoint Protection Manager to get through a squid proxy to get out to Microsoft and Symantec respectively to get MS patches and Symantec DAT files. The traffic needs to go through the squid proxy, through a firewall, and through an upstream McAfee gateway server. If it tries to take a path different than that upstream gateway to get out to the internet, it'll get dropped. However, once the traffic goes through the proxy, it tries to go directly to the vendor website and not go through the McAfee gateway, and therefore is getting blocked by the firewall. The traffic never reaches the McAfee gateway. If I configure a browser to use the proxy server and browse to some websites, it can get to http sites, but not https sites. Port 443 is what isn't getting through. I thought this line in squid.conf was supposed to send the traffic to an upstream cache_peer parent gateway, but I could easily be misunderstanding what its supposed to do. (I'm pretty new with squid) cache_peer <upstream gateway IP address> parent 8080 3130 proxy-only no-query no-netdb-exchange default login=<username>:<password> The Safe_ports and SSL_ports is the squid.conf default settings, and include both port 443 and port 80 traffic Thanks, PG

2 2

CentOS-announce Digest, Vol 140, Issue 10
by centos-announce-request＠centos.org 29 Oct '16

29 Oct '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:2124 Important CentOS 5 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 28 Oct 2016 13:34:09 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:2124 Important CentOS 5 kernel Security Update Message-ID: <20161028133409.GA23401(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:2124 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-2124.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 704498f1ec6f196882bf2dc25bf1f65d813ff84107a8476d5386663532f5206a kernel-2.6.18-416.el5.i686.rpm 0802fb601a7d1936e6607c747a0737c36791dcb2af156d6be30c81f2d0671465 kernel-debug-2.6.18-416.el5.i686.rpm bc8956c899a7fce81f371e15e9d4293297b1abb64da75c214ba086d046c6a9bd kernel-debug-devel-2.6.18-416.el5.i686.rpm db180509a4fa22d8e0151bed34f12dc1aa040b497f3ec0ba465388510a7b6df7 kernel-devel-2.6.18-416.el5.i686.rpm fcfabae71ac655ffaeaf5ab5f3a4c64d214684ef6f738ce2a5666c950ec9fdbd kernel-doc-2.6.18-416.el5.noarch.rpm 8489c9c93257895eb1b69ecebb173249fcf501ed10518bc2547222ec1c75f482 kernel-headers-2.6.18-416.el5.i386.rpm e7d00b03a37e0353c22343d3a996a33c893e220cccb1fb7f1981ba1d530b73ee kernel-PAE-2.6.18-416.el5.i686.rpm 36fefcec929f64c33b09d7e3f2924ce3c8b7d7a86d1272e7de731ad584a9b310 kernel-PAE-devel-2.6.18-416.el5.i686.rpm ad35ea63d8275960cafd5844f59babeb5199f2f7ba10df6e35f58f5cc63f3aa6 kernel-xen-2.6.18-416.el5.i686.rpm da05a5b93d8c3f1518ee7eb52792f655febc9b724301610bf7463fd91d14a41a kernel-xen-devel-2.6.18-416.el5.i686.rpm x86_64: cbedceb97046ac8274a6804c7da995dd8166c0d18f867e317e269091f197e68b kernel-2.6.18-416.el5.x86_64.rpm 31be4d5ec91c50abef7421dbdd3acd098d1d338b35a6b487cf4888071867852d kernel-debug-2.6.18-416.el5.x86_64.rpm 04a3c7d586ac2923ff1362cb1e72634cfe3aa54a5e84e175340043a51fa043ca kernel-debug-devel-2.6.18-416.el5.x86_64.rpm b0ce136908b8fb2575bdc11e882a705e494a0b1b423435f7f3d984556b7afd38 kernel-devel-2.6.18-416.el5.x86_64.rpm fcfabae71ac655ffaeaf5ab5f3a4c64d214684ef6f738ce2a5666c950ec9fdbd kernel-doc-2.6.18-416.el5.noarch.rpm 058216a53ff8b1bd75333ed1c700076f54365d209bfd4d54109299318edd1a49 kernel-headers-2.6.18-416.el5.x86_64.rpm 738534a54a6ca2d9b04e8116ec1147900eeff7b8a7b07f7fe6ca177ecaa51c66 kernel-xen-2.6.18-416.el5.x86_64.rpm 18a2ea3fe7513fd882ea8d9c84772bbfed55700e748a96fc0ebfacbab4da7380 kernel-xen-devel-2.6.18-416.el5.x86_64.rpm Source: 724e9e10418be6bbb6a1408b12344edcab9f745373013f337be3180d3877c7f4 kernel-2.6.18-416.el5.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 140, Issue 10 ************************************************

1 0

NFS help
by Larry Martell 28 Oct '16

28 Oct '16

We have 1 system ruining Centos7 that is the NFS server. There are 50 external machines that FTP files to this server fairly continuously. We have another system running Centos6 that mounts the partition the files are FTP-ed to using NFS. There is a python script running on the NFS client machine that is reading these files and moving them to a new dir on the same file system (a mv not a cp). Almost daily this script hangs while reading a file - sometimes it never comes back and cannot be killed, even with -9. Other times it hangs for 1/2 hour then proceeds on. Coinciding with the hanging I see this message on the NFS server host: nfsd: peername failed (error 107) And on the NFS client host I see this: nfs: V4 server returned a bad sequence-id nfs state manager - check lease failed on NFSv4 server with error 5 The first client message is always at the same time as the hanging starts. The second client message comes 20 minutes later. The server message comes 4 minutes after that. Then 3 minutes later the script un-hangs (if it's going to). Can anyone shed any light on to what could be happening here and/or what I could do to alleviate these issues and stop the script from hanging? Perhaps some NFS config settings? We do not have any, so we are using the defaults. Thanks!

7 32

odd sendmail question
by Fred Smith 28 Oct '16

28 Oct '16

I've looked thru all the stuff at sendmail.org (or whatever its name is now, they seem to have gone corporate...) and don't see anything relating to this: I get a series of log entries in /var/log/maillog, once or twice a day at various times--not 12 or 24 hours apart. not always the identical series either. here's the latest one: Oct 27 21:28:55 fcshome sendmail[7939]: starting daemon (8.14.7): SMTP+queueing@01:00:00 Oct 27 21:28:56 fcshome sendmail[7980]: starting daemon (8.14.7): SMTP+queueing@01:00:00 Oct 27 21:28:56 fcshome sm-msp-queue[7992]: starting daemon (8.14.7): queueing@01:00:00 Oct 27 21:29:19 fcshome sendmail[8054]: starting daemon (8.14.7): SMTP+queueing@01:00:00 Oct 27 21:29:19 fcshome sm-msp-queue[8093]: starting daemon (8.14.7): queueing@01:00:00 Oct 27 21:29:19 fcshome sendmail[8095]: starting daemon (8.14.7): SMTP+queueing@01:00:00 Anyone have a clue what this is all about? and why so many? -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- Show me your ways, O LORD, teach me your paths; Guide me in your truth and teach me, for you are God my Savior, And my hope is in you all day long. -------------------------- Psalm 25:4-5 (NIV) --------------------------------

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