search for: pam_ecryptfs

...to allocate memory. They usually look something like this (there are stack traces with more detail in the linked Debian bug report - this is just for illustration): __printf_buffer (libc.so.6 + 0x6261d) __vasprintf_internal (libc.so.6 + 0x87a6b) ___asprintf_chk (libc.so.6 + 0x11abef) n/a (pam_ecryptfs.so + 0x23d7) pam_sm_authenticate (pam_ecryptfs.so + 0x2ace) n/a (libpam.so.0 + 0x44de) pam_authenticate (libpam.so.0 + 0x3be3) n/a (/home/cjwatson/openssh/sshd-session + 0x3dbf0) But the code in pam_ecryptfs looks innocent. And in mlockall(2), I see this paragraph which looks relevant:...

...return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around password required pam_permit.so # and here are more per-package modules (the "Additional" block) password optional pam_ecryptfs.so # end of pam-auth-update config dovecot logs ------------------ May 26 13:14:39 prisa-appserver ntpdate[574]: Can't find host ntp.ubuntu.com: Name or service not known (-2) May 26 13:14:39 prisa-appserver ntpdate[574]: no servers can be used, exiting May 26 13:14:48 prisa-appserver sudo: pa...