Discuss April 2008

discuss@lists.centos.org

252 participants
275 discussions

Kickstart syntax for CentOS upgrade
by Alfred von Campe 29 Apr '08

29 Apr '08

I'd like to automate the upgrade from CentOS 4.6 to 5.1 as much as possible. Since upgrades per se are not really recommended, I'm planning to do a kickstart installation. However, I want to leave one of the existing partitions (/scratch) untouched during the installation. Here is my current layout (LogVol00 is swap so not shown in the df output below): # df -hl Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol01 36G 11G 24G 30% / /dev/sda1 99M 17M 78M 18% /boot /dev/mapper/VolGroup00-LogVol02 36G 9.7G 24G 29% /scratch # vgscan Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 # pvscan PV /dev/sda2 VG VolGroup00 lvm2 [74.41 GB / 32.00 MB free] Total: 1 [74.41 GB] / in use: 1 [74.41 GB] / in no VG: 0 [0 ] # lvscan ACTIVE '/dev/VolGroup00/LogVol01' [35.75 GB] inherit ACTIVE '/dev/VolGroup00/LogVol02' [35.72 GB] inherit ACTIVE '/dev/VolGroup00/LogVol00' [2.91 GB] inherit I've tried various alternatives of specifying the disk layout in the kickstart file, and here is my latest attempt: part /boot --fstype ext3 --onpart sda1 part pv.2 --noformat --onpart sda2 volgroup VolGroup00 --noformat --useexisting --pesize=32768 logvol swap --useexisting --fstype swap --name=LogVol00 -- vgname=VolGroup00 logvol / --useexisting --fstype ext3 --name=LogVol01 -- vgname=VolGroup00 But when I try to install CentOS 5.1 via kickstart, anaconda complains that "You have not defined a root partition (/), which is required for installation of CentOS to continue". Has anyone successfully installed CentOS 5.X via kickstart and preserved at least one partition on a logical volume, and if so, could you please share your kickstart file? Thanks, Alfred

2 2

RE: [CentOS] DVD reader: Hardware problem or OS glitch?
by Lanny Marcus 29 Apr '08

29 Apr '08

On 28 April 2008, Mike Peterson wrote: > Date: Mon, 28 Apr 2008 17:27:44 -0500 >From: "Mike Peterson" <mpeterson(a)mail.charlesfurniture.com> > Subject: RE: [CentOS] DVD reader: Hardware problem or OS glitch? > Message-ID: <00c901c8a97f$144a1800$de00000a@ITAW> >I have yet to get a DVD to read in CentOS 5. >I can install from DVD and then reboot and then the DVD drive is no longer >accessible. >It works with several live CD and DVD images with no problems however. >This is on an HP system. >I think it is an OS problem. I also suspect it is an OS problem, but, it seems to be very HW dependent. After I read your post, I got the FC6 Install DVD and put it into the DVD reader in my box. Zero problems. The same in my wife's box. But, in my daughter's box, I have the same situation that you described above. I suspect it is something about the DVD reader in that box. However, when it was my box (and newer), it worked OK and I believe it had CentOS 5 on it, before I let my daughter have it. > I will test in some other systems and let you know my results. Thank you! Very glad to know that I am not the only person with this problem! Lanny

1 0

xinetd question
by Jerry Geis 29 Apr '08

29 Apr '08

I am using centos 5.1 x86_64 I am wanting to restart xinetd when I do "service xinetd restart" it says xinetd unrecognized service when I do "/etc/init.d/xinetd restart" I get no such file or directory. How does one restart xinetd? THanks, Jerry

3 3

How to handle updates after rebuilding PHP?
by Niki Kovacs 29 Apr '08

29 Apr '08

Hi, One of our applications has some very specific requirements regarding PHP, so I had to rebuild it to add some functionality that's not included in the default configuration. First thing I removed every PHP-related package that was installed on the system: # yum remove `rpm -qa | grep php` Then I downloaded the PHP SRPM from http://mirror.centos.org/centos/5.1/os/SRPMS/ and installed it. Next I installed all the build dependencies using yum-builddep. I edited php.spec according to my needs and then built PHP: # rpmbuild -bb --clean php.spec Finally, I installed the resulting packages using 'rpm -ivh', in that order: - php-common - php-cli - php - php-ldap Problem: when I run 'yum check-update', Yum wants to update these php packages immediately, with some packages coming from [base] (not from [updates]). I'm puzzled, because PHP is not in [updates], only in [base]. Now I know I could simply add a line to /etc/yum.conf, something like: exclude=php-* But I *do* want to be notified somehow in case there's an update to PHP, so I can download the new SRPM from the updates/ directory and then rebuild it again. Any suggestions about this? Niki PS: on my desktop I use Arch Linux, where I have some individually rebuilt packages. When I do this, I simply increase the build number, so my packages don't get squashed, but I get an update notification when a new version is available. Maybe this is the way to go, but I don't know how I would do this with RPM.

3 3

sendmail and cups gets installed although not chosen in kickstart file
by Kai Schaetzl 29 Apr '08

29 Apr '08

I setup a kickstart file that contains only @core and several packages explicitely listed. postfix is listed, sendmail is not. And there's no package where I would think it needs cups. Nevertheless, after the install I now have postfix *and* sendmail on the machine and sendmail even being enabled. And cups is installed. How can I find out what forced them (and probably many other unwanted packages) on the installation? I thought maybe "rpm -q --whatrequires sendmail" would tell me, but it doesn't. Nothing requires it. Same for cups. So, why did it get installed? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

4 5

