search

keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
902 stars 37 forks source link

Latest Debian package hangs on install #4206

Open beastlyone opened 8 months ago

beastlyone commented 8 months ago

I am running Debian unstable and tried to upgrade to the latest version (6.2.3-20231016183016+06cb935ee3 ).

The upgrade starts normally with the following output:

Setting up keybase (6.2.3-20231016183016.06cb935ee3) ...
Autorestarting Keybase via systemd for xxxxxx.

The client restarts and then the upgrade process hangs (I left one attempt running for about 30 minutes). Quitting the client leads to the following:

mkdir: cannot stat ‘/keybase’: Transport endpoint is not connected
chown: cannot access '/keybase': Transport endpoint is not connected
chmod: cannot access '/keybase': Transport endpoint is not connected
dpkg: error processing package keybase (--configure):
 installed keybase package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 keybase

After some experimentation I found that stopping the keybase.mount service and then running "apt -f install" led to a successful upgrade.

SlySven commented 8 months ago

This also happens for the 'systemd'-less Devuan OS - after failing from inside aptitude I tried direct with dpkg: 

stephen@rachel:~$ sudo  dpkg --configure keybase
Setting up keybase (6.2.3-20231016183016.06cb935ee3) ...
Keybase not running via systemd for stephen.
Restart Keybase manually by running 'run_keybase' as stephen.
mkdir: cannot stat ‘/keybase’: Transport endpoint is not connected
chown: cannot access '/keybase': Transport endpoint is not connected
chmod: cannot access '/keybase': Transport endpoint is not connected
dpkg: error processing package keybase (--configure):
 installed keybase package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 keybase

However it didn't appear that there was a keybase service running that could be stopped - OTOH there were some files left in (my) /tmp filesystem:

stephen@rachel:~$ ls -l /tmp/runtime-stephen/keybase/
total 4
srwxr-xr-x 1 stephen stephen  0 Oct 20 12:26 kbfsd.sock
-rw-r--r-- 1 stephen stephen 66 Oct 20 12:26 keybased.info

and the keybased.info included details for a keybase daemon(?) with a PID that was non-existent at that time.

Using the -f ("force") option to apt install doesn't help either.

However I have just noticed that the /etc/cron.daily/keybase script includes lines like:

REPOCONFIG="deb http://prerelease.keybase.io/deb stable main"
SSLREPOCONFIG="deb https://prerelease.keybase.io/deb stable main"

However the machine with the problems is currently running Devuan "Chimaera" (equivalent to Debian "Bulleye") which is now "oldstable" as it hasn't been upgraded to "Daedalus" (equivalent to Debian "Bookworm") - I'll need to check what the status is on my other machine that has been so upgraded...