From: Steven A. DuChene [mailto:[EMAIL PROTECTED]
Sent: Sun 12/02/2006 14:12
To: Bernard Li; sisuite-devel@lists.sourceforge.net
Subject: RE: [Sisuite-devel] bug with lvm and systemimager?
So the initrd templates have to be installed on the server or
the client node?
I believe I do have those installed on the image server when
I tried the
3.6.3-1 rpm files but I will double check. The reason I ask about
if these get
installed on the golden client or the image server is that I am
just running
si_prepareclient on my goldenclient when I get this error and I
am used to
the older systemimager suite of tools
where prepareclient did
not really interact with the server yet. I was somewhat
surprised when I
initially ran just si_prepareclient that I was forced to use
a "-server"
option. I just checked the online documentation and it does not
mention
si_prepareclient or the fact that a "-server" option must be given
when
running si_prepareclient.
-----Original Message-----
>From:
Bernard Li <[EMAIL PROTECTED]>
>Sent: Feb 12, 2006 2:44 PM
>To:
"Steven A. DuChene" <[EMAIL PROTECTED]>,
sisuite-devel@lists.sourceforge.net
>Subject: RE: [Sisuite-devel] bug with
lvm and systemimager?
>
>Hi Steven:
>
>Looking at the
error message more carefully, it looks like you are missing the initrd_template
RPM for x86_64 - ignore the "bela" RPMs, you don't want to use
them.
>
>Cheers,
>
>Bernard
>
>P.S. We
should probably provide a better error message when the initrd_template files
are not found - such that the user can figure it out and grab the corresponding
files...
>
>________________________________
>
>From:
[EMAIL PROTECTED] on behalf of Steven A.
DuChene
>Sent: Sun 12/02/2006 13:34
>To:
sisuite-devel@lists.sourceforge.net
>Subject: [Sisuite-devel] bug with lvm
and systemimager?
>
>
>
>Please see the E-mail thread
below regarding a problem with running
>si_prepareclient on a cluster
client node that is built with LVM filesystems.
>After answering yes to
the two questions it intially asks it returns the
>following
error:
>
>Using "parted" to gather information about
disk:
> /dev/sda
>
>Use of uninitialized
value in concatenation (.) or string at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 797.
>Use of
uninitialized value in concatenation (.) or string at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 797.
>Use of
uninitialized value in concatenation (.) or string at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 797.
>link_stat
/usr/share/systemimager/boot/x86_64/standard/initrd_template/. : No such file or
directory
>rsync error: some files could not be transferred (code 23) at
main.c(620)
>Couldn't rsync -a
/usr/share/systemimager/boot/x86_64/standard/initrd_template/
/tmp/.systemimager.3/. at
/usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm line
58.
>
>See below for a list of filesystems mounted on that cluster
node.
>This was originally based on
the
>systemimager/systeminstaller/systemconfigurator packaged with the
latest
>OSCAR 4.2.1beta. At the suggestion of Bernard Li I also tried
upgrading both
>the client and the server to newer unreleased versions of
the sisuite of tools.
>I am still getting the same
errors.
>
>I have been telling the IBM people and others at this
site I am now working
>at how great of a tool systemimager & etc were
but now when I actually got
>to test it out on the one existing cluster I
ran into this problem.
>
>-----Forwarded
Message-----
>>From: "Steven A. DuChene"
<[EMAIL PROTECTED]>
>>Sent: Feb 12, 2006 5:46
AM
>>To: Bernard Li <[EMAIL PROTECTED]>,
oscar-devel@lists.sourceforge.net
>>Subject: RE: [Oscar-devel] bug with
lvm and systemimager?
>>
>>Nope, same thing happens with those
systemimager-*-3.6.3r3410bela-1
>>rpms from there. I also tried the
systemimager-*-3.6.3-1 rpms
>>as well on both the client and the server
but it all produces the same error
>>shown below after it tries to use
"parted" to gather information about the disk.
>>Running parted against
/dev/sda with a print option seems to work OK
>>but perhaps it craps
out if it attempts to run parted against the
/dev/vg0
>>device.
>>
>>-----Original
Message-----
>>>From: Bernard Li
<[EMAIL PROTECTED]>
>>>Sent: Feb 12, 2006 1:41
AM
>>>To: "Steven A. DuChene" <[EMAIL PROTECTED]>,
oscar-devel@lists.sourceforge.net
>>>Subject: RE: [Oscar-devel] bug
with lvm and systemimager?
>>>
>>>Hi
Steven:
>>>
>>>I believe LVM support was not added until
recently (into SystemImager), try the following RPMs and see if they
work:
>>>
>>>http://www.bcgsc.ca/downloads/oscar/systemimager/
>>>
>>>P.S.
This version of SystemImager has not been
released.
>>>
>>>Cheers,
>>>
>>>Bernard
>>>
>>>________________________________
>>>
>>>From:
[EMAIL PROTECTED] on behalf of Steven A.
DuChene
>>>Sent: Sun 12/02/2006 00:13
>>>To:
oscar-devel@lists.sourceforge.net
>>>Subject: [Oscar-devel] bug with
lvm and
systemimager?
>>>
>>>
>>>
>>>I
just tried to run si_prepareclient on a rhel3 cluster node here that is built
with lvm and I got a failure error from line 767 of
/usr/lib/systemimager/perl/Systemimager/Common.pm
>>>
>>>This
is with the systemimager-3.5.3 packaged with the the latest oscar-4.2.1
beta:
>>>
>>>Using "parted" to gather information about
disk:
>>>
/dev/sda
>>>
>>>Use of uninitialized value in
concatenation (.) or string at /usr/lib/systemimager/perl/SystemImager/Common.pm
line 797.
>>>Use of uninitialized value in concatenation (.) or
string at /usr/lib/systemimager/perl/SystemImager/Common.pm line
797.
>>>Use of uninitialized value in concatenation (.) or string at
/usr/lib/systemimager/perl/SystemImager/Common.pm line
797.
>>>link_stat
/usr/share/systemimager/boot/x86_64/standard/initrd_template/. : No such file or
directory
>>>rsync error: some files could not be transferred (code
23) at main.c(620)
>>>Couldn't rsync -a
/usr/share/systemimager/boot/x86_64/standard/initrd_template/
/tmp/.systemimager.3/. at
/usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm line
58.
>>>
>>>
>>>I don't know enough perl to
be able to tell what is wrong here.
>>>
>>>Here is what
the mounted filesystems on this compute node look like in case anyone
cares.
>>>
>>># mount
>>>/dev/sda3 on / type
ext3 (rw)
>>>none on /proc type proc (rw)
>>>none on
/dev/pts type devpts (rw,gid=5,mode=620)
>>>usbdevfs on
/proc/bus/usb type usbdevfs (rw)
>>>/dev/sda1 on /boot type ext3
(rw)
>>>none on /dev/shm type tmpfs (rw)
>>>/dev/vg0/tmp
on /tmp type ext3 (rw)
>>>/dev/vg0/usr on /usr type ext3
(rw)
>>>/dev/vg0/usr-local on /usr/local type ext3
(rw)
>>>/dev/vg0/var on /var type ext3
(rw)
>>>/dev/vg0/disk2 on /disk2 type ext3
(rw)
>>>storage001:/common1 on /home type nfs
(rw,addr=172.20.1.1)
>>>storage001:/common2 on /common type nfs
(rw,addr=172.20.1.1)
>>>storage001:/common2 on /app type nfs
(rw,addr=172.20.1.1)
>>>mgt:/opt/xcat on /opt/xcat type nfs
(rw,addr=172.20.0.1)
>>>mgt:/usr/local/mpich on /usr/local/mpich
type nfs (rw,addr=172.20.0.1)
>>>mgt:/usr/local/pbs on
/usr/local/pbs type nfs (rw,addr=172.20.0.1)
>>>mgt:/usr/local/maui
on /usr/local/maui type nfs
(rw,addr=172.20.0.1)
>>>mgt:/usr/local/MSI on /usr/local/MSI type
nfs (rw,addr=172.20.0.1)
>>>mgt:/usr/local/numeca on
/usr/local/numeca type nfs
(rw,addr=172.20.0.1)
>>>storage001:/htteng on /htteng type nfs
(rw,addr=172.20.1.1)
>>Oscar-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/oscar-devel
>
>
>
>-------------------------------------------------------
>This
SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
>for problems? Stop! Download the new AJAX search engine
that makes
>searching your log files as easy as surfing the
web. DOWNLOAD SPLUNK!
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
>_______________________________________________
>Sisuite-devel
mailing list
>Sisuite-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/sisuite-devel
>
>
