@tom-elliott Thanks for your attention on my tickets!
The most cryptic one (count= issue) is not solved by sgdisk -z before dd but after. I’m going to add some infos.
Thanks again for FOG: I’ve been using it by 6-7 years. I can multicast deploy a 20 dual boot pc classroom in 30 minutes!
@tom-elliott okay, so i tested it with 50-55 * * * * to check if the “-” is a problem.
The fogscheduler.log found a wake on lan task that should run.
[10-25-17 12:49:52 pm] * Task run time: Wed, 25 Oct 2017 12:49:52 +0200
[10-25-17 12:49:52 pm] * Found a wake on lan task that should run.
[10-25-17 12:49:52 pm] | Task sent to COMPUTER
But keeps on going …
[10-25-17 12:58:52 pm] * Task run time: Wed, 25 Oct 2017 12:58:52 +0200
[10-25-17 1:00:52 pm] * Task run time: Wed, 25 Oct 2017 13:00:52 +0200
[10-25-17 1:00:52 pm] * Found a wake on lan task that should run.
This would confirm that sth. with the “-” is translated to “*” because than it would be * * * * which should mean “At every minute.” That would also explain why it started at minute 49 …
Finally I solved it was because once that you delete the image name, can’t be empty name on the log so, is using the last image name that you use, even if the information is not true.
If you don’t delete any image the log is working ok. If you delete will use the previous name from the last usage. I believe that the best is that the log become in this field as “empty” to not confuse, but it is ok.
@Jim-Graczyk Do you still need assistance on deleting that snapin from the DB? When editing the snapin in the web UI you can see it’s ID in the URL. Note that down and open a terminal on your FOG server:
shell> mysql -u root -p
mysql> use fog;
mysql> DELETE FROM snapinAssoc WHERE saSnapinID = x;
mysql> DELETE FROM snapins WHERE sID = x;
Replace “x” in ... = x; with the ID you noted down earlier.
@tom-elliott Just looking at rom-o-matic 1b67a is the latest release. I’m not in a place right now to see what boot version is in 1.4.4. I can check later tonight. But I would suspect that 1.5.0RC9 will have the fixed version of ipxpe where/when/since ipxe7156.efi was removed from fog.
Sorry about the delay, but I wanted to see more data before responding.
The time zone change resolved a big part of the problem. All the times are now making more sense. I’m guessing the log store UTC because after changing the timezone setting, all Snapin Histories are as they should be - no time shifts.
I can only suppose that to have the times appear as they did originally, the initial time stamps may have been coming from the client. I would suggest this isn’t a good idea since PCs are notoriously out of sync, but these days with SNTP, not so much. One would think it would be desirable to use all time stamps from the server.
So… Thanks very much for pointing that out to me. I once knew timezone was a setting but seem to have forgotten…
To be thorough, I do want to point out something, just to be sure that what I’m seeing is by design.
Attached is a screenshot of the snapin history after a deployment for a machine.
Please note that there are only 5 Start Times for all 17 Snapins. It seems that the start time is only recorded for the first Snapin in a series of snapins executed in one pass of the FOG Service. Given the current report, one can determine the actual start time of a particular Snapin by doing the math (Add the previous snapin’s duration to the posted start time for the task). One can also determine the duration of each individual snapin by subtracting the previous snapin’s duration from the posted snapin duration.
Personally, I’d like to see the snapin start time be the start time for each snapin, not the start time of a group of snapins that just happen to run sequentially. Simialrly, I’d also like to see the duration as the duration of a single snapin, not a group.
If the current approach is by design, then ok. I certainly can live with what we have.