"Successfully created tasks...", but erros in multicast.log

[rado]

Hi, this is fresh 1.1.2 install (but I’ve had this issue also with 1.1.1) after uninstalling previous (I think it was 0.33) FOG version. Just installed it, imported clients (from ohter, 0.32, install), created image (I’ve older image files - not sure if partclone or partimage version - how can I find it out?), created group (called “cpu”), associated image with clients (through group setting), created multicast task and it said “Successfully created tasks for deployment to the following Hosts” with list of hosts, but there was no udpcast process and in multicast.log I found this:

[CODE]
[06-26-14 9:28:33 am] | Task (1) cpu is new!
[06-26-14 9:28:33 am] | Task (1) /images/cpu image file found.
[06-26-14 9:28:33 am] | Task (1) 16 client(s) found.
[06-26-14 9:28:33 am] | Task (1) cpu sending on base port: 63100
[06-26-14 9:28:33 am] CMD:
[06-26-14 9:28:33 am] | Task (1) cpu failed to start!
[06-26-14 9:28:33 am] | * Don’t panic, check all your settings!
[06-26-14 9:28:33 am] | even if the interface is incorrect the task won’t start.
[06-26-14 9:28:33 am] | If all else fails run the following command and see what it says:
[06-26-14 9:28:33 am] |
[06-26-14 9:28:33 am] | Task (1) cpu has been cleaned.

[06-26-14 9:28:43 am] | Task (2) cpu is new!
[06-26-14 9:28:43 am] | Task (2) /images/cpu image file found.
[06-26-14 9:28:43 am] | Task (2) 23 client(s) found.
[06-26-14 9:28:43 am] | Task (2) cpu sending on base port: 52558
[06-26-14 9:28:43 am] CMD:
[06-26-14 9:28:43 am] | Task (2) cpu failed to start!
[06-26-14 9:28:43 am] | * Don’t panic, check all your settings!
[06-26-14 9:28:43 am] | even if the interface is incorrect the task won’t start.
[06-26-14 9:28:43 am] | If all else fails run the following command and see what it says:
[06-26-14 9:28:43 am] |
[06-26-14 9:28:43 am] | Task (2) cpu has been cleaned.
[06-26-14 9:28:53 am] | Task (3) cpu is new!
[06-26-14 9:28:53 am] | Task (3) /images/cpu image file found.
[06-26-14 9:28:53 am] | Task (3) 24 client(s) found.
[06-26-14 9:28:53 am] | Task (3) cpu sending on base port: 54650
[06-26-14 9:28:53 am] CMD:
[06-26-14 9:28:53 am] | Task (3) cpu failed to start!
[06-26-14 9:28:53 am] | * Don’t panic, check all your settings!
[06-26-14 9:28:53 am] | even if the interface is incorrect the task won’t start.
[06-26-14 9:28:53 am] | If all else fails run the following command and see what it says:
[06-26-14 9:28:53 am] |
[06-26-14 9:28:53 am] | Task (3) cpu has been cleaned.
[06-26-14 9:29:03 am] | Task (4) cpu is new!
[06-26-14 9:29:03 am] | Task (4) /images/cpu image file found.
[06-26-14 9:29:03 am] | Task (4) 22 client(s) found.
[06-26-14 9:29:03 am] | Task (4) cpu sending on base port: 50724
[06-26-14 9:29:03 am] CMD:
[06-26-14 9:29:03 am] | Task (4) cpu failed to start!
[06-26-14 9:29:03 am] | * Don’t panic, check all your settings!
[06-26-14 9:29:03 am] | even if the interface is incorrect the task won’t start.
[06-26-14 9:29:03 am] | If all else fails run the following command and see what it says:
[06-26-14 9:29:03 am] |
[06-26-14 9:29:03 am] | Task (4) cpu has been cleaned.
[06-26-14 9:29:13 am] | Task (5) cpu is new!
[06-26-14 9:29:13 am] | Task (5) /images/cpu image file found.
[06-26-14 9:29:13 am] | Task (5) 3 client(s) found.
[06-26-14 9:29:13 am] | Task (5) cpu sending on base port: 64736
[06-26-14 9:29:13 am] CMD:
[06-26-14 9:29:13 am] | Task (5) cpu failed to start!
[06-26-14 9:29:13 am] | * Don’t panic, check all your settings!
[06-26-14 9:29:13 am] | even if the interface is incorrect the task won’t start.
[06-26-14 9:29:13 am] | If all else fails run the following command and see what it says:
[06-26-14 9:29:13 am] |
[06-26-14 9:29:13 am] | Task (5) cpu has been cleaned.
[/CODE]

Sometimes it doesn’t quit nicely but keeps logging something like this:

[CODE][06-26-14 9:54:34 am] | Task (13) cpu is no longer running.[/CODE]

I had (I think) default value in storage node interface setting - eth0, but changing it (to eth1.212) didn’t help.

Why there is no command in the log and why is it creating multiple tasks and not just 1 like it was in 0.32?

Thanks in advance.

[rado]

