Log4OM

When the syncing stopped I did a dis-connect/re-connect to no avail. I left the cluster on when I closed the log. The next day when I opened the log the f9 started to sync on it's own with no dis-connect/re-connect.

If you close the log, the cluster closes too.
I suppose there was a lack of informations from cluster or a disconnection/unavailability on their side.

Then I must have restarted the cluster. Is it possible that this is memory problem?

W6JMP wrote:Then I must have restarted the cluster. Is it possible that this is memory problem?

I read this thread when it was first posted and set my cluster to the SOTA cluster on 13th November, my computer has been running all the time until now without restart and the cluster has not stopped working

I think you have a local issue of either internet interruption, memory issue or something similar

Uhm... memory issue... i think not... cluster are automatically purged when spot is older than a predefined time.

Since no one else seems to have the problem, I think it may be time to write the issue off as a local anomaly. Log4Om is a great program and the SOTA cluster is tracking (syncing) correctly 90% of the time. I can (and do) track SotaWatch2, so not much chance of missing a spot. Having to manually enter a SOTA Q occasionally is no big deal.

Thanks for looking at my problem and thanks again for a TERRIFIC PROGRAM.

73 de gene w6jmp

Gene,
Do you have the same issues with other clusters?

What a great question. I'll take a look at that. tnx

All other clusters watched tracked perfectly on f9

BUT THIS COULD BE A BREAK THROUGH. This morning any post or spot marked SMS_NA did not sync to F9 from the SOTA cluster. I will watch further to see if there are any other spots that don't sync.

To all those who have been following this thread. The cause has been discovered and will be corrected with the next revision. The problem was the manner in which the spots were posted.

My thanks to Daniele.

73 de gene w6jmp