I have same problem in Ubuntu 18.04, +2 seconds in sshd logins.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805423
Title:
pam_motd needs a module option to disable in-line dynamic updates
To mana
This bug has not seen any activity in the last 6 months, so it is being
automatically closed.
If you are still experiencing this issue, please feel free to re-open.
Landscape Team
** Changed in: landscape-client
Status: New => Invalid
--
You received this bug notification because you ar
Any update, help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805423
Title:
pam_motd needs a module option to disable in-line dynamic updates
To manage notifications about this bug go to:
https:/
Here is an idea for a patch – but I am not sure if it actually works:
--- /usr/share/pyshared/landscape/lib/sysstats.py.orig 2012-07-26
15:26:42.0 +
+++ /usr/share/pyshared/landscape/lib/sysstats.py 2012-07-26
15:32:38.0 +
@@ -55,6 +55,13 @@ class MemoryStats(objec
Hey,
I tried your code:
1. $USER doesn't seem to be set in this context so it runs regardless.
;-) At least it doesn't seem to be set during the login.
2. Whenever I add strace, it magically works – without, it defuncts.
I looked around further and it took me a while to figure this out – so the
If you can reproduce it at least some times, I have some suggestions:
- hack the script to only run if you login as a certain user. In that way, you
can trigger it by logging in as, say, "ubuntu", and don't run if you login as
someone else. Something like this (untested):
--- /usr/share/landscap
Well, I am a 100% sure it's /usr/bin/landscape-sysinfo. It happened
fairly consistently last week. To a point where I couldn't login at all,
unless I rebooted the instance and logged in right away. We have now
removed the landscape-client to ensure login always works.
When I ran this script while
I tried to reproduce it a few times, but no luck. Does it happen often
to you? If yes, we may be able to come up with a debug strategy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805423
Title:
pa
I believe it's this: ami-6936fb00
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805423
Title:
pam_motd needs a module option to disable in-line dynamic updates
To manage notifications about this bu
Region is 'east1'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805423
Title:
pam_motd needs a module option to disable in-line dynamic updates
To manage notifications about this bug go to:
https:/
Hi Till,
yes, I saw that askubuntu process list.
What is the AMI you used, and in which region?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805423
Title:
pam_motd needs a module option to disabl
I have no such thing – my users are 'local'.
It's a stock 10.04.4, this is how it looks like right now:
till@statsd1:~$ ls -lah /etc/update-motd.d/
total 48K
drwxr-xr-x 2 root root 4.0K 2012-07-12 15:19 .
drwxr-xr-x 89 root root 4.0K 2012-07-13 10:25 ..
-rwxr-xr-x 1 root roo
Do you have any reason to believe "who" would stall? Do you have network
users, stored in ldap or nis? Doesn't look like it, but it doesn't hurt
to ask.
sysinfo uses this to get the logged in users:
def get_logged_in_users():
result = getProcessOutputAndValue("who", ["-q"], env=os.environ)
S
My login session never timeout, I was actually authenticated but never
saw a prompt.
I let it running (sitting there) over night and the shell was still
'active' there after 8 hours – but no prompt.
The load had nothing to do with this. I booted the server (pretty
blank), logged in and then furth
landscape-common installs a script in /etc/update-motd.d to display a
banner with some basic system information.
It will not run the main landscape-sysinfo binary if the load is higher
than the number of cores, see /usr/share/landscape/landscape-
sysinfo.wrapper:
#!/bin/sh
cores=$(grep -c ^proces
I want to add that it seems like the following removes the files as
well:
apt-get purge landscape-client
I did this to avoid having to maintain pam configuration. Maybe someone
escalate it there. I still fail to understand how you can add something
to the login process which might block the user
I'm on 10.04.4 (latest kernel, everything) and I just spent an entire
work-day debugging pam_motd behavior.
For some reason, one of the scripts fails (defuncts) when I try to log
into a server. Add to that, this server is on EC2 so there is no way to
use the terminal either.
Anyhow – for a sumary
This bug was fixed in the package pam - 1.1.3-5ubuntu1
---
pam (1.1.3-5ubuntu1) precise; urgency=low
* Merge from Debian unstable. Remaining changes:
- debian/libpam-modules.postinst: Add PATH to /etc/environment if it's
not present there or in /etc/security/pam_env.conf.
** Branch linked: lp:~ubuntu-core-dev/pam/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805423
Title:
pam_motd needs a module option to disable in-line dynamic updates
To manage notification
check_by_ssh does not open a tty. So it should not calculate the motd. I
did not thing about that. May be it could solve the nagios problem, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805423
T
20 matches
Mail list logo
