2.6.15-rc3: adduser: unable to lock password file

2.6.15-rc3: adduser: unable to lock password file

[JaniD++]

Hello, list,

I get this after upgrade from 2.6.14.2

[root@dy-xeon-1 etc]# adduser someuser
adduser: unable to lock password file
[root@dy-xeon-1 etc]#

I use nfsroot!

Thanks

Janos

Re: 2.6.15-rc3: adduser: unable to lock password file

[Trond Myklebust]

On Thu, 2005-12-01 at 23:47 +0100, JaniD++ wrote:
> Hello, list,
> 
> I get this after upgrade from 2.6.14.2
> 
> [root@dy-xeon-1 etc]# adduser someuser
> adduser: unable to lock password file
> [root@dy-xeon-1 etc]#
> 
> I use nfsroot!

I'm seeing no trouble with locking on 2.6.15-rc3 (with or without the
-onolock option). Could you please use 'strace' to get a dump of what
adduser is failing on?

Cheers,
 Trond

Re: 2.6.15-rc3: adduser: unable to lock password file

[JaniD++]

Hi,

----- Original Message ----- 
From: "Trond Myklebust" <trond.myklebust@fys.uio.no>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, December 02, 2005 1:02 AM
Subject: Re: 2.6.15-rc3: adduser: unable to lock password file


> On Thu, 2005-12-01 at 23:47 +0100, JaniD++ wrote:
> > Hello, list,
> >
> > I get this after upgrade from 2.6.14.2
> >
> > [root@dy-xeon-1 etc]# adduser someuser
> > adduser: unable to lock password file
> > [root@dy-xeon-1 etc]#
> >
> > I use nfsroot!
>
> I'm seeing no trouble with locking on 2.6.15-rc3 (with or without the
> -onolock option). Could you please use 'strace' to get a dump of what
> adduser is failing on?

OK, i will try it, if i can.... (this is a productive online system, maybe
next reboot)

There is some additional info:

[root@dy-xeon-1 root]# mount
192.168.0.1://NFS/ROOT-BASE/ on / type nfs
(rw,hard,rsize=8192,wsize=8192,timeo=5,retrans=0,actimeo=1)
none on /proc type proc (rw,noexec,nosuid,nodev)
192.168.2.100://DY_SYSTEM on /mnt/DY_SYSTEM type nfs
(rw,hard,rsize=16384,wsize=8192,timeo=5,retrans=0,actimeo=1,addr=192.168.2.1
00)
192.168.2.100://MAIL_STORE on /mnt/mail_store type nfs
(rw,hard,rsize=16384,wsize=8192,timeo=5,retrans=0,actimeo=1,noac,addr=192.16
8.2.100)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)
none on /sys type sysfs (rw)
none on /dev/cpuset type cpuset (rw)
/dev/md10 on /mnt/md10 type xfs
(rw,noexec,nosuid,nodev,dirsync,_netdev,noatime,osyncisdsync,noalign)
/dev/md31 on /mnt/md0 type xfs
(rw,noexec,nosuid,nodev,dirsync,_netdev,noatime,osyncisdsync,noalign)

The etc is on /  (the first line.)

After i change the kernel from 2.6.14.2 to 2.6.15-rc3, my system starts to
send error messages about user-existing.
First i starts to search the problem, and finally tracked down to kernel.
(I try to reboot with 15-rc3 and run adduser BEFORE all other service or
script, and the issue is the same.
Than i reboot back to 2.6.14.2, and the error message is gone!)

The adduser sends messages "unable to lock password file", and
sometime -usually first exec- "unable to lock shadow file".

If i know correctly, the nfsroot is only works with NFS v2.
Do you have try it with NFS or exactly on NFSROOT?

On the next reboot, i will try strace....


Cheers,

Janos

>
> Cheers,
>  Trond
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.15-rc3: adduser: unable to lock password file

[Marc Koschewski]

* JaniD++ <djani22@dynamicweb.hu> [2005-12-02 11:55:09 +0100]:

> Hi,
> 
> ----- Original Message ----- 
> From: "Trond Myklebust" <trond.myklebust@fys.uio.no>
> To: "JaniD++" <djani22@dynamicweb.hu>
> Cc: <linux-kernel@vger.kernel.org>
> Sent: Friday, December 02, 2005 1:02 AM
> Subject: Re: 2.6.15-rc3: adduser: unable to lock password file
> 
> 
> > On Thu, 2005-12-01 at 23:47 +0100, JaniD++ wrote:
> > > Hello, list,
> > >
> > > I get this after upgrade from 2.6.14.2
> > >
> > > [root@dy-xeon-1 etc]# adduser someuser
> > > adduser: unable to lock password file
> > > [root@dy-xeon-1 etc]#
> > >
> > > I use nfsroot!
> >
> > I'm seeing no trouble with locking on 2.6.15-rc3 (with or without the
> > -onolock option). Could you please use 'strace' to get a dump of what
> > adduser is failing on?
> 
> OK, i will try it, if i can.... (this is a productive online system, maybe
> next reboot)

I'd rather suggest to _not_ run -rc kernels on productive systems. :)

Marc

Re: 2.6.15-rc3: adduser: unable to lock password file

[JaniD++]

Hi,

> > OK, i will try it, if i can.... (this is a productive online system,
maybe
> > next reboot)
>
> I'd rather suggest to _not_ run -rc kernels on productive systems. :)

Thanks for the warning! :-)

