Member Avatar for Ritesh_4

Hello, anyone can tell me how I can fix the "Login timed out after 60 seconds" error, when the system is not even taking 60 seconds, since as soon as it loads, it gives this error when am trying to enter my login details. I have access to the system's files using WinSCP, so if I need to change any file settings will not be a problem... I am on a 7.04 Ubuntu server

  • 2 Contributors
  • 2 Replies
  • 208 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by Ritesh_4

Dani AI

Generated

Quick, practical diagnostic for ’s Ubuntu 7.04 report: the literal text "Login timed out after 60 seconds" is emitted by the login/shadow code when the auth child exits or blocks — in other words it’s usually a symptom of a blocked authentication path (PAM/NSS or a network auth service), not a literal keyboard timer. (patchwork.yoctoproject.org)

Because suggested clock sync, that’s worth a quick check, but on old Ubuntu servers the common causes are network-backed auth (winbind / pam_smbpass / pam_winbind, LDAP/NIS/SSSD) or NSS lookups that hang while waiting for a DC or LDAP server. A known Ubuntu/Samba interaction has pam_smbpass inserted into PAM and produced exactly this timeout; winbind behaviour is governed by /etc/nsswitch.conf so a failing network lookup will block logins. (lists.ubuntu.com)

Actionable steps (safe because you have WinSCP access — back up files first):

  • Look for relevant errors in the logs and config lines:
    grep -iE 'winbind|pam_smbpass|pam_winbind|ldap|nss' /etc/pam.d/* /etc/nsswitch.conf /var/log/auth.log /var/log/syslog
tail -n 200 /var/log/auth.log
  • If you see pam_smbpass.so migrate in /etc/pam.d/common-auth, make a backup and comment it out:
    cp /etc/pam.d/common-auth /etc/pam.d/common-auth.bak
sed -i '/pam_smbpass.so.*migrate/s/^/# /' /etc/pam.d/common-auth
  • If nsswitch.conf lists winbind in passwd/group, temporarily remove it or make files first (edit with WinSCP), then stop winbind before testing:
    /etc/init.d/winbind stop
# or: sudo service winbind stop

    If commenting the pam_smbpass line or removing winbind from NSS fixes the prompt, either remove/disable winbind or fix its startup/network ordering. (lists.ubuntu.com)

Other possibilities: wrong keyboard layout (entered password is different), very high load, or LDAP/NSS repeatedly timing out — check /var/log/auth.log and syslog for nss_ldap/pam/timeout errors and, if needed, boot to single-user/recovery to repair PAM safely. Back up any PAM changes — a bad PAM edit can lock accounts. (askubuntu.com)

Recommended Answers

All 2 Replies

Member Avatar for rubberman

It may be a clock syncronization problem. Make sure all your systems are getting clock updates using NTP. You can either use an internet NTP server such as NIST, etc, or you can set up a local server on your LAN which will keep all the PC's updated locally, yet it will keep updated from the Internet - allowing a large LAN installation to minimize the amount of NTP traffic going out of the firewalls.

Member Avatar for Ritesh_4

thanks rubberman

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.