filePro error - BLOB

[Fairlight]

Rule #1:  NEVER trust filePro to report its errors accurately.  EVER.

My suggestion:

strace -o /tmp/josefpdebug.txt -s 2048 -f [rest of filePro command]

Do what you need to do, then analyse /tmp/josefpdebug.txt with `less` for
clues.  You can, in general, start near the end, or search forwards for "A
System Error Has Occurred" and scroll backwards to find what it's -really-
using right before it breaks.

Even if you start from runmenu, it's going to show you every syscall, open,
read, write, close for -every- process, since the -f tells it to follow
forked children.

You may get at the bottom of what is -really- going on.  For instance, I
had a problem with (supposedly) index.A, but it was really a problem with
index.I, as shown by the fact it was sequentially opening indexes and
stopped opening them after J, preferring to segfault instead.

Don't get hung up on all the fcntl calls and such.  Focus on what happened
"right before" the error (it may be buried in a flurry of harmless fcntls),
and focus on open(), read(), write(), seek(), and the results of those
calls.  If you see it having issues with a particular file descriptor, like
the last thing it sensibly does is read() from fd 7, search backwards from
there to the last place that has "= 7" which was an open(), and you've
likely found your culprit.

It takes some acclimation, but seriously...this will tell you what -really-
happened.  Relying on filePro's idea of what happened has less chance of
being helpful than using a Magic 8-Ball.  Sometimes, I think your odds of
winning the lottery are higher than filePro accurately reporting an error
in anything other than a syntax check.  (And sometimes, even then...)

mark->

On Wed, Oct 02, 2013 at 09:36:51AM -0400, fpgroups . thus spoke:
> Hello everyone ...
> 
> The error:
> 
> *** A System Error Has Occurred ***
> /var/appl/fpt/filepro/marker/blob: No such file or directory
> 
> 
> The kicker:
> file "marker" does not have a "blob" field at all.
> 
> I've tried "blobfix" and problem persists.  If I >blob within
> filepro/marker, the error changes to
> 
> *** A System Error Has Occurred ***
> /var/appl/fpt/filepro/marker/blob: Success
> 
> 
> This is while running on a linux based server filepro version 5.7.00.02D4
> 
> filePro application was recently migrated from an SCO server and 'marker'
> is the ONLY file thus far that has encountered this error.  Funny thing is
> that the application is so old, BLOB was not even a word or anything anyone
> ever talked about in the filePro arena.
> 
> Really stuck with this - Your prompt assistance will be appreciated!
> 
> Regards,
> 
> 
> Jose Lerebours
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20131002/5d2a87ed/attachment.html 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 

-- 
Audio panton, cogito singularis.