@Tom-Elliott Hi Tom, I am running 7575

@tprice Did some testing. Manually updated the FOG snapins table:

INSERT INTO snapins (sID,sName,sDesc,sFilePath,sCreateDate,sCreator)
VALUES (“23”, “Esetv5”,“Blah”,/images/snapins/Esetv5-Inst.exe, Now(), “fog”);

And I can see something poping up in SNAPINS search page:

So the FOG application layer can get information from Database but the ability to ADD the information to the database from the FOG app layer is not working.

Hi there, I can upload the SNAPIN executable to the server fine. And I can see the file in the SNAPIN exist field (see image).

However after pressing the ‘Add’ button, the web page crashes. And when doing a search for snapins, there is nothing showing.

I have checked the SNAPIN Table within the FOG database. And there is no information regarding the new uploads.

I am to sure if the issue is between

• list item FOG application layer talking to the MariaDB. That is, it cannot update the fog database.
  OR

• An array variable within the “snapinmanagementpage.class.php”

:

FOG Version: 7575 (GiT)

HTTPD-Error Lod:

[Thu May 12 23:59:04.027045 2016] [:error] [pid 2417] [client xxx.xxx.xxx.xxx:52045] PHP Fatal error: Call to a member
function save() on null in /var/www/html/fog/lib/pages/snapinmanagementpage.class.php on line 161, referer: http://xxx.xxx.xxx.xxx/fog/management/index.php?nod

PHP Version:

[root@ahcaklfog02 /]# php -v
PHP 5.6.21 (cli) (built: Apr 28 2016 07:39:37)
Copyright 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright 1998-2016 Zend Technologies
[root@ahcaklfog02 /]# yum update -y

MariaDB version:

MariaDB [(none)]> SHOW VARIABLES LIKE “%version%”;
±------------------------±--------------------+
| Variable_name | Value |
±------------------------±--------------------+
| innodb_version | 5.5.46-MariaDB-37.6 |
| protocol_version | 10 |
| slave_type_conversions | |
| version | 5.5.47-MariaDB |
| version_comment | MariaDB Server |
| version_compile_machine | x86_64 |
| version_compile_os | Linux |
±------------------------±--------------------+

Celebration. It works. The things that I have changed was a complete new build of Centos 7, FOG (Version: 7306), and followed new documentation. This allowed me to register a machine and perform inventory but I could not start an upload (could not load images directory (/bin/fog. Upload).

Did some check regarding services and found NFS was not running. Once the latter was started, the ability to perform the partclone was successful.

I am very happy, thank you all

@Sebastian-Roth Hi there, I did not get this solved. I need to look at my switch and TFTP communication.

Hi there, I did not get it solved. But I think the issue within my Switch configuration. I have nine vlans. I have attached the Fog server on the vlan which is used by the workstations (.54) and the DHCP server is on a different vlans (.50).

I can ping the qdn, fqdn and reverser ping the FOG server within the main vlans.

The fog server is sitting on a Hyper-v host. The virtual switch is bridging the physical NIC.

So I need to figure out why the switch is answering the TFTP request. I suspect the ip helper and DHCP relay on the switch is the root cause.

Troy

Hi there, thanks for the response. I need to figure out why the tftp response is looping through my the switch.

It appears the IP Helper on the switch’s are enabled with port 0 relaying to our DHCP server.

Hi there, I am using undionly.kpxe in the Windows DHCP server.

The result from PCAP show now response from FOG server or anything related to port 69.

Regards
,timeout_issue.pcap

Hi Uncle Frank, the options for STP & RSTP are enabled at a global level. I will follow your suggestion and post results.

Thanks

Hi there, I have not be able to successfully PXE boot to menu. I get the dreaded Open TimeOut error.
I have installed Centos 7 (64bit) with FOG trunk. The installation completed successfully. I get the Web UI fine but I cannot load the FOG boot menu.
The fog installation is not using proxyDhcp as I am leveraging our existing DHCP server. So 66 & 67 have been configured appropriately.
The ability to perform TFTP -i xxx.xxx.xxx.xxx get undionly.pxe (from windows) and TFTP -v xxx.xxx.xxx.xxx -c get undionly.pxe (from Fog host server) all works tine.

The security layer on the fog server has been disabled.

The permissions for images, tftp, and ipx (under var/www/html/fog/services/) have been changed to 777.
The owners for the above folders are fog:root.

The network is a multiple vlan /subnet environment and STP and RSTP are turned at the switch level.

So I need some help with:

1. Troubleshooting why the PXE boot menu is not loading? is this due to the TFTP session is actually timing out or something else.
2. What is the best combination for installing FOG i.e. is Ubuntu better than Centos?

Thanks

Hi there, once I have Fog installed (latest version) onto Linux (tested Ubunt 12.01 and or Fedora 7).

What do I need to do to get the PXE menu to show? The DHCP has been configured as per Fog wiki suggestions.

I tend to get two results:

1. Configing (net0 [mac address] …) Error. 0x040ee119
2. PXE-32: TFTP open Timeout, PXE-MOF:Exiting Intel Boot Agent
3. TFTP. PXE-MOF:Exiting Intel Boot Agent

So I am not sure, if after installing FOG you need to perform additional configuration for the PXE boot menu.