@andythemayor Lol, my bad. I thought you were OP. I didn’t read…

Also, changing the memory to 256 resolved the issue, thanks for the help!

I am having this issue with 1.5.2

Just throwing this out there, might absolutely not be related and me just missunderstanding whats actually happening here.

I had problems Imaging a computer at point when switching from a hdd machine as image-source to an ssd.

I had to change the host primary disk to the correct one - I think from sda to sda2 or something along those lines - for this to work.

Rereading again I suppose this is in another direction, but just in case.

A pending host is a host with the FOG Client installed that is not registered in your FOG Server.
That FOG Client is calling home to your FOG Server and is added as a pending host - because it is unknown and therefore untrusted until you (the admin) claim it. Claiming is basically saying ‘Yes, that’s one of ours, trust it’

This was made aware a while ago and has been addressed in the github working branch which will become 1.5.3.

@wayne-workman
That worked!

Legend - exactly what I needed.
Nodes are visible and I can continue the project 😄

Where do I mark this as solved and buy you a virtual beer!

@george1421 I had downloaded the 6077 again and not 6078 🙂
END USER ERROR 🙂

@julianh said in Ubuntu upgrade to 16.04.4 LTS kills Fog:

I have a dedicated fog Server that was somewhat expensive with its SSD arrays, so I can’t migrate to a new box, I can’t afford it.

You could migrate to a VM first - then from the VM back to the nice hardware. Keep the VM as a spare - but first use the VM and ensure everything is correct and working - and imaging.

@adowns Seems like it is the same issue i’m having.

I’ve detailed in the topic I raised how I get this to ‘work’ for a small number of machines, but I would not call it a fix by any stretch of the imagination.

There is definately an underlying issue, and Tom is aware.

Please see https://forums.fogproject.org/topic/11799/1-5-2-on-debian-multicast-session

@tom-elliott said in Change menu boot order:

So ordering becomes problematic as the all hosts items show in either the non reg or reg hosts. So priority should go where? Should non reg hosts be displayed before or after all host items. Or vice versa? Similarly for reg hosts. Or should we just do it based on numbers.

I looked into this a bit then got lost how fog imported the pxeMenu table. I was hoping it was a sql query to where I could just add a new integer field to the table as display order. Then use a sql statement like
select * from pxeMenu order by pxeOrder asc, pxeID asc That would allow pxeOrder to override pxeID if set, otherwise pxeID indexing would work the same as it does now. You could default pxeOrder to 0 so the pxeMenu would work as it does today and then let the FOG Admin mix up the menu. But alas I could not pull it off, but it was the plan.

@vince-villarreal that’s the hope and those lines are added specifically so you can track the status more appropriately.

@tom-elliott That’s also at the very-tip-top of the ftp troubleshooting article, too. Saying that the problem is usually credentials, so go look at that first.

Also, this is the only FAQ that I could find (that I didn’t even know existed until now): https://wiki.fogproject.org/wiki/index.php?title=FAQ but there is no mention of FTP in there. I think that page should just be deleted since this information is covered in other places.

Turns out the error was related to DeepFreeze. A program that we use to prevent users from making changes to the public use computers in our Library.

The issue was resolved by opening the DeepFreeze console on the machine I was capturing from and clicking the button “Set Clone Flag”. This prepares the system for imaging and allows the hard disk partitions to be resized. After doing this step our deployments have all gone smoothly.

Thank you for all the help. Even though my issue was not FOG related. Hopefully our troubleshooting can help someone else down the road.

hello,
I couldn’t find a solution to unlock my situation, I tried many things on promox and on fog, without succes again. So I decided to start a new install on another post, separated from the proxmox and it’s working fine. I think I’ll keep this solution so, thanks for your help and sorry to leave an unsolved issue, see you later !

OK, got it.
This show and hide window confuse me a bit.
Thanks
Regards

I’m going to gues this is happening with kernel version 4.16.6? I ask because I found earlier the kernel architectures were backward. I’ve corrected this on the server, so you should be able to redownload the kernels and have success.