TFTP open timeout but it seems to work
-
the ip of the server is still the same (i also browse the FOG site with the ip in the address bar) and also in the dhcp server i see only it with his ip, maybe i can try to change it just for see what happen. thanks again
-
@lessndro You should do TCPDump at the earliest time possible.
It’s the one thing that will reveal what’s going on.
-
@lessndro How hard would it be to get a Chat session going and potentially a Teamviewer session?
My guess is the DHCP items are not setup properly and therefore not actually doing anything.
-
Hello guys, thanks a lot for your answers. Yesterday i was home so i didn’t tested anything, now i’m here.
i tried to follow the ‘IP conflict’ way… i changed the reservation from DHCP to another ip that i was sure it was free (192.168.148.192) i updated the DHCP fog info (i put again the undionly.kpxe instead of the .kkpxe) and followed the first part of this wiki https://wiki.fogproject.org/wiki//index.php?title=Change_FOG_Server_IP_Address and fortunately i found also this page https://www.designwright.com.au/articles/update-a-fog-server-ip-address because it explain how to modify the default.ipxe file (maybe someone should update the wiki!) and finally i can get in the FOG menù at every boot.
…and YES there was an ip conflict! from the dhcp server i could see the 192.16.148.25 (old ip) was free but probably a client took it because after i changed the FOG server to the new ip i could still ping 192.16.148.25 and i see a device from a ip scanner
unfortunately i don’t know how to understand which device it is because i tried to do ‘ping -a 192.16.148.25’ but i only get the ip address and also from Spicework if i try to search the mac address i can’t find it. I also tried to search the mac address on the DHCP server but nothing. Anyway it is just a curiosity because now i don’t need that ip.
NOW i have another problem, but i hope this time it will be easier. Since i update FOG to 1.2.0 i noticed that i lost every host previously registered, not a big problem because i register only a few hosts because it was a pretty new installation… the problem is that i cannot register any new host. If i try from the pxe menù to do a quick or a full registration i get this error:
and also if i try to register a new host on the the website it says ‘Host added’ but if i i click on ‘List All Hosts’ i can’t see any host. do you have any idea?
thanks a lot -
@lessndro
IP conflicts lol.To avoid that, you either need amazingly anal documentation skills from every single I.T. person in your organization,
Or.
Do not use static addresses, just simply make reservations in DHCP for your always-on equipment - and keep documentation on your reservations.
Because, if DHCP fails, you’re screwed anyways till it’s fixed, right? -
yeah, a lot of hours wasted for a trivial error… actually we are for re-do all the network and add a lot of new servers, it can be the right time for do a complete documentation.
what about the new error? I tried to google it but i can’t find others people with the same problem, i hope it is fixable!
thanks a lot----- UPDATE
I discovered i can’t modify anything, for example if a try to create a new image i can do it but after i don’t see the new image in the list, is like i have only read permissions…
-
@lessndro I’d first try to restart the database. If that didn’t work, I’d remove then reinstall it.
sudo service mysql restartMySQL
apt-get remove mysql mysql-server apt-get install mysql mysql-serverMariaDB
apt-get remove mariadb mariadb-server apt-get install mariadb mariadb-server -
unfortunately the restart didn’t change anything and also reinstalling mysql nothing happen.
i did
sudo apt-get remove mysql-server sudo apt-get install mysql-serverthanks for the support
-
Got FOG working by upgrading to Trunk. However in this particular instance, a new but less concerning problem emerged. Duplicate fog settings… Read further here: https://forums.fogproject.org/topic/5326/two-new-fog-client-settings
-
Hello Guys, i forgot to say one thing… yes it is working… we updated to trunk… BUT all this because Wayne Workman connected to our server and fixed it! thanks a lot for you help and your time!
thanks thanks thanks -
@lessndro said:
fortunately i found also this page https://www.designwright.com.au/articles/update-a-fog-server-ip-address because it explain how to modify the default.ipxe file (maybe someone should update the wiki!) and finally i can get in the FOG menù at every boot.
Glad someone found my boredom useful and thank you for referencing my site rather than copying and pasting the info. -
@Lesso Nice article.
Feel free to request access to the FOG Project’s WiKi.
We need more people that are good technical writers.
