@Wayne-Workman
damn. I couldn’t imagine, that this is so easy… sorry.

My system is Ubuntu Server 14.04.3.
I cannot fully understand why but this worked for me:

First add the proxy with:
export http_proxy=http://username:password@host:port/
export https_proxy=https://username:password@host:port/

Then put in /etc/sudoers:
Defaults env_keep=“https_proxy”

Last:
start the installfog.sh as root and not as sudo

Now it’s better - I still get the Info

 * Setting up storage..........................................OK
 * Setting up and starting DHCP Server......................... !!! No router address found !!!
 !!! No dns address found !!!
OK
 * Setting up and starting TFTP and PXE Servers................OK

but the script continues and everything seems to be ok.

@Wayne-Workman
yes in both files are the addresses set correctly

@Wayne-Workman I really don’t want to dissapoint you
I’ve updated now to the svn 6755 and still get the ! ! ! No router address found ! ! ! and ! ! ! No dns address found ! ! !
How I said before - the setup is complete and everything seems to work. I only get these two “warnings”

Here is my .fogsettings:

## Start of FOG Settings
## Created by the FOG Installer
## Version: 6755
## Install time: Sat 12 Mar 2016 05:58:49 PM CET
ipaddress='192.168.94.111'
interface='eth0'
submask='255.255.255.0'
routeraddress='192.168.94.1'
plainrouter='192.168.94.1'
dnsaddress='192.168.94.1'
dnsbootimage='192.168.94.1'
username='fog'
password="XXXXXX"
osid='2'
osname='Debian'
dodhcp='Y'
bldhcp='1'
blexports='1'
installtype='N'
snmysqluser=''
snmysqlpass=""
snmysqlhost=''
installlang=''
donate='0'
storageLocation='/images'
fogupdateloaded=1
docroot='/var/www/html/'
webroot='fog/'
caCreated='yes'
startrange='192.168.94.60'
endrange='192.168.94.99'
bootfilename='undionly.kpxe'
packages='apache2 php5 php5-json php5-gd....
noTftpBuild=''
notpxedefaultfile=''
sslpath='/opt/fog/snapins/ssl/'
## End of FOG Settings

And this is the dhcpd.conf:

...
next-server 192.168.94.111;
# Specify subnet of ether device you do NOT want service.
# For systems with two or more ethernet devices.
# subnet 136.165.0.0 netmask 255.255.0.0 {}
subnet 192.168.94.0 netmask 255.255.255.0{
    option subnet-mask 255.255.255.0;
    range dynamic-bootp 192.168.94.60 192.168.94.99;
    default-lease-time 21600;
    max-lease-time 43200;
    option routers 192.168.94.1;
    option domain-name-servers 192.168.94.1;
...

Perfect now! Installer and configs are all correct. From my side the problem is solved. Thanks!

@tom-elliott Thanks! Looks good and I will give it a try

@sebastian-roth Thanks!

@sebastian-roth
initially there was of course an internet connection but currently not possible.

We use version 1.5.8 and need to update to 1.5.9 because of problems with restoring images. With the 1.5.9 it seems to work fine.
We have multiple servers, where the installer will not be able to downlad packages and will fail then.
Which directories and files are important to copy, to upgrade the server from 1.5.8 to 1.5.9?
Are there any specific packages which should be installed?

Thanks in advance!

@sebastian-roth we have multiple installations - the most are currently on 1.5.8 and some on 1.5.9. But the changes in the web-ui shouldn’t be that huge

@sebastian-roth That would be nice - we use 1.5.8/9 currently.

@Sebastian-Roth
Yes just show it in the Web-UI

Hello guys,

is it possible to add an additional column with the information from host-inventory?
For example the “System Product”.
That could safe multiple steps to find out, which image should be assigned to which host.

Thanks

I don’t know if it has to do something with the timeout issue but in /etc/default/grub I added

GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"

because we want to use eth0 name instead of enp1s0.

I changed manually the kernels in /var/www/html/fog/service/ipxe/ to the 4.15.2 Kernel.

Now I get eth0 instead of enp1s0:

Starting syslogd: OK
Starting klogd: OK
Running sysctl: OK
Populating /dev using udev: done
Saving random seed: OK
Staring haveged: haveged: listening socket at 3
OK
Starting eth0 interface and waiting for the link to come u

With the older kernel the issue with the timeout is gone.

@Sebastian-Roth
I went through the wiki article and everything seems to be fine.

I saw that fog is downloading the kernels twice if you do an update. First time if you expand the kernel you want to download and click on “download”. (Kernel will be downloaded as “bzImage”) The second time after you enter the kernel name and click on “install” - this time the kernel will be downloaded with the new name.