RE: apt cache full, mandb update failed

2016-04-21 Thread Bonno Bloksma 
Hi Brian,

>> This morning I wanted to do an apt-get update / upgrade cycle on my 
>> system.  The update went ok, but during the upgrade I got a " No space 
>> left on device" warning.
>> [...]
>> Preparing to replace ssh 1:6.0p1-4+deb7u3 (using 
>> .../ssh_1%3a6.0p1-4+deb7u4_all.deb) ...
>> Unpacking replacement ssh ...
>> Processing triggers for man-db ...
>> /usr/bin/mandb: can't write to /var/cache/man/8774: No space left on 
>> device Processing triggers for hicolor-icon-theme ...
>> Processing triggers for mime-support ...
>> [...]
>> 
>> My /var partition had filled up, it seems out of the 3GB there was 
>> about 2.5GB in /var/cache/apt/archives.  The solution was simple, just 
>> an apt-get autoclean, I now have 2.2GB free on my /var partition. ;-)
>> 
>> But. What wanted apt write to that mandb and was that important?
>
> Apt calls dpkg and it is during the course of installing with dpkg that the 
> triggering process occurs. You can see this by doing
> 
>   dpkg -i /var/cache/apt/archives//openssh-server_1%3a6.0p1-4+deb7u4_i386.deb

Just did that again and it completed normaly. That is what I needed to know, 
now I know the mandb is up2date as well.
Thanks.

>>   /usr/bin/mandb: can't write to /var/cache/man/8774: No space left on 
>> device Was that that man page for ssh or something like that?
>
> Yes. mandb has an interest in what happens in /usr/share/man. Changes there 
> lead to its updating its database.
> For reasons you give it didn't happen, so dpkg issues a *warning*.
> Nothing too serious to stop the unpacking and setting up of all the updated 
> packages.

Well a disk full warning is pretty serious. But I get what you mean, a warning 
from mandb maintenance itself is not serious enough, just the reason why that 
happened.

>> After cleaning up I did another apt-get upgrade but it reported 
>> nothing to do.
>
> This is to be expected, surely. All packages are at their newest versions.

I had hoped the failed mandb update would register somewhere and a second 
attempt to "upgrade" would fix it.
Turns out I needed that dpkg line to do that.

>> So if it failed to update some files why did it 
>> complete anyhow?
> 
> Would you rather the upgrade came to a halt because of some relatively minor 
> issue?

Yes and no, according to apt-get it was a minor issue of a mandb update, the 
roor cause was a majot issue.
>
>  apt-get --reinstall install openssh-server
> 
> could be run after space is freed up.

I did it by running the dpkg line, same end result I guess.
Thank for the explanation and help fixing it.

Bonno Bloksma

Re: apt cache full, mandb update failed

2016-04-20 Thread Brian 
On Wed 20 Apr 2016 at 06:52:22 +, Bonno Bloksma wrote:

> This morning I wanted to do an apt-get update / upgrade cycle on my
> system.  The update went ok, but during the upgrade I got a " No space
> left on device" warning.
> [...]
> Preparing to replace ssh 1:6.0p1-4+deb7u3 (using 
> .../ssh_1%3a6.0p1-4+deb7u4_all.deb) ...
> Unpacking replacement ssh ...
> Processing triggers for man-db ...
> /usr/bin/mandb: can't write to /var/cache/man/8774: No space left on device
> Processing triggers for hicolor-icon-theme ...
> Processing triggers for mime-support ...
> [...]
> 
> My /var partition had filled up, it seems out of the 3GB there was
> about 2.5GB in /var/cache/apt/archives.  The solution was simple, just
> an apt-get autoclean, I now have 2.2GB free on my /var partition. ;-)
> 
> But. What wanted apt write to that mandb and was that important?

Apt calls dpkg and it is during the course of installing with dpkg that
the triggering process occurs. You can see this by doing

  dpkg -i /var/cache/apt/archives//openssh-server_1%3a6.0p1-4+deb7u4_i386.deb
 
>   /usr/bin/mandb: can't write to /var/cache/man/8774: No space left on device
> Was that that man page for ssh or something like that?

Yes. mandb has an interest in what happens in /usr/share/man. Changes
there lead to its updating its database. For reasons you give it didn't
happen, so dpkg issues a *warning*. Nothing too serious to stop the
unpacking and setting up of all the updated packages.

> After cleaning up I did another apt-get upgrade but it reported
> nothing to do.

This is to be expected, surely. All packages are at their newest
versions.

> So if it failed to update some files why did it
> complete anyhow?

Would you rather the upgrade came to a halt because of some relatively
minor issue?

  apt-get --reinstall install openssh-server

could be run after space is freed up.

Re: apt cache full, mandb update failed

2016-04-20 Thread Elimar Riesebieter 
* Bonno Bloksma  [2016-04-20 06:52 +]:

> Hi,
> 
[...]
> 
> My /var partition had filled up, it seems out of the 3GB there was about 
> 2.5GB in /var/cache/apt/archives.
> The solution was simple, just an apt-get autoclean, I now have 2.2GB free on 
> my /var partition. ;-)
> 
> But. What wanted apt write to that mandb and was that important? 
>   /usr/bin/mandb: can't write to /var/cache/man/8774: No space left on device
> Was that that man page for ssh or something like that?
> 
> After cleaning up I did another apt-get upgrade but it reported nothing to do.
> So if it failed to update some files why did it complete anyhow?

