package vsftpd 2.3.5-1ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

[Projetaty Soluções OpenSource]

Could not install 'vsftpd'

The upgrade will continue but the 'vsftpd' package may not be in a working state. Please consider submitting a bug report about it.

subprocess installed post-installation script returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: vsftpd
ProcVersionSignature: Ubuntu 3.2.0-44.69-generic 3.2.44
Uname: Linux 3.2.0-44-generic i686
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: i386
Date: Tue May 28 11:40:59 2013
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Blackbuntu - Release i386
MarkForUpload: True
SourcePackage: vsftpd
Title: package vsftpd 2.3.5-1ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to precise on 2013-05-28 (0 days ago)

[Robie Basak (racb)]

From log:

useradd: cannot lock /etc/passwd; try again later.
adduser: `/usr/sbin/useradd -d /srv/ftp -g ftp -s /bin/false -u 148 ftp' returned error code 1. Exiting.
dpkg: error processing vsftpd (--configure):
 subprocess installed post-installation script returned error exit status 1

[Robie Basak (racb)]

Thank you for your report.

This looks like a local configuration problem, rather than a bug in Ubuntu, so I'm marking this bug as Invalid.

Specifically, it looks like you have a /etc/passwd.lock lockfile left over from a previous problem.

You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug rather than a problem specific to your system, and then change the bug status back to New.