Best posts made by tian

@Tom-Elliott @Sebastian-Roth I just did a quick test with svn5107. Right now a deploy task has been running and the hard disk information has been kept. Tomorrow I’ll test some more and report back if there is still something wrong, but it looks like it is OK now.

Thanks everyone for fixing this.

@george1421 this should be the correct solution
We’re also on Ubuntu 16.04 and the fog installer is failing at exactly the same point. After running the commands to alter the root user in mysql the installer runs fine.
I think this problem re-occurs even when just updating the system by apt-get sometimes - so I am running the mysql alter commands every time after apt-get to be on the safe side.

First of all thanks for this great project. We just switched our productive system for the students computer rooms from FOG 0.32 to version 1.4.4 and want to say something about what we experienced. Currently everything is working fine.

• The capturing and deploying is more fast and, at the same time, has a better compression (old: PIGZ_COMP = -6, new: Zstd 12)
• The display of the deploy/capture progress in the web interface is really great
• The new FOG client is reacting more fast after cloning and is saving some additional time
• A date filter for imaging log and snapin log is missing (but it will be added some time later - I asked that in an earlier topic)
• Snapin files once uploaded are now kept and are not deleted when uploading a new file to an existing snapin - (I just will cleanup the snapin directory from time to time manually - think I saw a SQL statement to list the files currently assigned to snapins somewhere in the forums to make it a little bit more easy)

We had a minor problem with the new client:

• The snapins (some batch scrips and sfx-archives) created for FOG 0.32 we could use without problems on 1.4.4 and the new client, except where we used reg.exe to change registry entries: without the parameter “reg:64” the registry entries were written to HKLM\Software\Wow6432Node\abc (In the batch file the path was “HKLM\Software\abc” -> without “Wow6432Node” !). Adding “reg:64” solved that and it also might be better to tell it explicitly to write in the 64bit or the 32bit part.

Something that is also different to FOG 0.32 is the queuing behavior (when unicast group deploying a room):

• In FOG 0.32 there always was was a fixed order which computer was cloned - in the new one its like first come first serve
  – when all computers are starting simultaneously there are more deploying at the same time than allowed in the storage node’s “max clients” option: e.g. 13 are allowed and it has been 14 to 16 for the first deploy batch of a room, the later computers normally will start when it is below 13 again but it can happen that 2 will start at the same time again (depending on the moment they try to check in I think) and it might be 12->14 again
• In FOG 0.32 the text for computers when waiting in the queue displayed the number of computer in before one (based on the fixed order?) - in the new FOG it is different
  – computers that started up with the other computers but didn’t get a free slot always display “0 before me”
  – computers that didn’t start up at beginning (WoL didn’t work, network cable was plugged out, …) are displaying the number of computers deploying plus the number currently queued as computers before one. (e.g. 14 computers deploying, 5 queued = “No open slots, There are 19 before me” for the 20th computer switched on)

The queue behavior describe above is not a problem for us - we just have to get used to it.

Some change between git5221 and git5283 seemed to have solved the hostMAC table problem.

I cant see the increase anymore in git5283. Since the hostname changer service seemed to be related to it I tested the AD join and it still seems to work fine.

I’ll test some more, but it looks good now.

Hi matijn,

did you already try this?:
https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy

We’re not on Ubuntu 18.04 yet and still running 16.04. But every time we update the OS by apt-get (doesn’t matter if upgrade or dist-upgrade) and it contains a SQL update the things described in the link above needs to be done.

If that solves your problem and you have some sort of automatic updates turned on you could think about to deactivate them and run them regularly by yourself.

If that doesn’t solve your problem maybe someone else has another idea.

@Tom-Elliott @Sebastian-Roth sorry for the late reply - I now tested it with git6907 and the display is fine now.

Also thanks for correcting the hard disk related prefixes to binary.

Hi,

I’ve encountered some problems maybe related to the queuing when deploying a group of computers. The groups have a size of 25 and 31 computers and the problem occurs in fog versions 1.5.10.1615 and also 1.5.10.1639.

The problem is that all the computers in the group are starting fine by WoL, booting up PXE an then successfully enter the queue to start imaging but none of them are starting imaging and display:
“There are open slots, but XX before me on this node (in line for yy:yy:yy)”

• XX is a higher number between 18 an 31 as far as I could see. Lower , single digit numbers seem not to be present.
• On the Dashboard the status is like: Free: 0, Queued: 31 (or 25), Active 0
• Under Tasks all the Imaging-Tasks are there and have the Status “Checked in” (Pause symbol)
• in the database table “tasks” there are no other Tasks with the taskStateID 1, 2 or 3 except the 31/25 that should be there
• The Max. Client Size of the (only) main node is set to 13 and has been tried to set to 8 or 10 but no computers started imaging

The “workaround” to get it started is to force 13 computers manually by clicking the lightning button in the active tasks. Then the PCs are starting to get the image. What I could monitor:

• after 13 computers are forced to image the queued comupters display: “No open slots, There are XX before me” with XX now lower numbers stating at around 15 but no lower or single digit numbers as far as I could see
• in the group of 25 computers the last 12 automatically begin to start
• in the group of 31 computers the status after 13 finish is:
  – Free: 0, Queued: 18, Active 0 but no new computers begin to start imaging.
  –After forcing another 3 computers to start, additionally 3 begin to start automatically and the status is: Free: 0, Queued: 12, Active 6.
  – Now the status is Free: 0, Queued: 0, Active 13 (witch seems to be normal)
  – after finishing all the tasks the status will be Free: 13, Queued: 0, Active 0 again

Single computer deplyoment works just fine.

Any Idea what could cause this problem? The version (1.5.10.something - I’ll try to find out the version number) we used before 1.5.10.1615 didn’t have this problem.

Thanks.