Problems with Open-iSCSI and Infortrend A16E-G2130-4
by Santi Saez 29 Apr '08

29 Apr '08

Dear Srs, I'm getting this error when trying to connect to a Infortrend A16E- G2130-4 storage vía iSCSI. > Apr 29 10:24:40 vz-10 kernel: scsi1 : iSCSI Initiator over TCP/IP > Apr 29 10:24:41 vz-10 kernel: Vendor: IFT Model: A16E- > G2130-4 Rev: 361F > Apr 29 10:24:41 vz-10 kernel: Type: Direct- > Access ANSI SCSI revision: 04 > Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: 629145600 512-byte > hdwr sectors (322123 MB) > Apr 29 10:24:41 vz-10 kernel: sdb: Write Protect is off > Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: drive cache: write back > Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: 629145600 512-byte > hdwr sectors (322123 MB) > Apr 29 10:24:41 vz-10 kernel: sdb: Write Protect is off > Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: drive cache: write back > Apr 29 10:24:41 vz-10 iscsid: connection1:0 is operational now > Apr 29 10:24:44 vz-10 udevd-event[23432]: wait_for_sysfs: waiting > for '/sys/devices/platform/host1/session1/target1:0:0/1:0:0:0/ > ioerr_cnt' failed > Apr 29 10:25:06 vz-10 iscsid: Nop-out timedout after 15 seconds on > connection 1:0 state (3). Dropping session. > Apr 29 10:25:10 vz-10 iscsid: connection1:0 is operational after > recovery (2 attempts) > Apr 29 10:25:36 vz-10 iscsid: Nop-out timedout after 15 seconds on > connection 1:0 state (3). Dropping session. > Apr 29 10:25:39 vz-10 iscsid: connection1:0 is operational after > recovery (2 attempts) > Apr 29 10:26:05 vz-10 iscsid: Nop-out timedout after 15 seconds on > connection 1:0 state (3). Dropping session. > Apr 29 10:26:09 vz-10 iscsid: connection1:0 is operational after > recovery (2 attempts) > Apr 29 10:26:34 vz-10 iscsid: Nop-out timedout after 15 seconds on > connection 1:0 state (3). Dropping session. > Apr 29 10:26:38 vz-10 iscsid: connection1:0 is operational after > recovery (2 attempts) > Apr 29 10:27:03 vz-10 iscsid: Nop-out timedout after 15 seconds on > connection 1:0 state (3). Dropping session. > Apr 29 10:27:07 vz-10 iscsid: connection1:0 is operational after > recovery (2 attempts) > Apr 29 10:27:32 vz-10 kernel: sdb:<6>sd 1:0:0:0: SCSI error: > return code = 0x00020000 > Apr 29 10:27:32 vz-10 kernel: end_request: I/O error, dev sdb, > sector 0 > Apr 29 10:27:32 vz-10 kernel: Buffer I/O error on device sdb, > logical block 0 > Apr 29 10:27:32 vz-10 iscsid: Nop-out timedout after 15 seconds on > connection 1:0 state (3). Dropping session. > Apr 29 10:27:36 vz-10 iscsid: connection1:0 is operational after > recovery (2 attempts) > Apr 29 10:28:02 vz-10 iscsid: Nop-out timedout after 15 seconds on > connection 1:0 state (3). Dropping session. > Apr 29 10:28:05 vz-10 iscsid: connection1:0 is operational after > recovery (2 attempts) The problem appears to be related to udevd-event? The system is running CentOS 5.1, with kernel 2.6.18-53.1.14.el5PAE, and "iscsi- initiator-utils-6.2.0.865-0.8.el5". It's a strange problem.. I have no errors with CentOS 4.6, what can be the problem? Thanks!! Regards, -- Santi Saez

1 0

RE: [CentOS] SSH Key length
by Les Bell 29 Apr '08

29 Apr '08

"Joseph L. Casale" <jcasale(a)ActiveNetwerx.com> wrote: >> I see, how does one manipulate the keys used for data encryption after auth during file transfers for instance? << One doesn't; the session keys are randomly generated and are automatically renewed periodically. Best, --- Les Bell, RHCE, CISSP [http://www.lesbell.com.au] Tel: +61 2 9451 1144 FreeWorldDialup: 800909

1 0

Re: [CentOS] SSH Key length
by Les Bell 29 Apr '08

29 Apr '08

"Joseph L. Casale" <jcasale(a)ActiveNetwerx.com> wrote: >> What are the ramifications to a large key length when using pub/priv keys for ssh authentication. << No particular impact, especially for file transfer. The pub/priv keys are only used for authentication and a symmetric key is used for encrypting traffic during the session. I use a 2048-bit RSA key routinely - if it's any slower than a 1048-bit key during the authentication phase, it's not noticeable, and it has no impact on file transfer. Best, --- Les Bell, RHCE, CISSP [http://www.lesbell.com.au] Tel: +61 2 9451 1144 FreeWorldDialup: 800909

2 1

SSH Key length
by Joseph L. Casale 29 Apr '08

29 Apr '08

What are the ramifications to a large key length when using pub/priv keys for ssh authentication. I have some remote admin and file transfers to manage and only have ssh access w/o vpn to use for it. Thanks, jlc

1 0

OpenSSH Version
by Walter Hansen 28 Apr '08

28 Apr '08

I see that currently CENTOS is using 4.3p2 which does not support the new Match command in the sshd_config. I'm not sure, but I think that was added with 4.4. I was wondering how long it would be before we get to use this feature?

2 1

← Newer
1
2
3
4
5
6
7
8
...
28
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 April 2008