'Software index is broken' after upgrade from Feisty to Gutsy

Bug #154992 reported by Dan McCormick
6
Affects Status Importance Assigned to Milestone
xsp (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After upgrading from Feisty to Gutsy an error appears to have occurred with upgrade of mono-xsp
that now has the 'software index' broken leaving me unable to Add/Remove software.

Error message is...
---------------------------------------------------------------------------------------------------------------------------
Software index is broken

It is impossible to install or remove any software. Please use the package
manager "Synaptic" or run "sudo apt-get install -f" in a terminal to fix
this issue at first.
---------------------------------------------------------------------------------------------------------------------------

Neither Synaptic nor apt-get will fix the problem for me (information provided below).
So how do I proceed?

When I run the Synaptic package manager it shows the following 'Broken Dependencies'
---------------------------------------------------------------------------------------------------------------------------
Package | Installed Version | Latest Version | Description
mono-xsp 1.2.1-1ubuntu1 1.2.4-1.1ubunutu1 simple web server to run...
---------------------------------------------------------------------------------------------------------------------------

The Synaptic package manager allows options of 'upgrade', 'removal' and 'complete removal'
but attempts to perform these options all result in failure.

Apply 'upgrade' and we get
---------------------------------------------------------------------------------------------------------------------------
E: /var/cache/apt/archives/mono-xsp_1.2.4-1.1ubuntu1_all.deb: subprocess
pre-installation script returned error exit status 2
---------------------------------------------------------------------------------------------------------------------------

Apply 'removal' or 'complete removal' and we get
---------------------------------------------------------------------------------------------------------------------------
E: mono-xsp: subprocess pre-removal script returned error exit status 2
---------------------------------------------------------------------------------------------------------------------------

When I run "sudo apt-get install -f" I get the following information
---------------------------------------------------------------------------------------------------------------------------
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
libcairo-ruby libatk1-ruby libswfdec0.3 libflac++5c2 liboggflac3 libjack0.100.0-0 libglib2-ruby
libpango1-ruby libgdk-pixbuf2-ruby librexml-ruby mono-xsp-base mono-xsp libgtk2-ruby
libquicktime0
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  mono-xsp
The following packages will be upgraded:
  mono-xsp
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/69.7kB of archives.
After unpacking 4096B of additional disk space will be used.
Do you want to continue [Y/n]?
Preconfiguring packages ...
(Reading database ... 150523 files and directories currently installed.)
Preparing to replace mono-xsp 1.2.1-1ubuntu1 (using .../mono-xsp_1.2.4-1.1ubuntu1_all.deb) ...
 * Stopping XSP WebServer mono-xsp /etc/init.d/mono-xsp: 95: Syntax error: Bad fd number
invoke-rc.d: initscript mono-xsp, action "stop" failed.
dpkg: error processing /var/cache/apt/archives/mono-xsp_1.2.4-1.1ubuntu1_all.deb (--unpack):
 subprocess pre-installation script returned error exit status 2
postinst failed `abort-upgrade'
Errors were encountered while processing:
 /var/cache/apt/archives/mono-xsp_1.2.4-1.1ubuntu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
---------------------------------------------------------------------------------------------------------------------------

Revision history for this message
Daniel Hahler (blueyed) wrote :

It seems like stopping the old mono-xsp service fails.
I could not reproduce it by installing it from gutsy and stopping it.

Do you have manually edited the init script?

Please attach your current /etc/init.d/mono-xsp.

Changed in xsp:
status: New → Incomplete
Revision history for this message
Dan McCormick (dan-mccormick) wrote :

> It seems like stopping the old mono-xsp service fails.
> I could not reproduce it by installing it from gutsy and stopping it.
>
> Do you have manually edited the init script?
>
> Please attach your current /etc/init.d/mono-xsp.
>

I have not manually edited the init script for mono-xsp (or any of the init scripts for that matter).

My current init file has been attached.

Revision history for this message
Dan McCormick (dan-mccormick) wrote :

Managed to fix software index.

1) get PID of offending daemon

     sudo ps aux | grep -v grep | grep 'xsp.exe' | cut -c 10-15

2) manually kill offending daemon

3) sudo apt-get update

4) sudo apt-get install -f

Still don't understand why the automated update procedure got me into the bad state, but as far as I'm concerned at this point we can consider this issue closed.

Revision history for this message
Daniel Hahler (blueyed) wrote :

I've thought that the 95 in "95: Syntax error: Bad fd number" would refer to the line number in the init script, but it does not.

Revision history for this message
Mads Peter Rommedahl (lhademmor) wrote :

This bug report is being closed due to your last comment. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at [WWW] https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in xsp:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.