Estou trabalhando em uma caixa Debian wheezy x64, com dist-upgrade para:
Debian 7.7 (wheezy) 64-bit
kernel Linux 3.2.0-4-amd64
Está configurado com Linux RAID10, dm-crypt/LUKS e LVM. Eu instalei o VirtualBox do virtualbox-4.3_4.3.20-96996~Debian~wheezy_amd64.deb.
Embora inicialize e execute software, algo no insserv está quebrado. Por exemplo:
root@debian:/home/user# apt-get install iptables-persistent
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
iptables-persistent
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/10.3 kB of archives.
After this operation, 61.4 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package iptables-persistent.
(Reading database ... 133127 files and directories currently installed.)
Unpacking iptables-persistent (from .../iptables-persistent_0.5.7_all.deb) ...
Setting up iptables-persistent (0.5.7) ...
insserv: There is a loop between service mountnfs and nfs-common if started
insserv: loop involving service nfs-common at depth 12
insserv: loop involving service rpcbind at depth 10
insserv: loop involving service mountnfs at depth 13
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing iptables-persistent (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
iptables-persistent
E: Sub-process /usr/bin/dpkg returned an error code (1)
Recebo basicamente os mesmos erros com root@debian:/home/user# apt-get install -f. No entanto, alguns outros pacotes foram instalados com sucesso:
root@debian:/home/user# apt-get install p7zip
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
p7zip
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 386 kB of archives.
After this operation, 1,010 kB of additional disk space will be used.
Get:1 http://ftp.at.debian.org/debian/ wheezy/main p7zip amd64 9.20.1~dfsg.1-4 [386 kB]
Fetched 386 kB in 1s (299 kB/s)
Selecting previously unselected package p7zip.
(Reading database ... 133131 files and directories currently installed.)
Unpacking p7zip (from .../p7zip_9.20.1~dfsg.1-4_amd64.deb) ...
Processing triggers for man-db ...
Setting up iptables-persistent (0.5.7) ...
insserv: There is a loop between service mountnfs and nfs-common if started
insserv: loop involving service nfs-common at depth 12
insserv: loop involving service rpcbind at depth 10
insserv: loop involving service mountnfs at depth 13
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing iptables-persistent (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up p7zip (9.20.1~dfsg.1-4) ...
Errors were encountered while processing:
iptables-persistent
E: Sub-process /usr/bin/dpkg returned an error code (1)
Mas a instalação do iptables-persistent ainda não foi concluída.
A atualização dos padrões de nível de execução nfs-common não ajuda e mostra os mesmos erros:
root@debian:/home/user# update-rc.d nfs-common defaults
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match nfs-common Default-Start values (2 3 4 5 S)
insserv: There is a loop between service mountnfs and nfs-common if started
insserv: loop involving service nfs-common at depth 12
insserv: loop involving service rpcbind at depth 10
insserv: loop involving service mountnfs at depth 13
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
O Google não me mostrou nada de útil. Ea única pergunta semelhante aquifelizmente não é relevante.
Como posso consertar isso? Compreendo que a incompatibilidade de nível de execução para nfs-common possa ser relevante, mas não entendo como proceder.
Editar: conforme sugerido por wurtel, como não estou usando nfs, removi mountnfs, nfs-common e rpcbind. Tive que removê-los nessa ordem, para evitar erros de loop. Mas a definição dos padrões falhou:
root@debian:/home/user# update-rc.d -f rpcbind defaults
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match rpcbind Default-Start values (S 2 3 4 5)
root@debian:/home/user# update-rc.d -f nfs-common defaults
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match nfs-common Default-Start values (2 3 4 5 S)
insserv: There is a loop between service mountnfs and nfs-common if started
insserv: loop involving service nfs-common at depth 14
insserv: loop involving service rpcbind at depth 12
insserv: loop involving service mountnfs at depth 16
insserv: There is a loop between service mountnfs and nfs-common if started
insserv: loop involving service rsyslog at depth 17
root@debian:/home/user# update-rc.d -f mountnfs defaults
update-rc.d: using dependency based boot sequencing
update-rc.d: error: unable to read /etc/init.d/mountnfs
Pelo lado positivo, depois de conseguir remover novamente mountnfs, nfs-common e rpcbind, consegui instalar e configurar o iptables-persistent. No entanto, fiquei com update-rc.d: error: unable to read /etc/init.d/mountnfsos valores de nível de execução inicial padrão incompatíveis para rpcbind e nfs-common.
Pior ainda, acho que a configuração de padrões falha para outros pacotes no /etc/default/. Para alguns, é "incapaz de ler". Por exemplo:
root@debian:/etc/iptables# update-rc.d grub defaults
update-rc.d: using dependency based boot sequencing
update-rc.d: error: unable to read /etc/init.d/grub
Para outros, é a incompatibilidade de nível de execução inicial padrão. Por exemplo:
root@debian:/etc/default# update-rc.d halt defaults
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match halt Default-Start values (none)
update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match halt Default-Stop values (0)
E o resto funciona. Por exemplo:
root@debian:/etc/default# update-rc.d exim4 defaults
update-rc.d: using dependency based boot sequencing
No entanto, com mountnfs, nfs-common e rpcbind removidos, não vejo erros de loop para nenhum deles. Então isso parece ser apenas um sintoma dos erros do rc.d.
Mas isso deveria ser outra questão, eu acho.
Responder1
Eu tive um problema semelhante. Excluir initscripts.*de /var/lib/dpkg/info
Correr apt-get install -fdepois disso resolve o problema.
A solução foi retirada deaqui