Finally I could install boel_binaries with an alien --to-deb 
systemimager-x86-64boot-standard.rpm
But when I try to boot my client for restoring and image I have a timeout for 
sending with rsync the boel package: (this is a rsync log file)
2009/04/15 08:10:17 [3946] connect from iqtc2_34.iqtc.qt.ub.es 
(192.168.11.34)2009/04/15 08:10:17 [3946] rsync on 
boot/x86_64/standard/boel_binaries.tar.gz from iqtc2_34.iqtc.qt.ub.es 
(192.168.11.34)2009/04/15 08:10:17 [3946] building file list2009/04/15 08:20:18 
[3946] rsync error: timeout in data send/receive (code 30) at io.c(165) 
[sender=2.6.9]
But in the image server we can see that:
 lsof -i | grep rsyncrsync     3764        root    4u  IPv6  10057       TCP 
*:rsync (LISTEN)rsync     3764        root    5u  IPv4  10058       TCP *:rsync 
(LISTEN)rsync     3946        root    3u  IPv4  11100       TCP 
192.168.11.250:rsync->iqtc2_34.iqtc.qt.ub.es:56851 (ESTABLISHED)

So it seems that rsync is connecting to the client, but in the client's screen 
I can find this error:
rsync: read error: Connection reset by perr (104)rsync-error: error in rsync 
protocol data stream (code 12) at io.c(759) [ receuver=3.0.0pre6]rsync: 
connection unexpectedly closed (51 bytes received so far) [generator]

The rsync's version of my server is rsync --versionrsync  version 2.6.9  
protocol version 29
in golden client:
rsync --versionrsync  version 2.6.6  protocol version 29
and in the restored client (where it fails):
rsync version 3.0.0pre6 (with the shell booted by pxe)

Do you think that the problem is the rsync version? Did you encountered similar 
problems in your installation?
thanks in advance--- El dom, 12/4/09, Gorka Barracuda 
<gorka_barrac...@yahoo.es> escribió:

De: Gorka Barracuda <gorka_barrac...@yahoo.es>
Asunto: [sisuite-users] problems with missing boel_binaries 4.0.2 version
Para: sisuite-users@lists.sourceforge.net
Fecha: domingo, 12 abril, 2009 11:28

Dear Colleagues,
it seems that I haven't got any systemimager-x86-64boot-standard.deb that 
provides the boel binaries (I think that the si_prepareimage doesn't create 
boel_binaries.tar.gz). In SI webpage there is only the 386 version for debian. 
Did you know if I can use an older version, such as 3.6.3 for using this 
package?
thanks in advance.
p.s: I change the subject for this purpose. 

--- El sáb, 11/4/09, Gorka Barracuda <gorka_barrac...@yahoo.es> escribió:

De: Gorka Barracuda <gorka_barrac...@yahoo.es>
Asunto: Re: [sisuite-users] problems with lvm2
Para: sisuite-users@lists.sourceforge.net
Fecha: sábado, 11 abril, 2009 8:36

Hi!
First of all thanks for your response.
I used si_prepareclient to generate the golden client image and it seems that 
doesn't create any boel package.
I'll try to redo again the image, but only one question: si_prepareclient 
generates automatically the boel package?
These are my command that I use to generate golden_client's image:
si_prepareclient --server 192.168.10.250 

image server site:

si_getimage --golden-client 192.168.10.1 --image hp_proliant_dl160 
--ip-assignment dhcp -exclude /scratch -exclude /opt -exclude /home -exclude 
/sge 

And all the installed packages:
server: (debian x86-64)systemimager:~# dpkg -l | grep systemimager
ii  systemimager-boot-i386-standard   4.0.2                                
SystemImager boot binaries for i386 client nii  systemimager-common             
  4.0.2                                Utilities and libraries common to both 
the siF  systemimager-initrd-template-i386 4.0.2                                
SystemImager initre template for i386 clientii  systemimager-server             
  4.0.2                                Automate GNU/Linux installs and upgrades 
oveii  systemimager-server-flamethrowerd 4.0.2                                
SystemImager boot binaries for i386 client n
I
 installed
 the image server following the manual:
$ mkdir systemimager 
$ cd systemimager 
$ wget http://download.systemimager.org/pub/sis-install/install 
$ chmod u+x install 
$ ./install -v --download-only --tag stable --directory . \ 
> systemconfigurator \ 
> systemimager-client systemimager-common \ 
> systemimager-i386boot-standard systemimager-i386initrd_template \ 
> systemimager-server \ 
> systemimager-bittorrent systemimager-flamethrower 


$ dpkg -i systemconfigurator-*.deb \ 
> systemimager-common-*.deb systemimager-server-*.deb \ 
> systemimager-initrd_template-*.deb systemimager-boot-*-standard-*.deb \ 


