Posts made by Junkhacker

Blatantly copied from Tom’s signature:

[SIZE=12px]Basics: Please provide:[/SIZE]
[SIZE=12px]FOG Version (e.g. FOG 0.32, FOG 0.33, FOG 0.01)[/SIZE]
[SIZE=12px]OS Version (e.g. CentOS 6.5, Ubuntu 12.04, Redhat 6.5)[/SIZE]

[SIZE=12px]Have you checked your apache error logs? Can you provide information from these logs?[/SIZE]
[SIZE=12px]Debian based Location (normally)[/SIZE]
[SIZE=12px]/var/log/apache2/error.log[/SIZE]
[SIZE=12px]Redhat based Location (normally)[/SIZE]
[SIZE=12px]/var/log/httpd/error_log[/SIZE]

[SIZE=12px]Have you searched the forums for your issue yet?[/SIZE]
[SIZE=12px]Have you checked the [/SIZE][URL=‘http://fogproject.org/wiki’][SIZE=12px]wiki[/SIZE][/URL][SIZE=12px] yet?[/SIZE]
[SIZE=12px]Kernel Issues: [/SIZE][URL=‘http://fogproject.org/wiki/index.php/FAQ’][SIZE=12px]http://fogproject.org/wiki/index.php/FAQ[/SIZE][/URL]

There is a reason we do not name the undionly.kpxe file pxelinux.0 and it is because they have nothing to do with each other.
If a user sees that the file is named pxelinux.0, then they can assume, or a quick google search will tell them, that it is based on pxelinux of the syslinux project. At that point, they will have a lot of information at their disposal on how it works and how to configure it’s boot menu. All of that information will be wrong for their actual situation.
Keeping the file named undionly.kpxe prevents that confusion and only requires a minor DHCP reconfiguration for people who already have their server set up with pxelinux.0.

not sure if the installer supports entering the IP, but you could just install with default settings with [CODE]setup.exe fog-defaults=true /qb[/CODE] and over write the config file with your customized one. it’s located at [CODE]program files\fog\etc\config.ini[/CODE] on a 32bit machine

just for future reference, the “problem” is that it IS “brand new hardware.” Dell shipped the drive with a GPT windows install, and you have to properly wipe that out in order to image with legacy.

and you’re sure you’ve checked the password here?[ATTACH]718[/ATTACH] and [ATTACH]719[/ATTACH]

[url=“/_imported_xf_attachments/0/718_ftp_settings.png?:”]ftp_settings.png[/url][url=“/_imported_xf_attachments/0/719_storage.png?:”]storage.png[/url]

Blatantly copied from Tom’s signature:

[SIZE=12px]Basics: Please provide:[/SIZE]
[SIZE=12px]FOG Version (e.g. FOG 0.32, FOG 0.33, FOG 0.01)[/SIZE]
[SIZE=12px]OS Version (e.g. CentOS 6.5, Ubuntu 12.04, Redhat 6.5)[/SIZE]

[SIZE=12px]Have you checked your apache error logs? Can you provide information from these logs?[/SIZE]
[SIZE=12px]Debian based Location (normally)[/SIZE]
[SIZE=12px]/var/log/apache2/error.log[/SIZE]
[SIZE=12px]Redhat based Location (normally)[/SIZE]
[SIZE=12px]/var/log/httpd/error_log[/SIZE]

[SIZE=12px]Have you searched the forums for your issue yet?[/SIZE]
[SIZE=12px]Have you checked the [/SIZE][URL=‘http://fogproject.org/wiki’][SIZE=12px]wiki[/SIZE][/URL][SIZE=12px] yet?[/SIZE]
[SIZE=12px]Kernel Issues: [/SIZE][URL=‘http://fogproject.org/wiki/index.php/FAQ’][SIZE=12px]http://fogproject.org/wiki/index.php/FAQ[/SIZE][/URL]

[quote=“Sodden, post: 26670, member: 23191”]I’m running 12.04.4 LTS. Are you doing fresh installs or do you update ? I’ve done several updates maybe something broke along the way.[/quote]

I’ve been doing updates on top of updates on top of updates.
i tend to keep up to date with releases to help debug.

downloads of partimage format images are supported for backward compatibility, but all uploads are done in partclone format. partclone uploads can be sped up by reducing the compression level on the settings page.

if anyone still wanted this, here’s how you get it. add this file to your web-root/fog/lib/hooks folder
Most of the credit goes to Tom and Rowlett on this one.

[url=“/_imported_xf_attachments/0/714_AddHostSerial.hook.php?:”]AddHostSerial.hook.php[/url]

does your DHCP server need to be reset before changes apply?

[url]http://fogproject.org/wiki/index.php/Restoring_FOG_from_Backup[/url]
and [url]http://fogproject.org/wiki/index.php/Backing_up_FOG[/url]
added to the knowledge base how to guide section

this information pertains to fog 0.32
if you are using fog 1.0 (or fog 0.33b) the setting is changed on the configuration page under boot settings

have you tried setting the option 66 to the ip instead of the name?

i am running Ubuntu server 12.04 LTS with pam_service_name=vsftpd and no problems

you must create an image “profile” on the image management page. this profile tells fog where to store an image when it is saved, what kind of image it is, and allows you to assign that information to hosts for download. I suggest you create one named “default” and assign it to all of your hosts, for now. an image must be assigned to hosts before tasks can be scheduled.

a bunch of people liked those, so i’ll give you one more just to show more with ipxe

[CODE]
:MENU
menu
item --gap – ---------------- iPXE boot menu ----------------
item ipxedemo ipxe online boot demo
item shell ipxe shell
item return return to previous menu
item hostinfo details about this computer
choose --default return --timeout 5000 target && goto ${target}

:ipxedemo
chain http://boot.ipxe.org/demo/boot.php ||
goto MENU

:shell
shell ||
goto MENU

:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU

:hostinfo
echo This computer : ||
echo MAC address…${net0/mac} ||
echo IP address…${ip} ||
echo Netmask…${netmask} ||
echo Serial…${serial} ||
echo Asset number…${asset} ||
echo Manufacturer…${manufacturer} ||
echo Product…${product} ||
echo BIOS platform…${platform} ||
echo ||
echo press any key to return to Menu ||
prompt
goto MENU

autoboot
[/CODE]

here is an example of a menu for loading WinPE based ISO disks from a folder named ISO in the root of the web server
[CODE]:MENU
menu
item --gap – ---------------- iPXE boot menu ----------------
item WIN7PE64BIT Boot Windows 7 64 bit iso
item WIN7PE32BIT Boot Windows 7 32 bit iso
item shell ipxe shell
item return return to previous menu
choose --default WIN7PE64BIT --timeout 5000 target && goto ${target}

:WIN7PE64BIT
initrd http://${fog-ip}/ISO/Win7PE_x64.ISO
chain memdisk iso raw ||
goto MENU

:WIN7PE32BIT
initrd http://${fog-ip}/ISO/Win7PE_x86.ISO
chain memdisk iso raw ||
goto MENU

:ipxedemo
chain http://boot.ipxe.org/demo/boot.php ||
goto MENU

:shell
shell ||
goto MENU

:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU

autoboot[/CODE]

i feel i should point out that yesterday Tom and I came up with an idea and added it to the advanced.php file.
[CODE]print “set fog-ip “.$FOGCore->getSetting(‘FOG_WEB_HOST’).”\n”;
print “set fog-webroot “.basename($FOGCore->getSetting(‘FOG_WEB_ROOT’)).”\n”;
[/CODE]
have been added so that you may use the ipxe variables “fog-ip” and “fog-webroot” for the creation of menus. here is a usable example that you should be able to paste into your advanced menu setting field without modification.
[CODE]:MENU
menu
item --gap – ---------------- iPXE boot menu ----------------
item ipxedemo ipxe online boot demo
item shell ipxe shell
item return return to previous menu
choose --default return --timeout 5000 target && goto ${target}

:ipxedemo
chain http://boot.ipxe.org/demo/boot.php ||
goto MENU

:shell
shell ||
goto MENU

:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU

autoboot[/CODE]

ubuntu 14.04 is quite new and we’re still finding all it’s little quirks. the install is very smooth on most of the prior releases of ubuntu and a few other distros, requiring only the edit to the single config file for the sql password.

regarding the earlier question of speeding up the uploads, if you lower the FOG_PIGZ_COMP it can go much faster at the cost of a little more disk space.

and yes, there are probably more appropriate threads to post any other issues at this point