Fog 0.32 on Ubuntu 10.4, looks like computer is imaging but at the end there is nothing on the fog server. On the computer (Win 7), the imaging ends with a series of asterisks in a column. I’ll try another computer today (XP) and see if I have success. Not only did XP not image, it would choke on the PXE boot image. Just in case, I rebuilt the server with a different drive without success. These are machines that all work fine with 0.30.

If it helps at all, I found a web site that builds the answer file in a more “user friendly” mode than the Windows kit. Here’s the link:
[url]http://benosullivan.co.uk/windows-7-unattend-xml-generator/[/url]

So, I rebuild the server with plenty of space, kick off an image upload. I see it running. The process says complete but there is nothing in the /images/folder where the image is supposed to be. The computer currently is displaying an ever increasing column of * (asterisks). Is fog now sending and I must be patient?

Great stuff. We’ll be using Fog for a Win 7 deployment over the summer. What is this sleep? Everyone talks about it, but i can never seem to find any at work. Thanks for your post.

New server running Ubuntu 10.4 LTS with Fog 0.32 for testing. My initial test of an upload last night ended with the computer being imaged had a single asterisk that kept displaying, line after line, and the job status never went beyond Queued. I did witness the following:

PXE boot
Resizing the partition
Imaging with progress bar moving
Certain post imaging activity including resizing

If i look in the /images folder i do not see the image but rather a DEV folder with about 20 GB of stuff in it.

Any thoughts?

Thanks

Addendum. Give me more coffee, dig a hole, and bury me. The upload never completed because the partition was too small and ran out of room. May everyone have a chuckle at my expense.

It’s not exactly what I had hoped i could do, but it’ll get me where I need to go. Thanks!!

Now that I’ve had time to watch the entire video, I have a question. What does the sync process do? Does it make the image files from the storage node accessible to the main server without transferring the actual file?

Thanks,

Steve

I was hoping to be able to use them where they were. I see in the Wiki where you can specify a different nfs server to hold the images but the instructions seem incomplete. Am I correct that I need to establish the /images folder in the other server as a share? How is authentication handled? Thanks for posting.

I built a new fog server, exported / uploaded my hosts table, the issue now are my images. Is it possible to leave the old server and access them from the new server? Or should I copy them across the wire and manually enter them in the table? Can someone guide me as to the most efficient way to handle this?

Thanks.

Let’s see if I’m understanding correctly:

You want the PC, at boot time, to give the user an option to boot normally or re-image the system?

If this is what you want, I don’t believe Fog has that capability. Then again, I admit I am new to Fog myself and it may have capabilities I haven’t explored yet.

2. If I understand your question, you want the pc to re-image every time it boots? My rather limited experience with Fog says it can’t do that but you may want to look at Kimodo Time Machine as it does have the ability to do a system restore on every boot. Microsoft’s Steady State has a disk protect feature that also restores the drive at every boot, but it’s a discontinued product and doesn’t support Windows 7.

Got my Fog up on Centos and everything looks cool, except clients to be imaged don’t load and if you watch closely, there’s an error saying that /sbin/v86d can’t be executed. I browsed the server and sure enough, it’s not there. Do I need to install this from a separate package?

We use Fog here to deploy a variety of images running XP or Win 7 to either single computers or up to 20 at once. We love the intuitive interface, robust performance and the fact that it is so reliable. Good luck to you.

In my continued quest to install 0.32 on CentOS, I find that I am bit confused by the following:

“When you install CentOS do not install any version of PHP instead: Edit the /fog_0.29/lib/redhat/config.sh file and change any reference of “php” to “php53” (this will install PHP-5.3 during the FOG install)”

So, in the following:

packages=“httpd php php-gd php-cli mysql mysql-server php-mysql dhcp tftp-server nfs-utils vsftpd net-tools wget xinetd tar gzip make m4 gcc gcc-c++ htmldoc perl perl-Crypt-PasswdMD5 lftp clamav”;

Does that mean that everywhere php appears above (including php-mysql, etc.) it sould become php53-mysql or does it mean just the php standalone references.

Thanks to all who reply,

Steve

[quote=“Blackout, post: 2155, member: 1”]To fix the timezone issue, edit your php.ini and set the ‘date.timezone’ variable.

The installer does not use ‘php -v’ to check the version, it queries RPM.
Run this for me and post the output:
[code]rpm -q php53[/code][/quote]
Odd, on my base server php -v sez I have version 5.1. If I do an rpm-q php51, it said not installed, BUT if I try rpm -q php it correctly identifies 5.1 as the version. i also noticed that the wiki doc states in the CentOS install that it was tested with 0.30. Has any testing been done with 0.32 and CentOS or am I performing that function.

