/default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client

PaganLinuxGeek

I tried the undionly.kkpxe file to the same results…

I HAVE tried the standard FOG 1.2.0 configuration for dnsmasq as well as the older style (fog 0.32)
The dnsmasq.conf shown below has a menu that alllows me to choose which
My gut feeling is that something is preventing the connection to tftp when the client computer loads undionly, and follows the scripted instructions… However since I dont have the beta versions or the source I am at a loss to see what the potential causes are…

my machine has three NICS:
eno1 = 192.168.1.116
enp4s0 = 192.168.1.115
enp7s0 = 192.168.1.107

-----my current /etc/dnsmasq.conf file…-----
tftp-root=/tftpboot
#enable-tftp
#dhcp-boot=pxelinux.0
dhcp-option=vendor:PXEClient,6,2b
dhcp-no-override
#pxe-prompt=“Press F8 for boot menu…”, 3
#pxe-service=X86PC, “Boot from network”, pxelinux
#pxe-service=X86PC, “Boot from local hard disk”, 0
dhcp-range=192.168.1.116,proxy

#port=0
log-dhcp
dhcp-boot=undionly.kpxe,192.168.1.116
dhcp-option=17,/images
dhcp-option=pxe,66,192.168.1.116
pxe-prompt=“Press F8 for boot menu”, 15
pxe-service=X86PC,“iPXE Boot (Newer for Secure Boots)”, undionly
pxe-service=X86PC,“PXE Boot (Older machines)”, pxelinux
pxe-service=X86PC,“Boot from local hard disk”, 0
interface=eno1,enp7s0,enp4s0,lo

I have verified that the httpd, xinetd, and dnsmasq services are started, and firewalld is NOT.

Wayne Workman

Bump.

PaganLinuxGeek

Still working on it, with no success.

Wayne Workman

[quote=“PaganLinuxGeek, post: 42573, member: 2226”]Still working on it, with no success.[/quote]

So, out of curiosity (and some valid reason to bump this thread), I checked the Wiki’s Working device & Problematic Device list. The pavillion g7 is not listed in either.

PaganLinuxGeek

Well I wouldn’t want to list it as NOT WORKING until I can test it on a known functional FOG setup…
Anyone have one running in the panhandle of Florida?

Tom Elliott

Where I’m more confused, is this still based on 1.0.1? If so, can you, at the least, try more updated ipxe files?

PaganLinuxGeek

It is the latest stable release 1.2.0 running on Fedora Workstation 21 it was NOT an upgrade but a new installation as I had recently formatted and installed fedora 21.

I am using dnsmasq to proxy the dhcp options needed to network boot clients.
I HAVE check httpd logs and the clients do NOT progress to the point of requesting files via http
I did have logging enabled on dnsmasq to verify proper operation but have since disabled it again.
This setup is running on the HOST OS and NOT in a vm. I have been attempting to use a vbox vm to test this as well as my personal laptop a pavillion g7
Please let me know what other information you need and I will endeavor to provide it. I can ssh into this machine running at home and manipulate a virtualbox vm via x over ssh.

PaganLinuxGeek

[CODE][root@jezebelle ~]# cat /var/log/foginstall.log
Script started on Tue 17 Feb 2015 02:22:34 PM CST
Fedora

  ..#######:.    ..,#,..    .::##::.

.:###### .:;####:…;#;…
…##… …##;,;##::::.##…
,# …##…##:::## …::
## .::###,##. . ##.::#.:######::.
…##:::###::…#. … .#…#. #…#:::.
…:####:… …##…##::## … #
# . …##:,;##;:::#: … ##…
.# . .:;####;::::.##:::;#:…
# …:;###…

###########################################

FOG

Free Computer Imaging Solution

http://www.fogproject.org/

Developers:

Chuck Syperski

Jian Zhang

Peter Gilchrist

Tom Elliott

GNU GPL Version 3

###########################################

Version: 1.2.0 Installer/Updater

What version of Linux would you like to run the installation for?

      1) Redhat Based Linux (Redhat, CentOS, Mageia)
      2) Debian Based Linux (Debian, Ubuntu, Kubuntu, Edubuntu)

Choice: [1]

Staring Redhat / CentOS Installation.
…/lib/redhat/functions.sh: line 1: n#: command not found

FOG Server installation modes:
* Normal Server: (Choice N)
This is the typical installation type and
will install all FOG components for you on this
machine. Pick this option if you are unsure what to pick.

  * Storage Node: (Choice S)
      This install mode will only install the software required
      to make this server act as a node in a storage group

More information:
http://www.fogproject.org/wiki/index.php?title=InstallationModes

What type of installation would you like to do? [N]

