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

@Tom-Elliott /var/log/apache2/error.log

Hi,

When downloading a kernel I receive the messages as below

Debian 11
Fog: Version 1.6.0-beta.2083

Thanks

@Tom-Elliott me neither!

I have run a search on the server (Debian 11) and it appears I do not have one at all?

@Tom-Elliott It let me install without issue, I have not imaged anything yet

OUTPUT:
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 44827 mountd
100005 1 tcp 44615 mountd
100005 2 udp 53244 mountd
100005 2 tcp 58437 mountd
100005 3 udp 52261 mountd
100005 3 tcp 38371 mountd
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100227 3 tcp 2049
100003 3 udp 2049 nfs
100227 3 udp 2049
100021 1 udp 43652 nlockmgr
100021 3 udp 43652 nlockmgr
100021 4 udp 43652 nlockmgr
100021 1 tcp 44617 nlockmgr
100021 3 tcp 44617 nlockmgr
100021 4 tcp 44617 nlockmgr

@Tom-Elliott thanks Tom, updated

Hi,

When trying to update I receive the error below

I do not have a /etc/nfs.conf file, what should be in it?

!!!
!! The installer was not able to run all the way to the end as !!
!! something has caused it to fail. The following few lines are !!
!! from the error log file which might help us figure out what’s !!
!! wrong. Please add this information when reporting an error. !!
!! As well you might want to take a look at the full error log !!
!! in /root/fogproject/bin/error_logs/fog_error_1.6.0-beta.2082.log !!
!!!

install -d /usr/local/share/man/man1
install -m 644 udp-sender.1 udp-receiver.1 /usr/local/share/man/man1
install -d /usr/local/include/udpcast
install -m 644 rateGovernor.h /usr/local/include/udpcast
sed: can’t read /etc/nfs.conf: No such file or directory

Thanks

@Bristow-0 you may already do this. But you mentioned you clone the vm and not back it up. Would it not be best to run a proxmox backup of the fog server VM to another location like a Nas/share located elsewhere.

@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