Estoy trabajando en una caja Debian wheezy x64, con dist-upgrade a:
Debian 7.7 (wheezy) 64-bit
kernel Linux 3.2.0-4-amd64
Está configurado con Linux RAID10, dm-crypt/LUKS y LVM. He instalado VirtualBox desde virtualbox-4.3_4.3.20-96996~Debian~wheezy_amd64.deb.
Aunque arranca y ejecuta software, algo en insserv no funciona. Por ejemplo:
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)
Recibo básicamente los mismos errores con root@debian:/home/user# apt-get install -f. Sin embargo, algunos otros paquetes se instalan correctamente:
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)
Pero la instalación de iptables-persistent aún no se completa.
Actualizar los valores predeterminados del nivel de ejecución común de nfs no ayuda y muestra los mismos errores:
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
Google no me ha mostrado nada útil. Yla única pregunta similar aquíafortunadamente no es relevante.
¿Cómo puedo solucionar esto? Entiendo que la discrepancia en el nivel de ejecución de nfs-common pueda ser relevante, pero no entiendo cómo proceder.
Editar: según lo sugerido por wurtel, dado que no estoy usando nfs, eliminé mountnfs, nfs-common y rpcbind. Tuve que eliminarlos en ese orden para evitar errores de bucle. Pero la configuración de los valores predeterminados falló:
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
Lo bueno es que una vez que logré eliminar mountnfs, nfs-common y rpcbind nuevamente, pude instalar y configurar iptables-persistent. Sin embargo, me quedan update-rc.d: error: unable to read /etc/init.d/mountnfslos valores de nivel de ejecución de inicio predeterminados que no coinciden para rpcbind y nfs-common.
Peor aún, encuentro que la configuración predeterminada falla para otros paquetes en /etc/default/. Para algunos, es "incapaz de leer". Por ejemplo:
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 otros, es la discrepancia del nivel de ejecución de inicio predeterminado. Por ejemplo:
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)
Y el resto funciona. Por ejemplo:
root@debian:/etc/default# update-rc.d exim4 defaults
update-rc.d: using dependency based boot sequencing
Sin embargo, una vez eliminados mountnfs, nfs-common y rpcbind, no veo errores de bucle para ninguno de ellos. Entonces eso parece ser simplemente un síntoma de los errores de rc.d.
Pero creo que esa debería ser otra cuestión.
Respuesta1
Tuve un problema similar. Eliminar initscripts.*de /var/lib/dpkg/info
Ejecutar apt-get install -fdespués de eso soluciona el problema.
La solución fue tomada deaquí