https://forums.qrecall.com/recentTopics/list.page JForum - http://www.jforum.net
[b][tt]QR_COMMAND_SUCCESS[/tt][/b]: This is '1' if the command finished normally. Note that this does not mean "complete". It means there was not a failure. Cancelling an action is not considered to be a "failure."

[b][tt]QR_COMMAND_CANCELED[/tt][/b]: This variable is only present if the command was canceled. So if you want to do something when an action is canceled, you need to look for the presence of this value. The value is a number that indicates the source of the cancel message. For example, the value '4' means that a [tt]TERM[/tt] (i.e. "Quit") signal was sent by another process. It is not a user or process ID. See the [url=https://www.qrecall.com/sc/qr/help/3_0/English.lproj/guide/auto/action_scripts.html]documentation[/url] for a complete list of possible values and their meaning.

[b][tt]QR_COMMAND_EXCEPTION[/tt][/b]: The documentation isn't actually correct on this value. It will certainly be present if [tt]QR_COMMAND_SUCCESS[/tt] is '0', but it can also be present if something (like a user cancel) interrupted the normal progress of the action. This is, I believe, what you're seeing in your example.

I hope that helps a little, and if you follow up with a description of what you'd like your script to do I'm confident that something can be crafted that will accomplish that.]]> https://forums.qrecall.com/posts/preList/749/12357.page https://forums.qrecall.com/posts/preList/749/12357.page GMT https://forums.qrecall.com/posts/preList/5053/12329.page https://forums.qrecall.com/posts/preList/5053/12329.page GMT
Action 2025-03-24 20:01:37 Failure cs_pc_a/evt_journalAttr_38CC956E-31E0-4AAE-A6ED-331771D2BED4_44652778_459.journal

...or...

Action 2025-02-04 10:10:44 Failure speakerRecognition/24D60-915b2b7b58cda908d393076c1774553c56bf6550_15.1033.1-int8_conformer_matrix_split-15.1033.1-en-US.bnnsir


The files that are not captured are not consistent; they seem to cluster around different aspects of the system each time.

This problem just started showing up a couple of weeks ago. Does anyone have any ideas?]]> https://forums.qrecall.com/posts/preList/5055/12327.page https://forums.qrecall.com/posts/preList/5055/12327.page GMT https://forums.qrecall.com/posts/preList/948/12311.page https://forums.qrecall.com/posts/preList/948/12311.page GMT
sorry, this took a while as I was busy with other stuff ...

Uninstalling the old version (using the procedure you described) worked very well; I could reinstall QRECALL and [b]it is working again perfectly.

Thanks a lot for your great support and for this great product![/b]]]> https://forums.qrecall.com/posts/preList/5031/12308.page https://forums.qrecall.com/posts/preList/5031/12308.page GMT Start by sending a diagnostic report (QRecall app > Help > Send Report).]]> https://forums.qrecall.com/posts/preList/5005/12287.page https://forums.qrecall.com/posts/preList/5005/12287.page GMT
Let me start by saying that QRecall does not store "snapshots" in the traditional sense. It stores "delta"—each layer stores only the differences between it and the previously captured version of each item. See QRecall > Help > Guide > Layers > Understanding Layers for a complete explanation.

You can focus in on a layer (or a group of layers) by adjusting the shades (top and bottom) to narrow your view of what's been captured. But if you then try to recall those items (with both upper and lower shades in place), you won't be recalling all of your items. You'll only be recalling the items that changed and were recaptured in that layer (or layers). See the warning "Recalling folders with top layer shaded" at the end of the help section QRecall > Help > Guide > Layers > Layer Shades.

[quote=james_smith]I chose the right snapshot in the QRecall interface for the restore.
I made sure the incremental backup finished without any issues before I started restoring.
The file versioning looks okay for some documents, yet some files seem to be left out.[/quote]
Did you "choose" your layer by adjusting the shades? If so, then recalling a folder of items would only recall the items in that folder that were recaptured by those layers. All unaltered items would excluded from the capture.

The solution is to use the shades to find the version of the items you want to recall. This is done using the bottom shade, and the bottom shade only. (Basically, you're hiding more recent version of the items to locate and earlier version of that item.) Now a recall will include all of the items.

If you want to use the top shade, remember to run the top shade back to the top before recalling a folder or package.
]]> https://forums.qrecall.com/posts/preList/5024/12274.page https://forums.qrecall.com/posts/preList/5024/12274.page GMT
For all kinds of reasons, QRecall components can be mis-installed, or get mis-updated, or just don't run.

The simplest solution to these kinds of problems is to completely un-install QRecall and then reinstall it from scratch.

In QRecall 3, this is most thoroughly accomplished using the "[tt]uninstall[/tt]" script included in the QRecall application bundle. To do this, follow these steps:

[list]Quit all of your other applications (the uninstall will perform a system restart, so you want to make sure you've saved your work).[/list]
[list]Open the Terminal app[/list]
[list]In the terminal, execute this command:[/list][tt]    /Applications/QRecall.app/Contents/Resources/uninstall.sh[/tt]

The command will prompt you for your administrator password, uninstall all active QRecall components, and then restart your system.
(Note: this assumes QRecall is located in your [tt]/Applications[/tt] folder; if it isn't, adjust the path accordingly.)

[list]Following the restart, launch the QRecall application and let it reinstall itself.[/list]
That should resolve your problems. Let us know if it doesn't.
]]> https://forums.qrecall.com/posts/preList/4956/12150.page https://forums.qrecall.com/posts/preList/4956/12150.page GMT :)

[quote]Yes, the restart solved it, so it is working as expected.[/quote]
That's a relief to hear!