Interestingly, I’ve had this same problem with 0.32 FOG - no command on CMD: line in multicast.log, the task automatically deleted immediately after it was created, even it said the task was successfully started… the cause was image type - Single Partition (NTFS) - when I reuploaded the image using Multiple Partition - Single Disk type, the task started successfully and now I’m deploying.

But in 1.1.2 FOG I used older image - Multiple Partition - Single Disk - not Single Partition (NTFS)… I’ll try other image and create fresh new image and see if it helps.

[Tom Elliott]

I’m thinking, more and more, this is related to the OS Type of the image rather than the command itself. it’s unable to find the information based on what’s available.

Going to go out on a limb and say, this is most likely set as Windows 8.1 image? NTFS-Resizable to be specific?

Try changing to the OS Type to just plain jane Windows 8 for that image and try again.

[rado]

No, on 0.32 installation it’s Win XP - this was at first Single Partition (NTFS Only, Resizable) and didn’t work; after reuploading it as Multiple Partition Image - Single Disk (Not Resizable) it works.

On 1.1.2 it’s Win 7 it’s Multiple Partition Image - Single Disk (Not Resizable) and doesn’t work. But it’s older image, made (I think) using FOG 0.33 (or 0.32).

I’m not sure if these both are related but they have the same symptom - missing command in multicast.log.

[rado]

Well, I crated new image and everything seems ok - except it created 4 tasks (with 4 udpcast processes and multicast logs) with 24 clients per udpcast session (one is 13). It’s around 80 computers (all together). Is it ok? And if yes why is it now creating multiple tasks?

And regarding the old image - what could be wrong? I think I read in release info that old images are supported. I’m just asking - I’ve not lot of images, so it’s not much problem for me.

[Tom Elliott]

[quote=“rado, post: 32042, member: 21581”]Well, I crated new image and everything seems ok - except it created 4 tasks (with 4 udpcast processes and multicast logs) with 24 clients per udpcast session (one is 13). It’s around 80 computers (all together). Is it ok? And if yes why is it now creating multiple tasks?

And regarding the old image - what could be wrong? I think I read in release info that old images are supported. I’m just asking - I’ve not lot of images, so it’s not much problem for me.[/quote]

When you created the tasks, did you create 4 separate tasks for the what you needed, or did you have them all in one task and it created 4 separate tasks?

All should be fine, so long as the udp-sender commands are pointing at different ports.

[rado]

I started 1 task for whole group (around 80 clients) and it ended up with 4 (and second time with 5) tasks with the same number of udp-sender processes, logs etc. The tasks had variable number of clients (around 20 in average)…
Last time it ended in a mess - made few tasks (I think 3 or 4) and then it couldn’t find clients or what:

[CODE]
[07-02-14 1:59:50 pm] | Task (20) cpu is new!
[07-02-14 1:59:50 pm] | Task (20) /images/cpunew image file found.
[07-02-14 1:59:50 pm] | Task (20) cpu failed to execute, no clients are included!
[07-02-14 2:00:00 pm] | Task (15) cpu is already running PID 19255
[07-02-14 2:00:00 pm] | Task (16) cpu is already running PID 19448
[07-02-14 2:00:01 pm] | Task (17) cpu is already running PID 19639
[07-02-14 2:00:01 pm] | Task (18) cpu is already running PID 19831
[07-02-14 2:00:01 pm] | Task (19) cpu is already running PID 20015
[07-02-14 2:00:01 pm] | Task (20) cpu is new!
[07-02-14 2:00:01 pm] | Task (20) /images/cpunew image file found.
[07-02-14 2:00:01 pm] | Task (20) 1 client(s) found.
[07-02-14 2:00:01 pm] | Task (20) cpu sending on base port: 62908
[07-02-14 2:00:01 pm] CMD: cat “/images/cpunew/d1p1.img”|/usr/local/sbin/udp-sender --min-receivers 1 --portbase 62908 --interface eth1.212 --full-duplex --ttl 32 --nokbd;cat “/images/cpunew/d1p2.img”|/usr/local/sbin/udp-sender --min-receivers 1 --portbase 62908 --interface eth1.212 --full-duplex --ttl 32 --nokbd;
[07-02-14 2:00:01 pm] | Task (20) cpu has started.
[/CODE]

I don’t know what went wrong - I was testing change of multicast interface, so was changing interface, creating task, looking if it works, killing the task few times until this mess… then I just restarted server, because everything was too slow (which I observe since upgrade to 1.1.1, but I’m not sure if the problem is in FOG or my server)… strange things :)… maybe the creating and killing of tasks made a bit mess in the database or what…

BTW: is this ok? (it’s from code excerpt above):

[CODE]
[07-02-14 2:00:00 pm] | Task (15) cpu is already running PID 19255
[07-02-14 2:00:00 pm] | Task (16) cpu is already running PID 19448
[07-02-14 2:00:01 pm] | Task (17) cpu is already running PID 19639
[07-02-14 2:00:01 pm] | Task (18) cpu is already running PID 19831
[07-02-14 2:00:01 pm] | Task (19) cpu is already running PID 20015
[/CODE]