[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[IDV #HWF-642685]: Bundle created on one machine fails on others
- Subject: [IDV #HWF-642685]: Bundle created on one machine fails on others
- Date: Tue, 07 Jan 2014 10:26:46 -0700
> Unidata support,
>
> I offer further tidbits of info about this problem. (Where did the term
> "tidbit" come from, anyway?)
>
> When I access the same data source as before as a local file (instead of via
> our RAMADDA server), save the bundle, remove all displays and data, and
> reload the bundle, the display is created just fine, both on my office
> machine (where I created it) and on our student machines (which access a copy
> of the bundle placed within their reach). The data source(s) is (are)
> accessible as local file(s) to all of these machines (thanks to NFS mounts).
>
> The originally reported problem is looking like a RAMADDA issue to me.
>
> I'm running RAMADDA vs. 1.5.
>
> (Also, in case I didn't already say so, the original bundle, which accessed
> the data source files (via symbolic links to the real data files) via our
> RAMADDA server and time-aggregated them, failed to create a display on my
> office machine (where the bundle was created in the first place) as well as
> on all of our other machines. At least that failure is consistent!
>
> I've attached a revised version of the bundle that accesses the data source
> files as local files (so you can't load it yourselves. Also, since I had to
> recreate the bundle from scratch (because the original one using the RAMADDA
> server wouldn't work), there are inevitably going to be other differences
> between the two versions that don't pertain to the problem.
>
> By the way, if I create a bundle that fails due solely to data access issues
> like the one reported in this support request, is there a way to salvage all
> the display specifications so that I don't have to recreate them once the
> data access issue is resolved? That would save a lot of work! (Even editing
> the bundle by hand is something I'm willing to do, if I knew needs to be
> fixed in it, and how to fix it.)
>
> -- Dave
>
> ***************************************************************
> * Dr. Dave Dempsey | ^ ___ \|/
> *
> * Dept. of Earth & Climate Sciences | ) ^ /||_||\ --0-- *
> * San Francisco State University | ) ) / ||_|| \ /|\ *
> * 1600 Holloway Ave. | ) ) / ||_|| \
> *
> * San Francisco, CA 94132 | ) ) / ||_|| \ ^ *
> * | ) ) )
> ||_|| \ *
> * Phone: (415) 338-7716 | ) ) )~||~||~~~~ \~~*
> * FAX: (415) 338-7705 | ) ) ) ) ~ ~ ~ ~ ~ ~*
> * Email: address@hidden | ) ) ) ) ) ~ ~ ~ ~ *
> ***************************************************************
>
>
>
>
>
>
Dave,
I talked to Don and he believe it is fixed in the 1.6, you can reinstall
the 1.6 release.
Yuan
Ticket Details
===================
Ticket ID: HWF-642685
Department: Support IDV
Priority: Critical
Status: Closed