Discuss September 2011

discuss@lists.centos.org

268 participants
252 discussions

"Continious Repo" vs. 'normal' Centos-Base/Updates questions
by Robert Heller 08 Sep '11

08 Sep '11

I have some questions about the "Continious Repo". Does the "Continious Repo" replace the Centos-Base/Updates repo? Is the "Continious Repo" in a standard place on the CentOS mirrors? Ie. can I just add another line to my rsync script to get this repo? It is not possible for me to just update directly off the net (I have a slow and unreliable network connection) If I cannot rsync from a secondary mirror, is it possible / allowed to rsync from mirror.centos.org? If so, what is the proper rsync URL? -- Robert Heller -- 978-544-6933 / heller(a)deepsoft.com Deepwoods Software -- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments

3 4

Samba4: Current Packages? (CentOS6)
by Adam Tauno Williams 08 Sep '11

08 Sep '11

I see that Samab4 alpha11 is packaged in the repo. Are there any repo's out there with current S4 alpha packages? Or does anyone know where such packages might be found (OBS?, etc...)

1 0

Have not had any updates to Centos 5.5
by Todd Cary 08 Sep '11

08 Sep '11

I am running Centos 5.5 (2.6.18-238.19.1.el5 and when I submit yum -y update I get the message that nothing is marked for update. Is this correct or is there something wrong with the system? Many thanks... Todd -- Ariste Software Petaluma, CA 94952 http://www.aristesoftware.com

4 7

Centos6: missing link for mysqlclient
by Helmut Drodofsky 08 Sep '11

08 Sep '11

Hallo, I am installing snort from source. Besides of a lot of additional libraries, I needed a link ln -vfs /usr/lib64/mysql/libmysqlclient.so.16 /usr/lib64/libmysqlclient.so Are there reasons not to install with yum install mysql-devel ? I have found many discussions to add this link in context of installing from source, nor only for snort. Best regards Helmut

2 1

new ssd to play with
by Jerry Geis 08 Sep '11

08 Sep '11

I grabbed a new SSD M4-CT064M4SSD2 from Crucial. I am disappointed. I stuck the unit in an Atom machine (zotac) with CentOS 6 on the disk. It really doesn't "feel" faster than the previous 5400 RPM drive that was in it. The SSD is giving me (in the zotac running centos 6): hdparm -t /dev/sda /dev/sda: Timing buffered disk reads: 298 MB in 3.00 seconds = 99.30 MB/sec The Samsung 5400 RPM disk (in the zotac running Centos 6): hdparm -t /dev/sda /dev/sda: Timing buffered disk reads: 196 MB in 3.01 seconds = 65.02 MB/sec I'm not supper impressed at all. Sure the numbers say its "slightly" better but I don't "feel" it. I was expecting like really noticeable change in application load time or something - but not really. Just wondering... Is there something that has to be done to take advantage of the SSD performance? Thanks, jerry

8 10

CentoOS 6 x86_64 Updates
by Timothy Kesten 08 Sep '11

08 Sep '11

Hi Folks, is it correct that there were for a long time no more updates for CentOS 6 x86_64? I think the last update was offered before more than one month Thx Timothy P.S. sorry for that terrible english :-)

2 1

rsync -x does not do the same on EL 5.6 and 5.7
by Simon Matter 08 Sep '11

08 Sep '11

Hi, We re doing backups of all filesystems to a dedicated server using "rsync -x". Now, the latest CentOS versions (5.7/6.x) come with rsync-3.0.6 instead of rsync-2.x. That's nice but unfortunately it doesn't do the same as 2.x in certain situations. The problem is with the -x option, which does not delete content under a mount point anymore. It was my impression that this is a bug, but I've been told it's a feature. The problem has shown up after I have added a new mount point on a server. I've added a BZ for RedHat and also posted to the rsync list as below: https://bugzilla.redhat.com/show_bug.cgi?id=735981 https://lists.samba.org/archive/rsync/2011-September/026766.html Am I really the only one having problems with the new behaviour? It affects all user running "rsync -x". The problem only shows up after new mount points have been added to a subdirectory which is processed by rsync -x. That may be the reason why not many people relize it. Still, I don't see the logic behind the change which is why I take this here to hear what others think. Thanks, Simon

3 2

new memory not getting regonized
by sylvan.dcunha＠gmail.com 08 Sep '11

08 Sep '11

dear All, I had a Centos 5.5 OS running for about 6 months used as a Xen VM server prfectly running 3 Virtual machines Its a Sun Blade server with 8 core Xeon Proceesor with 32 GB Ram couple of days back I added another 32 gb ram . The bios shows the added ram that is now it shows me 64 GB but the Centos OS just recognizes 32gb only the OS details are: Centos release 5.5 final Kernel 2.6.18-194.32.1.el5xen on an x86_64 now also running uname -a shows me Linux hypervisor2 2.6.18-194.32.1.el5xen #1 SMP Wed Jan 5 18:44:24 EST 2011 x86_64 x86_64 x86_64 GNU/Linux shows that PAE support is not there I do believe that installing kernel PAE with yum should solve the problem but since the server is a online production server just wanted to verify if I would run into some problems apprecite your kinf help and suggestions regards sylvan

7 12

boot problem after disk change on raid1
by Bünyamin İzzet 08 Sep '11

08 Sep '11

