Bug#330852: login: Critical error - immediate abort
Package: login Version: 1:4.0.12-5 Severity: critical Justification: breaks unrelated software based on description of probl;em and resolution found in http://lists.debian.org/debian-user/1999/09/msg02354.html and that clouded:/# ls -l /bin/login -rwxr-xr-x 1 root root 31208 Sep 28 11:01 /bin/login clouded:/# date betting login is cuasing this problem The following exit with the message Critical error - immediate abort ssh to machine (note that ssh machine -t bash lets you in) cron This is not a complete report of broken systems, only what I've noticed in first few minutes after getting back into system -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.21 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages login depends on: ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libpam-modules0.79-2 Pluggable Authentication Modules f ii libpam-runtime0.79-2 Runtime support for the PAM librar ii libpam0g 0.79-2 Pluggable Authentication Modules l login recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330852: login: Critical error - immediate abort
reassign 330852 libpam0g severity 330852 important thanks On Thu, Sep 29, 2005 at 10:55:36PM -0700, David M. Dowdle wrote: Package: login Version: 1:4.0.12-5 Severity: critical Justification: breaks unrelated software based on description of probl;em and resolution found in http://lists.debian.org/debian-user/1999/09/msg02354.html and that clouded:/# ls -l /bin/login -rwxr-xr-x 1 root root 31208 Sep 28 11:01 /bin/login clouded:/# date betting login is cuasing this problem The following exit with the message Critical error - immediate abort ssh to machine (note that ssh machine -t bash lets you in) cron Er, you're apparently basing that conclusion on a 6-year-old report about a problem which doesn't actually resemble yours. And neither ssh nor cron have *anything* to do with /bin/login. Which doesn't make this a critical bug in login, it makes it impossible that it's a bug in login. The error message in question comes from a PAM_ABORT return from the Linux-PAM library, which has also just been upgraded in unstable; and I see that you're running the newest version. However, this error is not reproducible here, or on the systems of most other users, so I'll need information about the contents of your /etc/pam.d/ configuration in order to debug it. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#330852: login: Critical error - immediate abort
On 30/09/2005 at 00:04 -0700, Steve Langasek wrote: The error message in question comes from a PAM_ABORT return from the Linux-PAM library, which has also just been upgraded in unstable; and I see that you're running the newest version. However, this error is not reproducible here, or on the systems of most other users, so I'll need information about the contents of your /etc/pam.d/ configuration in order to debug it. I have a system (sid dist-upgraded today) where I get this error (with cron): | Sep 30 10:30:01 bacterio CRON[19683]: (pam_unix) session opened for user root by (uid=0) | Sep 30 10:30:01 bacterio CRON[19683]: Critical error - immediate abort On my desktop (also sid dist-upgraded today). Cron works perfectly. Attached is a tarball of /etc/pam.d of the failing system. Installing libpam0g=0.79-1 libpam-modules=0.79-1 libpam-runtime=0.79-1 makes the error disapear. Please, let me know if I can provide any additional information. Thanks. -- Kiko pam.d.tar.bz2 Description: Binary data
Bug#330852: login: Critical error - immediate abort
On Fri, Sep 30, 2005 at 11:12:53AM +0200, Kiko Piris wrote: On 30/09/2005 at 00:04 -0700, Steve Langasek wrote: The error message in question comes from a PAM_ABORT return from the Linux-PAM library, which has also just been upgraded in unstable; and I see that you're running the newest version. However, this error is not reproducible here, or on the systems of most other users, so I'll need information about the contents of your /etc/pam.d/ configuration in order to debug it. I have a system (sid dist-upgraded today) where I get this error (with cron): | Sep 30 10:30:01 bacterio CRON[19683]: (pam_unix) session opened for user root by (uid=0) | Sep 30 10:30:01 bacterio CRON[19683]: Critical error - immediate abort On my desktop (also sid dist-upgraded today). Cron works perfectly. Attached is a tarball of /etc/pam.d of the failing system. The PAM config itself looks fine. Can you please also forward the contents of your /etc/security/limits.conf? Installing libpam0g=0.79-1 libpam-modules=0.79-1 libpam-runtime=0.79-1 makes the error disapear. So you mean that this error only occurs with 0.79-2, *not* with 0.79-1? Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#330852: login: Critical error - immediate abort
On 30/09/2005 at 02:40 -0700, Steve Langasek wrote: The PAM config itself looks fine. Can you please also forward the contents of your /etc/security/limits.conf? Attached. It's empty (only comments). Installing libpam0g=0.79-1 libpam-modules=0.79-1 libpam-runtime=0.79-1 makes the error disapear. So you mean that this error only occurs with 0.79-2, *not* with 0.79-1? That's correct. -- Kiko # /etc/security/limits.conf # #Each line describes a limit for a user in the form: # #domaintype item value # #Where: #domain can be: #- an user name #- a group name, with @group syntax #- the wildcard *, for default entry #- the wildcard %, can be also used with %group syntax, # for maxlogin limit # #type can have the two values: #- soft for enforcing the soft limits #- hard for enforcing hard limits # #item can be one of the following: #- core - limits the core file size (KB) #- data - max data size (KB) #- fsize - maximum filesize (KB) #- memlock - max locked-in-memory address space (KB) #- nofile - max number of open files #- rss - max resident set size (KB) #- stack - max stack size (KB) #- cpu - max CPU time (MIN) #- nproc - max number of processes #- as - address space limit #- maxlogins - max number of logins for this user #- priority - the priority to run user process with #- locks - max number of file locks the user can hold #- sigpending - max number of pending signals #- msgqueue - max memory used by POSIX message queues (bytes) # #domain type item value # #* softcore0 #* hardrss 1 [EMAIL PROTECTED]hardnproc 20 [EMAIL PROTECTED]softnproc 20 [EMAIL PROTECTED]hardnproc 50 #ftp hardnproc 0 [EMAIL PROTECTED]- maxlogins 4 # End of file
Bug#330852: login: Critical error - immediate abort
On 30/09/2005 at 03:51 -0700, Steve Langasek wrote: Ok, the only module that's used by your cron config which actually changed between 0.79-1 and 0.79-2 was pam_env. Could you please upgrade to 0.79-2 again, confirm that you're still seeing the bug, then comment out pam_env in /etc/pam.d/cron to see if the problem goes away? You're right, it goes away commenting out pam_env. If that does fix it, please post your /etc/environment as well. It didn't exist, just touched it and the error went away. Thanks, Thank you, indeed. -- Kiko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330852: login: Critical error - immediate abort
On Fri, Sep 30, 2005 at 12:39:56PM +0200, Kiko Piris wrote: On 30/09/2005 at 02:40 -0700, Steve Langasek wrote: The PAM config itself looks fine. Can you please also forward the contents of your /etc/security/limits.conf? Attached. It's empty (only comments). Hrm. Installing libpam0g=0.79-1 libpam-modules=0.79-1 libpam-runtime=0.79-1 makes the error disapear. So you mean that this error only occurs with 0.79-2, *not* with 0.79-1? That's correct. Ok, the only module that's used by your cron config which actually changed between 0.79-1 and 0.79-2 was pam_env. Could you please upgrade to 0.79-2 again, confirm that you're still seeing the bug, then comment out pam_env in /etc/pam.d/cron to see if the problem goes away? If that does fix it, please post your /etc/environment as well. If it doesn't fix it, can you also try commenting out pam_limits, just for kicks? Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#330852: login: Critical error - immediate abort
Sorry for the misdirected finger pointing earlier. Touching /etc/environment, without making changes in /etc/pam.d/ (ie pam_env still being called) now allows logins via ssh, and cron jobs are starting to run again On Fri, 30 Sep 2005, Kiko Piris wrote: On 30/09/2005 at 03:51 -0700, Steve Langasek wrote: Ok, the only module that's used by your cron config which actually changed between 0.79-1 and 0.79-2 was pam_env. Could you please upgrade to 0.79-2 again, confirm that you're still seeing the bug, then comment out pam_env in /etc/pam.d/cron to see if the problem goes away? You're right, it goes away commenting out pam_env. If that does fix it, please post your /etc/environment as well. It didn't exist, just touched it and the error went away. Thanks, Thank you, indeed. -- Kiko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
