Latest FOG 0.33b

Tom Elliott · Apr 22, 2014, 4:23 PM

r1475 released.

Fixes the image size information so it should work properly now especially on multi partition images. Adds the image size and the on server file sizes to the list view. Thanks.

Tom Elliott · Apr 23, 2014, 11:06 AM

r1477 released last night.

Sorry about not updating.

Basically, just some minor changes. There’s now Date checking involved for the deployed/uploaded dates in the image and host pages. If it’s not a valid date (e.g. 0000-00-00 00:00:00) it will report as no data. Cleaned up the columns in the ImageManagementPage so things display a little bit nicer. Hopefully this works for everybody.

Tom Elliott · Apr 23, 2014, 11:23 AM

r1478 released.

Add’s the FOG Client/Prep link to the footer of the page so it’s always accessible.

Tom Elliott · Apr 23, 2014, 11:50 AM

r1479 released.

Add’s deploy date column to Host page.

Bill Arlofski · Apr 23, 2014, 11:58 AM

Tom, I just got my v0.33beta FOG server vm back up and updated. I see the new columns we spoke about for the images (image size etc) Thanks!

I am having an problem getting an imaging task to start.

The issue I am seeing is that when I submit the imaging task, no file gets created in the /tftpboot/pxelinux.cfg directory specific to this host, so it just keeps rebooting due to the imaging task never actually starting, but the task being active in the db.

I checked permissions on the /tftpboot dir and the /tftpboot/pxelinux.cfg dir and both are 755 fog:root

Apache server runs as apache, so I changed the ownership to the apache user and re-tested. Still, no file is created for the host in pxelinux.cfg directory.

Tom Elliott · Apr 23, 2014, 12:01 PM

I’m going to guess that you updated from 0.32 to 0.33?

Did you adjust the options 66/67 so that it points at the undionly.kpxe file?

The /tftpboot/pxelinux.cfg folder is not used in 0.33 anymore. Tasks are generated/checked directly from the database.

I’ll find the post with the changes needed to the FOG settings page so things will work properly for you.

EDIT: Link for what FOG Settings need updating if upgrading from 0.32 to 0.33:
[url]http://fogproject.org/forum/threads/fog-wont-load-past-kernal_thread_helper-0x6-0x10.10319/#post-25466[/url]

Did you clear the original tasks table so as not to cause issues with DEBUG Messages?
From mysql command in the fog database:
[code]truncate table tasks;[/code]

Bill Arlofski · Apr 23, 2014, 12:08 PM

[quote=“Tom Elliott, post: 25885, member: 7271”]I’m going to guess that you updated from 0.32 to 0.33?

Did you adjust the options 66/67 so that it points at the undionly.kpxe file?

The /tftpboot/pxelinux.cfg folder is not used in 0.33 anymore. Tasks are generated/checked directly from the database.

I’ll find the post with the changes needed to the FOG settings page so things will work properly for you.

Did you clear the original tasks table so as not to cause issues with DEBUG Messages?
From mysql command in the fog database:
[code]truncate table tasks;[/code][/quote]

Of course I didn’t follow any of the on-screen instructions when I ran the install.

I saw the dhcp options message and thought to myself “yeah, I already set up my dhcp server next-server option… I’m all set…”

Sorry for the static!

Making modifications now.

Bill Arlofski · Apr 23, 2014, 12:43 PM

Ok… I am new to iPXE and my first interaction does not appear to be a positive one.

My virtual test machine gets the undionly.kpxe from the tftp server, file prints out a few lines, and then hangs.

See image:

[ATTACH=full]672[/ATTACH]

If it matters/helps, my virtual machine is on a proxmox 3.1 server - so the VM is a qemu VM with a virtualized Intel e1000 NIC

[url=“/_imported_xf_attachments/0/672_FOG-iPXE-20140423.png?:”]FOG-iPXE-20140423.png[/url]

Bill Arlofski · Apr 23, 2014, 2:43 PM

OK, I have determined that this does appear to be some type of incompatibility with a Proxmox qemu VM.

My laptop successfully iPXE booted into the new FOG menu with a 400 second countdown to HD boot. Which it then wanted to boot from SAN (which does not exist)

I see in : [url]http://192.168.254.9/fog/service/ipxe/boot.php##params[/url]

that the (default) local boot is defined as:
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU

I alse see (in the web admin interface) where to set the default timeout, but I do not see where to change the sanboot to /dev/sda1 (or whatever that option would need to be)

I would be happy to offer any additional information on my proxmox VM system to help in that regard.

Also, I tried the virtuo and realteck NICs in the VM with no changes to iPXE hanging. Any thoughts on the VM being 64bit vs 32 bit?

