From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id EEC51138E66 for ; Tue, 25 Feb 2014 16:59:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 281F6E0B27; Tue, 25 Feb 2014 16:59:10 +0000 (UTC) Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0353DE0B21 for ; Tue, 25 Feb 2014 16:59:06 +0000 (UTC) Received: by mail-ie0-f176.google.com with SMTP id rd18so541498iec.7 for ; Tue, 25 Feb 2014 08:59:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nileshgr.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=ceeoFA55+xGnnHg6iCJDXOsmtxVFsRrXWb756vqD+DU=; b=IYQ0wH6k0TlUVbOI6rlp9vkSOzIPHM/oAd3pF5s9f1ENesBtM1AJy9nEAsmg6Fq5/u 1G8EyZVGMBLM6i/iU2ygJl8QvS92l8Vo2CrzDaCABZTIHt4M6CmI7YMGqpXYLbsuCfpL lCoLSgemm8Q3sd9KR6pwCEuncOzlY0OyG8gXI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=ceeoFA55+xGnnHg6iCJDXOsmtxVFsRrXWb756vqD+DU=; b=NgIDDdnvpEDxgz4asw6G1ZIOHZqQ6D7HCNTBIMboCjrTMQf/mNwOcgnU/etZ8g9HNh 9gVmjlCHTGnHFcdz6fsWjEPjApKDXqSrPk7qnK4IMuWMTFcG77/PqyfyzI0k7v5uNXpt bsKSv54KDYtFjOMTtohnNEb5BZNVuYlgwXQICKLH+NfuuYhPcO7caHcHXbE2KpMWSuFP ZvfkoBQ27+119MqIYWlvpOP7DrJqwJrV4ntRPDDXWGwy6nTLfNoJNWB8pN6irXnORmj9 e+L96M+sHhfgbPKhuLPADHbJcByXCQqu5FYlK3jiRiCRn3eS6c+vQuHFl5pZMwrDjqN6 f+pw== X-Gm-Message-State: ALoCoQln8iELzqls2d6f15wzKkFfWig++ufEHmpoU+fWuqRa7M5hygi1qZXHpjQUUdoUV3iKbGU4 X-Received: by 10.50.12.9 with SMTP id u9mr20918867igb.15.1393347545827; Tue, 25 Feb 2014 08:59:05 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.64.55.10 with HTTP; Tue, 25 Feb 2014 08:58:25 -0800 (PST) In-Reply-To: References: From: Nilesh Govindrajan Date: Tue, 25 Feb 2014 22:28:25 +0530 Message-ID: Subject: Re: [gentoo-user] vixie cron: PAM ERROR To: Gentoo User Mailing List Content-Type: multipart/alternative; boundary=089e0115fa7e84a3d604f33e01b0 X-Archives-Salt: 5a503736-a712-48b8-be44-e54819f90eb3 X-Archives-Hash: 13e590480d3b426c3517fdeacc669694 --089e0115fa7e84a3d604f33e01b0 Content-Type: text/plain; charset=UTF-8 On Tue, Feb 25, 2014 at 9:29 PM, Grant Edwards wrote: > On a newly installed system, I'm getting error messages from vixie cron > about PAM authentication errors: > > Feb 25 09:52:01 alpha crond[23085]: (root) PAM ERROR (Authentication > failure) > Feb 25 09:52:01 alpha crond[23085]: (root) FAILED to authorize user with > PAM (Authentication failure) > Feb 25 09:53:01 alpha cron[23118]: (root) CMD (echo "cron ran at $(date)" > >>/tmp/cron.out) > Feb 25 09:53:01 alpha crond[23122]: (root) PAM ERROR (Authentication > failure) > Feb 25 09:53:01 alpha crond[23122]: (root) FAILED to authorize user with > PAM (Authentication failure) > Feb 25 09:54:01 alpha cron[23153]: (root) CMD (echo "cron ran at $(date)" > >>/tmp/cron.out) > Feb 25 09:54:01 alpha crond[23157]: (root) PAM ERROR (Authentication > failure) > Feb 25 09:54:01 alpha crond[23157]: (root) FAILED to authorize user with > PAM (Authentication failure) > Feb 25 09:55:01 alpha cron[23160]: (root) CMD (echo "cron ran at $(date)" > >>/tmp/cron.out) > Feb 25 09:55:01 alpha crond[23164]: (root) PAM ERROR (Authentication > failure) > Feb 25 09:55:01 alpha crond[23164]: (root) FAILED to authorize user with > PAM (Authentication failure) > > AFAICT, it runs the scheduled command except for the very first time. > > I get the same results with normal user's crontab entries. > > -- > Grant Edwards grant.b.edwards Yow! Wow! Look!! A > stray > at meatball!! Let's > interview > gmail.com it! > > > Sounds like a pam configuration error. Try this? http://www.shanison.com/2012/02/08/crontab-error-failed-to-open-pam-security-session-success/ There are a couple of other blogs too on Google search, but all of them describe 'security error'. Your's seems to be different. --089e0115fa7e84a3d604f33e01b0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, Feb 25, 2014 at 9:29 PM, Grant Edwards <grant.b.edwards@gmail.= com> wrote:
On a newly installed syst= em, I'm getting error messages from vixie cron
about PAM authentication errors:

Feb 25 09:52:01 alpha crond[23085]: (root) PAM ERROR (Authentication failur= e)
Feb 25 09:52:01 alpha crond[23085]: (root) FAILED to authorize user with PA= M (Authentication failure)
Feb 25 09:53:01 alpha cron[23118]: (root) CMD (echo "cron ran at $(dat= e)" >>/tmp/cron.out)
Feb 25 09:53:01 alpha crond[23122]: (root) PAM ERROR (Authentication failur= e)
Feb 25 09:53:01 alpha crond[23122]: (root) FAILED to authorize user with PA= M (Authentication failure)
Feb 25 09:54:01 alpha cron[23153]: (root) CMD (echo "cron ran at $(dat= e)" >>/tmp/cron.out)
Feb 25 09:54:01 alpha crond[23157]: (root) PAM ERROR (Authentication failur= e)
Feb 25 09:54:01 alpha crond[23157]: (root) FAILED to authorize user with PA= M (Authentication failure)
Feb 25 09:55:01 alpha cron[23160]: (root) CMD (echo "cron ran at $(dat= e)" >>/tmp/cron.out)
Feb 25 09:55:01 alpha crond[23164]: (root) PAM ERROR (Authentication failur= e)
Feb 25 09:55:01 alpha crond[23164]: (root) FAILED to authorize user with PA= M (Authentication failure)

AFAICT, it runs the scheduled command except for the very first time.

I get the same results with normal user's crontab entries.

--
Grant Edwards =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 grant.b.edwa= rds =C2=A0 =C2=A0 =C2=A0 =C2=A0Yow! Wow! =C2=A0Look!! =C2=A0A stray
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 at =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 meatball!! =C2=A0Let's interview
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 gmail.com =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0it!



There are a couple of other blogs too on G= oogle search, but all of them describe 'security error'. Your's= seems to be different.
--089e0115fa7e84a3d604f33e01b0--