Hello.
I am trying to clone a recently upgraded box with openSUSE 10.3. This is the
golden node of a cluster of computers that had an old version of
systemimager running. I upgraded also the systemimager packages:
systemconfigurator-2.2.11-1
systemimager-common-4.0.2-1
systemimager-x86_64initrd_template-4.0.2-1
systemimager-client-4.0.2-1
And also installed:
perl-AppConfig-1.66-16
perl-File-HomeDir-0.65-26
On the server side, I also installed:
systemimager-common-4.0.2-1
systemimager-server-4.0.2-1
systemimager-x86_64boot-standard-4.0.2-1
systemconfigurator-2.2.11-1
When I am doing a si_prepareclient with --kernel and --modules options (full
output attached below) I got two warning messages at the end of the process:
WARNING: unable to detect kernel release of "/boot/vmlinuz-
2.6.22.5-31-default"!
WARNING: coulnd't create file /etc/systemconfig/systemconfig.conf (needed by
systemconfigurator)
I can go on with si_getclient but when I do the cloning in another machine
there is a problem running systemconfigurator because systemconfig.conf is
missing in the image.
Any ideas how can I fix it? Shoud I create the systemconfig.conf file
manually?
Thank you very much.
Jesús .-
Output of the si_prepareclient:
golden-client:~ # si_prepareclient --server 10.5.4.20 --kernel
/boot/vmlinuz-2.6.22.5-31-default --modules
/lib/modules/2.6.22.5-31-default/
Welcome to the SystemImager si_prepareclient command. This command may
modify
the following files to prepare your golden client for having it's image
retrieved by the imageserver. It will also create the /etc/systemimager
directory and fill it with information about your golden client. All
modified
files will be backed up with the .before_systemimager-4.0.2 extension.
/etc/services:
This file defines the port numbers used by certain software on your
system.
Entries for rsync will be added if necessary.
/tmp/fileIOkEBU:
This is a temporary configuration file that rsync needs on your golden
client
in order to make your filesystem available to your SystemImager server.
inetd configuration:
SystemImager needs to run rsync as a standalone daemon on your golden
client
until it's image is retrieved by your SystemImager server. If rsyncd is
configured to run as a service started by inetd, it will be temporarily
disabled, and any running rsync daemons or commands will be stopped.
Then,
an rsync daemon will be started using the temporary configuration file
mentioned above.
See "si_prepareclient --help" for command line options.
Continue? (y/[n]): y
*********************************** WARNING
***********************************
This utility starts an rsync daemon that makes all of your files accessible
by anyone who can connect to the rsync port of this machine. This is the
case until you reboot, or kill the 'rsync --daemon' process by hand. By
default, once you use si_getimage to retrieve this image on your
imageserver,
these contents will become accessible to anyone who can connect to the rsync
port on your imageserver. See rsyncd.conf(5) for details on restricting
access to these files on the imageserver. See the systemimager-ssh package
for a more secure method of making images available to clients.
*********************************** WARNING
***********************************
Continue? (y/[n]): y
One or more rsync daemons appear to be running on this machine. If you
continue, those daemons will be killed.
Continue? (y/[n]): y
Signaling xinetd to restart...
Using "parted" to gather information about disk:
/dev/sda
>>> Copying modules to new initrd from: /lib/modules/2.6.22.5-31-default/...
Use of uninitialized value in concatenation (.) or string at
/usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm line 151.
skipping directory /lib/modules/2.6.22.5-31-default//kernel
skipping non-regular file "lib/modules/2.6.22.5-31-default/build"
skipping non-regular file "lib/modules/2.6.22.5-31-default/source"
>>> Appending insmod commands to ./my_modules_dir/INSMOD_COMMANDS...
>> Using custom kernel: hotplug will be used to autodetect the needed
modules...
Use of uninitialized value in pattern match (m//) at
/usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm line 576.
WARNING: couldn't find a valid filesystem for initrd.img!
WARNING: trying with cpio initramfs...
>>> Choosing filesystem for new initrd: cpio
>>> Creating new initrd from staging dir: /tmp/.systemimager.31
>> cd /tmp/.systemimager.31 && find . ! -name "*~" | cpio -H newc --create
| gzip -9 > /etc/systemimager/boot/initrd.img
169755 blocks
>> ls -l /etc/systemimager/boot/initrd.img
-rw-r--r-- 1 root root 20800594 Feb 21 11:34
/etc/systemimager/boot/initrd.img
>> Evaluating initrd size to be added in the kernel boot options
>> (e.g. /etc/systemimager/pxelinux.cfg/syslinux.cfg):
>> suggested value -> ramdisk_size=95117.5
>>> Using kernel from: /boot/vmlinuz-2.6.22.5-31-default
>> ls -l /etc/systemimager/boot/kernel
-rw-r--r-- 1 root root 1594088 Feb 21 11:34 /etc/systemimager/boot/kernel
Starting or re-starting rsync as a daemon.....
done!
This client is ready to have its image retrieved. You must now run
the "si_getimage" command on your imageserver.
Your client has been successfully prepared. Boot kernel (copied from
this Linux distribution) and an initrd.img (generated by the
initrd_template package) can be found in /etc/systemimager/boot.
Automatically create configuration file for systemconfigurator:
>> /etc/systemconfig/systemconfig.conf
WARNING: unable to detect kernel release of "/boot/vmlinuz-
2.6.22.5-31-default"!
WARNING: coulnd't create file /etc/systemconfig/systemconfig.conf (needed by
systemconfigurator)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