Golden client: (SuSE)
r...@test:~# rpm -qa| grep 
systemimagersystemimager-i386initrd_template-4.0.2-1systemimager-client-4.0.2-1systemimager-x86_64initrd_template-4.0.2-1systemimager-common-4.0.2-1

Thanks for all
gorkab



--- El jue, 9/4/09, Infos E-Blokos <in...@e-blokos.com> escribió:

De: Infos E-Blokos <in...@e-blokos.com>
Asunto: Re: [sisuite-users] problems with lvm2
Para: sisuite-users@lists.sourceforge.net
Fecha: jueves, 9
 abril, 2009 3:41



 
 


 
if you do si_prepareclient it does 
boel_binaries.tar.gz

  ----- Original Message ----- 
  From: 
  Gorka 
  Barracuda 
  To: sisuite-users@lists.sourceforge.net 
  
  Sent: Thursday, April 09, 2009 7:59 
  AM
  Subject: Re: [sisuite-users] problems 
  with lvm2
  

  
    
    
      
        
        
        
        
        Thanks for your fast response dalamar. 
        

        You solved this problem.
        

        It seems that's working fine for this part but Now I have got some 
        problems with boel_binaries.tar.gz package for 64 bits that doesn't 
        exist. I will re-read again all documentation for looking for any 
        information.
        

        thanks for all
        

        gorkab--- El mié, 8/4/09, Dalamar 
        <d4la...@gmail.com> 
        escribió:

        
De: 
          Dalamar <d4la...@gmail.com>
Asunto: Re: [sisuite-users] 
          problems with lvm2
Para: 
          sisuite-users@lists.sourceforge.net
Fecha: miércoles, 8 abril, 2009 
          4:00


          Hi,

Which bootloader are you trying to use 
          ?

I experienced same problems trying to boot with "root" 
          kernel
parameter in "/dev/$VolumeGroup/$LogicalVolume" 
          format.
It's better to use 
          "/dev/mapper/$VolumeGroup-$LogicalVolume" as kernel
parameter and 
          as /etc/fstab entry.

With these changes I solved a similar 
          problem.

Hi,
d4lamar

2009/4/8 Gorka Barracuda <gorka_barrac...@yahoo.es>:
> 
          Dear All,
> I'm trying to restore an image with pxe server and 
          systemimager (4.0.2 in
> both sites -golden and server-) and I'm 
          obtaining this error:
> Unable to find volume group 
          "vgsys"
> Waitinf for device /dev/vgsys/root to appear: not 
          found --  extiing to
> /bin/sh:
> This is my 
          autoinstallscript.conf where you can see the lvm configuration
