Re: [sisuite-users] Fwd: New version, same errors :(
Hi. I would check your initrd.img and maybe make a new one pre-loading or with raid5. How such image could be prepared? I posted my autoinstall in the original post, here it is again: 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=106.97 p_type=primary p_name=- flags=boot,raid / part num=2 size=2097 p_type=primary p_name=- flags=raid / part num=3 size=2098 p_type=primary p_name=- flags=raid / part num=4 size=495803 p_type=primary p_name=- flags=raid / /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=106.97 p_type=primary p_name=- flags=boot,raid / part num=2 size=2097 p_type=primary p_name=- flags=raid / part num=3 size=2098 p_type=primary p_name=- flags=raid / part num=4 size=495803 p_type=primary p_name=- flags=raid / /disk disk dev=/dev/sdc 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=106.97 p_type=primary p_name=- flags=boot,raid / part num=2 size=2097 p_type=primary p_name=- flags=raid / part num=3 size=2098 p_type=primary p_name=- flags=raid / part num=4 size=495803 p_type=primary p_name=- flags=raid / /disk disk dev=/dev/sdd 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=106.97 p_type=primary p_name=- flags=boot,raid / part num=2 size=2097 p_type=primary p_name=- flags=raid / part num=3 size=2098 p_type=primary p_name=- flags=raid / part num=4 size=495803 p_type=primary p_name=- flags=raid / /disk raid name=/dev/md2 raid_level=raid5 raid_devices=4 spare_devices=0 persistence=yes layout=left-symmetric chunk_size=256K devices=/dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 / raid name=/dev/md1 raid_level=raid5 raid_devices=4 spare_devices=0 persistence=yes layout=left-symmetric chunk_size=256K devices=/dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 / raid name=/dev/md3 raid_level=raid5 raid_devices=4 spare_devices=0 persistence=yes layout=left-symmetric chunk_size=256K devices=/dev/sda4 /dev/sdb4 /dev/sdc4 /dev/sdd4 / raid name=/dev/md0 raid_level=raid1 raid_devices=4 spare_devices=0 persistence=yes devices=/dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 / fsinfo line=10 real_dev=/dev/md2 mp=/ fs=ext3 options=defaults dump=1 pass=1 / fsinfo line=20 real_dev=/dev/md0 mp=/boot fs=ext3 options=defaults dump=1 pass=2 / fsinfo line=30 real_dev=devpts mp=/dev/pts fs=devpts options=gid=5,mode=620 dump=0 pass=0 / fsinfo line=40 real_dev=tmpfs mp=/dev/shm fs=tmpfs options=defaults dump=0 pass=0 / fsinfo line=50 real_dev=/dev/md3 mp=/media fs=ext3 options=defaults dump=1 pass=2 / fsinfo line=60 real_dev=proc mp=/proc fs=proc options=defaults dump=0 pass=0 / fsinfo line=70 real_dev=sysfs mp=/sys fs=sysfs options=defaults dump=0 pass=0 / fsinfo line=80 real_dev=/dev/md1 mp=swap fs=swap options=defaults dump=0 pass=0 / boel devstyle=udev/ /config Regards, Stas. 2008/3/3, Tory M Blue [EMAIL PROTECTED]: On Sun, Mar 2, 2008 at 2:01 PM, Stas Oskin [EMAIL PROTECTED] wrote: -- Forwarded message -- From: Stas Oskin [EMAIL PROTECTED] Date: 02/03/2008 19:23 Subject: New version, same errors :( To: sisuite-users@lists.sourceforge.net Hi. I tried the latest stable version of sysimager, in hopes this has the RAID issues resolved. No luck - the image loading to client still stops with ADD_NEW_DISK. Attached below the dump of my autoinstall file, and the errors I'm receiving. Any help would be greatly appreciated. Regards, Stas. (autoinstall) SNIP (Only errors) Load software RAID modules. insmod: cannot insert `/lib/modules/2.6.21-boel_v4.0.2/kernel/drivers/md/md-mod.ko': File exists (-1): File exists insmod: cannot insert `/lib/modules/2.6.21-boel_v4.0.2/kernel/drivers/md/md-mod.ko': File exists (-1): File exists modprobe: module raid5 not found. modprobe: failed to load module raid5 modprobe: module raid6 not found. modprobe: failed to load module raid6 If your making a raid5 array shouldn't the raid5 module be found and installed? I would check your initrd.img and maybe make a new one pre-loading or with raid5. That sticks out like it's an issue to me.. I would also like to see your autoinstall
Re: [sisuite-users] si_psh usage
Seth Haines wrote:
Andrea,
This was on a 3.8.1 based server.
This bug has been fixed in 4.0.0.
Look at the diff below. In particular these two lines should resolve
your problem:
+ $cmd =~ s//\\/g;
+ $cmd = \$cmd\;
Maybe you should consider to move to 4.0.2 or if you don't want to
update you could try to apply the patch manually (BTW not the following
patch, just the two lines above otherwise, if I remember well, also some
changes in lib/SystemImager/Hostrange.pm module are needed).
-Andrea
Index: si_psh
===
--- si_psh (.../3.8.1/sbin/si_psh) (revision 4415)
+++ si_psh (.../4.0.0/sbin/si_psh) (revision 4415)
@@ -36,16 +36,26 @@
--hosts, -n=HOST_LIST List of target nodes. List can be separated by
comma, spaces or new line and can include
-ranges (e.g. node001-node256,node300 node400).
+ranges or host groups
+(e.g. node001-node256 node300,Login,Storage).
+Host groups must be defined by si_clusterconfig(8).
--hosts-file, -f=FILE File that contains the list of the target host.
-Every line can include one or more ranges
-(e.g. node001-node256,node300 node400).
+Every line can include one or more ranges or
+host groups
+(e.g. node001-node256 node300,Login,Storage).
+Host groups must be defined by si_clusterconfig(8).
--timeout, -t=NUM Set the timeout of the ssh sessions (default=15s).
--ssh-user, -l=USERRun the command as user USER.
+ --imaging, -i Run the command on imaging clients (that have a ssh
+ deamon enabled - add SSHD=y in the installation boot
+parameters and include a valid authorized_keys into
+ the initrd.img). See si_mkbootpackage(8) or
+si_prepareclient(8) for more details.
+
EOF
Getopt::Long::Configure(posix_default);
@@ -60,6 +70,7 @@
hosts-file|f=s= \my $hostlist_file,
timeout|t=i = \my $timeout,
ssh-user|l=s = \my $ssh_user,
+ imaging|i = \my $imaging,
) or die($help_info);
### BEGIN evaluate commad line options ###
@@ -79,27 +90,20 @@
$cmd = join(' ', @ARGV)
}
+# Evaluate target hosts.
my @hosts = ();
-if ($hostlist) {
- # Expand host ranges.
- @hosts = SystemImager::HostRange::expand_range_list($hostlist);
-} elsif ($hostlist_file) {
+if ($hostlist_file) {
# Read input file.
- open(IN, $hostlist_file) ||
+ open(IN, '', $hostlist_file) ||
die(error: could't read $hostlist_file!\n);
- chomp(@hosts = IN);
+ $hostlist .= ' ' . join(' ', IN);
close(IN);
- # Expand host ranges.
- my %expanded_hosts = ();
- foreach my $line (@hosts) {
- my @list = split(/,| |\n/, $line);
- foreach my $range (@list) {
- SystemImager::HostRange::expand_range(\%expanded_hosts,
$range);
- }
- }
- # Convert hosts hash into a list.
- @hosts = sort(keys(%expanded_hosts));
-} else {
+}
+if ($hostlist) {
+ # Expand host groups and host ranges.
+ @hosts = SystemImager::HostRange::expand_groups($hostlist);
+}
+unless (@hosts) {
die(error: no host defined!\nTry \--help\ for more options.\n);
}
@@ -115,12 +119,17 @@
$SystemImager::HostRange::concurrents = $concurrents;
}
-### END evaluate command line options ###
-
# Use the following ssh options.
my $ssh_opts = -x -o BatchMode=yes -o ConnectTimeout=$timeout -l $ssh_user;
+if ($imaging) {
+ $ssh_opts .= ' -o StrictHostKeyChecking=no -o
UserKnownHostsFile=/dev/null';
+}
+### END evaluate command line options ###
+
if ($cmd) {
+ $cmd =~ s//\\/g;
+ $cmd = \$cmd\;
SystemImager::HostRange::thread_pool_spawn('ssh', $ssh_opts, $cmd,
@hosts);
} else {
# Run in interactive mode.
@@ -135,6 +144,8 @@
if ((/^\s*$/) || (/^\s*exit\s*$/)) {
last;
}
+ $_ =~ s//\\/g;
+ $_ = \$_\;
SystemImager::HostRange::thread_pool_spawn('ssh', $ssh_opts,
$_, @hosts);
}
}
@@ -172,14 +183,15 @@
=item B--hosts | -n HOST_LIST
-List of target nodes.
-List can be separated by comma, spaces or new line and can include
-ranges (e.g. node001-node256,node300 node400).
+List of target nodes. List can be separated by comma, spaces or new line and
can
+include ranges or host groups (e.g. node001-node256 node300,Login,Storage).
+Host groups must be defined by si_clusterconfig(8).
=item B--hosts-file | -f FILE
-File that contains the list of the target hosts.
-Every line can include one or more
Re: [sisuite-users] Problem rebooting with lilo in OpenSUSE 10.3: could not find /dev/sda2
Hi Jesus,
comments below.
Jesus Sanchez wrote:
I've got some good news. At least now the cloned system boots. There
was something related with the modules and therefore with the initrd file.
I was using UYOK and not BOEL, sorry, but I tried to add some extra
modules in the file /etc/sysconfig/kernel, line starting with
INITRD_MODULES, run mkinitrd and repeat the whole process again
(si_prepareclient, si_getclient, PXE-booting + autoinstall, reboot, ...)
Now I can clone the system and when rebooting it starts using Grub,
what I didn't force because finally I didn't add the PREFERED param
under the BOOT section of systemconfig.conf file.
I check the autoinstall logging and I saw several things:
1. The system tries to run lilo but it can't because kernel is too
big (at least is what it says):
Error: Cannot execute /sbin/lilo.
Fatal: Kernel /boot/vmlinux-2.6.22.5-31-default.gz is too big
at /usr/lib/systemconfig/Boot.pm line 112
This is a problem with the kernel shipped with your distribution and
lilo, not a systemimager / systemconfigurator issue. To reduce the
kernel size you could try to strip(1) it and re-compress it again, but
this would mean changing the kernel provided by the distribution, that
is never a good idea... better to use grub at this point.
2. After that it installs grub
3. At the end systemconfigurator says it has modified the following
files:
/etc/lilo.conf
/etc/modprobe.conf
/etc/modules.conf
/etc/sysconfig/network/ifcfg-eth0
There are some strange things:
1. The lilo.conf file created by systemconfigurator seems to be
wrong, it has an orphan parameter which has to do with the root disk
partition named by-id ('tor_6L080M0_L26FVVDG-part2'). Here you are both
/etc/lilo.conf files, the original of the golden node and the one that
generates systemconfigurator
- /etc/lilo.conf of the golden node and the image
# Modified by YaST2. Last modification on Wed Feb 6 13:51:17 CET 2008
menu-scheme = Wb:kw:Wb:Wb
timeout = 80
lba32
change-rules
reset
read-only
prompt
message = /boot/message
boot = /dev/disk/by-id/scsi-SATA_Maxtor_6L080M0_L26FVVDG-part2
default = oS_10.3
image = /boot/vmlinuz-2.6.22.5-31-default
###Don't change this comment - YaST2 identifier: Original name: linux###
label = oS_10.3
append = resume=/dev/sda1 splash=silent showopts
vga = 0x314
initrd = /boot/initrd-2.6.22.5-31-default
root = /dev/disk/by-id/scsi-SATA_Maxtor_6L080M0_L26FVVDG-part2
image = /boot/vmlinuz-2.6.22.5-31-default
###Don't change this comment - YaST2 identifier: Original name: failsafe###
label = Failsafe
append = showopts ide=nodma apm=off acpi=off noresume edd=off 3
vga = normal
initrd = /boot/initrd-2.6.22.5-31-default
root = /dev/disk/by-id/scsi-SATA_Maxtor_6L080M0_L26FVVDG-part2
image = /boot/memtest.bin
###Don't change this comment - YaST2 identifier: Original name: memtest86###
label = Memory_Test
- end
- /etc/lilo.conf on the cloned machine (modified by systemconfigurator)
##
# This file is generated by System Configurator. #
##
# Do all the normal things lilo does
lba32
map=/boot/map
install=/boot/boot.b
vga=normal
# The number of deciseconds (0.1 seconds) to wait before booting
prompt
timeout=50
# The boot device where lilo installs the boot block
boot=/dev/sda
# the default label to boot
default=suse-10.3
# Device to be mounted as the root ('/')
root=/dev/sda2
#- Options for KERNEL0 -#
image=/boot/vmlinux-2.6.22.5-31-default.gz
label=suse-10.3
read-only
append=auto BOOT_IMAGE=oS_10.3 ro root=/dev/sda2
tor_6L080M0_L26FVVDG-part2 resume=/dev/sda1 splash=silent showopts
initrd=/boot/initrd-2.6.22.5-31-default
- end
This is a bug of si_prepareclient that doesn't resolve non-standard
symlinks created by udev. In terms of portability it would be better
to resolve this name in the standard name. If you have potentially
heterogeneous clients, using a device naming policy based on hardware
informations, like vendor ID, etc. could be a problem because different
clients that have a different hardware could use the same image.
For this I think the following patch could fix the problem. Could you
test it?
---
Index: sbin/si_prepareclient
===
--- sbin/si_prepareclient (revision 4415)
+++ sbin/si_prepareclient (working copy)
@@ -75,6 +75,7 @@
use lib USR_PREFIX/lib/systemimager/perl;
use strict;
use Carp;
+use Cwd 'abs_path';
use POSIX;
use File::Copy;
use File::Path;
@@ -746,6 +747,14 @@
$boot_dev =~ s/p[0-9]+$//;
}
+# Resolve non-standard symlink names created by udev.
+if (-l $boot_dev) {
+
[sisuite-users] bittorrent problem
hi to all new to the list.. i recently installed and used the systemimager distro all works fine, except when using the bittorrent deployment method, i got this error $: /etc/init.d/systemimager-server-bittorrent start Starting SystemImager's BitTorrent Transport: systemimager-server-bittorrent... tracker: ok ERROR: error in /etc/systemimager/bittorrent.conf: BT_INTERFACE not specified or not valid! failed. i dont understand the mentioned error since my bt_interface (eth0) seems to be ok any ideas or solution welcome ML extract from /etc/systemimager/bittorrent.conf : # Tracker state file. BT_TRACKER_STATE=/tmp/dstate # Tracker log file. BT_TRACKER_LOG=/var/log/systemimager/bittorrent-tracker.log # Interface used to seed files with bittorrent. BT_INTERFACES=eth0 # Set to yes if you want to compress the images before distributing # them via BitTorrent. Set to 'n' if the image server has an old CPU or # is not powerful in computations. # # Allowed values: y|n BT_COMPRESS=n BT_IMAGES=GX320_etch # Comma separated list of overrides to distribute with BitTorrent # (ex. BT_OVERRIDES=RHEL4_base,suse10,frontend,backend...) # IMPORTANT: no spaces between overrides!!! BT_OVERRIDES=GX320_etch -- Maurice Libes Tel : +33 (04) 91 82 93 25Centre d'Oceanologie de Marseille Fax : +33 (04) 91 82 93 03UMS2196CNRS- Campus de Luminy, Case 901 F-13288 Marseille cedex 9 Veuillez noter ma nouvelle adresse == [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Fwd: New version, same errors :(
OK, I managed to solve it. There were two issues: 1) The master looked for raid5.ko module, while I had raid456.ko. Changing the master script took care of this. 2) The mdadm --create failed due to specified --chunk 256 parameter, with the following errors: invalid sb on partition error importing sb -22 I fixed it by removing the --chunk 256 from the master script mdadm part. But now my deployed client has chunk size of 64K, while my golden client had a size of 256K. Such small chunk sizes probably unhealthy for disks, any idea how to solve it? Thanks, Stas. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] bittorrent problem
hi to all new to the list.. i recently installed and used the systemimager distro all works fine, except when using the bittorrent deployment method, i got this error $: /etc/init.d/systemimager-server-bittorrent start Starting SystemImager's BitTorrent Transport: systemimager-server-bittorrent... tracker: ok ERROR: error in /etc/systemimager/bittorrent.conf: BT_INTERFACE not specified or not valid! failed. i dont understand the mentioned error since my bt_interface (eth0) seems to be ok any ideas or solution welcome ML extract from /etc/systemimager/bittorrent.conf : # Tracker state file. BT_TRACKER_STATE=/tmp/dstate # Tracker log file. BT_TRACKER_LOG=/var/log/systemimager/bittorrent-tracker.log # Interface used to seed files with bittorrent. BT_INTERFACES=eth0 # Set to yes if you want to compress the images before distributing # them via BitTorrent. Set to 'n' if the image server has an old CPU or # is not powerful in computations. # # Allowed values: y|n BT_COMPRESS=n BT_IMAGES=GX320_etch # Comma separated list of overrides to distribute with BitTorrent # (ex. BT_OVERRIDES=RHEL4_base,suse10,frontend,backend...) # IMPORTANT: no spaces between overrides!!! BT_OVERRIDES=GX320_etch -- Maurice Libes Tel : +33 (04) 91 82 93 25Centre d'Oceanologie de Marseille Fax : +33 (04) 91 82 93 03UMS2196CNRS- Campus de Luminy, Case 901 F-13288 Marseille cedex 9 Veuillez noter ma nouvelle adresse == [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] bittorrent problem
Maurice Libes wrote: hi to all Maurice # Tracker log file. BT_TRACKER_LOG=/var/log/systemimager/bittorrent-tracker.log # Interface used to seed files with bittorrent. BT_INTERFACES=eth0 BT_INTERFACE will do the trick (so remove the trailing s_ ;-) -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] systemconfigurator --configrd on the SIS image
DongInn Kim wrote:
Hi Erich,
Thank you.
Basically, I got this question when I looked for some instructions about
updating kernel on the OSCAR cluster in the OSCAR admin manual.
http://svn.oscar.openclustergroup.org/trac/oscar/wiki/AdminGuide/Commands#ManagingRepositories
As you can see in the manual, all my purpose of running systemconfigurator
--configrd is make the new initrd of the updated kernel available on
oscarimage before deploying the oscarimage to the client node.
Actually, as Erich said, instead of running systemconfigurator in the
chrooted image on the image server the solution is to simply add
CONFIGRD = yes in etc/systemconfig/systemconfig.conf into the image.
In this way the systemconfigurator --configrd will be executed at the
end of the imaging.
So, do you think this manual has something wrong and we need to fix it? If
so, can you please revise the document properly?
The wiki must be fixed I think.
Please post your systemconfig.conf. That one should contain something like
CONFIGRD = YES
at the beginning.
==
[EMAIL PROTECTED] ~]# cat /etc/systemconfig/systemconfig.conf
[BOOT]
ROOTDEV = /dev/sda9
BOOTDEV = /dev/sda
DEFAULTBOOT = systemimager
[KERNEL0]
LABEL = systemimager
PATH = /boot/vmlinuz-2.6.9-55.ELsmp
INITRD = /boot/initrd-2.6.9-55.ELsmp.img
APPEND = ro root=LABEL=/12 rhgb quiet console=tty0
[EMAIL PROTECTED] ~]# chroot /var/lib/systemimager/images/oscarimage
[EMAIL PROTECTED] ~]# cat /etc/systemconfig/systemconfig.conf
# systemconfig.conf written by systeminstaller.
CONFIGBOOT = YES
CONFIGRD = YES
[BOOT]
ROOTDEV = /dev/sda6
BOOTDEV = /dev/sda
DEFAULTBOOT = 2.6.9-55.ELsmp
[KERNEL0]
PATH = /boot/vmlinuz-2.6.9-55.ELsmp
LABEL = 2.6.9-55.ELsmp
[KERNEL1]
PATH = /boot/vmlinuz-2.6.9-55.EL
LABEL = 2.6.9-55.EL
[EMAIL PROTECTED] ~]#
==
Yes, it does have the option on the systemconfig.conf of oscarimage.
Regards,
- DongInn
BTW DongInn have you tried to test this with Debian/Ubuntu? It seems
systemconfigurator is still using the old mkinitrd command (instead of
the new update-initramfs or mkinitramfs).
Erich, I think the patch below should be included (but I need to test it
before).
-Andrea
Index: lib/Initrd/Debian.pm
===
--- lib/Initrd/Debian.pm(revision 712)
+++ lib/Initrd/Debian.pm(working copy)
@@ -32,10 +32,14 @@
sub footprint {
my $class = shift;
-my $exe = /usr/sbin/mkinitrd;
-my $debconf = /etc/mkinitrd/mkinitrd.conf;
-if(-f $exe -e $debconf) {
-return 1;
+my @exe = ('/usr/sbin/mkinitrd',
+ '/usr/sbin/update-initramfs');
+my @debconf = ('/etc/mkinitrd/mkinitrd.conf',
+ '/etc/initramfs-tools/update-initramfs.conf');
+for (my $i = 0; $i $#exe + 1; $i++) {
+if(-f $exe[$i] -e $debconf[$i]) {
+return 1;
+}
}
return 0;
}
@@ -44,8 +48,14 @@
my ($class, $kernel) = @_;
my $version = kernel_version($kernel);
my $outfile = initrd_file($version);
-
-my $cmd = mkinitrd -o $outfile /lib/modules/$version;
+
+my $cmd;
+if (-f '/usr/sbin/update-initramfs') {
+$cmd = /usr/sbin/update-initramfs -k $version -u;
+} else {
+$cmd = mkinitrd -o $outfile /lib/modules/$version;
+}
+
my $rc = system($cmd);
if($rc != 0) {
carp(Debian style ramdisk generation failed.);
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] bittorrent problem
Bas van der Vlies a écrit : # Interface used to seed files with bittorrent. BT_INTERFACES=eth0 BT_INTERFACE will do the trick (so remove the trailing s_ ;-) i removed the trailing S (shame on me) but it's the same error, so the error didnt'come from this line /etc/init.d/systemimager-server-bittorrent start Starting SystemImager's BitTorrent Transport: systemimager-server-bittorrent... tracker: ok ERROR: error in /etc/systemimager/bittorrent.conf: BT_INTERFACE not specified or not valid! failed. here below... the output log from the start command.. the error seems to come from the si_installbtimage command don't know why tracker: ok + '[' -z GX320_etch ']' + BT_IMAGES='--images GX320_etch' + '[' '!' -z GX320_etch ']' + BT_OVERRIDES='--overrides GX320_etch' + '[' n = y ']' + '[' n = y ']' + si_installbtimage --quiet n n --images GX320_etch --overrides GX320_etch ERROR: error in /etc/systemimager/bittorrent.conf: BT_INTERFACE not specified or not valid! + '[' 255 -ne 0 ']' + echo failed. failed. + exit 1 this command seems to output the same error, with or without the needed arguments $ si_installbtimage ERROR: error in /etc/systemimager/bittorrent.conf: BT_INTERFACE not specified or not valid! $ si_installbtimage --quiet --compress n --images GX320_etch --update n ERROR: error in /etc/systemimager/bittorrent.conf: BT_INTERFACE not specified or not valid! any ideas? thanks -- Maurice Libes Tel : +33 (04) 91 82 93 25Centre d'Oceanologie de Marseille Fax : +33 (04) 91 82 93 03UMS2196CNRS- Campus de Luminy, Case 901 F-13288 Marseille cedex 9 Veuillez noter ma nouvelle adresse == [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] bittorrent problem
Maurice Libes wrote: Bas van der Vlies a écrit : # Interface used to seed files with bittorrent. BT_INTERFACES=eth0 BT_INTERFACE will do the trick (so remove the trailing s_ ;-) i removed the trailing S (shame on me) but it's the same error, so the error didnt'come from this line /etc/init.d/systemimager-server-bittorrent start Starting SystemImager's BitTorrent Transport: systemimager-server-bittorrent... tracker: ok ERROR: error in /etc/systemimager/bittorrent.conf: BT_INTERFACE not specified or not valid! failed. here below... the output log from the start command.. the error seems to come from the si_installbtimage command don't know why tracker: ok + '[' -z GX320_etch ']' + BT_IMAGES='--images GX320_etch' + '[' '!' -z GX320_etch ']' + BT_OVERRIDES='--overrides GX320_etch' + '[' n = y ']' + '[' n = y ']' + si_installbtimage --quiet n n --images GX320_etch --overrides GX320_etch ERROR: error in /etc/systemimager/bittorrent.conf: BT_INTERFACE not specified or not valid! + '[' 255 -ne 0 ']' + echo failed. failed. + exit 1 this command seems to output the same error, with or without the needed arguments $ si_installbtimage ERROR: error in /etc/systemimager/bittorrent.conf: BT_INTERFACE not specified or not valid! $ si_installbtimage --quiet --compress n --images GX320_etch --update n ERROR: error in /etc/systemimager/bittorrent.conf: BT_INTERFACE not specified or not valid! any ideas? thanks Which version of systemimager are you using? Could you post your new bittorrent.conf? Which distribution are you using? which is your default shell (ls -l /bin/sh)? -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Fwd: New version, same errors :(
Stas Oskin wrote: OK, I managed to solve it. There were two issues: 1) The master looked for raid5.ko module, while I had raid456.ko. Changing the master script took care of this. 2) The mdadm --create failed due to specified --chunk 256 parameter, with the following errors: invalid sb on partition error importing sb -22 I fixed it by removing the --chunk 256 from the master script mdadm part. But now my deployed client has chunk size of 64K, while my golden client had a size of 256K. Such small chunk sizes probably unhealthy for disks, any idea how to solve it? Thanks, Stas. Stas, thanks for reporting this problem. I've just fixed the raid456 naming issue in trunk: http://trac.systemimager.org/changeset/4416 Now, the chuck size issue seems a weird problem, it even seems a kernel bug... have you tried with UYOK? another interesting test could be to try with 4.1.1 BOEL: http://sourceforge.net/project/showfiles.php?group_id=259package_id=37046release_id=579248 Let me know. -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Fwd: New version, same errors :(
Hi. The strange thing with chunk, is that the partitions already contain SB - does the partitioning process creates it? The mdadm apparently tries to import it, and then fails. About UYOK, I followed Quick Start HOWTO, and part of it is the following command: si_prepareclient --server 192.168.1.1 This command should already have created UYOK kernel, correct? How can I try the stock BOEL then (perhaps this would solve it)? Also, is the 4.1.1 stable enough for production? Thanks, Stas. 2008/3/3, Andrea Righi [EMAIL PROTECTED]: Stas Oskin wrote: OK, I managed to solve it. There were two issues: 1) The master looked for raid5.ko module, while I had raid456.ko. Changing the master script took care of this. 2) The mdadm --create failed due to specified --chunk 256 parameter, with the following errors: invalid sb on partition error importing sb -22 I fixed it by removing the --chunk 256 from the master script mdadm part. But now my deployed client has chunk size of 64K, while my golden client had a size of 256K. Such small chunk sizes probably unhealthy for disks, any idea how to solve it? Thanks, Stas. Stas, thanks for reporting this problem. I've just fixed the raid456 naming issue in trunk: http://trac.systemimager.org/changeset/4416 Now, the chuck size issue seems a weird problem, it even seems a kernel bug... have you tried with UYOK? another interesting test could be to try with 4.1.1 BOEL: http://sourceforge.net/project/showfiles.php?group_id=259package_id=37046release_id=579248 Let me know. -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