Hello, I have two disks sda and sdb. One of the was broken so I have changed the broken disk with a working one. I started the server in rescue mode, and created the partional table, and added all the partitions to the software raid. *I have added the partitions to the RAID, and reboot.* # mdadm /dev/md0 --add /dev/sdb1 # mdadm /dev/md1 --add /dev/sdb2 # mdadm /dev/md2 --add /dev/sdb3 # mdadm /dev/md3 --add /dev/sdb4 *After reboot, server did not boot. So I do the followings:* # mount /dev/md1 /mnt/rescue # mount /dev/md0 /mnt/rescue/boot # mount -o bind /dev /mnt/rescue/dev # mount -o bind /proc /mnt/rescue/proc # mount -o bind /dev/shm /mnt/rescue/dev/shm # mount -o bind /sys /mnt/rescue/sys # chroot /mnt/rescue *I checked the device.map* # cat /boot/grub/device.map (hd0) /dev/sda (hd1) /dev/sdb *And, install the grub.* # grub Probing devices to guess BIOS drives. This may take a long time. GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd0,0) root (hd0,0) Filesystem type is ext2fs, partition type 0xfd grub> setup (hd0) setup (hd0) Checking if "/boot/grub/stage1" exists... yes Checking if "/boot/grub/stage2" exists... yes Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 15 sectors are embedded. succeeded Running "install /boot/grub/stage1 (hd0) (hd0)1+15 p (hd0,0)/boot/grub/stage2 /boot/grub/grub.conf"... succeeded Done. grub> root (hd1,0) root (hd1,0) Filesystem type is ext2fs, partition type 0xfd grub> setup (hd1) setup (hd1) Checking if "/boot/grub/stage1" exists... yes Checking if "/boot/grub/stage2" exists... yes Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd1)"... 15 sectors are embedded. succeeded Running "install /boot/grub/stage1 (hd1) (hd1)1+15 p (hd1,0)/boot/grub/stage2 /boot/grub/grub.conf"... succeeded Done. grub> quit quit *But it still does not boot. What should I do at this point? What do you suggest?* *Disk informations* # fdisk -l /dev/sd[ab] Disk /dev/sda: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00090dd1 Device Boot Start End Blocks Id System /dev/sda1 * 1 131 1052226 fd Linux raid autodetect /dev/sda2 132 5353 41945715 fd Linux raid autodetect /dev/sda3 5354 96733 734009850 fd Linux raid autodetect /dev/sda4 96734 182401 688128210 fd Linux raid autodetect Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf5c3aa6a Device Boot Start End Blocks Id System /dev/sdb1 * 1 131 1052226 fd Linux raid autodetect /dev/sdb2 132 5353 41945715 fd Linux raid autodetect /dev/sdb3 5354 96733 734009850 fd Linux raid autodetect /dev/sdb4 96734 182401 688128210 fd Linux raid autodetect *Raid info* # cat /proc/mdstat Personalities : [raid1] md3 : active raid1 sda4[0] sdb4[2] 688128128 blocks [2/1] [U_] resync=DELAYED md2 : active raid1 sda3[0] sdb3[2] 734009728 blocks [2/1] [U_] [>....................] recovery = 1.8% (13651648/734009728) finish=133.5min speed=89915K/sec md1 : active raid1 sdb2[2] sda2[0] 41945600 blocks [2/1] [U_] resync=DELAYED md0 : active raid1 sda1[0] sdb1[1] 1052160 blocks [2/2] [UU] unused devices: <none> *Mount informations* */dev/md0 is mounted /boot /dev/md1 is mounted / **/dev/md2 and /dev/md3 is for backup and some personal data* *Here is the grub.conf* # cat /mnt/rescue/boot/grub/grub.conf timeout 5 default 0 fallback 1 title CentOS (2.6.18-238.19.1.el5) root (hd1,0) kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/md1 vga=0x317 initrd /initrd-2.6.18-238.19.1.el5.img title CentOS (2.6.18-238.9.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-238.9.1.el5 ro root=/dev/md1 vga=0x317 initrd /initrd-2.6.18-238.9.1.el5.img title CentOS (2.6.18-194.26.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.26.1.el5 ro root=/dev/md1 vga=0x317 initrd /initrd-2.6.18-194.26.1.el5.img title CentOS (2.6.18-194.3.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.3.1.el5 ro root=/dev/md1 vga=0x317 initrd /initrd-2.6.18-194.3.1.el5.img title CentOS (2.6.18-164.15.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-164.15.1.el5 ro root=/dev/md1 vga=0x317 initrd /initrd-2.6.18-164.15.1.el5.img title CentOS Linux (2.6.18-164.11.1.el5) root (hd0,0) kernel /boot/vmlinuz-2.6.18-164.11.1.el5 ro root=/dev/md1 vga=0x317 initrd /boot/initrd-2.6.18-164.11.1.el5.img

2 6

big problem at boot
by Michel Donais 08 Sep '11

08 Sep '11

I restarted the a Centos 5.6 server tonight and I ran in this issue: I was able to boot. Then instead of a normal boot with graphical interface the system requested : 'Enter run level' 'INIT' I typed 5 then I got 'INIT: no more process left in this run level How can I recover from the situation? This is a production system back-up are made but left on the disk and transfer at the end of the day into an other system --- Michel Donais

4 7

← Newer
1
...
16
17
18
19
20
21
22
...
26
Older →

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 September 2011