I have put a report in the contacts that Sotawatch 3 is not logging here & comes up with object object in red, I have tried manually and no luck. Mark 2W0JMK having same problem.
Don PLP.
Got the same here 
Here also.
I have
- moved these reports from a cluster thread to their own thread
- just now could manually add a chase
- also just now I could manually add an activation
- I CANNOT upload an activation
I will look further but until notified otherwise, please don’t try to add QSOs.
2 Likes
OK everything should be working now. Don’t all rush to upload QSOs.
It was a space issue now resolved.
4 Likes
Thanks Andy.
1 Like
I found this problem too, after checking it had been reported I waited. Thanks for fixing it so quickly.
I did check the https://status.sota.org.uk/ status page but it wasn’t reporting any problems (except RBNHole).
Would it be possible to improve the status page so that it shows this type of problem?
73 Colin
1 Like
This issue was a tricky one. It was only fixed quickly because Andrew VK3ARR was still awake and thus both of us could bounce some ideas back before trying anything. And Andrew already had a typical MS error message captured… 100% accurate but you need to read it a few times and understand what it is really saying.
The DB file sizes were constrained and no more data could be added. But, existing data could be read and everything was working. I’m not sure how to add a status check for this. Normally the status checks are heartbeats that indicate the various servers are working. All of the servers were working 100% including the DB. It’s not easy in this case.
1 Like
All working for me thanks Andy
It works ! Thanks a lot for the ultra quick debugging.
73, de Bruno
A check on the datafiles that triggers a warning upon reaching a certain threshold near the set limit is pretty typical.
1 Like