package ntp 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1. That was during upgrade from Ubuntu 20.04 LTS to Ubuntu 22.4 LTS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ntp (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
That was during upgrade from Ubuntu 20.04 LTS to Ubuntu 22.4 LTS
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: ntp 1:4.2.8p15+
ProcVersionSign
Uname: Linux 5.4.0-173-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: eu-west-1
CloudSubPlatform: metadata (http://
Date: Fri Mar 8 15:47:51 2024
Ec2AMI: ami-08d173829f9
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2Availability
Ec2Imageid: ami-08d173829f9
Ec2InstanceType: t2.large
Ec2Instancetype: t2.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: eu-west-1
ErrorMessage: installed ntp package post-installation script subprocess returned error exit status 1
ProcCmdline: BOOT_IMAGE=
Python3Details: /usr/bin/
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageV
dpkg 1.21.1ubuntu2.3
apt 2.4.11
SourcePackage: ntp
Title: package ntp 1:4.2.8p15+
UpgradeStatus: Upgraded to jammy on 2024-03-08 (0 days ago)
tags: | removed: need-duplicate-check |
After the error reported, the upgrade process gave the following output
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
Setting up ntp (1:4.2. 8p15+dfsg- 1ubuntu2) ... netif.service is a disabled or a static unit not running, not starting it. system/ ntp.service; enabled; vendor preset: enabled) /usr/lib/ ntp/ntp- systemd- wrapper (code=exited, status=1/FAILURE)
ntp-systemd-
insserv: warning: current stop runlevel(s) (1) of script `ntp' overrides LSB defaults (empty).
Job for ntp.service failed because the control process exited with error code.
See "systemctl status ntp.service" and "journalctl -xeu ntp.service" for details.
invoke-rc.d: initscript ntp, action "start" failed.
× ntp.service - Network Time Service
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Fri 2024-03-08 15:57:10 UTC; 6ms ago
Docs: man:ntpd(8)
Process: 98959 ExecStart=
Mar 08 15:57:10 ip-172-31-35-186 ntpd[98984]: proto: precision = 0.625 usec (-21) share/zoneinfo/ leap-seconds. list'): good hash signature share/zoneinfo/ leap-seconds. list'): loaded, expire= 2024-12- 28T00:00: 00Z last=2017- 01-01T00: 00:00Z ofs=37
Mar 08 15:57:10 ip-172-31-35-186 ntpd[98984]: basedate set to 2022-02-04
Mar 08 15:57:10 ip-172-31-35-186 ntpd[98984]: gps base set to 2022-02-06 (week 2196)
Mar 08 15:57:10 ip-172-31-35-186 ntpd[98984]: leapsecond file ('/usr/
Mar 08 15:57:10 ip-172-31-35-186 ntpd[98984]: leapsecond file ('/usr/
Mar 08 15:57:10 ip-172-31-35-186 ntpd[98984]: unable to bind to wildcard address :: - another process may be running - EXITING
Mar 08 15:57:10 ip-172-31-35-186 ntpd[98959]: daemon child exited with code 1
Mar 08 15:57:10 ip-172-31-35-186 systemd[1]: ntp.service: Control process exited, code=exited, status=1/FAILURE
Mar 08 15:57:10 ip-172-31-35-186 systemd[1]: ntp.service: Failed with result 'exit-code'.
Mar 08 15:57:10 ip-172-31-35-186 systemd[1]: Failed to start Network Time Service.
invoke-rc.d: release upgrade in progress, error is not fatal
Upgrade complete
The upgrade has completed but there were errors during the upgrade
process.