error after running out of disk

Bug #1077740 reported by v1nce
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After i ran out of disk space I get this error after a daily update
(I run a french ubuntu 12.04 so the following messages are in French but translation would be "mais la version x est installée" = "but the x version is installed")

Les paquets suivants ont des dépendances non-satisfaites :

mysql-server-5.5: PreDepends: mysql-common (>= 5.5.24-0ubuntu0.12.04.1) mais la version 5.5.28-0ubuntu0.12.04.2 est installée
                  Depends: mysql-client-5.5 (>= 5.5.24-0ubuntu0.12.04.1) mais la version 5.5.28-0ubuntu0.12.04.2 est installée
                  Depends: perl (>= 5.6) mais la version 5.14.2-6ubuntu2.1 est installée
                  Depends: zlib1g (>= 1:1.1.4) mais la version 1:1.2.3.4.dfsg-3ubuntu4 est installée
                  Depends: upstart-job mais c'est un paquet virtuel
                  Depends: mysql-server-core-5.5 (= 5.5.24-0ubuntu0.12.04.1) mais la version 5.5.28-0ubuntu0.12.04.2 est installée

or

installArchives() failed: dpkg: dependency problems prevent configuration of mysql-server-5.5:
 mysql-server-5.5 depends on mysql-server-core-5.5 (= 5.5.24-0ubuntu0.12.04.1); however:
  Version of mysql-server-core-5.5 on system is 5.5.28-0ubuntu0.12.04.2.
dpkg: error processing mysql-server-5.5 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-server-5.5; however:
  Package mysql-server-5.5 is not configured yet.
dpkg: error processing mysql-server (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
Errors were encountered while processing:
 mysql-server-5.5
 mysql-server
Error in function:
dpkg: dependency problems prevent configuration of mysql-server-5.5:
 mysql-server-5.5 depends on mysql-server-core-5.5 (= 5.5.24-0ubuntu0.12.04.1); however:
  Version of mysql-server-core-5.5 on system is 5.5.28-0ubuntu0.12.04.2.
dpkg: error processing mysql-server-5.5 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-server-5.5; however:
  Package mysql-server-5.5 is not configured yet.
dpkg: error processing mysql-server (--configure):
 dependency problems - leaving unconfigured

I don't understand what is wrong.
There's enough disk space right now (6gb)
I "fixed" this by using dpkg --force-depends -i mysql-server_5.5.28-0ubuntu0.12.04.2_all.deb

In cache I got the following files
libmysqlclient18_5.5.28-0ubuntu0.12.04.2_amd64.deb
libqt4-sql-mysql_4%3a4.8.1-0ubuntu4.3_amd64.deb
mysql-client-5.5_5.5.28-0ubuntu0.12.04.2_amd64.deb
mysql-client-core-5.5_5.5.28-0ubuntu0.12.04.2_amd64.deb
mysql-common_5.5.28-0ubuntu0.12.04.2_all.deb
mysql-server_5.5.28-0ubuntu0.12.04.2_all.deb
mysql-server-5.5_5.5.28-0ubuntu0.12.04.2_amd64.deb
mysql-server-core-5.5_5.5.28-0ubuntu0.12.04.2_amd64.deb

System : ubuntu 12.04 64bits FR
It didn't occur after a system upgrade but in a daily update

Revision history for this message
Daniel Hartwig (wigs) wrote : Re: [Bug 1077740] [NEW] error after running out of disk

On 12 November 2012 06:11, v1nce <email address hidden> wrote:
> I "fixed" this by using dpkg --force-depends -i mysql-server_5.5.28-0ubuntu0.12.04.2_all.deb

Although that stops dpkg complaining, the problem likely still exists
and is maybe worse. Better to use:
# apt-get install -f

to make sure that required packages are installed.

Revision history for this message
v1nce (vincent-pennec) wrote :

I'm not sure but I think I tried apt-get install -f before manual installation (with no luck).
Now when I run apt-get install -f it's ok (0,0,0).

I don't really understand what it complained for as I got all the "missing" packages (maybe except for upstart-job (I don't know how to query virtual package)).

I looked at mysql and it was up and running after reboot so i think my command was rather safe.

I know this was a poor bug report (I should have waited before trying to fix it myself) so it can be closed anytime because I consider it fixed.
I reported it because the message 'Depends: foo (>= x) but version y is installed' looks odd to me

Revision history for this message
v1nce (vincent-pennec) wrote :

with y>x

Revision history for this message
Daniel Hartwig (wigs) wrote : Re: [Bug 1077740] Re: error after running out of disk

On 12 November 2012 21:05, v1nce <email address hidden> wrote:
> I'm not sure but I think I tried apt-get install -f before manual installation (with no luck).
> Now when I run apt-get install -f it's ok (0,0,0).
>
> I don't really understand what it complained for as I got all the
> "missing" packages (maybe except for upstart-job (I don't know how to
> query virtual package)).

