[SOLVED]Unable to install anything with apt

[wksmeditate]

The aptitude install command and aptitude safe-upgrade do not complete for me. Whenever I run these commands, I receive many messages stating:

Code: Select all

insserv: Starting vpnagentd_init depends on rmnologin and therefore on system facility `$all' which can not be true!

I am using Debian Squeeze. Here is the output for uname -a:

Code: Select all

Linux Debian 2.6.32-5-686 #1 SMP Tue Jun 1 04:59:47 UTC 2010 i686 GNU/Linux

Due to the length of the output, I will only post the beginning(ish) and end, because the middle is mostly "insserv: Starting vpnagentd_init [...]" statements. Here is the beginning output for aptitude safe-upgrade after I had agreed to install new packages:

Code: Select all

33 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/37.9MB of archives. After unpacking 8,192B will be used.
Writing extended state information...
Setting up util-linux (2.17.2-3.1) ...
insserv: warning: script 'K01vpnagentd_init' missing LSB tags and overrides
insserv: warning: script 'vpnagentd_init' missing LSB tags and overrides
insserv: There is a loop between service rmnologin and mountnfs if started
insserv:  loop involving service mountnfs at depth 9
insserv:  loop involving service nfs-common at depth 8
insserv: Starting vpnagentd_init depends on rmnologin and therefore on system facility `$all' which can not be true!

The end of my aptitude output is:

Code: Select all

