Re: No locks available.

2012-02-02 Thread Christofer C. Bell
On Tue, Jan 31, 2012 at 11:13 AM, lina wrote: > > $ fuser > -bash: fuser: command not found > > uname -a > Linux 2.6.9-42.0.10.ELlargesmp #1 SMP Tue Feb 27 09:59:08 EST 2007 > x86_64 x86_64 x86_64 GNU/Linux > > >From the looks of this uname(1) output, you're on a RHEL 4 (or clone) system and not

Re: No locks available.

2012-01-31 Thread lina
On Fri, Jan 27, 2012 at 5:08 AM, Panayiotis Karabassis wrote: > An idea: > > Can you see if this command returns any PIDs? Sorry I did not notice this email. > > $ fuser -m a.log $ fuser -bash: fuser: command not found uname -a Linux 2.6.9-42.0.10.ELlargesmp #1 SMP Tue Feb 27 09:59:08 EST 2007

Re: No locks available.

2012-01-26 Thread Panayiotis Karabassis
An idea: Can you see if this command returns any PIDs? $ fuser -m a.log On 01/21/2012 05:12 PM, lina wrote: > On Sat, Jan 21, 2012 at 10:53 PM, Camaleón wrote: >> On Sat, 21 Jan 2012 22:36:30 +0800, lina wrote: >> >>> On Sat, Jan 21, 2012 at 10:26 PM, Camaleón wrote: >> Can you please tel

Re: No locks available.

2012-01-21 Thread lina
On Sat, Jan 21, 2012 at 10:53 PM, Camaleón wrote: > On Sat, 21 Jan 2012 22:36:30 +0800, lina wrote: > >> On Sat, Jan 21, 2012 at 10:26 PM, Camaleón wrote: > >>> Can you please tell where is located that "a.log" file and what >>> software generates it? > >> The a.log is in the working directory. I

Re: No locks available.

2012-01-21 Thread Camaleón
On Sat, 21 Jan 2012 22:36:30 +0800, lina wrote: > On Sat, Jan 21, 2012 at 10:26 PM, Camaleón wrote: >> Can you please tell where is located that "a.log" file and what >> software generates it? > The a.log is in the working directory. In other servers, it works fine. > so it only has problem on

Re: No locks available.

2012-01-21 Thread lina
On Sat, Jan 21, 2012 at 10:26 PM, Camaleón wrote: > On Sat, 21 Jan 2012 17:37:28 +0800, lina wrote: > >> Few days ago I met below issue: >> >> Failed to lock: a.log. No locks available. >> >> the a.log is in present directory. I asked on other list wh

Re: No locks available.

2012-01-21 Thread Camaleón
On Sat, 21 Jan 2012 17:37:28 +0800, lina wrote: > Few days ago I met below issue: > > Failed to lock: a.log. No locks available. > > the a.log is in present directory. I asked on other list which is the > software related issue. > > was suggested to move the a.log

No locks available.

2012-01-21 Thread lina
Hi, Few days ago I met below issue: Failed to lock: a.log. No locks available. the a.log is in present directory. I asked on other list which is the software related issue. was suggested to move the a.log to another directory and moved back to continue. but not work. Can someone give me some