On Tue, Jun 24, 2003 at 11:54:15AM -0600, Boulytchev, Vasiliy wrote:
> I get this error once everyday, stopping the rrdtool from logging.
> I have researched this, but most threads lead to NFS, I am not running
> NFS on the box at question. Please explain the nature of this error.
> =20
> THA
ROTECTED]>
To: "Alister Burrell" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>;
Sent: Sunday, April 28, 2002 3:23 PM
Subject: [rrd-users] Re: Could not lock RRD
>
> Yesterday Alister Burrell wrote:
>
> >
> > Hrm may have misread Alex's post the
Thanks to all of the community of the rrdtool.
thanks to tobias oetiker who saved my live :-))it is working :-)) and many
thanks to all the people helping me through this debugging process :-)
cu ycae
Tobias Oetiker wrote:
> Yesterday Alister Burrell wrote:
>
> >
> > Hrm may have misread Al
Yesterday Alister Burrell wrote:
>
> Hrm may have misread Alex's post there these 12 hour shifts take their tole
> :(
>
> Are there problems accesing rrds over NFS for graphing ? I though it was
> just when it was updating as it tries to lock the file so no other process
> can mess with it while
.
Alister =)
--
Sent from my BlackBerry Wireless Handheld (www.BlackBerry.net)
-Original Message-
From: Alister Burrell <[EMAIL PROTECTED]>
To: '[EMAIL PROTECTED]' <[EMAIL PROTECTED]>
Sent: Sun Apr 28 21:39:11 2002
Subject: Re: [rrd-users] Re: Could not lock
Dear Alex,
Basicaly the Server A is the nfs server with all the files on it. Server B is
doing the whole rrd processing. Nothing is done on Server A. I cannot do the
nfs the other way around, cause the data on server A is very big and there is
no possibility to store this on server B :-(.
Hope yo
Yves Caetano wrote:
> i have a small problem with the rrdtool.or may be a bigger problem.
> when trying to update the rrd file, i get an error message "Could not
> lock RRD". I read some messages in the mailinglist that there are
> problems running the rrdtool over nfs.
Indeed there are. Th
Don't use NFS. I tried to get it working for weeks with no success.
Paul
>>> Ashton MacAndrews <[EMAIL PROTECTED]> 08/21/01 17:53 PM >>>
Having trouble locking across an NFS mount ...
unable to update `slog.rrd': could not lock RRD
Suggestions?
--
Unsubscribe mailto:[EMAIL PROTECTED]
Hel
At 14:50 21/08/01 -0700, you wrote:
>
>Having trouble locking across an NFS mount ...
>Suggestions?
I hate to sound blunt, but "Don't use NFS" comes to mind.
It has been mentioned many times that there is a bit performance hit when
using NFS. You should consider keeping the RRD files locally or
Alex van den Bogaerdt wrote:
>A few days ago somebody posted information on a client-server
>application that can access/update rrdtool files remotely. This
>is not on the basis of file sharing (nfs) but on the basis of
>sockets. It may have been on the MRTG list, not sure about that,
>if someb
Ashton MacAndrews wrote:
>
> Having trouble locking across an NFS mount ...
>
> unable to update `slog.rrd': could not lock RRD
>
> Suggestions?
Using nfs (for rrdtool) is not recommended. The obvious
solution is in this case also the best one (probably):
A few days ago somebody posted infor
On Tuesday 06 March 2001 22:44, Dave Plonka wrote:
> On Tue, Mar 06, 2001 at 04:22:01PM -0500, Paul C. Williamson wrote:
> > I am trying to run mrtg/rrd from box 2, but the configs and data live on
> > box 1. When I try to run 'box2/mrtg box1/mrtg.cfg', mrtg comes back to
> > tell me that rrdtool
On Tue, Mar 06, 2001 at 04:22:01PM -0500, Paul C. Williamson wrote:
>
> I am trying to run mrtg/rrd from box 2, but the configs and data live on box
> 1.
> When I try to run 'box2/mrtg box1/mrtg.cfg', mrtg comes back to tell me that
> rrdtool could not update blah.rrd with the data it retriev
13 matches
Mail list logo
