Display errors on queued computers (Unicast)

[Tom Elliott]

@tian So you have a few other tasks already running. THose messages are correct then.

[Tom Elliott]

Basically No open slots means all slots are taken up. The “There are 0 before me” means once a tasking completes, this host will start.

This timing is reset every 5 minutes or so so sometimes you might see the info shift. It’s all based on timing and how many clients are tasked and queued.

[tian]

@Tom-Elliott There is only one group deployment task running. I just wondered because I’m sure some time ago the output was different.

“There are 0 before me” is displayed for every one of the 6 queued computers now. On earlier fog versions (like 0.32) there has been also messages that 0, 1, 2, 3 … are in front of a computer. So there is no “fixed queue” anymore? (and the queued hosts are picked randomly now?)

Everything else is fine at the moment (pxe, partclone, renaming, active directory, snapins, …) so if this is the normal output now I just have to get used to it.

[Tom Elliott]

@tian Did all 6 show the same message in the first 5 minutes of it “waiting”?

[Tom Elliott]

I feel I need to describe. Beyond the 0 before me also showing.

the i is linux/sql shorthand for minutes. (date(‘Y-m-d H:i:s’))

This is because the m flag is often used by the “month” designator.

I could have the data show a TON more info for you (5 seconds), (2 minutes, 35 seconds), etc…

But it screws up the formatting of the line so I chose to go with the shorthand designations as used by the date command. This is solely there to show you somewhat nicer how long it’s been. I thought about TLA for this, but just went with the single letter for now.

[Wayne Workman]

@Tom-Elliott

A colon would look nicer.
0:5:35 left…

0:2:29 left…

[Tom Elliott]

@Wayne-Workman that’s not a timing to show you how long you have until you get to image
that’s a timing to show how long it’s been waiting.

[tian]

@Tom-Elliott said:

@tian Did all 6 show the same message in the first 5 minutes of it “waiting”?

I just watched the queued computers for 10+ minutes. All of the queued computers show “There are 0 before me” from the very beginning. The number never changes to 1, 2, 3 or sth. else.

Also thanks for the explanation for the time format.

[Wayne Workman]

@Tom-Elliott Well, still, it’d look nicer.

In line for 0:8:23

[Tom Elliott]

All should now be setup properly.

Please update and if you can test with multiples and let me know.

[tian]

@Tom-Elliott I just did a test with version 6971 and it looks different now but still seems not completely correct.
The number in “There are x before me” is counting now, but it displays the same number on all the queued computers again:

• When there are four comupter waiting it is “3” on all waiting computers
• with five computers it is “4” on all waiting computers
• at the end all six queued computers display “There are 5 before me” on all waiting computers
  I waited 10+ minutes again, but the computers didn’t display different numbers.

Here you can see the change of the number (that takes place on all computers) when one more computer is waiting:

[Tom Elliott]

@tian Can you update and try again? I re-adjusted how the counting is to work, in hopes it will work a little better.

[Cpasjuste]

Hi,

Just a little message to say that i do have the same problem with SVN 6975 : i have an “attempting to check in” loop when trying to restore an image. It was working fine before i updated (i don’t remember which version i was previously but it was SVN 69xx).

[Tom Elliott]

@Cpasjuste What do you mean? Pictures please if possible.

[Cpasjuste]

@Tom-Elliott sure, here it is ! So i create a basic task (deploy), then it just loop on the “attempting to check in”. This task did work fine (same machine/image) a few hours ago just before i update to latest git (svn).

[Cpasjuste]

Just a little more information i just found : if i click the “force task to start” button in the “Task Management”, then the deploy task does start. By the way, if you need some testing just send me a mail. I do have a good linux and developement knowledge which may help to debug if needed.

[Tom Elliott]

@Cpasjuste Should be fixed, sorry about that.

[Cpasjuste]

@Tom-Elliott

Thanks and no problem, we know what we sign for when we use the devel branch I’ll update in a few minutes and let you know.
Edit: i confirm that it’s fixed.

[tian]

@Tom-Elliott Thanks for your hard work. Now the numbers are changing and are different. But these are totally mixed up now (Version 6977):


The pictures were taken from different computers.
A lot of times there still are the same numbers to displayed on different computers at the same time (maybe the 5 seconds interval is too huge to see if there are moments with double numbers).

Is there anything else I can provide?

(In fog 0.32 the queued numbers were/are fine - with the difference that there was/is a delay till free slots can be used by queued computers. Now in the recent versions the computers starting up first gets the free slots - but that is ok.)

[Tom Elliott]

@tian While I’m glad we’re closer, I hope to have finally gotten this more properly solved. The checkin process was constantly updating the time which is why you would see the numbers change (depending on the other host checking in).

It should be good now, Hopefully.