What is the IP address to be used by this FOG Server? [192.168.1.116]

Would you like to setup a router address for the DHCP server? [Y/n] n

Would you like to setup a DNS address for the DHCP server and client boot image? [Y/n] n

Would you like to change the default network interface from eth0?
If you are not sure, select No. [y/N]n

Would you like to use the FOG server for DHCP service? [Y/n] n

This version of FOG has internationalization support, would
you like to install the additional language packs? [y/N] n

Would you like to donate computer resources to the FOG Project
to mine cryptocurrency? This will only take place during active
tasks and should NOT have any impact on performance of your
imaging or other tasks. The currency will be used to pay for
FOG Project expenses and to support the core developers working
on the project. For more information see:

http://fogproject.org/?q=cryptocurrency

Would you like to donate computer resources to the FOG Project? [y/N] n

#####################################################################

FOG now has everything it needs to setup your server, but please
understand that this script will overwrite any setting you may
have setup for services like DHCP, apache, pxe, tftp, and NFS.

It is not recommended that you install this on a production system
as this script modifies many of your system settings.

This script should be run by the root user on Redhat or with sudo on Ubuntu.

** Notice ** Redhat users will need to disable SELinux and iptables in
order to use FOG
Please see our wiki for more information at http://www.fogproject.org/wiki

Here are the settings FOG will use:
Base Linux: Redhat
Detected Linux Distribution: Fedora
Installation Type: Normal Server
Server IP Address: 192.168.1.116
DHCP router Address:
DHCP DNS Address:
Interface: eth0
Using FOG DHCP: 0
Internationalization: 0
Donate: 0

    DHCP will NOT be setup but you must setup your
    current DHCP server to use FOG for PXE services.

    On a Linux DHCP server you must set:
        next-server

    On a Windows DHCP server you must set:
        option 066 & 067

              Option 066 is the IP of the FOG Server: (e.g. 192.168.1.116)
              Option 067 is the undionly.kpxe file: (e.g. undionly.kpxe)

Are you sure you wish to continue (Y/N) y

Installation Started…

Installing required packages, if this fails
make sure you have an active internet connection.

Packages to be installed: httpd php php-cli php-common php-gd php-mysql mysql mysql-server tftp-server nfs-utils vsftpd net-tools wget xinetd tar gzip make m4 gcc gcc-c++ lftp
Skipping package: httpd (Already installed)
Installing package: php
Skipping package: php-cli (Already installed)
Skipping package: php-common (Already installed)
Installing package: php-gd
Installing package: php-mysql
Skipping package: mariadb (Already installed)
Skipping package: mariadb-server (Already installed)
Skipping package: tftp-server (Already installed)
Skipping package: nfs-utils (Already installed)
Installing package: vsftpd
Skipping package: net-tools (Already installed)
Skipping package: wget (Already installed)
Installing package: xinetd
Skipping package: tar (Already installed)
Skipping package: gzip (Already installed)
Skipping package: make (Already installed)
Skipping package: m4 (Already installed)
Skipping package: gcc (Already installed)
Installing package: gcc-c++
Skipping package: lftp (Already installed)

Confirming package installation.

Checking package: httpd…OK
Checking package: php…OK
Checking package: php-cli…OK
Checking package: php-common…OK
Checking package: php-gd…OK
Checking package: php-mysql…OK
Checking package: mysql…OK
Checking package: mysql-server…OK
Checking package: tftp-server…OK
Checking package: nfs-utils…OK
Checking package: vsftpd…OK
Checking package: net-tools…OK
Checking package: wget…OK
Checking package: xinetd…OK
Checking package: tar…OK
Checking package: gzip…OK
Checking package: make…OK
Checking package: m4…OK
Checking package: gcc…OK
Checking package: gcc-c++…OK
Checking package: lftp…OK

Configuring services.

Setting up fog user…OK
Setting up and starting MySQL…Note: Forwarding request to ‘systemctl enable mysqld.service’.
Created symlink from /etc/systemd/system/multi-user.target.wants/mysqld.service to /usr/lib/systemd/system/mysqld.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/mariadb.service to /usr/lib/systemd/system/mariadb.service.
OK
Backing up user reports…OK
Did you leave the mysql password blank during install? (Y/n) y
Setting up and starting Apache Web Server…Note: Forwarding request to ‘systemctl enable httpd.service’.
Created symlink from /etc/systemd/system/multi-user.target.wants/httpd.service to /usr/lib/systemd/system/httpd.service.
OK
You still need to install/update your database schema.
This can be done by opening a web browser and going to:

http://192.168.1.116/fog/management

Press [Enter] key when database is updated/installed.

