here it comes again 
now, i have a log file that your script created and i think this is not the usual situation. here is what happened now:
task was deploying and DURING that task the host data was updated with new mac address (i am aware that it is not best usage 
it was not me)
so i have the log, where to put it? mail maybe? it has many info about our setup, maybe not best to have it on a forum ,) let me know how to share with it with you.
Hi!
Are we coming close to stable release? Or is it far, needs more time to polish? 
Oh, i see. I will inform you if file is appearing.
No, not yet. During weekend we do nothing, and we have a pulsating imaging. As we change pcs we create new imaging waves 
trust me, it will happen. (Why post is solved?)
And again, impressive response time! Thanks again ok, i do preparation and wait fo the rabbit to jump out its nest. If i understand well, if a log appears it found something. Lets wait and hope. i will report back on next hit. (anyway you gave me good ideas on how to do some things for myself as i read through your script, nice work!)
Ok, just take your time. I am glad that you guys are so responsive in all ways of user interaction! I dont even get the clue about that moron on forum claiming that fogproject is dead… We should thank your work, not complain in such nonsense way.
@wayne-workman i am open for any idea. Issue is same on my end, i can fix it with previous methods you mention.
Guys, I know this topic is old, but i dont want to create a new topic as my issue now is the exact same as was in this topic. We here had solution to “fix database” with this issue, and i strongly hoped that the problem is only cos of some twisted database issue somehow, but now i again has it happening.
ATM, server is current uptodate 1.4.4, server os is debian 9.3, database is practically totally new (i kept only 2-3 image from old installation to make a new and flawless db. And colleagues report that host time-to-time disappeare from database.
As i has now key to find and eliminate it, i can solve this, but… god, it is so frustrating that i cant see the true reason for such. Issue is still same method as for creation: “dummy host” has mac, it gets deployed. new machine comes in, the original dummy is updated with new mac, deploying again. And on the mac update the host disappears sometimes! (mac is literally overwritten with new, which makes prev mac to be secondary or what? in host/mac pairing i see the new machine has the actual mac in db, but it has no primary mac. And as it has only 1 mac, it is “a host without mac” (as i cannot register a host without a mac, maybe gui wont display such hosts).
We previously cooperated in this matter, maybe with this post it can be continued towards a solution I hope at least.
Oh, good point. We do tests on it. As testing i did reset, not cold start. Will check and report.
@george1421 ok, sorry. i try to be more clear.
as it was suggested, i tried to use other exit type to see what is a working solution. it came out that grub is ok for that host (i did many test to see). we sat back and enjoy. a later time my colleague reported that problem is there again (actually i was no investigating personally as he was the same guy who reported it first, so i trusted his eyes to see it or not
i sent him back to make test restarts and it worked ok during tests. but if it worked on tests what may cause the random stuck, like on first ocasion? here we have a saying like “at dentists office no tooth hurts”. so when i am standing there and see restart test it is ok, but when my back is turned it stucks. ofc not all time, as i would kick that pc away to trash. but sometimes.
we will wait a few days to see if it is there or not again (btw it can still be a failing buggy bios)
we have something strange. the pc with the bootup issue produced same error, stuck at “boot from sandivice”, even when it is set to grub exit type. when we saw it, we did couple of restarts to reveal something, but all time it was booting ok. so, if it is not being inspected, it produced error.
anyone can guess what happens? if i did change exit type to and fro it does its things as expected. on “failtype” it fails, on “succestype” it succeeds. strange.
@george1421 it is not a problem at all, as we… well, never ever used fog client on pcs. we do use fog to replicate and deploy installed pcs.
Test was ok, the machine in question successfully continued boot with bios exit type set to grub. Thanks for the option we have in fog, as with older versions i guess it would be a full stop with those bios (btw manufacturer does not provide working solution for that)
ah, sounds nice! ok, will go to see what exit type works for that bugged crap thanks for help (btw do you happen to have performance statistic about how much speed reduction may come if all host (like 2k of host) are registered?)
Does it mean if i make a host registration (mac, os, anything) and i specify the exittype to anything other than default, it will boot and exit with that setting, not the fog system default, even if i give no task for that host? This is the true question, i can play with exit types, but i cant have set all host to the same exittype for testing
hello guys!
We just found a disturbing issue. Lab PCs are set to have boot order starting with pxe boot normally, then chained back to hdd. Here came the problem. We just discovered that some of the PCs are stuck at this point:
After a bit of investigations we found out that the fail and the success turns on the bios versions of the motherboards.
fail and stuck:
MB model: H61M-DS2
Bios vers: F9
Bios date: 2013.04.17.
BIOS id: 8a01ag07
success:
MB model: H61M-DS2
Bios vers: F9
Bios date: 2011.12.21.
BIOS id: 8a01ag07
I think it is something with bios exit type (general default is sanboot). Host is not regged in fog database (veryvery few pcs are perma regged) as the have tasks only at cloning. What can be the solution here? To set general exit type other from sanboot may result in inverted, but still existing problem, maybe a lot more issued computer.
What if i register pc but give zero task. Will the "host specific exittype work? or is it only applied at end of task?
Downgrading the bios in mass is ofc not an option too and i guess pc manufacturers wont give us a few new bios just for this.
Server type is 1.4.4., on debian 9.3…
Seems now all goes as wanted. THX a lot for help (can i mark my topic as solved somehow? in old forum i knew the way for it i guess, but not now)
Bah, imaging was ok, but that mistake i made somehow still lingers on. I know that I may correct it with full reinstall, but i think i learn more if i know more piece of the mechanism. Can you maybe take a look at this error i got?
anyway can i have rights to delete my own post? i need more coffee, i edited, reedited my prev post, then i wanted to purge it but with no rights)
@Sebastian-Roth
thanks a lot, following your guidelines i found the problematic part of config (actually i made mistakes then correcting too more steps than i previously tought (ip of server was the key, which was mistakeingly entered during the tries of installation tests.
now it is testing imaging (bah, finally i can start the true test for making hybrid bios/uefi combos work automatically; and selecting proper win10 image types.)