localzuk Posted December 2, 2011 Posted December 2, 2011 I've just tried to run an apt-get upgrade on the debian squeeze box which runs our Fog install and am getting a rather long error message, basically telling me that various loops will occur if I try. Setting up apache2.2-common (2.2.16-6+squeeze4) ...^Minsserv: warning: script 'S20FOGMulticastManager' missing LSB tags and overrides^M insserv: warning: script 'S20FOGScheduler' missing LSB tags and overrides^M insserv: warning: script 'S20FOGImageReplicator' missing LSB tags and overrides^M insserv: warning: script 'FOGScheduler' missing LSB tags and overrides^M insserv: warning: script 'FOGImageReplicator' missing LSB tags and overrides^M insserv: warning: script 'FOGMulticastManager' missing LSB tags and overrides^M insserv: There is a loop at service stop-bootlogd if started^M insserv: Starting FOGMulticastManager depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M insserv: Starting FOGScheduler depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M insserv: Starting FOGImageReplicator depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M insserv: Starting FOGMulticastManager depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M insserv: Starting FOGScheduler depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M insserv: Starting FOGImageReplicator depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M insserv: Starting FOGMulticastManager depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M insserv: Starting FOGScheduler depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M insserv: Starting FOGImageReplicator depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M insserv: Starting FOGMulticastManager depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M insserv: Starting FOGScheduler depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M insserv: Starting FOGImageReplicator depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M insserv: Starting FOGMulticastManager depends on stop-bootlogd and therefore on system facility `$all' which can not be true!^M (it goes on and on). Running dpkg -C returns the following The following packages have been unpacked but not yet configured. They must be configured using dpkg --configure or the configure menu option in dselect for them to work: clamav anti-virus utility for Unix - command-line interface apache2-mpm-prefork Apache HTTP Server - traditional non-threaded model apache2 Apache HTTP Server metapackage The following packages are only half configured, probably due to problems configuring them the first time. The configuration should be retried using dpkg --configure or the configure menu option in dselect: gdm3 Next generation GNOME Display Manager clamav-freshclam anti-virus utility for Unix - virus database update utili openssh-server secure shell (SSH) server, for secure access from remote apache2.2-common Apache HTTP Server common files cups Common UNIX Printing System - server and trying to do a dpkg --configure on any of those returns the above list of loop stuff. Any ideas how I can finish my update without it going weird?
localzuk Posted December 2, 2011 Author Posted December 2, 2011 After searching for random snippets of the errors being spat out, I discovered a page on the fogproject page where someone else had encountered this. Basically, the fix is to move the FOG* files out of /etc/init.d/ directory, do the apt-get upgrade, then move them back. 1
jinnantonnixx Posted December 2, 2011 Posted December 2, 2011 If it's of any use, I got into a hell of a mess with Squid one time and the machine was inside-out. Using dpkg --remove --force-remove-reinstreq got me out of this mess; I found it here: apt-get how to fix very broken packages | Shadows of epiphany
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now