@Tom-Elliott
Thanks for the quick fix. PXE-Boot is working again now! You are not only a good developer but also rocket-fast

i installed fog 1.5.7 (master-branch) 20 hours ago on a freshly downloaded blank debian 10.1

after correct setup and installatoin i ended up with an ftp-upload-failure (ftp says “wrong username for user fogproject”) after imagecapture.

i checked and saw that linux-user fog cant change passwd. but i can change the password for user fogproject with passwd… tried that and testing now.

really strange. other fog-installatoins worked out of the box…

just checked… there is no user fog after the standard-installation in my linux…!!!

@george1421 thanks for your answer. i will try that.

we used rstp because it is faster than stp. but it seems, its not fast enough for our switches…


Hello there.

I have a Network-Environment with about 200 PCs and 30 24-port Smartswitches. We use Fog in this Network now for over 6 years without any major problems.

A few days ago, we activated RSTP (not STP) on all our Switches because we get Looping when some employees plugin a wrong cable in the wall…

Some machines now seem to hang during the PXE-Boot of fog. Is there any optimization we could make to handle this problem? (all switches can configure RSTP-Settings like “hello time”, “max.age”, and so on.)

@tom-elliott said in FOG, what can and can't it do?:

I feel I must add the primary reason you won’t see a “central repository” for OS images lies down with the very simplistic case of licensing.

If there were a “central” repository, um, can you imagine the legal issues that would no doubt-ably ensue? Managing a repository itself would be extremely difficult, but licensing - especially in commercial OS’s - would be a nightmare.

Ultimately, while it would - from a purely technical standpoint - be possible to create a (very very very) generic set of OS’s that could be used by many, this would not come with your organizations set of software. (Admittedly vague in that you could automate some of the software layout with snapins.) This again is purely technical. Yes, it “could” be done. No, it most likely will not be done.

I could, however, understand central repo for OS’s that don’t require licensing (only one I can think of would be linux though) but even then you’re dealing with one person’s preferences for the layout of the OS vs. what might actually be required and/or more suitable to your environment.

OS-Images - generally available and upgradable with snapins (kinda) is the idea behind docker.com…

@Tom-Elliott
Thanks for the quick fix. PXE-Boot is working again now! You are not only a good developer but also rocket-fast

Server

• FOG Version: 1.3.4-RC1
• OS: Deb 8.6

Client

• Service Version: 11.8
• OS: Win7-SP1

Description

We had similar problems as described in this thread.

After switching to the “working 1.3.4”-branch (and also after switching to the dev-branch today), our fog-clients work fine now again (cheers) but we suddenly get the following error during the pxe-boot:

(i have to admit, that i also installed a few updates on my debian during the update. maybe i bugged a fog-service not to run properly anymore?)

any help with our running system highly appreciated! Thanks for your great work on this project!

@Tom-Elliott thanks for the quick 1.3.4-update. we also had duplicate mac-adresses and the server 500-error and our fog-clients stopped working (on 183 machines here…)
we found a virtualbox-mac and deletet it from the db as you suggested. after the update to 1.3.4 (fogserver reports version “47”), the clients started working again…

BUT…

…now we get an error during the network-boot:
“/fog/service/ipxe/boot.php… input/output error”
chainloading failed…

any suggestins?

I installed a new fog-server with debian 8 (trunk version 6547) and get an error when i try to capture a client.

Everything seems to work fine but in the end, the capture-process starts over and over again. Here is an image of the captured computer, just before the whole thing restarts:

i dont even know, how to stop the capturing-process. in the tast-list, there is no button to stop this.
any ideas what the problem is?

ok guys. first of all… tnx for the quick responses!

dont blame me. i rebooted the machine and tried once more… exactly the same… and it worked !!!

no clue, what happened… but tnx for your replies - u are quicker than a gunshot