Although older versions of those packages are installed, the
updated mysql-server states that it requires the more recent
versions, as indicated by the error:

 mysql-server-5.5: PreDepends: mysql-common (>=
5.5.24-0ubuntu0.12.04.1) mais la version 5.5.28-0ubuntu0.12.04.2 est
installée
                   Depends: mysql-client-5.5 (>=
5.5.24-0ubuntu0.12.04.1) mais la version 5.5.28-0ubuntu0.12.04.2 est
installée

The newer packages downloaded (you see them in /var/cache/apt), but
failed to install, presumably due to the disk space error.

>
> I looked at mysql and it was up and running after reboot so i think my
> command was rather safe.

The dpkg command is unsafe is because it ignores the package
dependencies. The program may actually run with the older packages,
and there may not even be any problems, but this can generally not be
assumed, otherwise it would not require particular versions of those
packages.

>
> I know this was a poor bug report (I should have waited before
> trying to fix it myself) so it can be closed anytime because I
> consider it fixed.

I am glad that you fixed your system.

The only issue here really is that apt proceeded with the operation
even though it would fail due to disk space. I believe this is
already reported, and the situation is unlikely to improve much
because this is something very hard for apt to *properly* check.

Generally, it is up to the system administrator to keep disk space
issues under control. Software can not reliably do this for you.

> I reported it because the message 'Depends: foo (>= x) but version y
> is installed' looks odd to me

The first part uses the packaging dependency format as this is the
best way to convey exactly which dependency causes the problem, and
what it's requirements are. Although not the most correct for natural
language, it does read well enough, and changing it is undesirable
because that may lead to ambiguity and make the task of diagnosing
problems (for packagers, developers, people familiar with that syntax)
a bit slower.

Regards

Revision history for this message
v1nce (vincent-pennec) wrote :

> The only issue here really is that apt proceeded with the operation
even though it would fail due to disk space. I believe this is
already reported, and the situation is unlikely to improve much
because this is something very hard for apt to *properly* check.

(Now) I understand that.
Before a daily update I was warned that there was not enough disk space to install all packages. So I tried to split the installation by choosing only some packages.
So, yes, I think I can put the blame on me and not onto the apt app.

> The first part uses the packaging dependency format as this is the
best way to convey exactly which dependency causes the problem, and
what it's requirements are. Although not the most correct for natural
language, it does read well enough, and changing it is undesirable
because that may lead to ambiguity and make the task of diagnosing
problems (for packagers, developers, people familiar with that syntax)
a bit slower.

I don't agree. I don't know if this is because of french translation but the text is clearly misleading to me.

mysql-server-5.5: ...
                  Depends: mysql-client-5.5 (>= 5.5.24-0ubuntu0.12.04.1) mais la version 5.5.28-0ubuntu0.12.04.2 est installée

can be read (by me) as

You try to update(*) mysql-server-5.5. To do this, you need to install first mysql-client-5.5 in a version that is above 5.5.24... but (you can't do it because) version 5.5.28... is (already) installed.

So (for me) it reads as the apt doesn't understand that 5.5.28 > 5.5.24.

I think plain text would be easier to read for anybody (unless there are apps that grep the output of aptcommand ?). At least for (unexperienced) reporters. May be a switch for a compact display for 'power users'

(*) with no more information this is what I read(/expect). From the detailed error I guess the real error occured when trying to (re)configure the sqlserver (what I didn't ask for) So I think that at least AFTER THE FAULTY PACKAGE NAME THERE SHOULD BE AN INDICATION OF WHAT ACTION FAILED. Was it installation, removal, update, configuration of installed package, cleaning after removal...

Just my 2 cents.

Revision history for this message
Daniel Hartwig (wigs) wrote :

On 13 November 2012 21:40, v1nce <email address hidden> wrote:
> I don't agree. I don't know if this is because of french translation but the text is clearly misleading to me.
>
> mysql-server-5.5: ...
> Depends: mysql-client-5.5 (>= 5.5.24-0ubuntu0.12.04.1) mais la version 5.5.28-0ubuntu0.12.04.2 est installée
>
> can be read (by me) as
>
> You try to update(*) mysql-server-5.5. To do this, you need to install
> first mysql-client-5.5 in a version that is above 5.5.24... but (you
> can't do it because) version 5.5.28... is (already) installed.
>
> So (for me) it reads as the apt doesn't understand that 5.5.28 > 5.5.24.

You are right, I didn't read the version numbers well enough.

It does seem that apt is confused about the first few, the only
dependency that is a problem is mysql-server-core-5.5.

Revision history for this message
Pander (pander) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apt (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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