![升级至焦点窝后无法登录驾驶舱](https://linux22.com/image/1017915/%E5%8D%87%E7%BA%A7%E8%87%B3%E7%84%A6%E7%82%B9%E7%AA%9D%E5%90%8E%E6%97%A0%E6%B3%95%E7%99%BB%E5%BD%95%E9%A9%BE%E9%A9%B6%E8%88%B1.png)
对于我来说,Cockpit 在 focus 上不起作用;但在 bionic 上它工作得很好。
根据“apt install cockpit”,版本 215-1 已安装,并在 https 端口 9090 上显示登录屏幕,但当我尝试登录时,它显示用户名或密码错误。使用“tail -f /var/log/syslog”显示用户名和密码正确;cockpit-session 调用 pam_ssh_add 加载我的私钥。
使用“apt install cockpit/focal-backports”(版本 218-1~ubuntu20.04.1)不会改变任何事情。
编辑于 2020 年 7 月 9 日:版本 223-1~ubuntu20.04.1 也失败了。
May 16 22:14:04 joe-laptop cockpit-tls[3419]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.
May 16 22:14:04 joe-laptop systemd[1]: Started Cockpit Web Service https instance factory (PID 3419/UID 124).
May 16 22:14:04 joe-laptop systemd[1]: Starting Socket for Cockpit Web Service https instance e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
May 16 22:14:04 joe-laptop systemd[1]: Listening on Socket for Cockpit Web Service https instance e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
May 16 22:14:04 joe-laptop systemd[1]: [email protected]: Succeeded.
May 16 22:14:04 joe-laptop systemd[1]: Started Cockpit Web Service https instance e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
May 16 22:14:04 joe-laptop cockpit-ws[3574]: cockpit-ws: Failed to open certificate file /run/cockpit/tls/e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855: No such file or directory
May 16 22:14:04 joe-laptop cockpit-session: pam_ssh_add: Identity added: /home/jms/.ssh/id_rsa (/home/jms/.ssh/id_rsa)
May 16 22:14:04 joe-laptop cockpit-session: pam_ssh_add: Identity added: /home/jms/.ssh/id_ecdsa (/home/jms/.ssh/id_ecdsa)
May 16 22:14:04 joe-laptop cockpit-session: pam_ssh_add: Identity added: /home/jms/.ssh/id_ed25519 (Joe@Joe-PC)
May 16 22:14:04 joe-laptop cockpit-ws[3586]: 3: Permission denied.
May 16 22:15:35 joe-laptop systemd[1]: cockpit-wsinstance-https@e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.service: Succeeded.
May 16 22:15:35 joe-laptop systemd[1]: cockpit-wsinstance-https@e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.socket: Succeeded.
May 16 22:15:35 joe-laptop systemd[1]: Closed Socket for Cockpit Web Service https instance e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
May 16 22:15:35 joe-laptop systemd[1]: cockpit-wsinstance-https@e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.service: Succeeded.
May 16 22:15:35 joe-laptop systemd[1]: cockpit-wsinstance-https@e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.socket: Succeeded.
May 16 22:15:35 joe-laptop systemd[1]: Closed Socket for Cockpit Web Service https instance e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
目录 /run/cockpit/tls 为空;没有证书。
编辑于 2020 年 7 月 28 日:在 github 上搜索 Ubuntu 的问题,出现了以下信息:
“如果用户登录 shell 是 tcsh 而不是 bash,则登录失败 #14060”
tcsh -c "exec cockpit-bridge >&3"
ws: Fix login with (t)csh (1-Jul-2020)
答案1
如果你最喜欢的登录 shell 是tcsh(或 csh),解决方法是创建一个使用狂欢为其登录 shell 并属于组须藤。