Hello, Thanks for your help. My problem is now solved. I provide you my solution. It could help someone in the future :
Recall : an Itanium (4 ways) node booted on the network with a systemimager Linux kernel release 2.4.9 If i boot the node with 4 GBytes of RAM, rsync meets some problems during big transfers with the rsync daemon on the server node (see the error messages in my previous mail) If i boot the node with only 512 MBytes of RAM, rsync works fine. For this, i modified the /tftpboot/elilo.conf file by adding the following line : append="mem=512M" Best regards, Cédric Lambert BULL S.A ECHIROLLES FRANCE Tel: +33 (0)4 76 29 73 87 Cedric Lambert wrote: > > Hello, > > Thanks for your help. Following your answers, I tried the same > experiences with rsync 2.5.5 on the client side and on the server side : > i have always an error but it's better now because this error is always > the same at each run :-) > > rsync -av --numeric-ids 102.1.1.104::ia64-boot/mkdosfs /tmp/ is still OK > rsync -av --numeric-ids 102.1.1.104::oscarimage/ /a/ fails with the > following error message : > > On the client node side: > ------------------------ > > receiving file list ... overflow : flags=0x45 l1=0 l2=203336 > lastname=ONETARY > ERROR: buffer overflow in receive_file_entry > rsync error: error allocating core memory buffers (code 22) at > util.c(238) > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Your autoinstall has failed. Please send the above messages to > [EMAIL PROTECTED] > > On the server side: > ------------------- > > rsync: error writing 4096 unbuffered bytes - exiting : connection reset > by peer > rsync error: error in rsync prototcol data stream(code 12) at io.c(463) > > I have not managed to find out the problem. Does anyone have an idea on > this problem ? > Could it be a problem with the NIC driver when my client node is booted > over the network or a problem coming from my hub (Centre COM MR 820 TR) > ? Anything else ? > Any help would be appreciated. > > Best regards, > > Cédric Lambert > > BULL S.A ECHIROLLES FRANCE > tel: +33 (0)4 76 29 73 87 > > [EMAIL PROTECTED] wrote: > > > > Cedric: There are good reasons that there is now a version 2.5.5 > > available at http://rsync.samba.org/ftp/rsync/rsync-2.5.5.tar.gz > > 2.4.6 is subject to lots of wierd little problems like that, and the contributors >have done a lot of fixes and enhancements (check out > > NEWS and OLDNEWS in the distribution). It's likely that if your problems > > actually are rsync problems, that they will be fixed by upgrading. > > > > Tim Conway > > [EMAIL PROTECTED] > > 303.682.4917 office, 303.921.0301 cell > > Philips Semiconductor - Longmont TC > > 1880 Industrial Circle, Suite D > > Longmont, CO 80501 > > Available via SameTime Connect within Philips, caesupport2 on AIM > > "There are some who call me.... Tim?" > > > > Cedric Lambert <[EMAIL PROTECTED]> > > Sent by: [EMAIL PROTECTED] > > 08/27/2002 09:00 AM > > Please respond to Cedric.Lambert > > > > > > To: [EMAIL PROTECTED] > > cc: CEDRIC LAMBERT <[EMAIL PROTECTED]> > > AIME LE-ROUZIC <[EMAIL PROTECTED]> > > (bcc: Tim Conway/LMT/SC/PHILIPS) > > Subject: rsync problem in systemimager > > Classification: > > > > Hello, > > > > I'm working on the oscar-1.3 release with my Linux Itanium's cluster to > > test cloning process via systemimager. > > After having succeeded to boot my client node via the network, when > > running the following script : /var/lib/systemimager/scripts/ced1.sh > > rsync is able to get small files (e.g : mkdosfs). However, when the > > script tries to rsync the whole oscar image in the following way : > > > > rsync -av --numeric-ids $IMAGESERVER::$IMAGENAME/ /a/ || shellout > > > > there is automatically an error which is different at each run. > > > > It can be : > > > > ... > > /usr/lib/locale/ar_LY.utf8/LC_MESSAGES/ > > rsync: connection unexpectedly closed (62950 bytes read so far) > > rsync error: error in rsync protocol data stream (code 12) at io.c(151) > > > > or : > > > > receiving file list ... unexpected tag -7 > > rsync error: error in rsync protocol data stream (code 12) at io.c(299) > > > > or : > > > > receiving file list ... unexpected tag 114 > > rsync error: error in rsync protocol data stream (code 12) at io.c(299) > > > > or : > > > > mkdosfs 2.8 (28 Feb 2001) > > receiving file list ... overflow : flags=0x73 l1=111 l2=197376 > > lastname=/usr/lib/locale/pt_PT.utf8@euro/LC_CTYPE > > ERROR: buffer overflow in receive_file_entry > > rsync error: error allocating core memory buffers (code 22) at > > util.c(238) > > > > and then the following message appears : > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > > Your autoinstall has failed. Please send the above messages to > > [EMAIL PROTECTED] > > > > After searching on the net and experimenting a lot of things, i have not > > managed to find out the problem. Even if the rsync command (rsync -av > > --numeric-ids $IMAGESERVER::$IMAGENAME/ /a/ ) looks to work between my > > server and a client node booted on its hard drive (not booted via the > > network). Between the nodes, a hub (Centre COM MR 820 TR) is present. > > > > Remarks : > > > > Here are some information on the server system used : > > > > - cat /etc/redhat-release : Red Hat Linux release 7.2 (Enigma) > > > > - uname -a : Linux eolepriv 2.4.9-18smp #1 SMP Tue Dec 11 12:59:00 EST > > 2001 ia64 unknown > > > > - release of rsync on the server and on the network booted client : > > rsync --version > > rsync version 2.4.6 protocol version 24 > > Written by Andrew Tridgell and Paul Mackerras > > > > - rsync on the server is running like this : /usr/bin/rsync --daemon > > --config=/etc/systemimager/rsyncd.conf > > > > - here is my rsyncd.conf : > > more /etc/systemimager/rsyncd.conf > > # > > # "SystemImager" > > # > > # Copyright (C) 1999-2002 Brian Elliott Finley > > <[EMAIL PROTECTED]> > > # > > # $Id: 10header,v 1.1.2.2 2002/03/22 00:25:40 brianfinley Exp $ > > > > ######################################################################## > > # # > > # WARNING: # > > # This file is automatically generated by SystemImager, do not edit! # > > # Everything you add directly to this file will be lost the next # > > # time it is generated. See the update_si_rsync manpage for details # > > # on how to have local entries added each time this file is # > > # generated. # > > # # > > ######################################################################## > > > > list = yes > > timeout = 600 > > dont compress = *.gz *.tgz *.zip *.Z *.ZIP *.bz2 *.deb *.rpm *.dbf > > uid = root > > gid = root > > use chroot = yes > > log file = /var/log/systemimager/rsyncd > > > > hosts allow = 102.1.1.104/255.255.255.0 > > > > [scripts] > > path = /var/lib/systemimager/scripts > > > > [i386-boot] > > path=/usr/share/systemimager/i386-boot > > > > [ia64-boot] > > path=/usr/share/systemimager/ia64-boot > > > > # only image entries below this line > > > > [oscarimage] > > path=/var/lib/systemimager/images/oscarimage > > > > Thanks for any help > > Best regards, > > > > Cédric Lambert > > > > BULL S.A ECHIROLLES FRANCE > > tel: +33 (0)4 76 29 73 87 > > -- > > To unsubscribe or change options: > > http://lists.samba.org/mailman/listinfo/rsync > > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html > -- > To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html