TFTP problem regarding local socket

dhartnett35 · 02-10-2005, 08:56 AM

I have a kickstart server that I almost had completed until TFTP started acting up and left me hanging.
I am using xinetd in Fedora Core 2. The TFTP version I am using is TFTP-hpa-40, the latest.
The error I am getting is this......

Feb 10 09:25:34 kickstart in.tftpd[10636]: cannot bind to local socket: Address already in use.

How do I determine where exactly this conflict is?

Any help would be very cool.

Dave

Brian Knoblauch · 02-10-2005, 09:13 AM

Sounds almost like you have tftpd running in xinetd (super server daemon) AND outside (as a normal daemon). It can't start in xinetd because there's another instance already bound to the port.

dhartnett35 · 02-10-2005, 10:23 AM

That's the funny thing. Its working properly for the most part. The daemon, in.tftpd, is supposed to run because of the file, TFTP, in the xinetd directory. This file specifically tells xinetd what to run. TFTP itself generates a PID, and is listening on an address. The daemon can't communicated with whatever socket its supposed to when a network connection is requested. the other stupid thing is that I completely reloaded the operating system and the communication error still exists.

Dave

dhartnett35 · 02-15-2005, 07:31 AM

FIREWALL!!! FIREWALL!!! FIREWALL!!!

My problem was all caused by my misconfigured IP Tables. The clue was to shut IP Tables down and run the server. Everything ran as it should have. Restarted IP Tables and the problem returned. Reconfigured and things are working OK.