up to date 16.04
--
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:
barki@ninja-network:~$ sudo apt-get update
sudo: unable to resolve host ninja-network
[sudo] password for barki:
Ign http://dl.google.com stable InRelease
Ign http://ppa.launchpad.net wily InRelease
Hit http://dl.google.com stable Release.gpg
Barki, sudo rm -f /etc/gshadow.lock ; sudo apt-get install -f
Thanks
--
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
W: Failed to fetch
http://ppa.launchpad.net/bzr/ppa/ubuntu/dists/wily/main/source/Sources
404 Not Found
W: Failed to fetch
http://ppa.launchpad.net/bzr/ppa/ubuntu/dists/wily/main/binary-
amd64/Packages 404 Not Found
W: Failed to fetch
I don't know what jetty is, and I never installed it, it must have came
with a package. I first noticed the terminal mentioning it after I
installed node.js so I'm guessing node.js installed it. Looking it up, I
see its a web server. I use apache2 so I have no reason to have jetty
installed, I've
Heres what happened when I tried to remove jetty:
horse@box:~$ sudo apt-get remove --purge jetty
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
jetty*
0 upgraded, 0 newly installed, 1 to remove and 3 not
** Changed in: shadow (Ubuntu Precise)
Assignee: (unassigned) = neilon johnson (neilonjohnson33)
** Changed in: shadow (Ubuntu)
Assignee: (unassigned) = neilon johnson (neilonjohnson33)
** Changed in: shadow (Ubuntu Quantal)
Assignee: (unassigned) = neilon johnson
Thank you very much for trying to help me, but it is too difficult for
me because I am just a user. After some updates ubuntu works very well
again.
Udo
Am 22.02.2013 17:08, schrieb neilon johnson:
** Changed in: shadow (Ubuntu Precise)
Assignee: (unassigned) = neilon johnson
There is a typo in changelog
* debian/passwd.upstart: Add an ++upstrat++ 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
This bug was fixed in the package shadow - 1:4.1.4.2+svn3283-3ubuntu5.1
---
shadow (1:4.1.4.2+svn3283-3ubuntu5.1) precise-proposed; urgency=low
* debian/passwd.upstart: Add an upstrat job to clear locks on
[shadow-]passwd/group. (LP: #523896).
-- Dmitrijs Ledkovs
I installed the versions of passwd and login from precise-proposed and
followed the testcase and the locks (/etc/passwd.lock and
/etc/group.lock) were removed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member
** Changed in: shadow (Ubuntu Precise)
Status: Fix Released = Fix Committed
** Changed in: shadow (Ubuntu Quantal)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: shadow (Ubuntu Precise)
Status: Fix Committed = Fix Released
--
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
On 23 September 2012 23:43, larrycornutt larrycorn...@yahoo.com wrote:
** Changed in: shadow (Ubuntu Precise)
Status: Fix Committed = Fix Released
No, it was not. The package in precise-proposed and is still pending
verification. If it passes verification that the bug will be fix
I suspect this is related to the mountall binary package?
Which deserves to be condemned to all hell.
How DARE the packagers INFECT a distribution with a binary
upon startup, other than the kernel?
The only binary code upon turning on any computer,
should be the kernel.
Everything else
I could fix this myself if it wasn't for unbelievably
ridiculous shit like this:
On Ubuntu:
root@38r8:~# set |wc -l
6705
…on standard Debian:
4r6s1:~# set | wc -l
50
4r6s1:~#
…really? *Really*?
On Sep 23, 2012, at 4:50 PM, Dmitrijs Ledkovs wrote:
On 23 September 2012 23:43,
FYI: There is a typo on the changelog:
* debian/passwd.upstart: Add an upstrat job to clear locks on
[shadow-]passwd/group. (LP: #523896).
upstrat vs. upstart
Cheers,
Raoul
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Chris, or anyone else affected,
Accepted shadow into precise-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/shadow/1:4.1.4.2+svn3283-3ubuntu5.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Branch linked: lp:ubuntu/precise-proposed/shadow
--
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 was fixed in the package shadow - 1:4.1.4.2+svn3283-3ubuntu7
---
shadow (1:4.1.4.2+svn3283-3ubuntu7) quantal; urgency=low
* debian/passwd.upstart: Add an upstrat job to clear locks on
[shadow-]passwd/group. (LP: #523896).
-- Dmitrijs Ledkovs dmitrij.led...@ubuntu.com
** 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
Fix uploaded into quantal, waiting in unapproved queue.
** Changed in: shadow (Ubuntu Quantal)
Status: In Progress = Fix Committed
** Changed in: shadow (Ubuntu Quantal)
Assignee: Dmitrijs Ledkovs (xnox) = (unassigned)
--
You received this bug notification because you are a member
Fix uploaded into precise-proposed, waiting in unapproved queue.
** Changed in: shadow (Ubuntu Precise)
Assignee: Dmitrijs Ledkovs (xnox) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~dmitrij.ledkov/ubuntu/quantal/shadow/clear-locks
** Branch linked: lp:~dmitrij.ledkov/ubuntu/precise/shadow/clear-locks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523896
** Changed in: shadow (Ubuntu Quantal)
Status: Triaged = In Progress
--
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
** Changed in: shadow (Ubuntu Precise)
Assignee: Canonical Foundations Team (canonical-foundations) = Dmitrijs
Ledkovs (dmitrij.ledkov)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523896
** Changed in: shadow (Ubuntu Quantal)
Assignee: Canonical Foundations Team (canonical-foundations) = Dmitrijs
Ledkovs (dmitrij.ledkov)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523896
Just got bit by this one again, clean lucid install. The fix is to rm
-f /etc/gshadow.lock.
sudo do-release-upgrade finishes with this:
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
Setting up dbus (1.4.18-1ubuntu1) ...
Regarding #17 - I did just experience this problem but with
/etc/group.lock instead of passwd. I did use a Guest session
immediately before I discovered the breakage. The Guest account crashed
when I attempted to play Open Arena, probably due to a fglrx bug. There
was a leftover guest-
** Changed in: shadow (Ubuntu Precise)
Milestone: ubuntu-12.04.1 = ubuntu-12.04.2
--
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.
i dont have permission to remove the files
--
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
verify that you are de root user command whoami else login with sudo su and
try the process for remove files
2012/7/11 nick s n123...@yahoo.com
i dont have permission to remove the files
--
You received this bug notification because you are subscribed to a
duplicate bug report (988995).
** Tags added: rls-q-incoming
--
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:
** Tags removed: rls-q-incoming
--
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:
typos1 - the bug description contains information about how to get
around the bug.
--
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
My upgrade to 12.04 has failed because of this.
I ve got an amd64 processor and using 64bit version, though.
What should I do get to get around it ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: bugpattern-written
--
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:
This has turned up on the radar again because whoopsie tries to call
adduser on upgrade to 12.04, and many users are finding their
/etc/passwd locked. We should update shadow to clear lock on boot.
** Also affects: shadow (Ubuntu Precise)
Importance: Undecided
Status: New
** Also
** Changed in: shadow (Ubuntu)
Assignee: Ubuntu Foundations Team (ubuntu-foundations-team) = Canonical
Foundations Team (canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm not really worried by the consistency of single files (each one are
updated atomically).
The problem is the inconsistency between files (e.g. /etc/passwd and
/etc/shadow).
I'm not sure what would be the worst case if for example /etc/passwd is updated
but /etc/shadow is not.
--
You
On Sat, Aug 06, 2011 at 08:43:29AM -, Nicolas François wrote:
I'm not really worried by the consistency of single files (each one are
updated atomically).
The problem is the inconsistency between files (e.g. /etc/passwd and
/etc/shadow). I'm not sure what would be the worst case if for
** 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
It's been suggested that this might be a duplicate of bug 432964, which
is described as system crash in guest session locks /etc/passwd
forever. Can the submitters of this bug and duplicates confirm whether
they've used Ubuntu guest sessions on the affected system, and whether
they saw crashes
** Changed in: shadow (Ubuntu)
Assignee: (unassigned) = Ubuntu Foundations Team (ubuntu-foundations-team)
--
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
, 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
** 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
** 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
** Tags added: armel
--
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:
Might be a duplicate of bug 432964.
** Changed in: shadow (Ubuntu)
Status: Incomplete = Confirmed
--
useradd: cannot lock /etc/passwd; try again later.
https://bugs.launchpad.net/bugs/523896
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
--
useradd: cannot lock /etc/passwd; try again later.
https://bugs.launchpad.net/bugs/523896
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I had the same situation on my ubuntu 9.10 Karmic , I was trying to add my user
id to dba Group in order to star
and stop the DB services by own ,
r...@ubuntu:~$ usermod -a -G dba raja
usermod: cannot lock /etc/passwd; try again later.
i checked for any process locked the /etc/passwd file but
I had the same situation here, it turns out it was a stuck useradd process -
destroying it got useradd working again, something like this:
killall -9 userdel
rm -f /etc/*lock
In my case the stuck useradd was caused by a bug in my own script, but
for the others, if it was caused by the
the same problem after install some packages
all installation programs ends with error by:
userdel: cannot lock /etc/shadow; try again later.
--
useradd: cannot lock /etc/passwd; try again later.
https://bugs.launchpad.net/bugs/523896
You received this bug notification because you are a member
Just a note for any future bug reporter:
It is now clear that it happens that the passwd or shadow (or group, or
gshadow) files can be locked.
The me also messages are not very useful (and will not make the resolution of
this bug, if it is really a bug, any faster).
Please provide instead any
I'm having the same problem trying to install open ssh server off a
fresh install although it is set up with nss to use ldap. The file
permissions are the same as on the other computers, fuser displays no
processes using the file and lslk also displays no locks. The groupadd
and groupmod work but
From what I could tell the passwd.lock and shadow.lock files had not
been removed. I don't remember the permissions but they looked correct
at the time. I can no longer reproduce the error as I have reloaded my
machine for a separate reason.
--
useradd: cannot lock /etc/passwd; try again
56 matches
Mail list logo