Configuring Fresh Clam…Skipped (See wiki for installation instructions)
Setting up storage…OK
Setting up and starting NFS Server…Note: Forwarding request to ‘systemctl enable rpcbind.service’.
Note: Forwarding request to ‘systemctl enable nfs.service’.
Failed to execute operation: No such file or directory
OK
Setting up and starting DHCP Server…Skipped
Setting up and starting TFTP and PXE Servers…Note: Forwarding request to ‘systemctl enable xinetd.service’.
OK
Setting up and starting VSFTP Server…Note: Forwarding request to ‘systemctl enable vsftpd.service’.
Created symlink from /etc/systemd/system/multi-user.target.wants/vsftpd.service to /usr/lib/systemd/system/vsftpd.service.
OK
Setting up sudo settings…OK
Setting up FOG Snapins…OK
Setting up and building UDPCast…OK
Installing init scripts…OK
Setting up FOG Services…OK
Starting FOG Multicast Management Server…OK
Starting FOG Image Replicator Server…OK
Starting FOG Task Scheduler Server…OK
Setting up FOG Utils…OK

Would you like to notify the FOG group about this installation?
* This information is only used to help the FOG group determine
if FOG is being used. This information helps to let us know
if we should keep improving this product.

Send notification? (Y/N)y

Thank you, sending notification…Done

Setup complete!

You can now login to the FOG Management Portal using
the information listed below. The login information
is only if this is the first install.

This can be done by opening a web browser and going to:

  http://192.168.1.116/fog/management

  Default User:
        Username: fog
        Password: password

Script done on Tue 17 Feb 2015 02:53:15 PM CST
[/CODE]

Wayne Workman

Note: Forwarding request to ‘systemctl enable nfs.service’.
Failed to execute operation: No such file or directory

Ok, Fedora 21 support wasn’t formally added to FOG till SVN 2920(ish), Which isn’t part of 1.2.0

I’d highly recommend trying SVN 2920, 2922, or the latest SVN

I’d do a fresh install, (OS and the whole 9 yards) and follow along with those Fedora 21 instructions.

The commands to install a specific SVN are in the instructions.

Junkhacker

personally, i recommend 2948. I’ve had no problems with it. the latest svn is bleeding edge and might be a bit glitchy at the moment.

Tom Elliott

[COLOR=#ffffff]Mostly cause I’m an idiot or something…apparently[/COLOR]

PaganLinuxGeek

[root@jezebelle ~]# systemctl status nfs.service
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled)
Active: active (exited) since Tue 2015-02-24 08:53:22 CST; 27min ago
Process: 1217 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=0/SUCCESS)
Process: 1215 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
Main PID: 1217 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/nfs-server.service
[root@jezebelle ~]# showmount -e 192.168.1.116
Export list for 192.168.1.116:
/images/dev *
/images *
[root@jezebelle ~]#

PaganLinuxGeek

[quote=“Wayne Workman, post: 42679, member: 28155”]Note: Forwarding request to ‘systemctl enable nfs.service’.
Failed to execute operation: No such file or directory

Ok, Fedora 21 support wasn’t formally added to FOG till SVN 2920(ish), Which isn’t part of 1.2.0

I’d highly recommend trying SVN 2920, 2922, or the latest SVN

I’d do a fresh install, (OS and the whole 9 yards) and follow along with those Fedora 21 instructions.

The commands to install a specific SVN are in the instructions.[/quote]

You are recommending a format and fresh install of the OS? then install a development version of the software? I just want to make sure I understand you correctly. Before you respond please see my post just prior to this showing that nfs is active and exporting the images and dev directories

Wayne Workman

[quote=“PaganLinuxGeek, post: 42686, member: 2226”]You are recommending a format and fresh install of the OS? then install a development version of the software? I just want to make sure I understand you correctly. Before you respond please see my post just prior to this showing that nfs is active and exporting the images and dev directories[/quote]

Because everything else that was tried hasn’t worked & because you don’t have a functioning 1.2.0 FOG machine, I think that re-installing the OS and going with SVN 2922 (or 2948) is very safe and probably the best next-step.

The installation script alone in 2922 does so much small tweaking for Fedora 21, it really vastly cut down on the things that had to be done to get FOG working on Fedora 21. As you did, I tried putting 1.2.0 on Fedora 21 originally; I documented what I did. My instructions were a mile long, consisted of over a dozen web page links, several dozen commands, notes, etc. I didn’t even know exactly what commands were making it work… But I did get uni-cast working on my own. Tom got me straightened out further with multicasting, and other issues. We worked together so he could fine tune the installation script for Fedora 21.

After SVN 2920, my instructions dropped from 12(ish) pages to six simple, uncomplicated pages.