The plot thickens. it says PHP53 not installed. One of the admins here suggested uninstalling the current PHP first. Or maybe uninstalling and downloading the package from PHP.net instead of using RPM. Thanks for your post

Well, I do have a snapshot of this VM in case I need to go back, but I did proceed with commenting out the command referenced above and rerun installfog.sh. All seemed to go well. i can log in, added / edited hosts, but when I deploy an image, the recipient does boot off the Fog server and loads but seems to hang at a line saying:

kernel_thread_helper. It seems hung at this point. I assume this is not normal? I’ll let it sit a bit to see if it works it’s way past this.

Due to an immediate need, I restored the VM from the snap shot. So, I get to do it all over again. Seems the php upgrade is the key to my upgrade issues. Can anyone offer up a repository or methodology for upgrading php such that my server will pass the test?

if anyone felt a cosmic disturbance in the force, it’s me. i edited install.sh (confession . . I really didn’t have a clue what I was doing) and commented out the line stating confirmPackageInstallation, reran the install and it seems to have successfully completed. The only issue I’ve run into so far is after a reboot, a warning is flooding my concole concerning this line in /opt/fog/service/common/functions.php: return date(“m-d-y g:i:s a”) The warning states that it is not safe to rely on the system’s timezone settings. You are required to use date.timezone setting or the date_default_timezone_set() function. If you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. Help?

The saga continues . . . as a test: Brand new VM running Centos 62. Edited the config.sh per the wiki doc, installed a newer repo than the one in the doc and it still chokes on checking package: php53 …Failed! Seems like I’m making a very basic and simple mistake. Below is the text from config.sh:

Yum packages to install

packages=“httpd php5.3 php5.3-gd php5.3-cli mysql mysql-server php-mysql dhcp tftp-server nfs-utils vsftpd net-tools wget xinetd tar gzip make m4 gcc gcc-c++ htmldoc perl perl-Crypt-PasswdMD5 lftp clamav”;
storageNodePackages=“httpd php5.3 php-cli mysql php-mysql nfs-utils vsftpd xinetd tar gzip make m4 gcc gcc-c++ lftp”; langPackages=“iso-codes”; dhcpname=“dhcp”;

when I do php -v it comes up as version 5.33 should all thos references be 5.33? Should it be 5.3 or just 53?

Thanks again to all who view this and reply.

I see (says the blind man). Looks like the php 53 check failed and the install aborted. Oddly, php -v on the server says 5.3.

So, Here’s what I’ve done:

Started with our existing server which is Red Hat running 0.30. I believe what I needed to do was to first upgrade PHP to 5.3 (done), download and extract fog 0.32 (done) and make the changes to config.sh as described in the installation guide for installing it on CentOS. I did do all that, ran the install script with the following results:

Here are the settings FOG will use:
Distro: Redhat
Installation Type: Normal Server
Server IP Address: 10.40.1.38
DHCP router Address:
DHCP DNS Address:
Interface: eth0
Using FOG DHCP: 0
Internationalization: 0

Are you sure you wish to continue (Y/N) y

Installation Started…

Installing required packages, if this fails
make sure you have an active internet connection.

• Skipping package: httpd (Already Installed)
• Installing package: php53
• Installing package: php53-gd
• Installing package: php53-cli
• Skipping package: mysql (Already Installed)
• Skipping package: mysql-server (Already Installed)
• Installing package: php53-mysql
• Skipping package: tftp-server (Already Installed)
• Skipping package: nfs-utils (Already Installed)
• Skipping package: vsftpd (Already Installed)
• Skipping package: net-tools (Already Installed)
• Skipping package: wget (Already Installed)
• Skipping package: xinetd (Already Installed)
• Skipping package: tar (Already Installed)
• Skipping package: gzip (Already Installed)
• Skipping package: make (Already Installed)
• Skipping package: m4 (Already Installed)
• Skipping package: gcc (Already Installed)
• Skipping package: gcc-c++ (Already Installed)
• Skipping package: htmldoc (Already Installed)
• Skipping package: perl (Already Installed)
• Skipping package: perl-Crypt-PasswdMD5 (Already Installed)
• Skipping package: lftp (Already Installed)
• Skipping package: clamav (Already Installed)

Confirming package installation.

• Checking package: httpd…OK
• Checking package: php53…Failed!

I log into my fog server now and it’s still saying version 0.30. This is obviously a learning experience for me so any guidance is greatly appreciated.

Thanks to all who take time to offer suggestions,

Steve