Client: Keybase service fails to start if a linux distribution does not support per-user systemd instances

[narkq]

After I upgraded linux client to version 1.0.38-20171221170044+4c1f9803e on CentOS 7, Keybase service failed to restart with message

Failed to execute operation: Process /bin/false exited with status 1

Setting environment variable KEYBASE_SYSTEMD=0 makes it work again.

[fitzha]

This is also happening for me on Ubuntu Server 16.04

Output of run_keybase:

Unmounting /keybase...
Shutting down kbfsfuse...
Starting via systemd.
Job for keybase.service failed because the control process exited with error code. See "systemctl --user status keybase.service" and "journalctl -xe" for details.

Output of journalctl -xe:

-- The result is failed.
Dec 29 18:48:11 keybase systemd[1967]: keybase.service: Unit entered failed state.
Dec 29 18:48:11 keybase systemd[1967]: keybase.service: Failed with result 'exit-code'.
Dec 29 18:48:11 keybase systemd[1967]: keybase.service: Service hold-off time over, scheduling restart.
Dec 29 18:48:11 keybase systemd[1967]: Stopped Keybase core service.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished shutting down.
Dec 29 18:48:11 keybase systemd[1967]: Starting Keybase core service...
-- Subject: Unit UNIT has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has begun starting up.
Dec 29 18:48:11 keybase systemd[1967]: keybase.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 29 18:48:11 keybase systemd[1967]: Failed to start Keybase core service.
-- Subject: Unit UNIT has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has failed.
--
-- The result is failed.
Dec 29 18:48:11 keybase systemd[1967]: keybase.service: Unit entered failed state.
Dec 29 18:48:11 keybase systemd[1967]: keybase.service: Failed with result 'exit-code'.
Dec 29 18:48:11 keybase systemd[1967]: keybase.service: Service hold-off time over, scheduling restart.
Dec 29 18:48:11 keybase systemd[1967]: Stopped Keybase core service.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished shutting down.
Dec 29 18:48:11 keybase systemd[1967]: keybase.service: Start request repeated too quickly.
Dec 29 18:48:11 keybase systemd[1967]: Failed to start Keybase core service.
-- Subject: Unit UNIT has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has failed.
--
-- The result is failed.
Dec 29 18:48:20 keybase systemd[1967]: Started Keybase Filesystem service.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.

[maxtaco]

cc @oconnor663

[oconnor663]

Dup of https://github.com/keybase/client/issues/9847.

[oconnor663]

The fix for this landed, and it'll go out with our next Linux build, probably tomorrow.

[oconnor663]

Just kidding it's going out in 10 minutes.

[oconnor663]

@fitzha for what it's worth, it doesn't look to me like you have the same problem. Maybe you could do a keybase log send and file a separate ticket?

[fitzha]

@oconnor663 Will do.

[fitzha]

@oconnor663 I've tried to replicate the problem on a fresh install of Ubuntu Server and I can't. Unfortunately I've deleted the virtual machine with the problem so I can't send a log now (derp). There was likely a configuration error on my end so I'd say it's safe to ignore (and obviously a ticket won't be created).

[narkq]

@oconnor663 Thank you very much!