** Description changed: Binary package hint: postfix Ubuntu 9.10, via Update Manager. SOLUTION: 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 abnormal 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 + == SRU template == + + [IMPACT] + + * Locked files prevent adding/removing/modifying system users & groups + * This can result in failure to upgrade/remove packages that use system user names + * The applied fix is to clear the locks on booting. + + [TESTCASE] + + * $ sudo touch /etc/passwd.lock + * $ sudo adduser testing523896 + * FAIL + * Upgrade to new package + * $ sudo adduser testing523896 + * FAIL + * $ sudo reboot (or shutdown & poweron machine in any other way) + * $ sudo adduser testing523896 + * PASS + + * Also you can touch the locks, check that they are there and run `$ + sudo start passwd` to clear them. + + [Regression Potential] + + * We are adding an extra job which will always run at boot, which will have a tiny impact on boot performance + + * The new job can be mis-used directly via `$ sudo start passwd`, but root user could clear the locks in the exact same way as well, before introducing this upstart job.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/523896 Title: useradd: cannot lock /etc/passwd; try again later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/523896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
