I am getting the same error when attempting a fresh install.
OS: Ubuntu 15.10
I have included the contents of the error_log below.

/usr/bin/lsb_release
/bin/systemctl
grep: /opt/fog/.fogsettings: No such file or directory
Reading package lists…
Building dependency tree…
Reading state information…
software-properties-common is already the newest version.
Suggested packages:
libcurl4-gnutls-dev python-pycurl-dbg python-pycurl-doc
The following NEW packages will be installed:
python-pycurl python-software-properties
0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B/55.9 kB of archives.
After this operation, 286 kB of additional disk space will be used.
dpkg: error: need an action option

Type dpkg --help for help about installing and deinstalling packages [*];
Use ‘apt’ or ‘aptitude’ for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked [*] produce a lot of output - pipe it through ‘less’ or ‘more’ !
E: Sub-process /usr/bin/dpkg returned an error code (2)
…/lib/common/functions.sh: line 488: ntpdate: command not found
gpg: keyring /tmp/tmp2v8x09lx/secring.gpg' created gpg: keyring /tmp/tmp2v8x09lx/pubring.gpg’ created
gpg: requesting key E5267A6C from hkp server keyserver.ubuntu.com
gpg: /tmp/tmp2v8x09lx/trustdb.gpg: trustdb created
gpg: key E5267A6C: public key “Launchpad PPA for Ondřej Surý” imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
OK
Hit http://us.archive.ubuntu.com wily InRelease
Hit http://security.ubuntu.com wily-security InRelease
Hit http://ppa.launchpad.net wily InRelease
Hit http://us.archive.ubuntu.com wily-updates InRelease
Hit http://us.archive.ubuntu.com wily-backports InRelease
Hit http://security.ubuntu.com wily-security/main Sources
Hit http://ppa.launchpad.net wily/main amd64 Packages
Hit http://us.archive.ubuntu.com wily/main Sources
Hit http://us.archive.ubuntu.com wily/restricted Sources
Hit http://security.ubuntu.com wily-security/restricted Sources
Hit http://ppa.launchpad.net wily/main i386 Packages
Hit http://us.archive.ubuntu.com wily/universe Sources
Hit http://security.ubuntu.com wily-security/universe Sources
Hit http://us.archive.ubuntu.com wily/multiverse Sources
Hit http://ppa.launchpad.net wily/main Translation-en
Hit http://us.archive.ubuntu.com wily/main amd64 Packages
Hit http://security.ubuntu.com wily-security/multiverse Sources
Hit http://us.archive.ubuntu.com wily/restricted amd64 Packages
Hit http://us.archive.ubuntu.com wily/universe amd64 Packages
Hit http://security.ubuntu.com wily-security/main amd64 Packages
Hit http://us.archive.ubuntu.com wily/multiverse amd64 Packages
Hit http://us.archive.ubuntu.com wily/main i386 Packages
Hit http://security.ubuntu.com wily-security/restricted amd64 Packages
Hit http://us.archive.ubuntu.com wily/restricted i386 Packages
Hit http://security.ubuntu.com wily-security/universe amd64 Packages
Hit http://us.archive.ubuntu.com wily/universe i386 Packages
Hit http://us.archive.ubuntu.com wily/multiverse i386 Packages
Hit http://security.ubuntu.com wily-security/multiverse amd64 Packages
Hit http://us.archive.ubuntu.com wily/main Translation-en
Hit http://us.archive.ubuntu.com wily/multiverse Translation-en
Hit http://security.ubuntu.com wily-security/main i386 Packages
Hit http://us.archive.ubuntu.com wily/restricted Translation-en
Hit http://security.ubuntu.com wily-security/restricted i386 Packages
Hit http://security.ubuntu.com wily-security/universe i386 Packages
Hit http://us.archive.ubuntu.com wily/universe Translation-en
Hit http://us.archive.ubuntu.com wily-updates/main Sources
Hit http://security.ubuntu.com wily-security/multiverse i386 Packages
Hit http://us.archive.ubuntu.com wily-updates/restricted Sources
Hit http://us.archive.ubuntu.com wily-updates/universe Sources
Hit http://security.ubuntu.com wily-security/main Translation-en
Hit http://us.archive.ubuntu.com wily-updates/multiverse Sources
Hit http://security.ubuntu.com wily-security/multiverse Translation-en
Hit http://us.archive.ubuntu.com wily-updates/main amd64 Packages
Hit http://us.archive.ubuntu.com wily-updates/restricted amd64 Packages
Hit http://security.ubuntu.com wily-security/restricted Translation-en
Hit http://us.archive.ubuntu.com wily-updates/universe amd64 Packages
Hit http://security.ubuntu.com wily-security/universe Translation-en
Hit http://us.archive.ubuntu.com wily-updates/multiverse amd64 Packages
Hit http://us.archive.ubuntu.com wily-updates/main i386 Packages
Hit http://us.archive.ubuntu.com wily-updates/restricted i386 Packages
Hit http://us.archive.ubuntu.com wily-updates/universe i386 Packages
Hit http://us.archive.ubuntu.com wily-updates/multiverse i386 Packages
Hit http://us.archive.ubuntu.com wily-updates/main Translation-en
Hit http://us.archive.ubuntu.com wily-updates/multiverse Translation-en
Hit http://us.archive.ubuntu.com wily-updates/restricted Translation-en
Hit http://us.archive.ubuntu.com wily-updates/universe Translation-en
Hit http://us.archive.ubuntu.com wily-backports/main Sources
Hit http://us.archive.ubuntu.com wily-backports/restricted Sources
Hit http://us.archive.ubuntu.com wily-backports/universe Sources
Hit http://us.archive.ubuntu.com wily-backports/multiverse Sources
Hit http://us.archive.ubuntu.com wily-backports/main amd64 Packages
Hit http://us.archive.ubuntu.com wily-backports/restricted amd64 Packages
Hit http://us.archive.ubuntu.com wily-backports/universe amd64 Packages
Hit http://us.archive.ubuntu.com wily-backports/multiverse amd64 Packages
Hit http://us.archive.ubuntu.com wily-backports/main i386 Packages
Hit http://us.archive.ubuntu.com wily-backports/restricted i386 Packages
Hit http://us.archive.ubuntu.com wily-backports/universe i386 Packages
Hit http://us.archive.ubuntu.com wily-backports/multiverse i386 Packages
Hit http://us.archive.ubuntu.com wily-backports/main Translation-en
Hit http://us.archive.ubuntu.com wily-backports/multiverse Translation-en
Hit http://us.archive.ubuntu.com wily-backports/restricted Translation-en
Hit http://us.archive.ubuntu.com wily-backports/universe Translation-en
Reading package lists…
ii apache2 2.4.18-1+deb.sury.org~wily+2 amd64 Apache HTTP Server
ii php5 5.6.18+dfsg-1+deb.sury.org~wily+1 all server-side, HTML-embedded scripting language (metapackage)
php5-json
ii php5-json 1.3.9-1+deb.sury.org~wily+4 amd64 JSON module for php5
ii php5-gd 5.6.18+dfsg-1+deb.sury.org~wily+1 amd64 GD module for php5
ii php5-cli 5.6.18+dfsg-1+deb.sury.org~wily+1 amd64 command-line interpreter for the php5 scripting language
ii php5-curl 5.6.18+dfsg-1+deb.sury.org~wily+1 amd64 CURL module for php5
mysql-server-core-5.6
mysql-server-5.6
mysql-server
ii mysql-server 5.6.28-0ubuntu0.15.10.1 all MySQL database server (metapackage depending on the latest version)
ii mysql-client 5.6.28-0ubuntu0.15.10.1 all MySQL database client (metapackage depending on the latest version)
ii tftpd-hpa 5.2+20140608-3ubuntu1 amd64 HPA’s tftp server
ii tftp-hpa 5.2+20140608-3ubuntu1 amd64 HPA’s tftp client
ii nfs-kernel-server 1:1.2.8-9ubuntu10 amd64 support for NFS kernel server
ii vsftpd 3.0.2-20ubuntu1 amd64 lightweight, efficient FTP server written for security
ii net-tools 1.60-26ubuntu1 amd64 NET-3 networking toolkit
ii wget 1.16.1-1ubuntu1 amd64 retrieves files from the web
ii xinetd 1:2.3.15-4 amd64 replacement for inetd with many enhancements
ii sysv-rc-conf 0.99-7 all SysV init runlevel configuration tool for the terminal
ii tar 1.27.1-2 amd64 GNU version of the tar archiving utility
ii gzip 1.6-4ubuntu1 amd64 GNU compression utilities
ii build-essential 12.1ubuntu2 amd64 Informational list of build-essential packages
ii cpp 4:5.2.1-3ubuntu1 amd64 GNU C preprocessor (cpp)
ii gcc 4:5.2.1-3ubuntu1 amd64 GNU C compiler
ii g++ 4:5.2.1-3ubuntu1 amd64 GNU C++ compiler
ii m4 1.4.17-4 amd64 macro processing language
ii htmldoc 1.8.27-8ubuntu1 amd64 HTML processor that generates indexed HTML, PS, and PDF
ii lftp 4.6.3a-1 amd64 Sophisticated command-line FTP/HTTP/BitTorrent client programs
ii openssh-server 1:6.9p1-2ubuntu0.1 amd64 secure shell (SSH) server, for secure access from remote machines
dpkg-query: no packages found matching php5-gettext
Reading package lists…
Building dependency tree…
Reading state information…
E: Unable to locate package php5-gettext

