When I have experienced the issue in the past I have always found that the phantom hosts added to new groups were only the most recent hosts that were registered. Whether that be 2 hosts or 5 phantoms

Running the SQL maintenance commands from the wiki (as mentioned I think updates also helped) seemed to resolve

Hi,

you will need to use GIT to get to RC builds, see link below. Only final builds are published to sourceforge

https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk#Git

@Fernando-Gietz just got around to checking this, and yes all working with 1.4.0-RC-14

Just set this up, thanks

@falko

SOLVED!!

After trying to download the client I now have the FOG Server set up after getting https://github-cloud.s3.amazonaws.com unblocked by our provider LGFL (along with the below four links from yesterday)

http://downloads.sourceforge.net/project/freeghost/InitList/init.xz
http://downloads.sourceforge.net/project/freeghost/InitList/init_32.xz
http://downloads.sourceforge.net/project/freeghost/KernelList/bzImage
http://downloads.sourceforge.net/project/freeghost/KernelList/bzImage32

Thanks all

EDIT: 2017-05-29

For Client: https://github-production-release-asset-2e65be.s3.amazonaws.com

For Dev/working branches
https://fogproject.org/inits/init.xz
https://fogproject.org/inits/init_32.xz
https://fogproject.org/kernels/bzImage
https://fogproject.org/kernels/bzImage32

@irishfoguser

no, when you upgrade to git trunk you will be on the master branch which is at 1.3.5

to get to 1.4.0 RC1 you would have to checkout the dev-branch

git checkout dev-branch
cd bin
./installfog.sh

Thanks @george1421 I wanted to know if anyone had them and was able to image with FOG. I don’t see it being an issue but we won’t get the test unit until after this coming week

I actually find it relatively fast and simple to spin up a new FOG server.

Use the Turnkey Linux LAMP stack found here. (A headless Debian 8 base, with pre-installed support tools; Webmin, Adminer database management web app, Web based command line terminal)

My quick install notes may be of use for someone

EDIT: It may be worth speaking to the team at TurnkeyLinux.org

when I said we I meant as in my office lol, but that’s great thanks. I shall take a look at this in the week

@george1421 said in Replicating drivers across FOG servers:

@Wayne-Workman said in Replicating drivers across FOG servers:

Two approaches here.

Create a fake image and make its path /images/drivers and setup the fake image so it’s shared with the other servers via groups or whatever way you have the images set up.

This is the option we use. You should also be able to set this “fake image” to disable so someone won’t try to deploy it, but enable replication so the drivers will be sent to the remote fog/storage nodes.

I also use this method

@george1421 @EduardoTSeoane thanks guys, picking up from Kallum here as he is not on site.

In this new Image Build, we are experiencing the same issue as discussed here where it seems the SetupComplete in Windows 10 21H2 runs but does not run as administrator so unable to change service settings.

Is anyone able to confirm this?

we are also experiencing this where it appears the SetupComplete is running but not being run as an Administrator so unable to make changes/start the service as my colleague has experienced. in the post below

https://forums.fogproject.org/topic/16327/windows-10-21h2-fogservice-not-starting/2

@Tom-Elliott Thanks Tom for checking this, I just updated (1.5.7.585) however and still spammed by the success boxes

Hi,

I have updated to Working-1.6 (1.5.7.853)

During Install on setting up and starting nfs server it reports [failed to get unit file state for nfs-server.service no such file or directory] but it does start OK.

As for imaging I am unable to image from the pxe menu

But I can deploy tasks from the web gui & when I do it returns maybe 20 or so success boxes. This issue also happens when on a Host Management page and I click Update (if I changed the image etc.)

Another issue is at the end of when the image is deployed I receive

I also seem unable to export the database from the Save Configuration page

Server is: Debian 8.11 Jessie
Version: Working-1.6 (1.5.7.853)
Kernel: 4.19.64

@Tom-Elliott ok, no worries

Does branch 1.6 not use the 0.11.17 client?

@Sebastian-Roth

Hi,

Server is: Debian 8.11 Jessie

and yes I have jumped to 1.6 and back to Dev-Branch before (everything seemed to work OK, this was a few weeks ago maybe so no Database Upgrade).

This time however I used VM snapshot to roll back (instead of a downgrade), I’m back in work on Friday so I may be able to get more info then

Hi,

Having Issues updating from Dev-Branch 1.5.7.58

1. Updating to latest Dev-Branch = Database failed to update

2. Updating to latest Working-1.6 = NFS Service failure

Have rolled back VM as we are currently imaging some new machines so unable to get any more info right now. but I can try the update again soon hopefully if more info is needed

@Sebastian-Roth said in Anyone in UK have hardware from stone?:

@falko Do you know the specs of the machine yet? Mainboard, disk, network chip?

No not in detail, will hopefully get that info on Monday.

Thanks @george1421 I wanted to know if anyone had them and was able to image with FOG. I don’t see it being an issue but we won’t get the test unit until after this coming week