[Sisuite-devel] question about "rsync: failed to set times"

[Jing CDL Sun]

Hello,

I am using systemimager-4.0.0-1 to clone RedHatEL-Server5 on xblade
machines, but I ran into rsync problems, many "rsync: failed to set times"
have be displayed for all the symbol links in the image.
After searched by google, I find this is a RedHat bugzilla, though the
warning message is ugly, it will not effect the normal rsync function. But
in my case, after many these warning messages, the rsync stopped, and gave
an error message of "some files could not be transferred (code 23) at
main.c(1298)", I am not sure why this happened, could someone help me?
thank you in advance.

This is the console screen when rsync stopped:
--------------------------------------------------
rsync: failed to set times on "/a/usr/sbin/vigr": Function not implemented
(38)
rsync: failed to set times on "/a/usr/tmp": Function not implemented (38)
/rsync: failed to set times on "/a/var/ct/IW": Function not implemented
(38)
-rsync error: some files could not be transferred (code 23) at main.c(1298)
a
Killing off running processes.

write_variables
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
This is the SystemImager autoinstall system

Your autoinstall has failed. You can use the shell prompt to try and see
--------------------------------------------------

By the way I have see the log file in /tmp/si.log, but these is no any clue
in it.







Best Regards,
-----------------------------
Sun Jing(Ë)
IBM China Software Development Laboratory
Tel: [phone] ext.3625 E-mail: ***@cn.ibm.com
Address:5F Deshi Building No.9 Shangdi East Road Haidian District,Beijing
City P.R.China 100085, P.R.China.

[Jing CDL Sun]

Additionally, is there a way to avoid these warning messages? except
rebuilding the rsync packages in a lower distribution.









