Multicast as Unicast

[Tom Elliott]

@danilopinotti What do you mean?

[Tom Elliott]

@danilopinotti See, hosts get their individual tasks so we can track it for logging purposes, but is it creating multiple multicast tasks still?

[JJ Fullmer]

Where are you seeing things running as unicast and as sending an image?
On your task list it looks like you have all multi-cast tasks and some of them just didn’t start.

Can you try to explain the problem you’re having again because I’m having trouble following.

Also, you’re on 1.2? Time to upgrade to trunk

[danilopinotti]

@Tom-Elliott Still creating a multiples multicast tasks

[Tom Elliott]

@danilopinotti What version are you running? In the signature it says 6323, have you tried upgrading?

[danilopinotti]

@Tom-Elliott said:

n the signature it says 6323, have you tried upgrading

The first time in 6323.
I’m upgrading today and now 6455

[Tom Elliott]

@Tom-Elliott said:

truncate table multicastSessions;
truncate table multicastSessionsAssoc;
delete from tasks where taskTypeID=8;

How are you running these? Do you have any information/output from running those commands?

[danilopinotti]

@Tom-Elliott said:

ing those commands?

Yes, im running
truncate table multicastSessions;
0 rows affected

truncate table multicastSessionsAssoc;
0 rows affected

delete from tasks where taskTypeID=8;
8 rows affected

For each test i try this

[Wayne Workman]

I can confirm that the output 0 rows affected is the standard output when a table with rows is truncated. Don’t ask me why, it just is.

[Tom Elliott]

@danilopinotti So, for clarity, after running the truncate code, and recreating the multicast tasks, the multicast tasks are still generating independent multicast tasks for each host?

[danilopinotti]

@Tom-Elliott said:

are still generating independent multicast tasks for each host?

It does not create a multicast to each host. It creates multiple multicast sessions, each session will not always have only one computer.
After running the SQL Querys nothing change

[danilopinotti]

I re-installed the Fog and somehow solved the problem.
To re-install I also created a new virtual machine.
By the way, a note. I don’t know whether or not deliberate it, but in the installation, i’ve set the Fog to use the eth1 interface, and even then, the default storage was set to eth0.

[Tom Elliott]

@danilopinotti the defined interface is leftovers from before fog 1.0.0. While I can fix it, it’s such a minimal thing it’s probably easier to just update after install. Though I will work to see what I can do.

[Wayne Workman]

@danilopinotti said:

in the installation, i’ve set the Fog to use the eth1 interface, and even then, the default storage was set to eth0.

Tom got that fixed in the trunk.