Rochus Schmid wrote: > hello, > > during an upgrade of our little cluster to open suse 10.2 (both image server > and clients: 2.6.18.2-34) i installed the recent systemimager 4.0.0-1 > (systemconfigurator 2.2.10-2). > > si_getimage and configuring the server (for netboot) works fine. > but when i boot another client it boots fine (no UYOK), partitions et. > but the rsync prints tons of errors always saying: > > rsync: failed to set times on .... > and ends with an error message. here the autoinstall process stops. > > i did not find anything related in the systemimager archives but the problem > is mentioned in a samba mailing list: > https://bugzilla.samba.org/show_bug.cgi?id=4977 > > obviously rsync tries to change the modification times for certain > directories? ... i am probably getting about 20% of what is discussed here > but my impression is that this is actually not really a problem but the > autoinstall script stops due to the error message. > > can i suppress the behavior of rsync to report an error in this case? and how > should i do that? or am i doing soemthing terribly wrong. > > any help would be highly appreciated (my coworkers are deperately waiting for > the cluster to be up and running again :-)
I can confirm that the rsync into the SystemImager initrd.img has been compiled on a 2.6.22 kernel, but we're using a 2.6.21 for the standard BOEL kernel. :-( I'm sure the fix for this particular case would be to simply update the BOEL kernel to 2.6.22, or just build SystemImager from source on a kernel < 2.6.22. But how to handle all the possible different UYOK kernels? This is not a simple issue. Anyway, to quickly proceed, an ugly workaround would be to simply comment the "|| shellout" in your .master script (/var/lib/systemimager/scripts/) at end of the rsync line (near line 372), or just use a different transport, i.e. BitTorrent (http://wiki.systemimager.org/index.php/BitTorrent). Moreover, could you open a ticket in our new bug tracking system (http://www.systemimager.org/trac/newticket)? It's still in beta, but hopefully we'll to open it "for production" very soon. In the while I'll start thinking to a smart solution to resolve (maybe updating rsync to the 3.0.0pre4 pre-release into the SystemImager initrd.img, that doesn't seem to correctly handle this problem)... Thanks for reporting, -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
