Correction, it is "UseDNS no".
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/300151
Title:
ssh slow during logon, when ENTERING INTERACTIVE SESSION
To manage notifications about t
Restart the dbus service on the ssh server "sudo restart dbus" - that should
help.
If not, try adding "UseDNS=no" to your ssh server's sshd_config file and
restart the service "sudo restart ssh"
If the UseDNS trick works, check your dns server setup.
--
You received this bug notification becaus
Using Oneiric, I am still experiencing the delay noted above. The server
showing this delay is currently very underutilized, that is, low CPU
utilization, lots of free RAM, low net if utilization, etc. There are no
process hogs.
Stopping/restarting avahi-daemon did not help at all. No console-kit
No, I don't see consolekit consuming lots of memory. That said, I can
see some consolekit zombies:
[tris...@babylon ~] ps -le | grep Z
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
5 Z 0 4658 1 0 80 0 - 0 exit ?00:00:00
console-kit-dae
5 Z 0
On Fri, Oct 09, 2009 at 01:43:32PM -, tristan_lefebure wrote:
> I do experience the same symptoms on Jaunty, i.e. 20s break in
> "Entering interactive session." while loging through ssh. Any idea if
> this is the same bug?
>
Do "top" on your server and see if consolekit something occupies 10
I do experience the same symptoms on Jaunty, i.e. 20s break in
"Entering interactive session." while loging through ssh. Any idea if
this is the same bug?
--
ssh slow during logon, when ENTERING INTERACTIVE SESSION
https://bugs.launchpad.net/bugs/300151
You received this bug notification because
** Changed in: openssh (Ubuntu)
Status: Invalid => Fix Released
** Changed in: openssh
Status: Invalid => Fix Released
** Changed in: consolekit
Status: Invalid => Fix Released
--
ssh slow during logon, when ENTERING INTERACTIVE SESSION
https://bugs.launchpad.net/bugs/30015
Good to hear! Thank you.
--
ssh slow during logon, when ENTERING INTERACTIVE SESSION
https://bugs.launchpad.net/bugs/300151
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-ser
Yes, fixed in Jaunty.
i
On Sat, Jun 06, 2009 at 12:11:58AM -, Jeff Enns wrote:
> I'm just checking to see if this issue has been resolved. The bug this
> was related to was fixed in a later release. Let me know this is or is
> not the case. Thank you!
>
> ** Changed in: consolekit
>
I'm just checking to see if this issue has been resolved. The bug this
was related to was fixed in a later release. Let me know this is or is
not the case. Thank you!
** Changed in: consolekit
Status: New => Invalid
** Changed in: openssh
Status: New => Invalid
** Changed in: op
On Mon, Nov 24, 2008 at 11:46:35PM -, James Westby wrote:
> This sounds similar to bug 284229, is console-kit-daemon using a lot
> of CPU on the system you are logging in to?
Yep, quite a bit of cpu used by it
--
ssh slow during logon, when ENTERING INTERACTIVE SESSION
https://bugs.launchpad
Hi,
This sounds similar to bug 284229, is console-kit-daemon using a lot
of CPU on the system you are logging in to?
Thanks,
James
--
ssh slow during logon, when ENTERING INTERACTIVE SESSION
https://bugs.launchpad.net/bugs/300151
You received this bug notification because you are a member of U
** Also affects: consolekit
Importance: Undecided
Status: New
--
ssh slow during logon, when ENTERING INTERACTIVE SESSION
https://bugs.launchpad.net/bugs/300151
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
oops, bad paste, first ssh took 25 seconds.
--
ssh slow during logon, when ENTERING INTERACTIVE SESSION
https://bugs.launchpad.net/bugs/300151
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs maili
I think that I have a track. Based on similar "su" problems, I decided
to explore the possibility that it is the fault of "dbus". Based on
results below, I believe it to be the case and I reassign this issue to
"dbus". Restarting dbus fixes this issue.
So I did:
1) time how long ssh to localhost
15 matches
Mail list logo
