search

ArtemGr / Sidekick

Dice and LFG bot for Discord.
MIT License
250 stars 39 forks source link

sidekick offline? #243

Closed bofrich closed 4 years ago

bofrich commented 4 years ago

It was working earlier and it is currently offline for me.

ted366 commented 4 years ago

I was just coming here to report the same.

ArtemGr commented 4 years ago

Lately we see a pattern of a) Discord services being temporarily disrupted at night; b) our failover kicking in; c) Discord resetting our bot token due to attempts of the failover shards to connect.

BTW, Discord says "It appears your bot, Sidekick, has connected to Discord more than 1000 times within a short time period. Since this kind of behavior is usually a result of a bug we have gone ahead and reset your bot's token" and there's no way to verify that message, because the "short time period" is unspecified, but our log shows only about 10 re-connection attempts, not 1000, so the message is most likely simply false.

    dice:3094 ˢ38] 00:03:32] Got an ack from 62.75.219.56:9999
    dice:3621 ˢ10] 00:03:34] run_disco_shard] Shard 10 is starting failover.
    dice:3621 ˢ50] 00:03:39] run_disco_shard] Shard 50 is starting failover.
    dice:3094 ˢ40] 00:03:41] Got an ack from 62.75.219.56:9999
    dice:3621 ˢ6] 00:03:44] run_disco_shard] Shard 6 is starting failover.
    dice:3621 ˢ52] 00:03:49] run_disco_shard] Shard 52 is starting failover.
    dice:3094 ˢ55] 00:03:50] Got an ack from 62.75.219.56:9999
    dice:3621 ˢ33] 00:03:54] run_disco_shard] Shard 33 is starting failover.
    dice:3094 ˢ17] 00:03:59] Got an ack from 62.75.219.56:9999
    dice:3621 ˢ43] 00:04:00] run_disco_shard] Shard 43 is starting failover.
    dice:3621 ˢ41] 00:04:00] run_disco_shard] Shard 41 is starting failover.
    dice:3621 ˢ58] 00:04:05] run_disco_shard] Shard 58 is starting failover.
    dice:3094 ˢ23] 00:04:08] Got an ack from 62.75.219.56:9999
    dice:3621 ˢ2] 00:04:10] run_disco_shard] Shard 2 is starting failover.
    dice:3621 ˢ5] 00:04:15] run_disco_shard] Shard 5 is starting failover.
    dice:3094 ˢ16] 00:04:17] Got an ack from 62.75.219.56:9999
    dice:3621 ˢ13] 00:04:20] run_disco_shard] Shard 13 is starting failover.
    dice:3621 ˢ60] 00:04:25] run_disco_shard] Shard 60 is starting failover.
    dice:3094 ˢ40] 00:04:26] Got an ack from 62.75.219.56:9999
    dice:3621 ˢ34] 00:04:30] run_disco_shard] Shard 34 is starting failover.
    dice:3094 ˢ11] 00:04:35] Got an ack from 62.75.219.56:9999
    dice:3621 ˢ61] 00:04:35] run_disco_shard] Shard 61 is starting failover.
    dice:3621 ˢ49] 00:04:41] run_disco_shard] Shard 49 is starting failover.
    dice:3094 ˢ17] 00:04:44] Got an ack from 62.75.219.56:9999
    dice:3621 ˢ59] 00:04:46] run_disco_shard] Shard 59 is starting failover.
    dice:3621 ˢ3] 00:04:51] run_disco_shard] Shard 3 is starting failover.
    dice:3621 ˢ7] 00:04:51] run_disco_shard] Shard 7 is starting failover.
    dice:3621 ˢ63] 00:04:51] run_disco_shard] Shard 63 is starting failover.
    dice:3621 ˢ25] 00:04:51] run_disco_shard] Shard 25 is starting failover.
    dice:3621 ˢ14] 00:04:51] run_disco_shard] Shard 14 is starting failover.
    dice:3094 ˢ23] 00:04:53] Got an ack from 62.75.219.56:9999
    thread 'main' panicked at '!connect: Connection closed', src/dice.rs:3165:20

Refactoring of high availability failover is tracked at #232.

P.S. Let me also mention that the bot was restarted right away, but the shards need some time to go up due to the way the Discord protocol is designed.