I wrote:
> I've noticed that the config file I set up seems to be ignored, and I
> haven't gotten around to investigating why.
I looked into this today. The basic problem seemed to be rather simple.
The HOWTO I followed wasn't very clear about the TFTP server setup, and
I didn't have a second server running on the standard TFTP port. So I
fixed that, and cold booted the MVP.
Now the problem is that it appears to hang when trying to load the
config file (or shortly thereafter), and the MVP perpetually shows the
screen with the www.mvpmc.org logo.
Here's the way the TFTP server is being launched by inetd:
tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd \
--tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 \
--mcast-addr 239.239.239.0-255 --mcast-ttl 1 \
--maxthread 100 --verbose=5 /var/lib/tftpboot
16869 dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd \
--tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 \
--mcast-addr 239.239.239.0-255 --mcast-ttl 1 \
--maxthread 100 --verbose=5 /var/lib/tftpboot
And here's what's seen in the log:
in.tftpd[8354]: connect from 192.168.0.242 (192.168.0.242)
atftpd[8354]: Advanced Trivial FTP server started (0.7)
atftpd[8354]: Serving dongle.bin.ver to 192.168.0.242:2048
atftpd[8354]: Serving dongle.bin to 192.168.0.242:2049
atftpd[8354]: timeout: retrying...
last message repeated 5 times
in.tftpd[8363]: connect from 192.168.0.242 (192.168.0.242)
atftpd[8363]: Advanced Trivial FTP server started (0.7)
atftpd[8363]: Serving /var/lib/tftpboot/dongle.bin.config to
192.168.0.242:2048
atftpd[8363]: Serving /var/lib/tftpboot/dongle.bin.xml to
192.168.0.242:2050
atftpd[8354]: timeout: retrying...
atftpd[8354]: recvmsg: Connection refused
atftpd[8354]: tftpd_file.c: 926: recvfrom: Connection refused
atftpd[8354]: timeout: retrying...
atftpd[8354]: recvmsg: Connection refused
atftpd[8354]: tftpd_file.c: 926: recvfrom: Connection refused
atftpd[8354]: atftpd terminating after 300 seconds
atftpd[8354]: Main thread exiting
atftpd[8363]: atftpd terminating after 300 seconds
atftpd[8363]: Main thread exiting
A few things look concerning. One is that when a request is made for
dongle.bin{.ver}, atftpd doesn't show the path to the file, but when the
dongle.bin.config is requested, it shows the path. The MVP should have
no knowledge of that path, except it is specified as part of the DHCP
config:
dhcp-boot=/var/lib/tftpboot/dongle.bin,mythtv,192.168.0.203
so I would understand it if it appeared as part of the request for
dongle.bin, but it doesn't.
Another is that there is no dongle.bin.xml file, and yet atftpd doesn't
report any error.
Some quick experimentation with a TFTP client shows:
% tftp -i mythtv GET /var/lib/tftpboot/dongle.bin junk1
Transfer successful: 2929184 bytes in 12 seconds, 244098 bytes/s
Which logs:
in.tftpd[17837]: connect from 192.168.0.200 (192.168.0.200)
atftpd[17837]: Advanced Trivial FTP server started (0.7)
atftpd[17837]: Serving /var/lib/tftpboot/dongle.bin to
192.168.0.200:2458
and:
% tftp -i mythtv GET dongle.bin junk2
Transfer successful: 2929184 bytes in 11 seconds, 266289 bytes/s
atftpd[17837]: Serving dongle.bin to 192.168.0.200:2479
So apparently the path is irrelevant and ignored.
Attempting to transfer a non-existent file results in:
% tftp -i mythtv GET bogus junk3
Error on server : File not found
atftpd[17837]: Serving bogus to 192.168.0.200:2493
So atftpd is appropriately replying with an error code, but is failing
to log the error. (I guess I'll file a bug report against atftpd.)
Lastly, manually transferring the conf file seems to work fine:
% tftp -i mythtv GET /var/lib/tftpboot/dongle.bin.config junk4
Transfer successful: 144 bytes in 1 second, 144 bytes/s
atftpd[18100]: Serving /var/lib/tftpboot/dongle.bin.config to
192.168.0.200:2580
Maybe it is just the contents of my config file that is causing the
problem. It contains:
echo "TZ=EST+5EDT,M4.1.0/2,M10.5.0/2; export TZ" > /etc/shell.config
. /etc/shell.config
mvpmc -s mythtv -D mythtv -T --web-port&
(Where mythtv has been substituted for the actual FQDN of my MythTV server.)
The other troubling thing is the timeouts and "Connection refused" messages:
atftpd[8354]: timeout: retrying...
last message repeated 5 times
atftpd[8354]: timeout: retrying...
atftpd[8354]: recvmsg: Connection refused
atftpd[8354]: tftpd_file.c: 926: recvfrom: Connection refused
atftpd[8354]: timeout: retrying...
atftpd[8354]: recvmsg: Connection refused
atftpd[8354]: tftpd_file.c: 926: recvfrom: Connection refused
These are being logged by the atftpd process serving dongle.bin, and
appear even for a successful MVP boot.
Different command line options for atftpd might clear up the timeouts,
but less likely the connection refused errors, and just today the log
showed:
in.tftpd[14717]: connect from 192.168.0.242 (192.168.0.242)
atftpd[14717]: Advanced Trivial FTP server started (0.7)
atftpd[14717]: Serving dongle.bin.ver to 192.168.0.242:2048
atftpd[14717]: Serving dongle.bin to 192.168.0.242:2049
atftpd[14717]: timeout: retrying...
last message repeated 6 times
atftpd[14717]: recvmsg: Connection refused
atftpd[14717]: tftpd_file.c: 926: recvfrom: Connection refused
atftpd[14717]: timeout: retrying...
atftpd[14717]: tftpd_file.c: 931: abnormal return value 7
atftpd[14717]: tftpd_file.c: 931: abnormal return value 7
atftpd[14717]: timeout: retrying...
atftpd[14717]: tftpd_file.c: 931: abnormal return value 7
Abnormal return value? This again was on a successful boot. Seems like
either the MVP implementation of TFTP is buggy or atftpd is.
-Tom
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Mvpmc-users mailing list
Mvpmc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/