Because /var/cache/man/ resides on the apt-get autocleaned /var
partition?

Sigh
Elimar
-- 
  Alles was viel bedacht wird ist bedenklich!;-)
 Friedrich Nietzsche

Re: apt cache full, mandb update failed

2016-04-20 Thread Dan Ritter 
On Wed, Apr 20, 2016 at 06:52:22AM +, Bonno Bloksma wrote:
> Hi,
> 
> This morning I wanted to do an apt-get update / upgrade cycle on my system.
> The update went ok, but during the upgrade I got a " No space left on device" 
> warning.
> [...]
> Preparing to replace ssh 1:6.0p1-4+deb7u3 (using 
> .../ssh_1%3a6.0p1-4+deb7u4_all.deb) ...
> Unpacking replacement ssh ...
> Processing triggers for man-db ...
> /usr/bin/mandb: can't write to /var/cache/man/8774: No space left on device



The good news is that anything in a directory named cache should be a
temporary (but long lived) file that can be regenerated if it
needs to be.

In a tmp directory, on the other hand, you should assume that any file
can be deleted arbitrarily.

And in a spool directory, you should assume that files need to remain
there until their purpose is complete.

apt cache full, mandb update failed

2016-04-20 Thread Bonno Bloksma 
Hi,

This morning I wanted to do an apt-get update / upgrade cycle on my system.
The update went ok, but during the upgrade I got a " No space left on device" 
warning.
[...]
Preparing to replace ssh 1:6.0p1-4+deb7u3 (using 
.../ssh_1%3a6.0p1-4+deb7u4_all.deb) ...
Unpacking replacement ssh ...
Processing triggers for man-db ...
/usr/bin/mandb: can't write to /var/cache/man/8774: No space left on device
Processing triggers for hicolor-icon-theme ...
Processing triggers for mime-support ...
[...]

My /var partition had filled up, it seems out of the 3GB there was about 2.5GB 
in /var/cache/apt/archives.
The solution was simple, just an apt-get autoclean, I now have 2.2GB free on my 
/var partition. ;-)

But. What wanted apt write to that mandb and was that important? 
  /usr/bin/mandb: can't write to /var/cache/man/8774: No space left on device
Was that that man page for ssh or something like that?

After cleaning up I did another apt-get upgrade but it reported nothing to do.
So if it failed to update some files why did it complete anyhow?

Bonno Bloksma


The complete log in case it is needed:
Log started: 2016-04-20  08:18:15
(Reading database ... ^M [.] Reading database ... 100%^M
(Reading database ... 43462 files and directories currently installed.)
Preparing to replace imagemagick-common 8:6.7.7.10-5+deb7u3 (using 
.../imagemagick-common_8%3a6.7.7.10-5+deb7u4_all.deb) ...
Unpacking replacement imagemagick-common ...
Preparing to replace libmagickwand5:i386 8:6.7.7.10-5+deb7u3 (using 
.../libmagickwand5_8%3a6.7.7.10-5+deb7u4_i386.deb) ...
Unpacking replacement libmagickwand5:i386 ...
Preparing to replace libmagickcore5-extra:i386 8:6.7.7.10-5+deb7u3 (using 
.../libmagickcore5-extra_8%3a6.7.7.10-5+deb7u4_i386.deb) ...
Unpacking replacement libmagickcore5-extra:i386 ...
Preparing to replace libmagickcore5:i386 8:6.7.7.10-5+deb7u3 (using 
.../libmagickcore5_8%3a6.7.7.10-5+deb7u4_i386.deb) ...
Unpacking replacement libmagickcore5:i386 ...
Preparing to replace openssh-server 1:6.0p1-4+deb7u3 (using 
.../openssh-server_1%3a6.0p1-4+deb7u4_i386.deb) ...
Unpacking replacement openssh-server ...
Preparing to replace openssh-client 1:6.0p1-4+deb7u3 (using 
.../openssh-client_1%3a6.0p1-4+deb7u4_i386.deb) ...
Unpacking replacement openssh-client ...
Preparing to replace imagemagick 8:6.7.7.10-5+deb7u3 (using 
.../imagemagick_8%3a6.7.7.10-5+deb7u4_i386.deb) ...
Unpacking replacement imagemagick ...
Preparing to replace ssh 1:6.0p1-4+deb7u3 (using 
.../ssh_1%3a6.0p1-4+deb7u4_all.deb) ...
Unpacking replacement ssh ...
Processing triggers for man-db ...
/usr/bin/mandb: can't write to /var/cache/man/8774: No space left on device
Processing triggers for hicolor-icon-theme ...
Processing triggers for mime-support ...
Setting up imagemagick-common (8:6.7.7.10-5+deb7u4) ...
Setting up libmagickcore5:i386 (8:6.7.7.10-5+deb7u4) ...
Setting up libmagickwand5:i386 (8:6.7.7.10-5+deb7u4) ...
Setting up libmagickcore5-extra:i386 (8:6.7.7.10-5+deb7u4) ...
Setting up openssh-client (1:6.0p1-4+deb7u4) ...
Setting up openssh-server (1:6.0p1-4+deb7u4) ...
[] Restarting OpenBSD Secure Shell server: sshdESC[?25lESC7ESC[1G[ESC[32m 
ok ESC[39;49mESC8ESC[?12lESC[?25h.
Setting up imagemagick (8:6.7.7.10-5+deb7u4) ...
Setting up ssh (1:6.0p1-4+deb7u4) ...
Log ended: 2016-04-20  08:18:28