Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I can see these lines in journalctl for the attempted login, but I do not understand how to fix it. Do I need to define $TERM somewhere? And why now when it worked before?
Code:
Nov 05 18:30:02 fedserv audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=cockpit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 05 18:30:02 fedserv audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=cockpit-wsinstance-https-factory@7-45284-992 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 05 18:30:02 fedserv audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=cockpit-wsinstance-https@e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 05 18:30:02 fedserv systemd[1]: cockpit-wsinstance-https-factory@7-45284-992.service: Deactivated successfully.
Nov 05 18:30:02 fedserv audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=cockpit-wsinstance-https-factory@7-45284-992 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 05 18:30:02 fedserv cockpit-ws[45290]: json_object_get_string_member: assertion 'node != NULL' failed
Nov 05 18:30:02 fedserv audit[45294]: USER_AUTH pid=45294 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:cockpit_session_t:s0 msg='op=PAM:authentication grantors=pam_usertype,pam_localuser,pam_unix acct="tepsys" exe="/usr/libexec/cockpit-session" hostname=::ffff:192.168.50.204 addr=::ffff:192.168.50.204 terminal=? res=success'
Nov 05 18:30:02 fedserv audit[45294]: USER_ACCT pid=45294 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:cockpit_session_t:s0 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="tepsys" exe="/usr/libexec/cockpit-session" hostname=::ffff:192.168.50.204 addr=::ffff:192.168.50.204 terminal=? res=success'
Nov 05 18:30:02 fedserv audit[45294]: CRED_ACQ pid=45294 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:cockpit_session_t:s0 msg='op=PAM:setcred grantors=pam_localuser,pam_unix acct="tepsys" exe="/usr/libexec/cockpit-session" hostname=::ffff:192.168.50.204 addr=::ffff:192.168.50.204 terminal=? res=success'
Nov 05 18:30:02 fedserv audit[45294]: USER_ROLE_CHANGE pid=45294 uid=0 auid=1000 ses=20 subj=system_u:system_r:cockpit_session_t:s0 msg='pam: default-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 selected-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 exe="/usr/libexec/cockpit-session" hostname=::ffff:192.168.50.204 addr=::ffff:192.168.50.204 terminal=? res=success'
Nov 05 18:30:02 fedserv cockpit-session[45294]: pam_ssh_add: Identity added: /home/tepsys/.ssh/id_rsa (tepsys@fedora)
Nov 05 18:30:02 fedserv cockpit-session[45294]: pam_unix(cockpit:session): session opened for user tepsys(uid=1000) by (uid=0)
Nov 05 18:30:02 fedserv audit[45294]: USER_START pid=45294 uid=0 auid=1000 ses=20 subj=system_u:system_r:cockpit_session_t:s0 msg='op=PAM:session_open grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_ssh_add,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask,pam_lastlog acct="tepsys" exe="/usr/libexec/cockpit-session" hostname=::ffff:192.168.50.204 addr=::ffff:192.168.50.204 terminal=? res=success'
Nov 05 18:30:02 fedserv audit[45294]: CRED_REFR pid=45294 uid=0 auid=1000 ses=20 subj=system_u:system_r:cockpit_session_t:s0 msg='op=PAM:setcred grantors=pam_localuser,pam_unix acct="tepsys" exe="/usr/libexec/cockpit-session" hostname=::ffff:192.168.50.204 addr=::ffff:192.168.50.204 terminal=? res=success'
Nov 05 18:30:02 fedserv cockpit-ws[45311]: tput: No value for $TERM and no -T specified
Nov 05 18:30:02 fedserv cockpit-ws[45312]: tput: No value for $TERM and no -T specified
Nov 05 18:30:02 fedserv cockpit-ws[45313]: tput: No value for $TERM and no -T specified
Nov 05 18:30:02 fedserv cockpit-ws[45314]: tput: No value for $TERM and no -T specified
Nov 05 18:30:02 fedserv cockpit-ws[45315]: tput: No value for $TERM and no -T specified
Nov 05 18:30:02 fedserv cockpit-ws[45316]: tput: No value for $TERM and no -T specified
Nov 05 18:30:02 fedserv cockpit-ws[45317]: tput: No value for $TERM and no -T specified
Nov 05 18:30:02 fedserv cockpit-ws[45318]: tput: No value for $TERM and no -T specified
Nov 05 18:30:02 fedserv cockpit-ws[45319]: tput: No value for $TERM and no -T specified
Nov 05 18:30:02 fedserv cockpit-ws[45298]: open terminal failed: not a terminal
Nov 05 18:31:32 fedserv systemd[1]: cockpit-wsinstance-https@e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.service: Deactivated successfully.
Nov 05 18:31:32 fedserv audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=cockpit-wsinstance-https@e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 05 18:31:32 fedserv systemd[1]: cockpit-wsinstance-https@e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.socket: Deactivated successfully.
Nov 05 18:32:02 fedserv systemd[1]: cockpit.service: Deactivated successfully.
Nov 05 18:32:02 fedserv audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=cockpit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 05 18:32:02 fedserv systemd[1]: cockpit-wsinstance-http-redirect.socket: Deactivated successfully.
Nov 05 18:32:02 fedserv systemd[1]: cockpit-wsinstance-http.socket: Deactivated successfully.
Nov 05 18:32:02 fedserv systemd[1]: cockpit-wsinstance-https-factory.socket: Deactivated successfully.
Ok so I tried creating a new user to see if they could log in and was able to login with the new user.
Ssh is working fine for the original user, but I still can't login on the web console.
/var/log/btmp isn't showing any failed login attempts.
I'm not sure where else to be looking
So I've found that if I enter my username and leave the password field blank and click "Login" it brings me to another page asking for the password. If I enter the password here, I get an "Authentication failed" instead of Permission denied", and additionally this error appears
Code:
cockpit-session: pam_ssh_add: Failed adding some keys
Which I can find references to online, including this one https://github.com/cockpit-project/cockpit/issues/3820. But I don't have any of the other errors mentioned, and I've not edited limits.conf. Still searching for a solution. I'll update if I find the issue
Last edited by angryJellyBean; 11-06-2021 at 09:29 PM.
Well I couldn't find any more info on the issue, and since I needed a working user I ended up deleting and recreating the user. I would have rather found the root cause of the issue and fixed it properly but I lacked the knowledge of where to search, and with no responses here, I chose a more brute force approach. Marking Solved, even though it's not a proper solution
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