Compiling your own rom allows you to embed scripting for things like chainloading.
Additionally the ipxe.iso provided by ipxe.org does not support the [B]colour [/B]command which will cause the boot.php to fail

Removing bg.png allowed the menu appear but upon selecting Quick Registration the bzImage32 hung around 78%. Really feels like my compile options on rom-o-matic.eu are simply off. Anyone else use this website?

Yes I’m able to view the graphic from within the [B]Green [/B]zone as well. Spun up a VM inside the firewall and was able to view the graphic as well. I’m beginning to wonder if my compile options are not set correctly on the rom-o-matic.eu site. I thought for sure I check PNG support. In the meantime I’ll comment out the bg.png line in BootMenu.class.php to see if I get further.
[ATTACH]1968[/ATTACH]

[url=“/_imported_xf_attachments/1/1968_CaptureInsideFogNetwork.PNG?:”]CaptureInsideFogNetwork.PNG[/url]

Absolutely I can. Spun up a SliTaz VM hit the URL to see the PNG and viola…
The timeout issue is specific to an iPXE host [B]outside [/B]the FOG Network as my previous post showed an internal client connected fine and displayed the background.

[ATTACH]1967[/ATTACH]

[url=“/_imported_xf_attachments/1/1967_Capture.PNG?:”]Capture.PNG[/url]

