Latest FOG 0.33b
-
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] -
[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]<facepalm>
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.
-
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]
-
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 MENUI 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!
-
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.
-
wait. ignore the 64bit vs 32bit coment.
-
[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).
-
/var/www/fog/lib/fog/BootMenu.php
Lines: 107, 221, and 340 -
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?
-
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? - Task complete!
-
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.
-
This post is deleted! -
[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
-
[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.
-
[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
-
[quote=“Mr.Myagy, post: 25935, member: 23824”]Ubuntu as recommended, 14.04 as the latest :D[/quote]
Actually, 14.04 isn’t supported as of yet, it was only released 6 days ago, I am working to try to find the pieces the need to be doctored to work with FOG, but my solid recommendation is Ubuntu 10.04-13.10
-
I managed to create a Windows 8 image, but the second computer loads PartClone, but only displays the first 2 lines on it, then hangs (for quite some time now…). No loading bar, no nothing. last line is: Starting to restore image (-) to device (/dev/sda1)
I switched to PartImage and I only get a (very) blue screen with “Please wait…”. Nothing happens.Any help would be greatly appreciated as I’ve already lost 10 hours of today trying to do this (fog 0.32 and now fog 0.33).
-
r1480 released.
Adds an option to the pxe menu in fog configuration to change the Type from exit or sanboot.
-
r1481 released.
With this comes a few changes/tweaks to make things that little bit more user friendly.
The ipxe boot menu now has a gap between where it tells you it’s registered or not and the actual menu items.
The ! at the end of the registered host is now removed.
Host/Group Management pages have changed title’s of Deploy/Upload to Download/Upload. Deploy, in my eyes, means to Send the tasking, where Download/Upload/etc… are the actual jobs they’re performing (e.g. Uploading from client to server, Downloading from server to client.)
blame.php now longer tries to reference the Functions class as it doesn’t exist anyway.
Fog Client link should work properly now.
Should allow for Hooks to be unregistered now if needed. (haven’t tested and don’t know anything about it.)
Hopefully you all enjoy, thanks.
-
As of release 1483 these steps are no longer required.
[S]Ubuntu 14.04 error with ftp confirmed.[/S]
[S][CODE]* Image uploaded[/S]
[S]* Task complete![/S]
[S] * FOGFTP: Login failed. Host: 192.168.x.y, Username: fog, Password: 2352489ccf2681c243c44dc8e2b3e852, Error: ftp_login(): Login incorrect.[/S]
[S] * FOGFTP: Login failed. Host: 192.168.x.y, Username: fog, Password: 2352489ccf2681c243c44dc8e2b3e852, Error: ftp_login(): Login incorrect.[/S]
[S][…][/S]
[S][/CODE][/S][S]The fix is to edit the /etc/passwd file[/S]
[S][code][/S]
[S]sudo gedit /etc/passwd[/S]
[S][/code][/S][S]Edit the bottom line to look like the following[/S]
[S][code][/S]
[S]fog
1001:1001::/home/fog:/bin/bash[/S]
[S][/code][/S][S]Save and reboot, all should be well.[/S]
