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 it's writing to it. 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 RRD Yves, Think you missed the point let me reclarify for you. You are having problems with the update of the rrd so why not run the rrdtool update from server A rather than running it on server b on the files stored on server A as you are doing now. If for some reason you want to keep all the processing and upadtes on server b why not use rsh or ssh so they are started from server b but actually run on server a. Hope this helps a little Alister =) -------------------------- Sent from my BlackBerry Wireless Handheld (www.BlackBerry.net) -----Original Message----- From: Yves Caetano <[EMAIL PROTECTED]> To: Alex van den Bogaerdt <[EMAIL PROTECTED]> CC: RRD users <[email protected]> Sent: Sun Apr 28 21:26:29 2002 Subject: [rrd-users] Re: Could not lock RRD 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 you can give me some advise. thanks cu ycae Alex van den Bogaerdt wrote: > 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. The problem is that locking over nfs cannot be > done in a reliable way. > > > The rrd files are on a file server, and a processing server is connected > > to this file server through nfs to get the rrd files to process. > > Let's give the two servers a name: A and B. > > What I think you said is: > - on server A you have your RRD files > - on server A you run "rrdtool update" > - server B has mounted some of the disk of server A > - on server B you run "rrdtool graph" and receive an error > > What probably works for you is to nfs mount the other way around; let > server A access server B. Then you can start "rrdtool graph" on server > A and still write the images directly to server B > > HTH > -- > __________________________________________________________________ > / [EMAIL PROTECTED] [EMAIL PROTECTED] \ > | work private | > | My employer is capable of speaking therefore I speak only for myself | > +----------------------------------------------------------------------+ > | Technical questions sent directly to me will be nuked. Use the list. | > +----------------------------------------------------------------------+ > | http://faq.mrtg.org/ | > | http://rrdtool.eu.org --> tutorial | > +----------------------------------------------------------------------+ -- Yves Caetano Ubizen Security Analyst We Secure e-Business Phone +352 26 31 58 60 http://www.ubizen.com Fax +352 26 31 58 69 http://www.securitywatch.com -- Attached file removed by Listar and put at URL below -- -- Type: application/x-pkcs7-signature -- Desc: S/MIME Cryptographic Signature -- Size: 2k (2925 bytes) -- URL : http://www.ee.ethz.ch/~slist/pantomime/35-smime.p7s -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/rrd-users WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/rrd-users WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
