Seems that TFTP was not prepared by installer
-
@george1421 said in Seems that TFTP was not prepared by installer:
This kind of tells me that your installer didn’t finish correctly, the default.ipxe file is built by the installer.
Strange, did not see any errormessages…
-
The “FOG Modified Version” string appears, to me, to be related to debian/ubuntu. This, however, does not mean it is a requirement as using rpcbind variants might work better for the server in which case IT would be used. You stated /tftpboot/default.ipxe wasn’t created?
-
@Tom-Elliott
Was not created, no. Don’t even have a /tftpboot-directory -
Then, as @george1421 state, it would seem your installer didn’t finish.
When it asked you to open the browser and goto update the schema, did you go back to the console and press enter to continue on?
-
@Tom-Elliott
You mean after updating/installing the database scheme? Yes, I did.But, it was the second attempt of installation.
First time I did something wrong with the 2 NICs, because I did not understand the questions in the installer about the router-adress for DHCP-Server (and still don’t understand it completely :)) so the first installation endet up with an error-message (something about the DHCP-Server).
The second install went well, and as mentioned I did not see any error-messages. -
@Tywyn Did you install as server or storage node?
-
@Tywyn There’s an error_logs folder in the fogproject/bin folder (where you extracted the download). There will be a log file of the most recent installation, there’s probably some more detailed information in there.
-
@Tom-Elliott
Normal Server -
@Quazz
Hm hm … thought over to reinstall about an hour ago but aborted the reinstall. It seems, that this try overwrote the log-files from the last install. So I have none from my orignal installation.Maybe I should do another, clean reinstallation.
Is it just the sudo ./installscript.sh? Or do I have to remove some files/databases?Do I have to set router address for DHCP-Server to 192.168.100.1 ?
Are those settings then correct:
* Here are the settings FOG will use: * Base Linux: Debian * Detected Linux Distribution: Debian GNU/Linux * Server IP Address: 192.168.100.1 * Server Subnet Mask: 255.255.255.0 * Interface: enp3s1 * Installation Type: Normal Server * Internationalization: 0 * Image Storage Location: /images * Using FOG DHCP: Yes * DHCP router Address: 192.168.100.1Interface enp3s1 is the one, which listens to 192.168.100.1
-
@Tywyn The router address should be the address of the router, it’s unlikely to be the FOG server. This is information used by the DHCP server (which will run on the FOG server in your case it seems) to inform DHCP clients of where the router is they should use.
You can change this information in /opt/fog/.fogsettings
-
@Quazz said in Seems that TFTP was not prepared by installer:
You can change this information in /opt/fog/.fogsettings
Just a small amendment to Quazz’s post.
You can / fix change this information in /opt/fog/.fogsettings and then just rerun the installer. No need to do a clean install
-
Hm … seems I have no /opt/fog/.fogsettings:
# ls -la /opt/fog insgesamt 12 drwxr-xr-x 3 root root 4096 Jul 11 12:31 . drwxr-xr-x 3 root root 4096 Jul 10 13:48 .. drwxr-xr-x 3 root root 4096 Jul 10 13:48 snapins -rw-r--r-- 1 root root 0 Jul 11 12:31 undionly.kpxe -
@Tywyn said in Seems that TFTP was not prepared by installer:
no /opt/fog/.fogsettings == no installer finish.
I have done that a few times where I use putty for installation and want to copy the url out of the putty window and I hit crtl-c to copy (which is the wrong keystroke for linux and the installer aborts).
-
Additional info about installing on debian 9.0.0: It seems, that /sbin/ifconfig is not installed by default anymore, but the installer looks for it.
So you have to install net-tools. -
@Tywyn it only uses ifconfig if needed. We try ip addr too
-
@Tom-Elliott said in Seems that TFTP was not prepared by installer:
@Tywyn it only uses ifconfig if needed. We try ip addr too
Thought I saw an error message there …
-
@george1421 More specifically CTRL+C tries to abort the current command/script in terminal, this is also true on Windows. (making it one of the more confusing key strokes)
-
This post is deleted! -
I’m guessing you deleted your message because you found the .fogsettings file after all.
As for your DHCP concerns, this might be because your router is also handing out DHCP information.
If you cannot modify your router’s DHCP settings to hand out TFTP/PXE bootfiles and if you cannot turn it off, then you should like into using ProxyDHCP
-
@Quazz You are right. I was looking in /etc/fog (for what reason ever :))
There is no router involved.
I have the fog-server connected to a switch (cisco SF100D-05) and my test-client connected to the same switch.
Strange thing is: in the beginning I got ip-adresses on pxe boot via dhcp.
Now not anymore. But: starting Windows and setting network to use dhcp immediatly gets an ip address.
dhcp-Server is the fog-server
