(I've been having problems posting to the list - apologies if this appears multiple times!)
Hi!
Can anyone help?
I've got Ubuntu 10.04 LTS - the Lucid Lynx installed, and I rebooted it today, because it seemed a bit sluggish, bit sluggish, and ever since I've had problems logging in and/or authenticating.
The only thinks I recall changing are there were a few updates downloaded, and I'd tweaked my Samba config file (smb.conf) and also been playing with the nvidia driver settings, enabling it and disabling it. This machine's a server, and it controls it's own logins, i.e. it doesn't authorise them somewhere else. When I reboot it, I see the greeter, I type in my password, and then it sits there for ages - at least a minute, before I see the logged in desktop. I can try switching to a virtual console (alt-f1 etc) and logging in there, and it takes ages and usually times out (timeout after 60 seconds message).
It also happens if I try to ssh into the machine.
Once the machine has been up for a while, the login response on a virtual terminal seems to be better, but I also get the problem using SUDO. I also get the problem logging in to Thunderbird on this machine, which uses IMAP to get the mail of this machine, and uses PAM to authenticate.
I've looked in the logs and can't see anything obviously wrong. ISTM that this is a problem with PAM authentication, but I've not changed anything, nor do I know what to do about it or what to change.
I've installed Bootchart, but there's nothing obviously wrong with that.
Any ideas?
Regards Steve
On 6 Aug 2010, at 21:35, steve-ALUG@hst.me.uk wrote:
(I've been having problems posting to the list - apologies if this appears multiple times!)
Hi!
Can anyone help?
I've got Ubuntu 10.04 LTS - the Lucid Lynx installed, and I rebooted it today, because it seemed a bit sluggish, bit sluggish, and ever since I've had problems logging in and/or authenticating.
The only thinks I recall changing are there were a few updates downloaded, and I'd tweaked my Samba config file (smb.conf) and also been playing with the nvidia driver settings, enabling it and disabling it. This machine's a server, and it controls it's own logins, i.e. it doesn't authorise them somewhere else. When I reboot it, I see the greeter, I type in my password, and then it sits there for ages - at least a minute, before I see the logged in desktop. I can try switching to a virtual console (alt-f1 etc) and logging in there, and it takes ages and usually times out (timeout after 60 seconds message).
It also happens if I try to ssh into the machine.
Once the machine has been up for a while, the login response on a virtual terminal seems to be better, but I also get the problem using SUDO. I also get the problem logging in to Thunderbird on this machine, which uses IMAP to get the mail of this machine, and uses PAM to authenticate.
I've looked in the logs and can't see anything obviously wrong. ISTM that this is a problem with PAM authentication, but I've not changed anything, nor do I know what to do about it or what to change.
I've installed Bootchart, but there's nothing obviously wrong with that.
Any ideas?
Check that the machine can resolve DNS. I've seen quite big delays in logging in and especially when using sudo when a machine has unreachable/unresponsive DNS servers.
On 06/08/10 22:13, David Reynolds wrote:
Check that the machine can resolve DNS. I've seen quite big delays in logging in and especially when using sudo when a machine has unreachable/unresponsive DNS servers.
Yes that will cause problems, Also look at the pam.d configuration.
Specifically which modules are optional and which are required in the login config file.
Were you using anything funky for samba authentication and some automated way of setting it up (i.e using swat) to set up something like winbind to authenticate samba against a Windows Domain ? As that can and will mess with pam authentication. Is it possible that you enabled this configuration by mistake ?
Also is SELinux installed as ISTR that can hook into pam and a problem there could be causing a delay.
Wayne Stallwood wrote:
On 06/08/10 22:13, David Reynolds wrote:
Check that the machine can resolve DNS. I've seen quite big delays in logging in and especially when using sudo when a machine has unreachable/unresponsive DNS servers.
AFAICS, DNS is working OK. I can ping and tracert.
Yes that will cause problems, Also look at the pam.d configuration.
Specifically which modules are optional and which are required in the login config file.
Sorry, loads of files in pam.d - which one is the login config file? anyway, reading comments in file "common-password", it mentions using pam-auth-update to manage selection of other modules. I ran this and found that log-in via NT domain was enabled, which is not what I want to do, as this machine is the server, there are no windows servers. I disabled that option, and am just about to retry. Will let you know tomorrow!
Were you using anything funky for samba authentication and some automated way of setting it up (i.e using swat)
No, manually edited config file Will check it.
to set up something like
winbind to authenticate samba against a Windows Domain ?
Hopefully not!
As that can and
will mess with pam authentication. Is it possible that you enabled this configuration by mistake ?
Absolutely possible, but don't know how if I did.
Also is SELinux installed as ISTR that can hook into pam and a problem there could be causing a delay.
SELinux not installed, AppArmour is installed I think though.
Thanks for your help. Will update progress later. To late now. Must sleep! :-)
Cheers Steve
On 06/08/10 23:48, Wayne Stallwood wrote:
On 06/08/10 22:13, David Reynolds wrote:
Check that the machine can resolve DNS. I've seen quite big delays in logging in and especially when using sudo when a machine has unreachable/unresponsive DNS servers.
Yes that will cause problems, Also look at the pam.d configuration.
Specifically which modules are optional and which are required in the login config file.
Were you using anything funky for samba authentication and some automated way of setting it up (i.e using swat) to set up something like winbind to authenticate samba against a Windows Domain ? As that can and will mess with pam authentication. Is it possible that you enabled this configuration by mistake ?
Also is SELinux installed as ISTR that can hook into pam and a problem there could be causing a delay.
SELinux not installed, AppArmour is installed I think though.
Thanks for your help so far. Will keep plugging away! Cheers Steve
On 06/08/10 23:48, Wayne Stallwood wrote:
On 06/08/10 22:13, David Reynolds wrote:
Check that the machine can resolve DNS. I've seen quite big delays in logging in and especially when using sudo when a machine has unreachable/unresponsive DNS servers.
AFAICS, DNS is working OK. I can ping and tracert.
Yes that will cause problems, Also look at the pam.d configuration.
Specifically which modules are optional and which are required in the login config file.
Sorry, loads of files in pam.d - which one is the login config file? anyway, reading comments in file "common-password", it mentions using pam-auth-update to manage selection of other modules. I ran this and found that log-in via NT domain was enabled, which is not what I want to do, as this machine is the server, there are no windows servers. I disabled that option, and tried it, but it didn't seem to make a difference. :-(
Were you using anything funky for samba authentication and some automated way of setting it up (i.e using swat)
No, manually edited config file Will check it.
to set up something like winbind to authenticate samba against a Windows Domain ?
Hopefully not!
As that can and will mess with pam authentication. Is it possible that you enabled this configuration by mistake ?
Absolutely possible, but don't know how if I did.
Also is SELinux installed as ISTR that can hook into pam and a problem there could be causing a delay.
SELinux not installed, AppArmour is installed I think though.
Thanks for your help so far. Will keep plugging away! Cheers Steve
steve-ALUG@hst.me.uk wrote:
On 06/08/10 23:48, Wayne Stallwood wrote:
Were you using anything funky for samba authentication and some automated way of setting it up (i.e using swat)
No, manually edited config file Will check it.
to set up something like winbind to authenticate samba against a Windows Domain ?
Hopefully not!
As that can and will mess with pam authentication. Is it possible that you enabled this configuration by mistake ?
Absolutely possible, but don't know how if I did.
Hmm, I unistalled Samba, then rebooted, attempted to log in and it logged in at normal (fast) speed. I then tried to login from a virtual console (ctrl-alt-f2) and the first login attempt said "No Login Servers", then after that it logged in OK.
So it's something to do with SAMBA, but my samba config file smb.conf has not changed significantly in ages.
Is PAM trying to authenticate via Samba? If so how do I tell it not to?
And help appreciated. Thanks! :-)
Steve
AHA!
Samba was the clue. Uninstalling and reinstalling Samba, I filtered the available apps by the word Samba, and there was WinBind installed. I then recalled that I had installed it a while ago, thinking I've heard that name before; I probably need that. I have now removed it and seem to have fast logins again.
Please feel free to point at me and call me a numpty.
Cheers Steve
-
David Reynolds -
steve-ALUG＠hst.me.uk -
Wayne Stallwood