Thanks!

Tom Elliott · Apr 23, 2014, 2:58 PM

Bill,

Sanboot is not as you’re thinking it is. On most systems, that particular sequence of lines works great. That line really just tells the system to boot from the hard-drive.

However, there are some known issues where sanboot doesn’t like to operate properly. Most notably with HP and Dell’s. For that, you have to change the sanboot lines to simply say exit and all should work.

Bill Arlofski · Apr 23, 2014, 2:59 PM

wait. ignore the 64bit vs 32bit coment.

Bill Arlofski · Apr 23, 2014, 3:04 PM

[quote=“Tom Elliott, post: 25895, member: 7271”]Bill,

Sanboot is not as you’re thinking it is. On most systems, that particular sequence of lines works great. That line really just tells the system to boot from the hard-drive.

However, there are some known issues where sanboot doesn’t like to operate properly. Most notably with HP and Dell’s. For that, you have to change the sanboot lines to simply say exit and all should work.[/quote]

The laptop in question is an IBM Thinkpad (well, Lenovo).

Where do I modify the sanboot line? I see that the default.ipxe file specifies: [url]http://192.168.254.9/fog/service/ipxe/boot.php[/url]

But that php file creates the boot menu on the fly from a db query based on the host’s MAC address(es).

Tom Elliott · Apr 23, 2014, 3:07 PM

/var/www/fog/lib/fog/BootMenu.php
Lines: 107, 221, and 340

Mr.Myagy · Apr 23, 2014, 4:29 PM

A little bit of help here, please?

installed latest FOG from svn onto ubuntu 14.04.
When trying to network boot from a client, it either works correctly, or says something like:

[CODE]Configuring (net0 00:00:DE:AD:BE:EF)… ok
/default.ipxe… Connection timed out (some ipxe url…)[/CODE]

How can I make it so it boots every time?

Mr.Myagy · Apr 23, 2014, 4:54 PM

Just finished uploading an image, and now I get:

[CODE]* Image uploaded

Task complete!
* FOGFTP: Login failed. Host: 192.168.x.y, Username: fog, Password: 2352489ccf2681c243c44dc8e2b3e852, Error: ftp_login(): Login incorrect.
* FOGFTP: Login failed. Host: 192.168.x.y, Username: fog, Password: 2352489ccf2681c243c44dc8e2b3e852, Error: ftp_login(): Login incorrect.
[…]
[/CODE]

P.S.: I haven’t changed the default password after install. The only steps I performed were: register host, create image, assign image to host, upload image. And now I get the above. Any help?
Please?

Wolfbane8653 · Apr 23, 2014, 4:58 PM

Check your [FONT=Ubuntu][COLOR=#555555]FOG_TFTP_FTP_USERNAME[/COLOR][/FONT] and [FONT=Ubuntu][COLOR=#555555]FOG_TFTP_FTP_PASSWORD[/COLOR][/FONT]. Make sure these are correct.

Jaymes Driver · Apr 23, 2014, 5:23 PM

This post is deleted!

Mr.Myagy · Apr 23, 2014, 5:23 PM

[quote=“Wolfbane8653, post: 25920, member: 3362”]Check your [FONT=Ubuntu][COLOR=#555555]FOG_TFTP_FTP_USERNAME[/COLOR][/FONT] and [FONT=Ubuntu][COLOR=#555555]FOG_TFTP_FTP_PASSWORD[/COLOR][/FONT]. Make sure these are correct.[/quote]

Coming back with the solution, I realised I couldn’t login via telnet localhost 21, using the correct password. After some digging and some pure luck, I found that /etc/passwd didn’t have any login shell for user fog. I added the shell and everything started working

Jaymes Driver · Apr 23, 2014, 5:24 PM

[quote=“Mr.Myagy, post: 25932, member: 23824”]Coming back with the solution, I realised I couldn’t login via telnet localhost 21, using the correct password. After some digging and some pure luck, I found that /etc/passwd didn’t have any login shell for user fog. I added the shell and everything started working :)[/quote]

Glad you got it fixed, which OS are you running FOG on?

I have noticed this issue on Ubuntu 14.04 but haven’t the time to troubleshoot it yet.

Mr.Myagy · Apr 23, 2014, 5:26 PM

[quote=“Jaymes Driver, post: 25933, member: 3582”]Glad you got it fixed, which OS are you running FOG on?

I have noticed this issue on Ubuntu 14.04 but haven’t the time to troubleshoot it yet.[/quote]

Ubuntu as recommended, 14.04 as the latest

Latest FOG 0.33b

222

12.2k

17.3k

155.5k