@Sebastian-Roth said in Newbe Fog installation issue:
When I did the testing with Ubuntu 18.04 server I ran into the missing universe section issue. Not sure about desktop though.
That is very strange. I didn’t add any repositories to my 18.04 server. I made sure vim and git were installed, and configured SSL the way my setup needs it, that was it. I do fully update the OS before very test run though.
The tests I have going use Ubuntu 18.04 Server, not desktop.
There’s another issue open on github about this very thing I believe: https://github.com/FOGProject/fogproject/issues/261
That guy’s answer was to add the universe repository. I guess Ubuntu desktop 18.04 doesn’t come with that repo enabled by default.
@dseecharran22 This has been a common problem for years for those with managed switches.
Here is a related thread: https://forums.fogproject.org/topic/12393/dhcp-lease-failing/9?page=2
Try to turn off fast-spanning-tree.
Just an update,
You will notice that the link in my signature is different, the one there is the new one.
Long story short, I setup an email server for myself, which caused DNS & ssl problems to arrise with the fogtesting dashboard. So - I moved the site to a t2.nano in AWS. The same VM here at my house is still doing 100% of all testing, but when it gets done it does a quick rsync to the aws box to update the website with the new dashboard & files.
@LaurentB said in I don't see some hosts:
it’s in its basic function that it add the different MAC and that’s the source of my problem…
Can you elaborate on this? Is the MAC that it adds the same every time or different every time? Does the FOG Client see this MAC?
@LaurentB Has anyone suggested figuring out how to create an exception for the FOG Client inside of forticlient? This is going to be what needs done, since you have determined that forticlient is what’s preventing the FOG Client from working.
@LaurentB said in I don't see some hosts:
see the client in my hosts BUT it was offline with the red sign “Connection time out”
Just a comment on that, the red dot just means pings to that host are not working. This does not mean the FOG Client is not working. Often, I have had the red dot and the FOG Client works just fine.
I put in a shebang. It should work now, please re-download the install file.
@Quazz I think when there is not a shebang, the linux terminal interprets it as a bash script. I looked back in the commit history, there has never been a shebang in that script… it’s worked several times. At any rate, I’m going to add it.
@fredlwal The package assumes an internet connection is available during installation because dnsmasq and other things are required for this to work. If they are not installed, it attempts to install them.
@Pere-Pozo-Miro You can learn a lot from this:
https://wiki.fogproject.org/wiki/index.php?title=Replication
@Zerpie What version of fog are you using? I ask because I’m pretty sure late fog versions always run fixparts for you, automatically.
@yrubdarb What branch are you on?
@danuel That’s neat. And appreciated. But, Ubuntu 18 is installing out-of-box for me for 37 days straight now (see my signature).
@george1421 said in Multiple FOG servers in one network:
You will need a way to map the pxe booting computer to a specific fog server.
ISC-DHCP can also do it. You can define a next-server for a specific MAC address, though doing that at scale would royally suck.
@JimmyJ0516 Try to follow this: https://www.cyberciti.biz/tips/linux-send-wake-on-lan-wol-magic-packets.html
You’ll need to install etherwake.
I’m going to try to address this more in-depth when I get home.
@JimmyJ0516 So if the CLI does not work for WOL of some system on your network, then you are having network problems, not fog problems. This is because these CLI commands you’re following do not involve FOG, all they involve is Linux and your network.
@kafluke said in Cannot stop FOG capture:
How do I cancel the process on the remote server?
FOG does not support resizable LVM partitions. The only way to stop it at this point is to reboot. KVM should allow you to force-stop the machine.