@zer0cool just where I wrote it already. Right now Joe is very very limited in his ability to help with the project so it really is just me at this point. We have our other people but they are very busy as well.
Hi Sorry for the late reply I think I have balls things up completely and have got into a confused mess.
So I initially had the machine connected to the business lan with a static I.P address as I needed internet access to update the centos box and to install the required fog packages.
I then proceeded to keep the static connection connected and ran the setup script, during the setup process I specifically told FOG to use the isolated network address,
server ip address 192.168.22.3 ( isolated network)
using fog DHCP: yes
DHCP router address:
So the FOG server has a I.P address on the isolated network, and no DHCP router address,
At the end of the installation It is asking me to access the management console with a web address the issue is I cannot access this address as it is on a different subnet from main network.
Lastly When I check the status of the DHCP service.
systemctl status dhcpd.service
No subnet declaration for P4p1 ( 192.168.21.32)
ignoring requests on p4p1. If this is not what you
want pleae write a subnet declaration
in your dhcpd.conf file for the
network segement. to which interface
p4p1 is attached…
I don’t wan’t to use p4p1 for DHCP… more importantly I seem to missing a dhcpd.conf file I mean it’s just completely blank???
Yep I need some help :) go easy on me people
Update this is bizzare I restarted the server and I now have a dhcp configuration file in etc/dhcp
I have hooked up a laptop to the isolated network card and have tested the PXE booting aspect this works fine, And this laptop is getting a I.P address in the .22 isolated range, So DHCP is working wahey.
And it looks like I’ve run into my first new issue on a fresh install. I’ve just run the Fog installer and got to the bit to install/update the database schema, but I am unable to reach the web interface. Not sure where to go from here.
Are you really updating to 1.5 or 1.5.4? 1.5.0 I believe had issues with plugins (if I’m to remember correctly, but am pretty sure this has since been fixed.) The problem, truly, was with all Plugins, as it wouldn’t create the database needed for the plugin when it was installed.
Can you get us more information and possibly provide the apache error logs when you attempt to do something? (Debian = /var/log/apache2/error.log, Redhat = /var/log/httpd/error_log)