Hi guys, @Wayne-Workman @Tom-Elliott

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.

Thanks.

Hi Tom,

It seems that works fine, shows all tasks and the daemon doesn’t show anormal behavour.

0_1508415265464_Screenshot-2017-10-19 http fog6 lgp ehu es.png

@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; mysql> quit shell>

Replace “x” in ... = x; with the ID you noted down earlier.

@sebastian-roth I don’t know how that happened but I copied the srvpublic.crt from a backup and it is fixed.

Thanks for all the help

@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.

@tom-elliott

Tom,

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.

0_1507741140553_d0a33bc5-87b8-455b-bb7d-f18054867b0e-image.png

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.

Thanks,

Jim

@ch3i Bump?

@tom-elliott Oh Ok… Thanks for the help. Now to just get the PXE working on my local subnet I will be good to go. This is a local network issue. 🙂

Thanks for the help.

Had same problem here, also have some errors on the following accesscontrol plugin

Adding some rules with empty fields says you cannot save (you solve this by entering some stuff and then editing to erase it).

After add some user to a role, It doesn’t show up on the role member section but it is added. If you want to remove some users from a role you need to edit the table RoleUserAssoc).

You cannot hide the accesscontrol menu by the default rules created by the plugin, you need to add it. (Just add it following the other rules).

*Same problem as above about memory size exhausted.

*After enable some plugin, the appareance of the main menu doubles the height size in some sub-menus. (my screen is 1366x768).

I wish i could help fixing there kind of things but just a networking specialist =(. I’m just can report some of the errors I find.

Latest Version: 1.4.4
Latest Development Version: 1.5.0-RC-9
Latest SVN Version: 6078

@wayne-workman said in Boot File Testing for SR:

@george1421 said in Boot File Testing for SR:

@psycholiquid Pssst… to adjust the small font size try this FOS kernel parameter vga=792

vga=792 should be 1024x768x24 video mode, and clean your monitor, please!!! 😛

ref: https://unix.stackexchange.com/questions/71231/grub2-and-kernel-vga-parameter/114980

#wiki worthy

LOL I don’t think you should wiki me having to clean my monitor… LOL I kid.

@Tom-Elliott

I have been keeping an eye out on this issue with replication myself, im running V52 of working branch, should I wait until RC10 to come out to update? So far I think everything is functioning normally for replication but figured I could wait until RC10.

@tom-elliott problem solved, i talked to our firewall admin to free the server from proxy usage, after that i could easily add my pushbullet account and could also simply download the current oui.txt for the mac list.

So i am going to think that something is wrong with group the fog server belongs to on our firewall server because it already was in a group that is free from forced proxy usage (must be some missconfiguration or something).

Bild Text

Regards X23

Solved in working branch. Thanks Tom.

@sebastian-roth I found the error was only in regards to the checkbox. It worked the “first” login entry you make, but the modal window wasn’t closing. So you would press the delete button again, causing the invalid login (as it was at that point invalid as no credentials were being passed anymore).

@THEMCV Please read through this: https://forums.fogproject.org/topic/10279/hostnamechanger

RC9 will have a big changelog 😉

@tom-elliott

Thanks Tom. The two fixes worked, so the image protection and manual add of a host are working.

We still cannot delete any snapins associated with any host, so this isn’t Solved for us. Should I post this issue separately in a different section of the forum? Can you give us any idea what to look at?

Thanks for your help,

Jim

@sebastian-roth I marked it solved as I fixed it in working just didn’t update here.

Fixed in working.

Fixed in working.