TFTP error on server

[idiart33]

Hi !

I have a server in 172.16.0.1.
I have tftp error when I launch it.
failed to start LSB : tftp-hpa’s tftp server (picture 1)

And when I try to start the VM since OS, I get an IP adress (172.16.0.10) but I see a tftp error (tftp open timeout) (picture 2)

Anybody know how to solve it please ?

[idiart33]

In the /tftpboot/pxelinux.cfg/default file I had a bad IP.
I change it but I still have same error after rebooting the server.

[Sebastian Roth]

@idiart33 Please run systemctl status tftpd-hpa and post the full output here.

[idiart33]

It’s the file you ask me !

[idiart33]

I edit the file /tftpboot/default.ipxe because I found a bad IP in chain=…

But I still have a tftp problem when I boot the server.

[idiart33]

I have a snapshot before changing IP of server.

I can restore and change IP adress if it’s better.

[george1421]

@idiart33 OK the issue here is that the tftp service can’t start, it can’t bind to the ipv4 socket. This typically means that there is already a service running bound to that socket. So far there is no other problems other than tftp, so you don’t need to look at fog settings at the moment. Having to hand edit the default.ipxe file means that you do have some fixup to do with fog because the IP address changed after you installed FOG.

STOP... I just looked at your previous posts "In the /tftpboot/pxelinux.cfg/default file I had a bad IP." why is syslinux installed on this computer? FOG uses iPXE for its boot loader. This tells me you don't have a standard FOG install. Are you installing FOG side by side with another opensource project?

Lets first try to understand why tftp is not starting.

Please run these command:

systemctl status tftpd-hpa

Make sure the service is still in the state of not being able to bind to the socket.

Then run:

netstat -an|grep :69

You should not get any response.

If you get a response like below you already have a tftp service running on your computer. I’m going t guess you WILL get a response like below, but lets see.

netstat -an|grep :69
udp        0      0 0.0.0.0:69              0.0.0.0:*

Another test would be this command:

ps aux|grep tftp

With the status of can not bind to the socket, I would expect this to return some value too. What this test does is to check to see if a service with tftp in the name is running in memory.

[idiart33]

When I do

systemctl status tftpd-hpa

I have this :

In fact with :

netstat -an|grep :69

I don’t get any response

With :

ps aux|grep tftp

I get this :

[idiart33]

@george1421 STOP… I just looked at your previous posts “In the /tftpboot/pxelinux.cfg/default file I had a bad IP.” why is syslinux installed on this computer? FOG uses iPXE for its boot loader. This tells me you don’t have a standard FOG install. Are you installing FOG side by side with another opensource project?

I have apache2, mysql and php installed on this server.

I have my exam tomorrow so it’s very urgent !

[george1421]

@idiart33 Ok is there a tftp log in /var/logs directory? There has to be a clue somewhere why the tftp server isn’t starting.

You could also try to manually start it to see if there is any usable hints.

cd /etc/init.d
./tftpd-hpa start

I don’t know what status 71 is, but I’m hoping it will tell us what it doesn’t like.

[idiart33]

There is proftpd.log file but no tftp log.

When I manually try to start it :

[idiart33]

This post is deleted!

[idiart33]

@george1421 said in TFTP error on server:
I don’t know what status 71 is, but I’m hoping it will tell us what it doesn’t like.

I found this IP : 10.23.2.1 on the /etc/default/tftpd-hpa file

I reboot my server but I still have the same problem

[Sebastian Roth]

@idiart33 What do you get when running the command journalctl -xe??

[Sebastian Roth]

@idiart33 As well please post the contents of your /etc/default/tftpd-hpa. I have a feeling that there is a miss-configuration in that.

[idiart33]

I resolve my tftp error.

I had change my IP config of the server. So it was the /etc/default/tftpd-hpa file the problem.

But when I start a vm since OS I have this :

@Sebastian-Roth Yes you’re right, it’s this file !

[Sebastian Roth]

@idiart33 What version of FOG do you have?! Just asking because the error message clearly shows that the init file you use is years old (in December 2017 we changed the inits a bit and the error message you posted in the picture is from before that!)

[idiart33]

I have the 1.3.4 version

[idiart33]

The VM WITH Windows work. But I think I need more space on the server.

Is it possible to add more store ?

[Sebastian Roth]

@idiart33 Why do you use such an old version? Currently we have 1.5.6! I can’t even remember when 1.3.4 was still fresh.

What I see in the picture “Processing Partition: /dev/sda ()” makes me think that FOG is not able to properly deploy and re-read the partition table before it tries to deploy the data to the partitions.

Probably best if you cancel the task in the webUI, schedule a new one with debug enabled and step through the whole process manually. Take pictures of the whole process and post here. We might be able to find what’s wrong.

But this is just a quick idea. We really don’t know enough to be sure we can help you. The setup is way to old and we shouldn’t really spend time on digging up problems with such old versions. Possibly it’s just an error that was fixed long time ago.