pam_acct_mgmt(): user account has expired (was Re:Login
larrykh465 at SoftHome.net
Mon Mar 8 01:09:16 PST 2004
On Saturday, March 06, 2004 5:42:56 PM Barry Hawkins
<ly5t5 at allthingscomputed.com> wrote:
On Mar 4, 2004, at 1:33 PM, Gerard Seibert wrote:
> I am running FreeBSD 5.2.1 - RELEASE #0: Mon Feb 23 20:45:55 GMT 2004
> It seems that I can no longer log into my system. Upon boot-up, the
> usually login appears. I enter my normal login and then my password. I
> then greeted with this error message:
> BudMan login: pam_acct_mgmt(1): user account has expired
> Login Incorrect.
> Shortly afterwards I receive these error messages:
> BudMan cron _secure_path: /usr/home/ges/.login_conf is not owned
> The last error message will repeat with the number getting
> This is a fresh install of FreeBSD. The only thing I added was KDE 3.2
> today. Can anyone tell me what has happened and how do I get back into
> Thanks in advance!
> Gerard Seibert
> gerard-seibert at rcn.com
I am having a similar issue logging in on 5.2.1-RC2, and it seems to
have happened around the time I added a user and some groups using the
KUser utility in KDE. All accounts, including root, are "expired". My
error message is:
login: pam_acct_mgmt(): user accound has expired
Then, a bit later, I receive messages like the following:
kernel: psmintr: out of sync (0008 != 0000)
kernel: psmintr: discard a byte(1)
On a side note, the message really does display "accound" instead of
"account"; it's not a typo of mine. Searches on the following phrases
within the questions and newbies mailing lists produced no leads for me
'pam_acct_mgmt(): user accound has expired'
Barry C. Hawkins
All Things Computed
********** Reply Separator **********
Sunday, March 07, 2004 1:44:11 PM
That is exactly what I was doing when this problem occurred. I am going
to the KDE site and report this problem. It might be a bug of some sort.
You might want to do the same if you have not all ready.
As a side bar, in the master.passwd file, near the top, is an entry
that includes: "Charlie &". Is it possible, or should I say, advisable
to change that entry manually or just leave it as is?
gerard-seibert at rcn.com
I had a similar problem when I upgraded from FBSD 4.9/KDE 3.14 to 4-stable/
KDE 3.2 ie:
I could not su from a console window it would give me the account expired msg
and if tried to change consoles by <ctrl>,<alt>, <Fx> I could not log in as
I could login as root from kdm
I used Kuser and reset the passwords for root and my other 2 users and it
started working again, I can su and login to other consoles as expected
dont know if this helps as I am a newbee and most of the stuff that people are
asking about is either way over my head or the answer I know comes directly
from the hand book.
More information about the freebsd-questions