Re: apt-cacher internal error (died)
Disclaimer: I run apt-cacher-ng, and have never looked at apt-cacher.
On Wed 07 Sep 2022 at 17:50:16 (+0100), Adam Weremczuk wrote:
> SERVER
>
> Wed Sep 7 17:06:40 2022|error [10088]: Failed to open/create
> /var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb for return:
> Permission denied at /usr/sbin/apt-cacher line 735, <GEN13> line 4.
> Wed Sep 7 17:07:58 2022|warn [20848]: Warning: unable to close
> filehandle __ANONIO__ properly: Bad file descriptor at
> /usr/sbin/apt-cacher line 1539.
>
> Permissions seem fine:
>
> ls -al /var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb
> lrwxrwxrwx 1 proxy proxy 51 Aug 22 18:13
> /var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb ->
> /var/cache/apt/archives/memtest86+_5.01-3_amd64.deb
>
> ls -al /var/cache/apt/archives/memtest86+_5.01-3_amd64.deb
> -rw-r--r-- 1 myuser users 75142 Nov 18 2021
> /var/cache/apt/archives/memtest86+_5.01-3_amd64.deb
>
> All folders in both paths are 755.
I don't understand the commingling of apt-cacher and apt; is this
how apt-cacher is designed to work? When I install a new package
on a client, the server does not use /var/cache/apt/archives/,
but only its /var/cache/apt-cacher/ directories, from which it
will serve clients.
If someone was logged in to a client and installing package foo,
and I happened to be logged in to the server and installing foo
directly (not via apt-cacher), it would appear from your logs
that we'd both be trying to use the same directory. How would
the permissions work then, and if I cleaned apt's cache, where
would apt-cacher serve the deleted foo file from?
BTW Who is myuser and who is apt-cacher running as?
Cheers,
David.
Reply to: