Comment 16 for bug 523896

thnax for the solution............

Best Regards
Akil Afzal Dhrubo

Intern Technical Analyst
Standard Chartered Bank

Institute of Information Technology
University of Dhaka

From: Brian Murray <email address hidden>
To: <email address hidden>
Sent: Thursday, July 28, 2011 2:08 AM
Subject: [Bug 523896] Re: useradd: cannot lock /etc/passwd; try again later.

** Changed in: shadow (Ubuntu)
    Assignee: (unassigned) => Ubuntu Foundations Team (ubuntu-foundations-team)

You received this bug notification because you are subscribed to a
duplicate bug report (684168).

  useradd: cannot lock /etc/passwd; try again later.

Status in “shadow” package in Ubuntu:

Bug description:
  Binary package hint: postfix

  Ubuntu 9.10, via Update Manager.


  Look for /etc/group.lock, /etc/passwd.lock and /etc/shadow.lock files
  and remove them.

  Be careful to only remove the files ending in 'lock' or else you might
  damage your system.

  Please do not add comments just containing "Me too", instead please provide any information that could indicate why the files were locked:
  * the list of locked files:
      ls /etc/passwd.lock /etc/shadow.lock /etc/group.lock /etc/gshadow.lock

  * check the /var/log/auth.log for any message that could indicate the
  failure of any other tool (prior to the failure which reported the
  locked file)

  * any anormal operation on the machine (reset, shutdown while the
  computer is still running)

  ProblemType: Package
  Architecture: i386
  Date: Thu Feb 18 09:49:47 2010
  DistroRelease: Ubuntu 9.10
  ErrorMessage: subprocess installed post-installation script returned error exit status 1
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: fglrx
  Package: postfix 2.6.5-3
  ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
  SourcePackage: postfix
  Title: package postfix 2.6.5-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
  Uname: Linux 2.6.31-19-generic i686

To manage notifications about this bug go to: