Posts made by chad-bisd

review the installfog.sh files and associated scripts to see where the check is failing and maybe why. Other than that, use Ubuntu 10.04 LTS

We appreciate all the work you do!

Fog uses NFS to connect to storage nodes and download images.

Look here for some information regarding pxe/tftp over vpn.

[url]http://fogproject.org/forum/threads/tftp-issues.823/#post-4112[/url]

Please do not post the same quest in multiple forums.

[url]http://fogproject.org/forum/threads/fog-and-site-to-site-vpn.1005/[/url]

In my situtation, the computer (Win 7 Pro 32 bit) is imaged, renamed, and joined to the domain all while connected to the wired network. When windows boots up before or after the domain join, the wireless network card auto connects to the local wireless because the image has the wireless network preconfigured on it and set to automatically connect.

So, by the time I unplug the wired LAN and move the computer, Fog already knows about the wireless MAC and it’s waiting in the host information tab as a pending MAC.

I don’t currently do anything with snap-ins, but I have plans to implement them for some things and it would be nice to know that they’ll work as long as the wireless MAC is approved for each host.

I think the Fog client is a .Net program. On Windows 7, it’s using .Net 3.5 or above. Maybe on older versions of windows it’s using an older version of .Net that is less memory efficient.

The important part of the memory usage is the memory - non-paged pool, because that is memory the Fog client is not able to page out to disk when it’s not in use.

Have you checked /tftpboot/pxelinux.cfg/ to see if any file other than “default” is present?

Also check your MySQL database to see if any tasks are still hung in the database.

If you need to change kernels so you can register hosts, you have to replace the bzImage file in /tftpboot/fog/kernel.

If you need to use a specific kernel for tasks you create or schedule using the Fog WebUI, then you can name it something other than bzImage and specify a custom kernel in the host or group kernel information.

[B]All tasks run from the Fog boot menu use the default bzImage kernel because that is hard coded into the menu file.[/B]

[B][/B]

I think microsoft gives away a free version of it’s .net compiler, like Visual Studio Express or something?

Is there a way to accept all pending MACs at once or do you still have to go host to host to see if it has a pending mac that needs approval?

I have done installs both ways. Fog install basically grabs the latest of each required package using apt-get. So as long as your mostly up to date and not running a conflicting package, it probably won’t matter. Fog install does grab more than just apache, mysql, and php.

You will have to register them with the Fog server before you can multicast to them. There are modifications to Fog which allow multicasting without registration, but those changes are 3rd party and not officially supported.

When you install the Fog client, did you disable all the other features that you don’t use like the screen resolution, user clean, directory cleanup etc?

What model of machines are you trying to image? Are they all the same? If not, have you tried registering different models and gotten the same results? This could be as simple as needing a different kernel.

Fog will overwrite the MBR to setup the partition layout and then lay the data down on the disk. Should not be an issue to overwrite a previous install of another OS. I’m sure there are exceptions, but normally this will not be a problem.

The developers are busy with their paying jobs at the moment and only have minimal time to commit to Fog. Version 0.33 is nearing beta stages, but still unstable.

As for a roadmap, no idea. Generally the community asks for stuff and the developers give what they can when they can.

There are two spots that require the mysql password for a normal 1 server Fog install. 1 is for the Web UI, 1 is for the FogImageReplicator service. The error you are getting is related to the FogImageReplicator service. If you tail the log file, you’ll probably see it when you stop and restart the service.

I don’t know if this will help your issues with the PXE menu options not working, but it may resolve your issue with error in the log file.

To set a quick image password, you have to set a master password. Once you have set the master password, you can edit the passwords for individual tasks. For a normal “Full Host Registration and Inventory” you should NOT need a password unless you’ve set one for the fog.reginput setting in the Web UI.

Are you stuck trying to select a task and getting blocked by a password requirement, or are the tasks scheduling and what you expect to happen is not happening?

[url]http://www.fogproject.org/wiki/index.php/Installation_on_CentOS_5.3[/url]

Looks like there may be some modifications to the install script or package requirements for CentOS installs.

Are you sure nothing else changed?

Did the Fog server get a new IP address when you moved to the new DHCP server?

It seems you are getting/using the text based fog boot menu? Normally after the pxelinux.cfg/default file is loaded, you get the graphical Fog menu, but it looks like you get the text menu with a boot prompt, which times out and then tries to boot from a blank hard drive.