PXE Boot stopped working
-
I need help troubleshooting why PXE boot is no longer working from client computers.
I installed FOG version 1.2.0 a few months ago. The OS is [FONT=Arial][COLOR=#333333]Ubuntu 10.04.[/COLOR][/FONT] I was seeing the PXE boot menu on machines with network boot as first priority. I successfully uploaded a number of images.
Something has changed since than and I no longer see the PXE boot menu when I start a client machine. I have installed all the suggested updates to Ubuntu.
Now at the end of the PXE boot sequence I get a message “/default.ipxe…no such file or directory”. The machine proceeds to start Windows.
On the FOG server I see that /tftpboot/default.ipxe exists.
Also, /etc/default/tftpd-hpa contains the line TFTP_DIRECTORY = “/tftpboot”
Can anyone offer ideas about how to diagnose the problem?
-
My guess is it’s related to one of the many updates you performed.
You may need to take a look into what’s being requested and Why it’s failing. Another option is to try the undionly files in trunk.
These are found at:
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp[/url]
They should specifically direct the files to the appropriate file and protocol needed.
-
How do I look at what’s being requested/failing?
Are you suggesting that I copy the undionly files from trunk to the Ubuntu machine?
Thanks
-
Copy the files in trunk to the fog server in /tftpboot.
You could use wireshark to watch the traffic.
-
Great, I’ll give it a try
-
[LIST]
[]Try using the TFTP troubleshooting. It may clue you in on the rights and existence of the files needed for IPXE boot. [url]http://fogproject.org/wiki/index.php/Tftp_timeout…#TFTP_Testing[/url]
[]Have you restarted the server lately? It is possible that the firewall re-initialized at boot. [url]http://fogproject.org/wiki/index.php/Tftp_timeout…#Ubuntu[/url]
[*]Have you had a network switch replaced lately? [url]http://fogproject.org/wiki/index.php/Tftp_timeout…#Check_Network_Switch_settings[/url]
[/LIST]
…and what Tom said! -
When did the problem start? This AM all of my FOG servers stopped working. The only change was a critical MySQL update that was preformed overnight. When I log into the FOG management window (browser) it want to run the database schema intaller/updater like it is a new install. Running it fails with an error. Trying to run it from the command line also result in an error.
Specifically if run from root: cd ~;mysqldump --allow-keywords -x -v fog > fogbackup.sqld: command not found
– Connecting to localhost…
mysqldump: Got error: 2002: Can’t connect to local MySQL server through socket ’
/var/run/mysqld/mysqld.sock’ (2) when trying to connectI am running Ubuntu 14.04LTS Fog 1.2.0
Mark
-
[quote=“Mark Cheavens, post: 40949, member: 28207”]When did the problem start? This AM all of my FOG servers stopped working. The only change was a critical MySQL update that was preformed overnight. When I log into the FOG management window (browser) it want to run the database schema intaller/updater like it is a new install. Running it fails with an error. Trying to run it from the command line also result in an error.
Specifically if run from root: cd ~;mysqldump --allow-keywords -x -v fog > fogbackup.sqld: command not found
– Connecting to localhost…
mysqldump: Got error: 2002: Can’t connect to local MySQL server through socket ’
/var/run/mysqld/mysqld.sock’ (2) when trying to connectI am running Ubuntu 14.04LTS Fog 1.2.0
Mark[/quote]
Make sure the mysql server is actually running![code]service mysql restart[/code]
This problem isn’t something I did, or fog is doing and you’re particular case has told you EXACTLY the problem was in the update. This doesn’t mean anything is actually wrong, but from what I can tell, the update stopped the mysql service but failed to restart it.
-
It look as though copying the files from trunk fixed the problem.
Can you tell me why?
-
I already did. The files in trunk are setup better to implicitly state what file and protocol to use
-
Thanks Tom.
OK, so I assume that the previous files were dynamic?
-
I’m going to say yes? It’s actually supposed to use the last protocol, but for whatever reason it seems to forget what the last protocol used was, which should always be tftp as that’s how it gets the undionly file to begin with.
-
Thanks again.
I have another question. I can’t seem successfully schedule a delayed task. The task never starts.
Should I open that in a new thread?
-
Restarting mysql did solve my issue. Sorry to have hijacked this thread, but since the other was generic stating that pxe was not working and was posted on the same date I thought it might be of relevance. All of my FOG servers are running again.
Sincerely,
Mark -
No,
Check your server timezones?
/etc/php5/apache/php.ini (date.timezone=America/New_York)
/etc/php5/cli/php.ini (date.timezone=America/New_York)
Change your America/New_York to match your particular timezone.
Then you’ll have to restart the apache server:
[code]sudo service apache2 restart[/code]
And restart the FOG Services that use the scheduler and such:
[code]sudo service FOGMulticastManager restart
sudo service FOGImageReplicator restart
sudo service FOGScheduler restart[/code] -
In /etc/php5/cli/php.ini the date.timezone field was commented out and no time zone was specified.
I’ll test it in a bit.
Does the America/New_York part have to be in quotes? It is in quotes in the other file.
-
It does not need to be in quotes, though it doesn’t hurt it either.
-
Thanks for your quick replies.
-
I just tried a manual upload. I have been busy with something else and I wasn’t monitoring the progress. I thought it would have been done some time ago and the FOG server showed 99.85% complete. I looked at the client and it was displaying FOGFTP: login failed with user “fog” and incorrect password every few seconds.
I did not recognize the password it was attempting to use.
Where do I edit that password? Could it have something to do with the files I copied from trunk?
-
It would not have anything to do with the files you downloaded from trunk.
To fix, I would recommend changing the Unix user fog with:
[code]sudo passwd fog[/code] Specify your new password and confirm it as required.Then go to Storage Management Page->List All Nodes->Your relevant node->Management Password and change this password to what you changed in the above step.
Then, go to FOG Configuration Page->FOG Settings->TFTP Server->FOG_TFTP_FTP_PASSWORD. Set the password to the same you set above, then all should be back to operational.
Hopefully this helps.