No, but it’s farther along that my initial attempt. At first it was hanging on the boot file, which has since been resolved.
The fact that it makes it through the firewall, parses the boot.php file fine and times out on loading bg.png led me to believe that the iPXE iso I generated from rom-o-matic.eu did not support png. I went through again and verified and it’s still getting stuck on passing the bg.png file. Perhaps the timeout setting is too low. If so I don’t know where to change it. I know it’s not the FOG_PXE_MENU_TIMEOUT setting as I’ve changed that with no effect. Any ideas?

First and foremost I’m using VirtualBox for all machines mentioned in this thread. The issue I’m having is that [B]only[/B] iPXE machines outside the Fog Server network are timing out. Based on the output, I successfully connect to the server, parse the boot.php file and when trying to transfer the bg.png poof connection timed out

I’ve included a simplistic graphic of my setup. If anyone could provide insight it would be greatly appreciated.
[IMG]https://www.dropbox.com/s/3tbkwqm7fm10jin/iPXE.png?dl=0[/IMG]

[url=“/_imported_xf_attachments/1/1961_iPXE.png?:”]iPXE.png[/url]

[quote=“Tom Elliott, post: 39607, member: 7271”]This is good.

This is good.

What do you mean a text file? Is it asking you to download a file or is it displaying text in the browser? Can you give us some of the output?

colour --rgb 0xff0000 0 is the correct syntax

The english spelling never worked. iPXE was never coded using US English syntax. All the error you’re seeing means is that the ipxe.iso you have does not have the command tools built into it.[/quote]

I’m running into the same error. I’m using a website, [url]https://rom-o-matic.eu[/url] , to build my ipxe.iso.
I’m guessing that I’m missing some build options that deal with the command tools.
Have any of you used this site before to build your ISO? If so can you tell me what option(s) I must select in order to rectify this issue?

SaxxAppeal, I’ve configured a VirtualBox VM of Ubuntu 14 Desktop with Fog 1.0.1 with iPxe loading. Currently uploading a Win7 HID image ( another virtual machine ) and noticed the upload time is quite slow. It could be that I have simply taxed the physical hardware too much but I thought I would ask in case you had similar results since you’ve done something similar with the VMs.