SOTA SSO down?

I can’t get to SOTAWatch or SOTL.AS. Looks like the SOTA SSO service is down. Anyone else having issues?

EDIT: Looks like an issue between my internet and SOTA SSO. Went on mobile hotspot and it’s working fine.

1 Like

You can always check https://status.sota.org.uk/

2 Likes

It is the same for me. I am unable to import a 52 line csv log for today’s activation of GU/GU-002. This is what I see after trying to upload the file:

73 Phil GU4OBK/P

If SSO was down you wouldn’t be logged in Phil.

Capture

Both SSO servers are working fine.

                                  My traceroute  [v0.94]
debdev (10.1.0.21) -> xxx.xx.xxx.xxx                              2023-06-17T17:50:16+0100
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                  Packets               Pings
 Host                                           Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 10.1.0.1                                     0.0%     8    0.3   0.3   0.3   0.4   0.0
 2. (waiting for reply)
 3. sgyl-core-2a-xe-002-0.network.virginmedia.n  0.0%     8   16.0   9.8   8.3  16.0   2.6
 4. (waiting for reply)
 5. 86.85-254-62.static.virginmediabusiness.co.  0.0%     8   21.1  22.7  21.1  28.2   2.3
 6. ae-8.a02.londen12.uk.bb.gin.ntt.net          0.0%     7   21.4  22.8  21.2  30.3   3.3
 7. ae-0.r21.londen12.uk.bb.gin.ntt.net          0.0%     7   22.6  29.5  21.7  60.0  13.9
 8. ae-3.a02.londen14.uk.bb.gin.ntt.net          0.0%     7   22.3  22.6  22.0  24.1   0.7
 9. ae-0.a03.londen14.uk.bb.gin.ntt.net          0.0%     7   34.9  27.2  21.9  34.9   5.3
10. 62.73.179.138                                0.0%     7   22.7  22.7  21.9  24.5   0.8
11. (waiting for reply)
12. (waiting for reply)
13. (waiting for reply)
14. (waiting for reply)
15. sso-3.sota.org.uk                            0.0%     7   20.7  22.7  20.6  31.3   3.8

                                  My traceroute  [v0.94]
debdev (10.1.0.21) -> xxx.xxx.xxx.xxx                             2023-06-17T17:51:45+0100
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                  Packets               Pings
 Host                                           Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 10.1.0.1                                     0.0%     5    0.4   0.4   0.3   0.4   0.0
 2. (waiting for reply)
 3. sgyl-core-2a-xe-002-0.network.virginmedia.n  0.0%     5    8.3  11.5   8.3  18.9   4.3
 4. (waiting for reply)
 5. 86.85-254-62.static.virginmediabusiness.co.  0.0%     5   21.6  21.7  21.0  22.4   0.5
 6. 213.46.175.122                               0.0%     5   21.9  22.0  21.0  22.8   0.7
 7. if-ae-65-2.tcore2.ldn-london.as6453.net     75.0%     5   26.9  26.9  26.9  26.9   0.0
 8. if-ae-15-2.tcore2.l78-london.as6453.net      0.0%     5   26.2  27.7  25.0  33.5   3.5
 9. if-ae-14-2.tcore2.av2-amsterdam.as6453.net   0.0%     5   26.3  25.8  24.7  26.6   0.8
10. if-ae-11-2.tcore1.ad1-amsterdam.as6453.net   0.0%     5   25.1  25.5  24.9  26.4   0.6
11. 80.231.80.6                                  0.0%     5   25.7  26.9  24.9  33.0   3.4
12. (waiting for reply)
13. (waiting for reply)
14. (waiting for reply)
15. (waiting for reply)
16. (waiting for reply)
17. sso-4.sota.org.uk                            0.0%     4   36.4  30.9  28.5  36.4   3.7

Your case Phil is something else, indicative of the DB being down but as SOTAwatch is displaying spots and I can click on a summit ref and get the summit page, then the DB is working. There are some other bits of software we’re scrutinising and we have some culprits for this under suspicio but we’re still watching the logs etc. for now.

Cancel the upload because it’s never going to finish. Log out, clear your cache, log in and try again.

1 Like

Thanks Andy. My log is in the SOTA database now. I had an extra part line 53 at the end of the csv file with the data of callsign and reference only. I don’t know if the software I use to produce the csv file put it in or the database did. I cleareds the data in line 53 and the database accepted my log.

73 Phil GU4OBK/P (until Wednesday)

2 Likes