On Wed, 22 Jan 2003, [iso-8859-1] "L�veill�, Marc" wrote:
> rsync -av 192.168.1.200::boot/i386/standard/boel_binaries.tar.gz /tmp
> rsync:failed to connect to 192.168.1.200 : connection refused.
There was a bug identified in SystemImager 3.0 yesterday that in some
environments (e.g., RH 7.3), the rsync daemon is not started properly on
the head node. This causes exactly what you are seeing -- connectivity to
the head node is fine, but it can't pull the image down because rsyncd is
not running. You can verify this by doing a ps on the head node and
checking to see that rsyncd is not running.
The solution is to edit /etc/rc.d/init.d/systemimager on the head node.
One of the first executable lines in the script is:
PATH=....a bunch of stuff
Change it to:
export PATH=...a bunch of stuff
And run:
service systemimager start
Then reboot your client node, and it should be able to pull down the
image.
The SIS guys are aware of this problem, and are working one getting a fix
in the OSCAR tree.
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users