I know it, already.
But have no choice. :(
The older kernels didnt know what i have needed! :-/

eg: i try the 2.6.15-rc3 because 2.6.14.2 gives me this messages:

KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (148)
nfs: server 192.168.2.100 not responding, still trying
nfs: server 192.168.2.100 not responding, still trying
nfs: server 192.168.2.100 not responding, still trying
nfs: server 192.168.2.100 not responding, still trying
nfs: server 192.168.2.100 not responding, still trying
NETDEV WATCHDOG: eth0: transmit timed out
e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
nfs: server 192.168.2.100 OK
nfs: server 192.168.2.100 OK
nfs: server 192.168.2.100 OK
nfs: server 192.168.2.100 OK
nfs: server 192.168.2.100 OK

So, i really did not see different! :-D

Cheers,

Janos

>
> Marc

Re: 2.6.15-rc3: adduser: unable to lock password file

[JaniD++]

Hi,

----- Original Message ----- 
From: "Trond Myklebust" <trond.myklebust@fys.uio.no>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, December 02, 2005 1:02 AM
Subject: Re: 2.6.15-rc3: adduser: unable to lock password file


> On Thu, 2005-12-01 at 23:47 +0100, JaniD++ wrote:
> > Hello, list,
> >
> > I get this after upgrade from 2.6.14.2
> >
> > [root@dy-xeon-1 etc]# adduser someuser
> > adduser: unable to lock password file
> > [root@dy-xeon-1 etc]#
> >
> > I use nfsroot!
>
> I'm seeing no trouble with locking on 2.6.15-rc3 (with or without the
> -onolock option). Could you please use 'strace' to get a dump of what
> adduser is failing on?

Here is the strace-s output:     (20KB)
http://download.netcenter.hu/bughunt/20051203/adduser.log

This problem is always on on 2.6.15-rc3, and newer on 2.6.14.2

Cheers,
Janos

>
> Cheers,
>  Trond
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.15-rc3: adduser: unable to lock password file

[Trond Myklebust]

On Sat, 2005-12-03 at 14:00 +0100, JaniD++ wrote:

> Here is the strace-s output:     (20KB)
> http://download.netcenter.hu/bughunt/20051203/adduser.log
> 
> This problem is always on on 2.6.15-rc3, and newer on 2.6.14.2

OK... Looks like it is bailing out after the lines

link("/etc/passwd.2522", "/etc/passwd.lock") = 0
stat64("/etc/passwd.2522", {st_mode=S_IFREG|0600, st_size=5, ...}) = 0

I'll bet the stat64 is filing to show that the file now has 2 links.

As a first step, could you please grab the 2 patches

  http://client.linux-nfs.org/Linux-2.6.x/2.6.15-rc4/linux-2.6.15-01-nfs-cache-init.dif
and
  http://client.linux-nfs.org/Linux-2.6.x/2.6.15-rc4/linux-2.6.15-02-fix_cache_consistency.dif

and see if they fix the problem?

Cheers,
  Trond

Re: 2.6.15-rc3: adduser: unable to lock password file

[JaniD++]

----- Original Message ----- 
From: "Trond Myklebust" <trond.myklebust@fys.uio.no>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Saturday, December 03, 2005 4:11 PM
Subject: Re: 2.6.15-rc3: adduser: unable to lock password file


> On Sat, 2005-12-03 at 14:00 +0100, JaniD++ wrote:
>
> > Here is the strace-s output:     (20KB)
> > http://download.netcenter.hu/bughunt/20051203/adduser.log
> >
> > This problem is always on on 2.6.15-rc3, and newer on 2.6.14.2
>
> OK... Looks like it is bailing out after the lines
>
> link("/etc/passwd.2522", "/etc/passwd.lock") = 0
> stat64("/etc/passwd.2522", {st_mode=S_IFREG|0600, st_size=5, ...}) = 0
>
> I'll bet the stat64 is filing to show that the file now has 2 links.
>
> As a first step, could you please grab the 2 patches
>
>
http://client.linux-nfs.org/Linux-2.6.x/2.6.15-rc4/linux-2.6.15-01-nfs-cache-init.dif
> and
>
http://client.linux-nfs.org/Linux-2.6.x/2.6.15-rc4/linux-2.6.15-02-fix_cache_consistency.dif
>
> and see if they fix the problem?

done.
No change. :(

Cheers,

Janos



>
> Cheers,
>   Trond
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.15-rc3: adduser: unable to lock password file

[Trond Myklebust]

On Sun, 2005-12-04 at 15:45 +0100, JaniD++ wrote:
> >
> http://client.linux-nfs.org/Linux-2.6.x/2.6.15-rc4/linux-2.6.15-01-nfs-cache-init.dif
> > and
> >
> http://client.linux-nfs.org/Linux-2.6.x/2.6.15-rc4/linux-2.6.15-02-fix_cache_consistency.dif
> >
> > and see if they fix the problem?
> 
> done.
> No change. :(

OK. There is one more patch that I fed into 2.6.15-rc5 and that might
help. Either grab 2.6.15-rc5 from kernel.org, og grab it from

http://client.linux-nfs.org/Linux-2.6.x/2.6.15-rc4/linux-2.6.15-05-fix_attr_updates.dif

Cheers,
 Trond

Re: 2.6.15-rc3: adduser: unable to lock password file

[JaniD++]

>
> OK. There is one more patch that I fed into 2.6.15-rc5 and that might
> help. Either grab 2.6.15-rc5 from kernel.org, og grab it from
>
>
http://client.linux-nfs.org/Linux-2.6.x/2.6.15-rc4/linux-2.6.15-05-fix_attr_updates.dif

Yes, this patch solved the problem. :-)

Thanks,
Janos

>
> Cheers,
>  Trond
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/