You are not logged in.
Hi,
I'm trying to run tftp server but it fails:
# systemctl start tftpd
Job for tftpd.service failed. See 'systemctl status tftpd.service' and 'journalctl -xn' for details.
Here is an output from journalctl -xn:
Jul 11 07:40:29 localhost systemd[1]: Starting hpa's original TFTP daemon...
-- Subject: Unit tftpd.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit tftpd.service has begun starting up.
Jul 11 07:40:29 localhost systemd[1]: tftpd.service failed to run 'start' task: Invalid argument
Jul 11 07:40:29 localhost systemd[1]: Failed to start hpa's original TFTP daemon.
-- Subject: Unit tftpd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit tftpd.service has failed.
--
-- The result is failed.
tftpd.service looks like this:
[Unit]
Description=hpa's original TFTP daemon
[Service]
ExecStart=/usr/bin/in.tftpd -s /srv/tftp/
StandardInput=socket
StandardOutput=inherit
StandardError=journal
I'm using kernel 3.15.0 compiled on my own (without ipv6).
Any idea what is the problem?
Last edited by wtx (2014-07-11 06:16:56)
Offline
You should query the journal for all related tftpd messages. Use something like:
journalctl -u tftpd.service -b
I see that the tftp-hpa package also ships with a socket file as well. You might try socket activation (enable just the tftpd.socket), as it might just want the network to be up before it starts. I had that problem with vsftpd in the past, and socket activation makes it work every time since it will not be starting the service until the network is fully up.
Offline
Yes, you were right. I started tftpd.socket and now it works! Thank you. Problem solved.
Offline
Please mark the thread as [Solved]. This can be done by editing the first post.
Additionally, I think that this might also be solvable by having some basic ordering in the service file. If it were to have After=network.target network-online.target it would probably help. Particularly if you were to use systemd-networkd.service along with the systemd-networkd-wait-online.service.
Offline