Re: tftp not working on almalinux 9
On 20.05.25 15:31, Jerry Geis via AlmaLinux Users wrote:
Hi -
I followed these steps: https://computingforgeeks.com/setup-tftp-server-on-centos-rhel-rocky- linux/ <https://computingforgeeks.com/setup-tftp-server-on-centos-rhel- rocky-linux/>
Don't do that. Those instructions are often from people who really don't understand what they are doing. Step 2 messes everything totally up. Someone doesn't understand how systemd works and how to overwrite unit files...
now I get this: systemctl status tftp-server.service × tftp-server.service - Tftp Server Loaded: loaded (/etc/systemd/system/tftp-server.service; enabled; preset: disabled) Active: failed (Result: resources) TriggeredBy: ○ tftp-server.socket Docs: man:in.tftpd CPU: 0
May 20 08:27:27 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- server.service: Cannot add dependency job, ignoring: Unit tftp- server.socket has a bad unit file setting.
As the error says: your tftp-server.socket is broken. Which probably comes because of step 2 above. # systemctl cat tftp-server.socket will show the content of the active configuration.
May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- server.service: Got no socket. May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- server.service: Failed to run 'start' task: Invalid argument May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- server.service: Failed with result 'resources'. May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: Failed to start Tftp Server.
this is my file after removing start arguments: more tftp-server.service [Unit] Description=Tftp Server Requires=tftp-server.socket Documentation=man:in.tftpd
[Service] ExecStart=/usr/sbin/in.tftpd /tftpboot StandardInput=socket
[Install] WantedBy=multi-user.target Also=tftp-server.socket
STill does not start.
Yes. Changing that file doesn't make sense either. The tftp-server.socket unit is broken.
What are the correct steps for setting up TFTP .
The correct steps are fairly simple: # dnf -y install tftp-server # systemctl enable --now tftp.socket That's all what is necessary to get it running. After it's running, make necessary changes if you need something different. But that's done via the standard systemd overrides and not by putting different files with different names into /etc/systemd/system... I would recommend in your current setup to remove those copied files # /bin/rm /etc/systemd/system/tftp-server.service # /bin/rm /etc/systemd/system/tftp-server.socket # systemctl daemon-reload # systemctl enable --now tftp.socket And then check if you can access it... -Gerald
Gerald Vogt wrote:
On 20.05.25 15:31, Jerry Geis via AlmaLinux Users wrote:
Hi - I followed these steps: https://computingforgeeks.com/setup-tftp-server-on-centos-rhel-rocky- linux/ <https://computingforgeeks.com/setup-tftp-server-on-centos-rhel- rocky-linux/> Don't do that. Those instructions are often from people who really don't understand what they are doing. Step 2 messes everything totally up. Someone doesn't understand how systemd works and how to overwrite unit files... now I get this: systemctl status tftp-server.service × tftp-server.service - Tftp Server Loaded: loaded (/etc/systemd/system/tftp-server.service; enabled; preset: disabled) Active: failed (Result: resources) TriggeredBy: ○ tftp-server.socket Docs: man:in.tftpd CPU: 0 May 20 08:27:27 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- server.service: Cannot add dependency job, ignoring: Unit tftp- server.socket has a bad unit file setting. As the error says: your tftp-server.socket is broken. Which probably comes because of step 2 above.
# systemctl cat tftp-server.socket
will show the content of the active configuration.
May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- server.service: Got no socket. May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- server.service: Failed to run 'start' task: Invalid argument May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- server.service: Failed with result 'resources'. May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: Failed to start Tftp Server. this is my file after removing start arguments: more tftp-server.service [Unit] Description=Tftp Server Requires=tftp-server.socket Documentation=man:in.tftpd [Service] ExecStart=/usr/sbin/in.tftpd /tftpboot StandardInput=socket [Install] WantedBy=multi-user.target Also=tftp-server.socket STill does not start. Yes. Changing that file doesn't make sense either. The tftp-server.socket unit is broken. What are the correct steps for setting up TFTP . The correct steps are fairly simple:
# dnf -y install tftp-server # systemctl enable --now tftp.socket
That's all what is necessary to get it running.
After it's running, make necessary changes if you need something different. But that's done via the standard systemd overrides and not by putting different files with different names into /etc/systemd/system...
I would recommend in your current setup to remove those copied files
# /bin/rm /etc/systemd/system/tftp-server.service/https://cookie-clicker2.com/ # /bin/rm /etc/systemd/system/tftp-server.socket # systemctl daemon-reload # systemctl enable --now tftp.socket
And then check if you can access it...
-Gerald This is where the long-term stability comes in. Instead of modifying or creating entirely new files in /etc/systemd/system, which can lead to issues during updates or if the original service definition changes, using systemd overrides is the correct approach.
participants (2)
-
Gerald Vogt -
oliviawilde168＠outlook.com