We know beyond doubt that SVN 2922 works on Fedora 21, and have instructions written specifically for this.

If you don’t want to do a re-install or use the SVN, maybe Tom will help.

PaganLinuxGeek

Ugh. this machine doubles as my workstation. Lots of work to re-install this beast… Where can I get svn 2922? Perhaps I can round up a older alower machine to install 21 on and then this developmental version.

If I knew what the failed actions were I could likely ammend or perform them manually. I had to do that with 0.32 on fedora 19, and 20…

Wayne Workman

[quote=“PaganLinuxGeek, post: 42688, member: 2226”]Ugh. this machine doubles as my workstation. Lots of work to re-install this beast… Where can I get svn 2922? Perhaps I can round up a older alower machine to install 21 on and then this developmental version.

If I knew what the failed actions were I could likely ammend or perform them manually. I had to do that with 0.32 on fedora 19, and 20…[/quote]

The command to get 2922 is in the Fedora 21 instructions on the Wiki.

Literally every single step is covered there.

[url]http://fogproject.org/wiki/index.php/FOG_(r2922)_Configuration_on_Fedora_21_Workstation_inside_Windows_Server_2012_Hyper-V_using_ProxyDHCP[/url]

As far as amending 1.2.0, that’s a Tom question.

PaganLinuxGeek

I noticed today that the last line shown on the vbox console has the WRONG ip address. (It’s showing tftp://192.168.1.1/default.ipxe…
Now I’ve set dnsmasq.conf to use .116 What would cause the clients to default to the .1 ip instead? is there another file somewhere that undionly.kpxe is referencing?

Wayne Workman

[quote=“PaganLinuxGeek, post: 42706, member: 2226”]I noticed today that the last line shown on the vbox console has the WRONG ip address. (It’s showing tftp://192.168.1.1/default.ipxe…
Now I’ve set dnsmasq.conf to use .116 What would cause the clients to default to the .1 ip instead? is there another file somewhere that undionly.kpxe is referencing?[/quote]

Simple question but, in your install log, you answered no for using FOG as a dhcp server. Have you covered DHCP options 66 & 67, made sure they are correct?

[url]http://fogproject.org/wiki/index.php/FOGUserGuide#DHCP_Settings[/url]

Junkhacker

the line in the ipxe embeded script that loads default.ipxe is [CODE]chain tftp://${next-server}/default.ipxe[/CODE] i’m not sure how it could both load the undionly.kpxe file and get the location of the default.ipxe file wrong

PaganLinuxGeek

I cannot modify those options in the router my ISP provided. That is why I am using dnsmasq
I tried installing the svn suggested over my existing fog install. The “devel” version I guess shows the server IP…
I’m trying to understand why it’s pulling the router’s IP instead of what dnsmasq is sending…

[CODE][root@jezebelle tftp]# cat /etc/dnsmasq.conf
tftp-root=/tftpboot
#enable-tftp
dhcp-option=vendor:PXEClient,6,2b
dhcp-no-override
dhcp-range=192.168.1.107,proxy
#port=0
log-dhcp
dhcp-boot=undionly.kpxe,192.168.1.107
dhcp-option=17,/images
dhcp-option=pxe,66,192.168.1.107
pxe-prompt=“Press F8 for boot menu”, 9
pxe-service=X86PC,“iPXE Boot (Newer for Secure Boots)”, undionly
pxe-service=X86PC,“PXE Boot (Older machines)”, pxelinux
pxe-service=X86PC,“Boot from local hard disk”, 0
#interface=eno1,enp7s0,enp4s0,lo
[/CODE]

[CODE][root@jezebelle tftp]# ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.116 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::922b:34ff:fed4:e03 prefixlen 64 scopeid 0x20<link>
ether 90:2b:34:d4:0e:03 txqueuelen 1000 (Ethernet)
RX packets 2713 bytes 207258 (202.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 40 bytes 9597 (9.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf7600000-f7620000

enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.115 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::6a05:caff:fe0a:5e3 prefixlen 64 scopeid 0x20<link>
ether 68:05:ca:0a:05:e3 txqueuelen 1000 (Ethernet)
RX packets 2704 bytes 205402 (200.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 35 bytes 9194 (8.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xf74c0000-f74e0000

enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.107 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::922b:34ff:fed4:df3 prefixlen 64 scopeid 0x20<link>
ether 90:2b:34:d4:0d:f3 txqueuelen 1000 (Ethernet)
RX packets 441929 bytes 66602075 (63.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1299172 bytes 1874321485 (1.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 76552 bytes 1155843438 (1.0 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 76552 bytes 1155843438 (1.0 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 6e:1a:c0:4e:a2:a6 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[/CODE]