Jing CDL
Sun/China/***@IBM
CN To
Sent by: sisuite-dev
sisuite-devel-bou <sisuite-***@lists.sourceforge.ne
***@lists.source t>
forge.net cc

Subject
2007-12-05 10:46 [Sisuite-devel] question about
"rsync: failed to set times"










Hello,

I am using systemimager-4.0.0-1 to clone RedHatEL-Server5 on xblade
machines, but I ran into rsync problems, many "rsync: failed to set times"
have be displayed for all the symbol links in the image.
After searched by google, I find this is a RedHat bugzilla, though the
warning message is ugly, it will not effect the normal rsync function. But
in my case, after many these warning messages, the rsync stopped, and gave
an error message of "some files could not be transferred (code 23) at
main.c(1298)", I am not sure why this happened, could someone help me?
thank you in advance.

This is the console screen when rsync stopped:
--------------------------------------------------
rsync: failed to set times on "/a/usr/sbin/vigr": Function not implemented
(38)
rsync: failed to set times on "/a/usr/tmp": Function not implemented (38)
/rsync: failed to set times on "/a/var/ct/IW": Function not implemented
(38)
-rsync error: some files could not be transferred (code 23) at main.c(1298)
a
Killing off running processes.

write_variables
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

This is the SystemImager autoinstall system

Your autoinstall has failed. You can use the shell prompt to try and see
--------------------------------------------------

By the way I have see the log file in /tmp/si.log, but these is no any clue
in it.

[Bernard Li]

Hi Jing:

This is a known bug if you search through the sisuite-users mailing-list:

http://www.mail-archive.com/sisuite-***@lists.sourceforge.net/

and it is already fixed in the 4.0.x branch.

Please try these development snapshots -- they should work better for you:

http://therealms.org/oss/systemimager/snapshots/

Cheers,

Bernard

Post by Jing CDL Sun
Hello,
I am using systemimager-4.0.0-1 to clone RedHatEL-Server5 on xblade
machines, but I ran into rsync problems, many "rsync: failed to set times"
have be displayed for all the symbol links in the image.
After searched by google, I find this is a RedHat bugzilla, though the
warning message is ugly, it will not effect the normal rsync function. But
in my case, after many these warning messages, the rsync stopped, and gave
an error message of "some files could not be transferred (code 23) at
main.c(1298)", I am not sure why this happened, could someone help me? thank
you in advance.
--------------------------------------------------
rsync: failed to set times on "/a/usr/sbin/vigr": Function not implemented
(38)
rsync: failed to set times on "/a/usr/tmp": Function not implemented (38)
/rsync: failed to set times on "/a/var/ct/IW": Function not implemented
(38)
-rsync error: some files could not be transferred (code 23) at main.c(1298)
a
Killing off running processes.
write_variables
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
This is the SystemImager autoinstall system
Your autoinstall has failed. You can use the shell prompt to try and see
--------------------------------------------------
By the way I have see the log file in /tmp/si.log, but these is no any clue
in it.
Best Regards,
-----------------------------
Sun Jing(孙靖)
IBM China Software Development Laboratory
Address:5F Deshi Building No.9 Shangdi East Road Haidian District,Beijing
City P.R.China 100085, P.R.China.
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
sisuite-devel mailing list
https://lists.sourceforge.net/l

[Jing CDL Sun]

Hi Bernard,

Thank you for your reply.

Sorry I did not find the original thread before, bother you again.

I will try this 4.0.1 branch now, thank you.

By the way, when using 4.0.0, I also find other 2 problem, please help me
to confirm if it is my usage error:
1. systemconfigurator can not find /vmlinuz-2.6.18-8.el5
my kernel and initrd are located in /a/boot, but I see in the master
script, there is a code line like:
sed -i 's:/boot::g' /a/etc/systemconfig/systemconfig.conf
then after this sed, [KERNEL0] section becomes to:
LABEL =....
PATH = /vmlinuz-2.6.18-8.el5 (please note, the original PATH =
/boot/vmlinuz-2.6.18-8.el5)

I am not sure about the purpose of this sed, but after this installation
shell out with error message:
kernel /vmlinuz-2.6.18-8.el5 can not be found. Please forgive my
impertinence, I just comment this code line out,
while this time systemconfigurator can work find.

2. after firstboot, kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(0,0)
I checked the grub, and compared it with Golden master, it seems that
INITRD has been set wrongly,
it is the same with kernel(INITRD = /vmlinuz-2.6.18-8.el5), after I
corrected it with INITRD = /initrd-2.6.18-8.el5.img,
the system can boot successfully.
I looked into the code of si_prepareclient,
/etc/systemconfig/systemconfig.conf file was generated wrongly.


Jing.

[Bernard Li]

Are you using the latest version of SystemConfigurator?

http://sourceforge.net/project/showfiles.php?group_id=24006&package_id=17960

Cheers,

Bernard

Post by Jing CDL Sun
Hi Bernard,
Thank you for your reply.
Sorry I did not find the original thread before, bother you again.
I will try this 4.0.1 branch now, thank you.
By the way, when using 4.0.0, I also find other 2 problem, please help me
1. systemconfigurator can not find /vmlinuz-2.6.18-8.el5
my kernel and initrd are located in /a/boot, but I see in the master script,
sed -i 's:/boot::g' /a/etc/systemconfig/systemconfig.conf
LABEL =....
PATH = /vmlinuz-2.6.18-8.el5 (please note, the original PATH =
/boot/vmlinuz-2.6.18-8.el5)
I am not sure about the purpose of this sed, but after this installation
kernel /vmlinuz-2.6.18-8.el5 can not be found. Please forgive my
impertinence, I just comment this code line out,
while this time systemconfigurator can work find.
2. after firstboot, kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(0,0)
I checked the grub, and compared it with Golden master, it seems that
INITRD has been set wrongly,
it is the same with kernel(INITRD = /vmlinuz-2.6.18-8.el5), after I
corrected it with INITRD = /initrd-2.6.18-8.el5.img,
the system can boot successfully.
I looked into the code of si_prepareclient,
/etc/systemconfig/systemconfig.conf file was generated
wrongly.
Jing.

[Andrea Righi]

Post by Jing CDL Sun
Hi Bernard,
Thank you for your reply.
Sorry I did not find the original thread before, bother you again.
I will try this 4.0.1 branch now, thank you.
By the way, when using 4.0.0, I also find other 2 problem, please help
1. systemconfigurator can not find /vmlinuz-2.6.18-8.el5
my kernel and initrd are located in /a/boot, but I see in the
sed -i 's:/boot::g' /a/etc/systemconfig/systemconfig.conf
LABEL =....
PATH = /vmlinuz-2.6.18-8.el5 (please note, the original PATH =
/boot/vmlinuz-2.6.18-8.el5)
I am not sure about the purpose of this sed, but after this
kernel /vmlinuz-2.6.18-8.el5 can not be found. Please forgive my
impertinence, I just comment this code line out,
while this time systemconfigurator can work find.
2. after firstboot, kernel panic - not syncing: VFS: Unable to mount
root fs on unknown-block(0,0)
I checked the grub, and compared it with Golden master, it seems that
INITRD has been set wrongly,
it is the same with kernel(INITRD = /vmlinuz-2.6.18-8.el5), after I
corrected it with INITRD = /initrd-2.6.18-8.el5.img,
the system can boot successfully.
I looked into the code of si_prepareclient,
/etc/systemconfig/systemconfig.conf file was generated wrongly.

Both problems #1 and #2 are already fixed in the 4.0.x branch as well.

-Andrea

[Jing CDL Sun]

Bernard,

I have verified systemimager-4.0.1, and all these three problems I met in
v4.0.0 are all fixed,
v4.0.1 is good for me, thank you.





Best Regards,
-----------------------------
Sun Jing(Ë)
IBM China Software Development Laboratory
Tel: [phone] ext.3625 E-mail: ***@cn.ibm.com
Address:5F Deshi Building No.9 Shangdi East Road Haidian District,Beijing
City P.R.China 100085, P.R.China.