Register / Login | Desktop view |
* failed to read directory
Ming-Li Wang wrote:One problem remains: I still can't restart QR scheduler after forcing it to quit in the Activity Monitor. Quit and restarted QR several times, but the scheduler never came up. A diagnostic report has been sent.
Other issues:
1. I used "sudo qrecall captureprefs list -r -s /" to check the QR Capture Preferences settings, and it aborted with the following error midway through the process:
* failed to read directory
2. There are a few dozen of "Unable to communicate with helper" warnings and one "Unexpected problem; scheduler stopping immediately" error in the log.
James Bucanek wrote:QRecall's scheduler is managed by the launchd service. launchd is set to run the scheduler all the time, unless the QRecallScheduler process exits with a non-zero status. launchd will also throttle, or eventually stop running, the scheduler if it repeatedly crashes or is forcibly terminated too often.
Relaunching the QRecall application won't help, because it's launchd's run the process.
Ming-Li Wang wrote:1. I used "sudo qrecall captureprefs list -r -s /" to check the QR Capture Preferences settings, and it aborted with the following error midway through the process:
* failed to read directory
This isn't surprising, because you don't have permission to read those directories. Use sudo qrecall captureprefs list -r -s / instead.
Hmmm. The "scheduler stopping immediately" error might be the reason your scheduler isn't running...
Ming-Li Wang wrote:I did use "sudo", didn't I?
QRecallScheduler &