[quote]in the older version, when creating a new archive, the "Data redundancy" by default is set to "1:8" (which I think is a good choice); but the current version, by default, redundancy is switched off.[/quote]
I was encountering too many customers who had redundancy turned on for archives stored on RAID or cloud drives, which themselves provide their own error correction, which is—dare I say it?—redundant. So I made this particular feature "opt-in".

[quote]BTW: when I find some time I might test the redundancy (by "destroying" some data using a hex-editor) :-)[/quote]
Have fun! That's the way we test it here. (I even wrote a custom tool that scrambles random bits of a file so I could automate the tests.)]]> https://forums.qrecall.com/posts/preList/4943/12132.page https://forums.qrecall.com/posts/preList/4943/12132.page GMT
[quote=Olfan]By the time I took notice the log file was some 180GiB in size. I panicked, killall'ed QRecallHelper and deleted the QRecall.log so it wouldn't choke my Mac with clogged local storage. [URL=https://sharpedgeshop.com/collections/gyuto-knives-chefs-knife]https://sharpedgeshop.com/collections/gyuto-knives-chefs-knife[/URL] [/quote]

That was clearly the right thing to do. Once the connection to the volume was broken, the helper process was useless anyway.

QRecall's pretty fanatic about logging everything it does, but even I'm having trouble thinking of anything that would generate 180GB of log data without stopping. Most logging is self-limiting: you get an error, or three, or a hundred, but ultimately the process gives up, logs one final "I've given up" message, and terminates.

The only code that will log an error and continue to plow ahead is during a repair, and that code (at least in QRecall 3.0) does limit the number of messages it logs before logging just a summary. There is also code that corrects slightly damaged data, but if the drive was dis-connected there's no way successive corrections could be successful.

So without a peak at what was getting logged, I can't offer much in the way of useful suggestions, other that what you've already done.[/quote]
Your troubleshooting approach seems quite thorough, especially given the intricacies of handling log data. It's impressive how QRecall is designed to log and handle errors, limiting the potential for runaway log growth.]]> https://forums.qrecall.com/posts/preList/4845/12109.page https://forums.qrecall.com/posts/preList/4845/12109.page GMT
Any ideas?]]> https://forums.qrecall.com/posts/preList/4935/12098.page https://forums.qrecall.com/posts/preList/4935/12098.page GMT What tasks get assigned to what CPU is completely outside QRecall's control. That's entirely the job of the Darwin kernel and I know of no way to influence it.

Also note that modern, mobile, CPUs often have one core that's more powerful, with auxiliary cores that are more efficient. So intensive tasks vs. light/periodic tasks are going to favor one core, or one type of core, over others.[/quote]
Thank you for shedding light on the intricacies of CPU tasks allocation.]]> https://forums.qrecall.com/posts/preList/1913/12072.page https://forums.qrecall.com/posts/preList/1913/12072.page GMT
/UserName/ExcludeMeDir[/quote]
This might be because your home folder is mounted on an another (not the startup) volume? This creates confusion for the bookmarks.


[quote]I deleted this so there are no entries in the [b]Specific Items[/b] section and I'll trying entering it as a reg exp pattern now:

path
//Volumes/OtherHD/Users/UserName/ExcludeMeDir

pattern:
*

infinity: checked[/quote]
Close ;)

Absolute patterns are anchored to the root directory of each volume.

You'd actually want something like this:
[code]/Users/UserName // ExcludeMeDir [ ] glob[/code]
To exclude the entire folder, or to be more subtle:
[code]/Users/UserName/ExcludeMeDir // * [ ] glob[/code]
to exclude just the contents of that folder.

If you're still having problems, there are even more esoteric things to try.]]> https://forums.qrecall.com/posts/preList/4887/12062.page https://forums.qrecall.com/posts/preList/4887/12062.page GMT https://forums.qrecall.com/posts/preList/4907/12048.page https://forums.qrecall.com/posts/preList/4907/12048.page GMT Not Command, Control. ;) Option+Control changes to "Delete" to "Disconnect...", ... but you figured it out ;)

[quote]Checking the cascade scheduled action seemed okay, running it wouldn't work, though.[/quote]
This also isn't making any sense, since both the action and the interactive command end up doing the same thing: launching a background instance of QRecallHelper to preform the action.

I'm also seeing really anomalous messages in your log, like this one:[code]unreadable sequence file; using legacy sequence[/code]Which makes no sense because this file gets recreated during the repair and is readable by the user.

So I have to suspect that there's some strangeness(™) going on with the storage device and/or the security framework.

I have two suggestions.

First, make sure there are no restrictions on QRecall by going to the System Settings > Privacy & Security > Files and Folders. Find the various QRecall component (particularly QRecallHelper) and make sure everything is enabled. (Alternatively, add QRecallHelper to the Full Disk Access category.)

Second suggestion is, if the QRecall02 volume is only used for QRecall archives, select the volume in the Finder, choose Get Info, and at the bottom check "Ignore ownership on this volume".

[quote]I did notice that the qrstackconfigs in the archive and in the Stacks prefs folder differ in many places but couldn't see what the differences mean.[/quote]
UUIDs are case insensitive, pretty much everywhere in QRecall.

[quote]Can't see why it gets a nil instead of the guid that's there.[/quote]
It would appear that it can't read the file, just like the regular actions can't read the [b]sequence.index[/b], neither of which makes any sense.

And if you try any of these suggestions, please follow up with another diagnostic report. Thanks!]]> https://forums.qrecall.com/posts/preList/4904/12042.page https://forums.qrecall.com/posts/preList/4904/12042.page GMT