When I specify the --mcast-all-addr (or --mcast-rdv-addr) option on the
receiver, udpcast exits and displays "SIGSEGV". I am using the 20060525
versions of the initrd and linux files for PXE booting. I have also tried
using the 20060525 cd and had the same problem. I really appriciate all the
hard work you have put into udpcast. Udpcast is crucial to our department
and has served us very well.
Texas Tech University
I'm creating my own boot disk to do a re-image from udpcast. I'm a little
new at this but have been using linux for about a year and a half now as my
desktop machine. I've had a decent amount of experience coding so I'm no
stranger to that either.
I've got an boot disk based off of slackware 10.2. The boot disk loads up a
ramdisk and then mounts the target hard disk on /mnt/target and then uses
udp-receiver to receive a tarball into that directory. So theoretically all
data should go to the hard disk. Everything is fine until udp-receiver is
started. Once it starts, the Inactive memory usage begins steadily rising
until it has reached a value about 2 mb below the memory limit, where the
amount of free memory begins oscillating. This amount of inactive memory
remains until the bash script that started udpcast exits.
The command line used to start udp-receiver is
udp-receiver --nokbd 2>/udpcast-log | pv -pets --file size--
$pkgfn is the name of the tarball.
Normally this is not an issue. But sometimes, the memory peaks out, and the
kernel kills either udp-receiver or another crucial process. Whoops. The
boot disk works fine for 128 MB memory computers, but not on 64 MB memory
Anybody ever have this happen before? Any ideas??
Thanks very much for any help/guidance,
Dermot Fitzgerald wrote:
> I've been attempting to set up a sender on Windows (XP, 2003) using a compressed disk image made by g4u.
> The problem is that the application runs a few seconds then exits.
I tried it here myself (XP), and it works flawlessly...
> No indication is given if there was an error (even if the --Logfile myLogFile option is used).
> Can anyone tell me what I might be doing wrong? Has anyone else had this experience?
Actually, currently --log (note the lower case l, and abscence of file)
is only taken into account at the sender, not the receiver (although
both do understand the option). On the sender, it logs various statistics.
> Thanks a lot,
Just trying out udpcast, using PXE after having recompiled the kernel to
support a serial console (headless machines).
This is what I get :
RAMDISK: Couldn't find valid RAM disk image starting at 0.
Kernel panic: VFS: Unable to mount root fs on unknown-block(1,0)
It seems that the initrd is wrong (downloaded at
# file initrd
It's not in bzip2 format, it's not cpio either.. so am I doing something
really wrong or is the file corrupted ?
# md5sum initrd
Hey, I just noticed the new cast-o-matic with the option to add things.
It's a great idea, and I've been trying to use it. However, I've been
running into problems.
First, it seems even though I'm telling it I want to preconfigure the boot
disk menu, the floppy image is still prompting me for every option. I
need to send this to an associate whom will not really understand the
options given, and preconfiguring will be my best bet.
Another thing, I statically built sfdisk and made a script for it to load
so I can partition the drive before dumping a partition load, but the
problem is, it executes the commands after the udp boot disk menu/options
are run, so if the hard drive isn't partitioned, I have no /dev/hda1
Is there a way to make it so my sfdisk runs before the udpcast menu?
Before the options are set?
Thanks for your response, I think I encountered one of the "slow" machines
today while I was running some tests. I guess there are just some slow
ones in every group.
I met with some network analysts from my university today and they
explained how since the network is operating on a mixed CGMP/IGMPv2
environment multicasts are sometimes flaky. So, now that I may have found
a source of the problem my question is if any has any experience using
udpcast in a mixed environment, and if so what steps they took to make
udpcast more reliable. And also if there is a version of udpcast that uses
IGMPv2 rather than IGMPv3.
Our county really loves using udpcast, it such a helpful product. We
just got in new Dell computers, Optiplex GX620, with the nic Broadcom
NetXtreme 57xx Gigabit controller. I have the ver. 20062503 of udpcast
that we are using. I choose the Broadcom NetXtreme II BCM5706/5708
driver on the cd and it acts like it is going to work, but after I put
in the IP and subnet mask and hit enter I get error messages of
SIOCSIFADDR: no such device, SIOSCINETMASK: no such device,
SIOCSIBRDADDR: no such device. Can anyone help me? We have 120 computers
Haywood County Schools
-----BEGIN PGP SIGNED MESSAGE-----
I've had excellent repeated success with the Udpcast boot disks imaging
physical drives between computers as long as there is only one hard
drive on the IDE chain on each machine. I've backed-up and restored
numerous times with different systems. This is fine except I want to
keep my backups as image files on a larger volume.
I have not been successful getting the udp-receiver executed on Fedora
Core 5 on the target machine to play with udp-sender from the boot disk
on a notebook I want to back up. I'm hoping to use the Fedora machine
to back up and restore several other machines on my network to a new
250GB drive mounted on the Fedora box.
On the notebook (or any machine to be backed up) I boot from the Udpcast
boot CD and manually set the IP address. I take the default values for
everything else, except I select no compression. I then start
udp-sender on the CD-booted machine. It executes with the normal
Then I go to the Fedora machine and execute the following:
"udp-receiver --file <path/file.img> --log <path/file.log>" and press
enter. The sender machine immediately acknowledges and establishes a
connection with the receiver machine. The sender machine displays the
"Press any key to start" message, but udp-receiver on the Fedora machine
shows nothing in response. The receiver machine (Fedora box) appears to
sit idle as if it is not getting something it needs; there is no "Press
any key to start" message on the receiver machine. If I hit a key on
the sender machine anyway to get it started it starts transmitting but
promptly starts displaying timeout lines and eventually quits. After
killing the receiver with CTRL-C, two empty files, <path/file.img> and
<path/file.log> are on the target volume. There is nothing in those
files, even when viewed with a hex editor. I have observed that the two
systems are using different multicast addresses, but they still find
I have scoured the man pages of both udp-receiver and udp-sender, and
experimented with several Udpcast switch combinations to no avail. I've
tried --nosync, --broadcast, --mcast-all-addr, --mcast-rdv-address
(which crashed the sender and displayed a SIG message), --nokbd,
- --autostart 50, --ttl 1, --rexmit-hello-interval 1000,
- --retries-until-drop 100 (which also crashed the sender and displayed a
SIG message), --point-to-point, and -b 1024. Nothing changed from any
of that; udp-receiver never provides a "Press any key to start" message,
even after the sender recognizes the established connection and displays
the "Press any key to start" message.
I also tried booting the receiving machine from the Udpcast boot CD and
trying the --file <path/file.img> option there, but it just seemed to
transfer a physical copy of the /boot folder from the sending machine.
So, I repartitioned the target drive and am hoping there is some way to
make Udpcast work in my configuration by writing physical images of the
source drives to logical image files on the target drive. And,
naturally, I would like to restore from image files on the storage
volume mounted on the Fedora machine to physical disks on the target
Mark Caldwell Walker
GnuPG public key is available at
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v18.104.22.168 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----