Not able to login to cockpit GUI

Latest response

Hi,
I am not able to login to my cockpit gui using root user. I installed RHV 4.0 package on my server. While installting RHV 4.0 package I created root user. Then I login to system using root user and gave "yum update". Packages got updated with 4.1 version. I rebooted my system once. I am able to login with root user using putty but when I try to login using cockpit use its saying "wrong user name or password".

Here are my details:

USING PUTTY:

login as: root
root@10.53.197.121's password:
Last login: Mon May 29 08:01:02 2017 from 10.53.197.105

node status: DEGRADED
Please check the status manually using nodectl check

Admin Console: https://10.53.197.121:9090/

[root@masterPC_121 ~]#
[root@masterPC_121 ~]# nodectl check
Status: WARN
Bootloader ... OK
Layer boot entries ... OK
Valid boot entries ... OK
Mount points ... OK
Separate /var ... OK
Discard is used ... OK
Basic storage ... OK
Initialized VG ... OK
Initialized Thin Pool ... OK
Initialized LVs ... OK
Thin storage ... OK
Checking available space in thinpool ... OK
Checking thinpool auto-extend ... OK
vdsmd ... BAD
[root@masterPC_121 ~]#

USING COCKPIT GUI:

Please help me!!!

Responses

Hi there,

Any error messages that give further feedback on the issue? (/var/log/messages, and/or /var/log/secure) Do you have ssh keys in use with Putty? Try changing the password one more time and confirm you can log from another location (not using ssh keys).

Hi there,

check selinux mode ( enforcing or permissive ) it must be permissive mode and try to login, it's work try.

Hello!

I have the same issue. Here's what I get in the logs. Is the "cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received." relevant?

==> /var/log/messages <==
May  6 14:12:37 tupu systemd[1]: Starting Socket for Cockpit Web Service http-redirect instance.
May  6 14:12:37 tupu systemd[1]: Starting Socket for Cockpit Web Service http instance.
May  6 14:12:37 tupu systemd[1]: Starting Socket for Cockpit Web Service https instance factory.
May  6 14:12:37 tupu systemd[1]: Listening on Socket for Cockpit Web Service http-redirect instance.
May  6 14:12:37 tupu systemd[1]: Listening on Socket for Cockpit Web Service http instance.
May  6 14:12:37 tupu systemd[1]: Listening on Socket for Cockpit Web Service https instance factory.
May  6 14:12:37 tupu systemd[1]: Starting Cockpit Web Service...
May  6 14:12:38 tupu systemd[1]: Started Cockpit Web Service.
May  6 14:12:38 tupu cockpit-tls[3807]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.
May  6 14:12:38 tupu systemd[1]: Started Cockpit Web Service https instance factory (PID 3807/UID 994).
May  6 14:12:38 tupu systemd[1]: Starting Socket for Cockpit Web Service https instance e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
May  6 14:12:38 tupu systemd[1]: Listening on Socket for Cockpit Web Service https instance e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
May  6 14:12:38 tupu systemd[1]: Started Cockpit Web Service https instance e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
May  6 14:12:38 tupu systemd[1]: cockpit-wsinstance-https-factory@6-3807-994.service: Succeeded.

==> /var/log/secure <==
May  6 14:12:38 tupu unix_chkpwd[3819]: check pass; user unknown
May  6 14:12:38 tupu unix_chkpwd[3820]: check pass; user unknown
May  6 14:12:38 tupu unix_chkpwd[3820]: password check failed for user (root)
May  6 14:12:38 tupu cockpit-session[3818]: pam_unix(cockpit:auth): authentication failure; logname= uid=993 euid=993 tty= ruser= rhost=::ffff:10.100.3.133  user=root

==> /var/log/messages <==
May  6 14:12:40 tupu cockpit-ws[3814]: cockpit-session: open(/var/log/btmp) failed: Permission denied