I looked through your log and wanted to mention a few things:
1) Calibration started at 1:33:29 and failed at 1:40:35
2) Looking at the log for the star detection output during that time you can see that it starts out OK, but has trouble finding stars before it fails:[2022-02-07T01:33:32.328 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 10 stars, 0.09s"
[2022-02-07T01:33:55.935 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 33 stars, 0.08s"
[2022-02-07T01:34:19.577 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 40 stars, 0.09s"
[2022-02-07T01:34:43.188 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 40 stars, 0.09s"
[2022-02-07T01:35:06.990 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 35 stars, 0.10s"
[2022-02-07T01:35:30.698 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 27 stars, 0.07s"
[2022-02-07T01:35:54.327 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 34 stars, 0.08s"
[2022-02-07T01:36:17.907 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 32 stars, 0.08s"
[2022-02-07T01:36:41.554 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 28 stars, 0.07s"
[2022-02-07T01:37:01.113 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 17 stars, 0.04s"
[2022-02-07T01:37:01.179 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 17 stars, 0.05s"
[2022-02-07T01:37:24.851 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 20 stars, 0.05s"
[2022-02-07T01:37:48.447 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 9 stars, 0.04s"
[2022-02-07T01:38:12.172 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 23 stars, 0.09s"
[2022-02-07T01:38:36.088 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 3 stars, 0.03s"
[2022-02-07T01:38:36.120 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 1 stars, 0.03s"
[2022-02-07T01:38:59.951 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 12 stars, 0.06s"
[2022-02-07T01:39:23.896 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 3 stars, 0.05s"
[2022-02-07T01:39:23.954 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 1 stars, 0.05s"
[2022-02-07T01:39:47.779 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 1 stars, 0.03s"
[2022-02-07T01:39:47.802 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 1 stars, 0.02s"
[2022-02-07T01:40:11.968 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 5 stars, 0.05s"
[2022-02-07T01:40:12.016 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 1 stars, 0.04s"
[2022-02-07T01:40:35.856 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 1 stars, 0.03s"
So, I wonder if a cloud did pass by around 1:40am that wasn't there at 1:37am (or some other optical issue like perhaps shooting through a tree, etc).
3) Of course, it would be nice if Ekos recovered on its own after that--and, e.g. retried a few minutes later.
It does seem to retry, but fails to restart because of a scheduler configuration: See below:
Guiding fails and restars:
[2022-02-07T01:44:20.660 GMT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'M 81' is guiding, guiding procedure will be restarted in 20 seconds."
but then fails again
[2022-02-07T01:45:22.100 GMT DEBG ][ org.kde.kstars.ekos.guide] - Multistar: findTopStars 10
[2022-02-07T01:45:22.123 GMT DEBG ][ org.kde.kstars.ekos.guide] - "Select # x y flux HFR SNR score"
[2022-02-07T01:45:22.123 GMT DEBG ][ org.kde.kstars.ekos.guide] - No suitable star detected.
[2022-02-07T01:45:22.124 GMT INFO ][ org.kde.kstars.ekos.guide] - "Failed to select an auto star."
[2022-02-07T01:45:22.211 GMT DEBG ][ org.kde.kstars.ekos.capture] - Guiding state changed from "Selecting star" to "Calibration error"
The scheduler then aborts the job, and I believe would try and restart it, but unfortunately the job had a "fixed start time" and the scheduler wasn't smart enough to ignore that.
[2022-02-07T01:45:22.360 GMT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'M 81' is stopping guiding..."
[2022-02-07T01:45:22.361 GMT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'M 81' is aborted."
[2022-02-07T01:45:43.125 GMT INFO ][ org.kde.kstars.ekos.scheduler] - "Only aborted jobs left in the scheduler queue, rescheduling those."
[2022-02-07T01:45:43.187 GMT INFO ][ org.kde.kstars.ekos.scheduler] - Option to sort jobs based on priority and altitude is true
[2022-02-07T01:45:43.298 GMT INFO ][ org.kde.kstars.ekos.scheduler] - "Warning: job 'M 81' has fixed startup time 07/02 01:30 set in the past, marking invalid."
[2022-02-07T01:45:22.218 GMT INFO ][ org.kde.kstars.ekos.scheduler] - "Warning: job 'M 81' calibration failed."I'd recommend constraining the scheduler without the fixed startup time.
4) This probably wouldn't have made a difference, but you don't need to recalibrate every time you slew. What I do is calibrate once near the meridian and equator, and reuse that as follows
Note that "reset guide calibration after each mount slew" is unchecked, and "store and reuse calibration when possible" is checked.
However, you have to know whether or not to check or uncheck "Reverse DEC on ..." which is a mount-specific setting.
You can find that out experimentally. Calibrate on one side of the merfian, then go over to the other side and try guiding for a minute.
Guiding will be terrible in DEC if you have the setting wrong. It will be pushing in the wrong direction and should quickly move far from the target.