package tftpd-hpa 5.2+20150808-1.2build2 failed to install/upgrade: installed tftpd-hpa package post-installation script subprocess returned error exit status 1

[Nigel Hathaway]

Upgrade 20.04 -> 22.04

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: tftpd-hpa 5.2+20150808-1.2build2
ProcVersionSignature: Ubuntu 5.4.0-177.197-generic 5.4.268
Uname: Linux 5.4.0-177-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed May 1 08:49:28 2024
ErrorMessage: installed tftpd-hpa package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-11-15 (1993 days ago)
InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04
PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.3
 apt 2.4.12
SourcePackage: tftp-hpa
Title: package tftpd-hpa 5.2+20150808-1.2build2 failed to install/upgrade: installed tftpd-hpa package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to jammy on 2024-05-01 (0 days ago)

[Paride Legovini (paride)]

Hello and thanks for this bug report. I tried reproducing this issue by

1. installing tftpd-hpa on a clean Focal system (LXD container)
2. checking that tftpd-hpa is running fine
3. upgrading to Jammy
4. checking that tftpd-hpa is running fine

The upgrade went fine and the updated tftpd-hpa is functional. Was tftpd-hpa functional before the upgrade? Are you able to reproduce the issue with your configuration? I'm marking this report as Incomplete for now.

[Nigel Hathaway (nhathaway)]

Whether it was working previously is a good question to which I don't know the answer. Probably not.

It didn't leave a broken system with any half-installed package.

'systemctl status tftpd-hpa' reveals it fails to start.

I purged and re-installed, and I get the same error on installed, and it is purely caused by it failing to start the service.

The cause is this: in.tftpd[418904]: cannot bind to local IPv4 socket: Address already in use

The reason is because we have dnsmasq serving on that port.

I have now disabled tftpd-hpa.

Looks like a false alarm.

[Mitchell Dzurick (mitchdz)]

Thank you for the response Nigel!

> Looks like a false alarm

Would you like to close this bug then?

I'm also curious how often this issue occurs, maybe the maintainer script should be improved to check for port availability before attempting to start the unit.