insserv: There is a loop between service rmnologin and mountall-bootclean if started
insserv:  loop involving service mountall-bootclean at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing util-linux (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 util-linux
Setting up util-linux (2.17.2-3.1) ...
Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...
Initializing package states...
Writing extended state information...
Reading task descriptions...

EDIT: Here are my sources.list

Code: Select all

# 
# deb cdrom:[Debian GNU/Linux testing _Squeeze_ - Official Snapshot i386 NETINST Binary-1 20100612-04:03]/ squeeze main

#deb cdrom:[Debian GNU/Linux testing _Squeeze_ - Official Snapshot i386 NETINST Binary-1 20100612-04:03]/ squeeze main

deb http://ftp.us.debian.org/debian/ squeeze main
deb-src http://ftp.us.debian.org/debian/ squeeze main

deb http://security.debian.org/ squeeze/updates main
deb-src http://security.debian.org/ squeeze/updates main

deb http://ftp.us.debian.org/debian/ squeeze main contrib non-free

What can I do to be able to install using aptitude once again?

[kedaha]

Hi!
May be due to a bug. Did you install freevo?

[wksmeditate]

I did not install freevo. I am also unable to remove programs using the package manager it seems. These are the files it wants to update:

Code: Select all

The following packages will be upgraded:
  acpi-support-base bsdutils debhelper firmware-iwlwifi iptables iso-codes 
  libc-ares2 libcomerr2 libcurl3 libcurl3-gnutls libdevmapper1.02.1 
  libdrm-intel1 libdrm-nouveau1 libdrm-radeon1 libdrm2 libenca0 
  libmetacity-private0 libmng1 libmodplug0c2 libpango1.0-0 
  libpango1.0-common libparted0debian1 libss2 metacity metacity-common 
  mobile-broadband-provider-info mutt nvidia-glx nvidia-kernel-dkms 
  nvidia-kernel-source udisks usbutils x11-utils 
The following partially installed packages will be configured:
  util-linux 
The following packages are RECOMMENDED but will NOT be installed:
  nvidia-vdpau-driver 

Could my problem have something to do with util-linux being only partially installed?

[kedaha]

Just one or two suggestions because I'm no expert so I hope someone else can also offer advice. You can always send in a bug report using the report bug tool. When did this problem start? Type "history" in the root terminal and locate the last thing you did before it occurred.
After googling the error messages and finding this bug report with the subject: "Many insserv warnings "depends on rmnologin" it seems you have a similar problem. From the report it can be inferred that the problem could be solved by purging a conflicting program whose init scripts cause trouble with insserv.

[bugsbunny]

The problem appears to be the third party Cisco software you have installed. Also what version of Debian are you running?

[wksmeditate]

To solve this problem I deleted the directory where the Cisco AnyConnect VPN Client had been installed to (/opt/Cisco/) and then removed the init.d file called vpnagentd. I should have searched google for vpnagentd rather than the long error message. Instead of looking for key terms within the error message, I simply searched google for an already solved problem that matched my own, but unfortunately just found similar issues due to other conflicting programs (nothing regarding my vpn client). This really wasn't a Debian problem and was just a dumb user issue. Next time I install something I will be sure to restart my computer to ensure that no unexpected issues appear with the newly installed software.

[bugsbunny]

If you need a Cisco vpn client try checking out vpnc (found in lenny as well as squeeze/sid) or openconnect (squeeze/sid)

They both have plugins for network-manager (if you use it) network-manager-vpnc and network-manager-openconnect

[manawiz]

I hit this same problem, have used vpnc before, and never intentionally installed the LSB-less Cisco proprietary vpn client. The problem was an SSL vpn I need to use for my company had silently installed the offending component; still not quite sure how it did that, but it did. I solved the problem without uninstalling, since I need the SSL vpn, by adding these LSB headers to /etc/init.d/vpnagentd_init:

root@i7mana:/etc/init.d# cat vpnagentd_init
#!/bin/sh

### BEGIN INIT INFO
# Provides: vpnagentd_init
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start Cisco vpn agent daemon at boot time
# Description: Cisco vpn agent daemon (believe installed by company ssl client)
### END INIT INFO
...

After that regenerating the initramfs was error-free.

[timblaktu]

Another problem with the Cisco client on Debian systems is that the install script vpn_install.sh doesn't successfully install the vpnagentd_init service. It relies on chkconfig, which is not installed on Debian systems by default. The symptom of this problem is that when you run the vpnui, the GUI flickers on the screen for a moment, but vanishes before you can see the error. If you look in the cisco log, you will see evidence of the vpnagentd_init service not being available. If you run vpn_uninstall.sh, install chkconfig via aptitude, then rerun vpn_install.sh the client works properly.

I also found that I get the same aptitude errors the OP mentioned when I 'sudo aptitude upgrade' without having performed the aforementioned steps.

[romain145]

To solve this problem I deleted the directory where the Cisco AnyConnect VPN Client had been installed to (/opt/Cisco/) and then removed the init.d file called vpnagentd. I should have searched google for vpnagentd rather than the long error message. Instead of looking for key terms within the error message, I simply searched google for an already solved problem that matched my own, but unfortunately just found similar issues due to other conflicting programs (nothing regarding my vpn client). This really wasn't a Debian problem and was just a dumb user issue. Next time I install something I will be sure to restart my computer to ensure that no unexpected issues appear with the newly installed software.

More than 1 year after : thank you for this usefull post
And shame on Cisco...

[gcb]

think i also had this problem. what i *think* was the cause:

1. installed vmware-player
2. aptitude update updated kernel from 3.1 to 3.2

after that initscripts died complaining about infinite loops...

Code: Select all

...repeat those lines ad nauseum...
insserv:  loop involving service mountnfs-bootclean at depth 12
insserv: There is a loop between service minissdpd and mountkernfs if started
insserv:  loop involving service mountkernfs at depth 1
insserv:  loop involving service vmware-USBArbitrator at depth 1
insserv:  loop involving service kbd at depth 13
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing initscripts (--configure):
 subprocess installed post-installation script returned error exit status 1

the fix was:

Code: Select all

sudo mv /etc/init.d/vmware* ~/init.vmware/

[mikelj]

I hit this same problem, have used vpnc before, and never intentionally installed the LSB-less Cisco proprietary vpn client. The problem was an SSL vpn I need to use for my company had silently installed the offending component; still not quite sure how it did that, but it did. I solved the problem without uninstalling, since I need the SSL vpn, by adding these LSB headers to /etc/init.d/vpnagentd_init:

root@i7mana:/etc/init.d# cat vpnagentd_init
#!/bin/sh

### BEGIN INIT INFO
# Provides: vpnagentd_init
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start Cisco vpn agent daemon at boot time
# Description: Cisco vpn agent daemon (believe installed by company ssl client)
### END INIT INFO
...

After that regenerating the initramfs was error-free.

This is a Google/forums/user miracle. Thanks so much for posting this to a fixed problem. Shame on Cisco indeed.

I can't tell you how much I appreciate this.

[linux001]

I hit this same problem, have used vpnc before, and never intentionally installed the LSB-less Cisco proprietary vpn client. The problem was an SSL vpn I need to use for my company had silently installed the offending component; still not quite sure how it did that, but it did. I solved the problem without uninstalling, since I need the SSL vpn, by adding these LSB headers to /etc/init.d/vpnagentd_init:

root@i7mana:/etc/init.d# cat vpnagentd_init
#!/bin/sh

### BEGIN INIT INFO
# Provides: vpnagentd_init
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start Cisco vpn agent daemon at boot time
# Description: Cisco vpn agent daemon (believe installed by company ssl client)
### END INIT INFO
...

After that regenerating the initramfs was error-free.

Nearly five years later, I thank you for this advice, which resolved failure on my Debian system of the apt package management tool in the presence of a concurrent Cisco vpn installation. As others have said, shame on Cisco for releasing poorly debugged code.