Paramétrage de bind9 (1:9.8.1.dfsg.P1-4ubuntu0.21) ... rndc-confgen: create keyfile: file not found dpkg : erreur de traitement de bind9 (--configure) : le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 Des erreurs ont été rencontrées pendant l'exécution : bind9 E: Sub-process /usr/bin/dpkg returned an error code (1)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Paramétrage de bind9 (1:9.8.
rndc-confgen: create keyfile: file not found
dpkg : erreur de traitement de bind9 (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Des erreurs ont été rencontrées pendant l'exécution :
bind9
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bind9 1:9.8.1.
ProcVersionSign
Uname: Linux 3.2.0-23-
ApportVersion: 2.0.1-0ubuntu17.15
AptOrdering: bind9: Configure
Architecture: i386
Date: Mon Mar 6 01:38:54 2017
DpkgHistoryLog:
Start-Date: 2017-03-06 01:38:52
Commandline: apt-get install --fix-missing bind9
DuplicateSignature: package:
ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
RelatedPackageV
bind9utils 1:9.8.1.
apparmor 2.7.102-0ubuntu3.10
SourcePackage: bind9
Title: package bind9 1:9.8.1.
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
mtime.conffile.
tags: | removed: need-duplicate-check |
Hello and thank you for filing this bug report!
Setting bind9 (1: 9.8.1.dfsg. P1-4ubuntu0. 21) ...
* Starting domain name service ... bind9 ESC [80G
ESC [74G [ESC [31mfailESC [39; 49m]
Invoke-rc.d: initscript bind9, action "start" failed.
Dpkg: bind9 processing error (--configure):
The installed post-installation script subprocess returned a status output error 1
It seems like you have kept possbly a previous bind9 configuration (/etc/bind/ named.conf. local is modified) and perhaps bind9 is now able to start. Can you verify that bind9 is able to start?
Thanks,
Nish