DongInn Kim wrote: > Hi Andrea, > > I have tested again but this time I could go through even though I still get > the rsync connection problems. Can you please look into this logs and see > what happened? BTW, can you imagine how hard to type the console information > here? Basically systemmonitor thing does not work on the OSCAR crispy branch > now.
OK, all the "nc connection refused" errors are the reason of the monitoring failure. Did you allow your clients to reach the image server on port 8181? Moreover to get the console messages on your client your image server must be able to reach the imaging client on port 8181 (it's always 8181). If you don't want to use the si_monitortk interface you can always get the virtual console output by a simple "telnet imaging_client 8181 > /tmp/imaging_client.out". Just some systemimager hidden tricks... ;-) Anyway, in the output you posted apparently there're no rsync errors receiving oscarimage. You should try to enable verbose file listing (see --listing option in si_mkautoinstallscript(8)) in order to have some detailed info and see *where* exactly it fails. Otherwise you should try to update rsync to a more recent version, or try to limit the bandwidth on the server side, for example appending the "--bwlimit=8192" parameter to the OPTION variable in /etc/init.d/systemimager-server-rsyncd. Moreover, did you use some special network settings via pre-install scripts (like increasing the tcp buffer size, etc.)? -Andrea ------------------------------------------------------------------------- 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-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