> 
          (it seems correct according to my golden client's partitions):
> 
          <!--
>
>   autoinstallscript.conf
> 
            vi:set filetype=xml:
>
>   This file 
          contains partition information about the disks on your golden
> 
            client.  It is stored here in a generic format that 
          is used by your
>   SystemImager server to create an 
          autoinstall script for cloning this
> 
            system.
>
>   You can change the 
          information in this file to affect how your target
> 
            machines are installed.  See "man 
          autoinstallscript.conf" for details.
>
> -->
> 
          <config>
>   <disk dev="/dev/sda" 
          label_type="msdos" unit_of_measurement="MB">
>    
           <!--
>       This disk's output was 
          brought to you by the partition tool "parted",
>    
             and by the numbers 4 and 5 and the letter Q.
> 
              -->
>     <part 
           num="1"  size="271"  p_type="primary"  p_name="-" 
           flags="boot"
> />
>     <part 
           num="2"  size="2155"  p_type="primary" 
           p_name="-"  flags="-" />
>    
           <part  num="3"  size="*"  p_type="extended" 
           p_name="-"  flags="lba" />
>    
           <part  num="5"  size="*"  p_type="logical" 
           p_name="-"  flags="lvm"
> lvm_group="vgsys" 
          />
>   </disk>
>   <disk 
          dev="/dev/sdb" label_type="msdos" unit_of_measurement="MB">
> 
              <!--
>       This 
          disk's output was brought to you by the partition tool 
          "parted",
>       and by the numbers 4 and 5 
          and the letter Q.
>     -->
> 
              <part  num="1"  size="2155" 
           p_type="primary"  p_name="-"  flags="-" />
> 
              <part  num="2"  size="*" 
           p_type="extended"  p_name="-"  flags="lba" 
          />
>     <part  num="5"  size="*" 
           p_type="logical"  p_name="-"  flags="lvm"
> 
          lvm_group="vgsys" />
> 
            </disk>
>
>   <lvm 
          version="2">
>     <lvm_group name="vgsys" 
          max_log_vols="0" max_phys_vols="0"
> 
          phys_extent_size="4096K">
>       <lv 
          name="root" size="10485760K" />
>      
           <lv name="scratch" size="209715200K" />
> 
                <lv name="var" size="5242880K" 
          />
>     </lvm_group>
> 
            </lvm>
>   <fsinfo 
           line="10" real_dev="/dev/vgsys/root" mp="/" 
           fs="ext3"
> options="acl,user_xattr" dump="1" pass="1" 
          />
>   <fsinfo  line="20" 
          real_dev="/dev/sda1" mp="/boot"  fs="ext3"
> 
          options="acl,user_xattr" dump="1" pass="2" />
> 
            <fsinfo  line="30" real_dev="/dev/vgsys/scratch" 
          mp="/scratch"  fs="xfs"
> options="defaults" dump="1" 
          pass="2"
>  />
>   <fsinfo 
           line="40" real_dev="/dev/vgsys/var" mp="/var" 
           fs="xfs"
> options="defaults" dump="1" pass="2" 
          />
>   <fsinfo  line="50" 
          real_dev="/scratch/SuSE" mp="/SuSE"  fs="none"
> 
          options="rw,bind" dump="0" pass="0" />
> 
            <fsinfo  line="60" 
          real_dev="iqtc1.qt.ub.es:/sgeinst" mp="/sgeinst"
> 
           fs="nfs" options="bg,hard,intr" dump="0"
>  pass="0" 
          />
>   <fsinfo  line="70" 
          real_dev="/dev/sda2" mp="swap"  fs="swap"
> 
          options="defaults" dump="0" pass="0" />
> 
            <fsinfo  line="80" real_dev="/dev/sdb1" mp="swap" 
           fs="swap"
> options="defaults" dump="0" pass="0" 
          />
>   <fsinfo  line="90" real_dev="proc" 
          mp="/proc"  fs="proc"
> options="defaults" dump="0" 
          pass="0" />
>   <fsinfo  line="100" 
          real_dev="sysfs" mp="/sys"  fs="sysfs"
> options="noauto" 
          dump="0" pass="0" />
>   <fsinfo 
           line="110" real_dev="debugfs" mp="/sys/kernel/debug"
> 
           fs="debugfs" options="noauto" dump="0" pass="0
> " 
          />
>   <fsinfo  line="120" real_dev="usbfs" 
          mp="/proc/bus/usb"  fs="usbfs"
> options="noauto" dump="0" 
          pass="0"  forma
> t="no" />
> 
            <fsinfo  line="130" real_dev="devpts" 
          mp="/dev/pts"  fs="devpts"
> options="mode=0620,gid=5" 
          dump="0" pass="0"
> />
>   <boel 
          devstyle="udev"/>
> </config>
> The commands used 
          for creating the images:
>
> si_prepareclient --server 
          192.168.10.250
>
>
> si_getimage --golden-client 
          192.168.10.1 --image hp_proilant_dl160
> --ip-assignment dhcp 
          -exclude /scratch -exclude /opt -exclude /home -exclude
> 
          /sge
>
>
> and the pxe default config file 
          :
>
> DISPLAY 
          /X86PC/UNDI/linux-install/message.txt
> PROMPT 1
> DEFAULT 
          proilantdl160
> LABEL proilantdl160
>      
             kernel vmlinuz_hp_dl160
>      
             append vga=normal IMAGENAME=hp_proilant_dl160 
          initrd=initrd_hp_dl160
> roo
> 
          t=/dev/vgsys/root
>
> Could anybody help me?
> 
          Thanks in advance,
> best regards
> 
          gorkab
>
>
>
> 
          
------------------------------------------------------------------------------
> 
          This SF.net email is sponsored by:
> High Quality Requirements 
          in a Collaborative Environment.
> Download a free trial of 
          Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> 
          _______________________________________________
> sisuite-users 
          mailing list
> sisuite-users@lists.sourceforge.net
> 
          https://lists.sourceforge.net/lists/listinfo/sisuite-users
>
>

------------------------------------------------------------------------------
This 
          SF.net email is sponsored by:
High Quality Requirements in a 
          Collaborative Environment.
Download a free trial of Rational 
          Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
sisuite-users 
          mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


-- 
  
This message has been scanned for viruses and 
dangerous content by MailScanner, and is 
  
believed to be clean. 
  
  

  ------------------------------------------------------------------------------
This 
  SF.net email is sponsored by:
High Quality Requirements in a Collaborative 
  Environment.
Download a free trial of Rational Requirements Composer 
  Now!
http://p.sf.net/sfu/www-ibm-com
  
  

  _______________________________________________
sisuite-users 
  mailing 
  list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

 -- 

This message has been scanned for viruses and

dangerous content by
MailScanner, and is

believed to be clean.


-----Adjunto en línea a continuación-----

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
-----Adjunto en línea a continuación-----

_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users





      
-----Adjunto en línea a continuación-----

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
-----Adjunto en línea a continuación-----

_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users





      
-----Adjunto en línea a continuación-----

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
-----Adjunto en línea a continuación-----

_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users



      
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to