BUG cluster

[fe-ax]

Expected Behavior

stay connected

Actual Behavior

disconnects

Steps to Reproduce

use cluster

[07:54:32] No lured pokestops in vicinity. Search for normal ones instead. Move to destiny. 3 lured pokestops will be in range of 50m. Arrive in 16.7865123168m.
[07:54:36] No lured pokestops in vicinity. Search for normal ones instead. Move to destiny. 3 lured pokestops will be in range of 50m. Arrive in 15.6602194739m.
[07:54:41] No lured pokestops in vicinity. Search for normal ones instead. Move to destiny. 3 lured pokestops will be in range of 50m. Arrive in 9.98004002201m.
[07:54:45] No lured pokestops in vicinity. Search for normal ones instead. Move to destiny. 3 lured pokestops will be in range of 50m. Arrive in 5.99300669829m.
[07:54:48] Arrived at destiny. 3 pokestops are in range of 50m.
[07:54:50] Server seems to be busy or offline - try again - 1/5
[07:55:00] Server seems to be busy or offline - try again - 1/5
[07:55:08] Server seems to be busy or offline - try again - 1/5
^C[07:55:09] Exiting PokemonGo Bot
[07:55:09]
[07:55:09] Ran for 0:03:39
[07:55:09] Total XP Earned: 50 Average: 820.58/h
[07:55:09] Travelled 0.31km
[07:55:09] Visited 1 stops
[07:55:09] Encountered 0 pokemon, 0 caught, 0 released, 0 evolved, 0 never seen before
[07:55:09] Threw 0 pokeballs
[07:55:09] Earned 0 Stardust
[07:55:09]
[07:55:09] Highest CP Pokemon:
[07:55:09] Most Perfect Pokemon:

[leovarmak]

@marco208 you mean that the bot closes after sometime ? Why not use a bash script to restart it if it quits ?

[Agentscreech]

I think what he's saying is that it'll run for a bit, then it'll start giving you the "Server seems busy" error. I've seen this too just this evening. It'll go fine for a few min, then it'll start getting that message. If I let it sit for a while, it'll go longer, but still hit this wall eventually.

UPDATE: Latest logs show that I get this error every single time when the bot "arrives at destiny" which is what the OP's log says too

[00:13:34] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 56.1677103184m.
[00:13:39] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 112.799700546m.
[00:13:42] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 97.6293790098m.
[00:13:46] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 81.8866156534m.
[00:13:51] Lured pokemon at fort 4ba1e6bb19b04e9690e44fe0db3f8c9c.16
[00:13:51] A Wild Magikarp appeared! [CP 117] [Potential 0.38]
[00:13:51] IV [Stamina/Attack/Defense] = [3/12/2]
[00:13:54] Using Pokeball (chance: 46.87%)... (40 left!)
[00:13:55] Captured Magikarp! [CP 117] [Potential 0.38] [3/12/2] [+210 exp]
[00:14:00] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 66.1152533726m.
[00:14:04] Releasing Magikarp with CP 117 and IV 0.38. Matching release rule: CP < 140 AND IV < 0.9.
[00:14:04] Exchanging Magikarp [CP 117] [Potential 0.38] for candy!
[00:14:09] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 80.4587716947m.
[00:14:13] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 69.5559579692m.
[00:14:17] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 54.3631665619m.
[00:14:21] Lured pokemon at fort ac8d257a513446c2bca4d4bba2ae97b5.11
[00:14:22] A Wild Pidgey appeared! [CP 232] [Potential 0.31]
[00:14:22] IV [Stamina/Attack/Defense] = [1/2/11]
[00:14:24] Using Pokeball (chance: 38.66%)... (39 left!)
[00:14:25] Captured Pidgey! [CP 232] [Potential 0.31] [1/2/11] [+210 exp]
[00:14:26] Pidgey has been evolved!
[00:14:31] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 42.9493953299m.
[00:14:34] Releasing Pidgeotto with CP 445 and IV 0.31. Matching release rule: CP < 750 AND IV < 0.9.
[00:14:34] Exchanging Pidgeotto [CP 445] [Potential 0.31] for candy!
[00:14:38] [x] Next egg incubates in 1.84 km
[00:14:39] Now at Pokestop: Three Graces
[00:14:39] Spinning ...
[00:14:39] Loot:
[00:14:39] 50 xp
[00:14:40] - 2x Pokeball (Total: 41)
[00:14:40] - 1x Potion (Total: 11)
[00:14:40] PokeStop on cooldown. Time left: 4 minutes, 59 seconds
[00:14:42] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 148.604163234m.
[00:14:46] -- Discarded 1x Potion (keeps only 10 maximum)
[00:14:47] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 133.121068295m.
[00:14:51] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 119.50463907m.
[00:14:55] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 107.941366557m.
[00:14:59] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 95.2875048992m.
[00:15:03] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 80.3672025425m.
[00:15:07] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 65.254932891m.
[00:15:11] Lured pokemon at fort 2111033b73304af3ae36cd8d1ca9cc43.16
[00:15:11] A Wild Zubat appeared! [CP 188] [Potential 0.51]
[00:15:11] IV [Stamina/Attack/Defense] = [7/7/9]
[00:15:14] Using Pokeball (chance: 43.22%)... (40 left!)
[00:15:14] Captured Zubat! [CP 188] [Potential 0.51] [7/7/9] [+210 exp]
[00:15:19] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 50.3483187605m.
[00:15:23] Releasing Zubat with CP 188 and IV 0.51. Matching release rule: CP < 400 AND IV < 0.8.
[00:15:23] Exchanging Zubat [CP 188] [Potential 0.51] for candy!
[00:15:28] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 81.9409057811m.
[00:15:32] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 67.3865832906m.
[00:15:35] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 53.981644772m.
[00:15:40] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 525.737015861m.
[00:15:44] Something rustles nearby!
[00:15:44] A Wild Psyduck appeared! [CP 726] [Potential 0.6]
[00:15:44] IV [Stamina/Attack/Defense] = [1/13/13]
[00:15:47] Catch Rate with normal Pokeball is low (29.94%). Thinking to throw a Razz Berry... (5 left!)
[00:15:48] Threw a berry! Catch Rate with normal Pokeball has increased to 44.91%
[00:15:48] Using Pokeball (chance: 44.91%)... (39 left!)
[00:15:48] [-] Attempted to capture Psyduck - failed.. trying again!
[00:15:50] Using Pokeball (chance: 44.91%)... (38 left!)
[00:15:51] [-] Attempted to capture Psyduck - failed.. trying again!
[00:15:53] Using Pokeball (chance: 44.91%)... (37 left!)
[00:15:54] [-] Attempted to capture Psyduck - failed.. trying again!
[00:15:56] Using Pokeball (chance: 44.91%)... (36 left!)
[00:15:57] [-] Attempted to capture Psyduck - failed.. trying again!
[00:15:59] Using Pokeball (chance: 44.91%)... (35 left!)
[00:16:00] Captured Psyduck! [CP 726] [Potential 0.6] [1/13/13] [+210 exp]
[00:16:05] Lured pokemon at fort 06874bf64a2d4375988ea867e558596a.16
[00:16:05] A Wild Oddish appeared! [CP 372] [Potential 0.76]
[00:16:05] IV [Stamina/Attack/Defense] = [14/10/10]
[00:16:08] Using Pokeball (chance: 51.86%)... (39 left!)
[00:16:08] Captured Oddish! [CP 372] [Potential 0.76] [14/10/10] [+210 exp]
[00:16:13] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 117.376320298m.
[00:16:17] Releasing Oddish with CP 372 and IV 0.76. Matching release rule: CP < 400 AND IV < 0.8.
[00:16:17] Exchanging Oddish [CP 372] [Potential 0.76] for candy!
[00:16:22] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 229.779441041m.
[00:16:26] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 392.161490279m.
[00:16:29] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 379.365117204m.
[00:16:33] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 368.241271873m.
[00:16:38] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 357.597344924m.
[00:16:41] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 344.13492967m.
[00:16:46] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 329.184592314m.
[00:16:50] Move to destiny. 1 lured pokestops will be in range of 50m. Arrive in 316.885898018m.
[00:16:53] Lured pokemon at fort ac8d257a513446c2bca4d4bba2ae97b5.11
[00:16:53] A Wild Pidgey appeared! [CP 401] [Potential 0.44]
[00:16:53] IV [Stamina/Attack/Defense] = [7/2/11]
[00:16:57] Catch Rate with normal Pokeball is low (29.94%). Thinking to throw a Razz Berry... (4 left!)
[00:16:57] Threw a berry! Catch Rate with normal Pokeball has increased to 44.91%
[00:16:57] Using Pokeball (chance: 44.91%)... (33 left!)
[00:16:58] Captured Pidgey! [CP 401] [Potential 0.44] [7/2/11] [+210 exp]
[00:16:59] Pidgey has been evolved!
[00:17:04] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 25.8674680502m.
[00:17:05] Now at Pokestop: Olympic Topographic Map
[00:17:05] Spinning ...
[00:17:05] Loot:
[00:17:05] 50 xp
[00:17:05] - 1x Pokeball (Total: 34)
[00:17:05] - 1x Greatball (Total: 1)
[00:17:05] - 1x Super Potion (Total: 21)
[00:17:05] PokeStop on cooldown. Time left: 4 minutes, 59 seconds
[00:17:07] Arrived at destiny. 1 pokestops are in range of 50m.
[00:17:09] -- Discarded 1x Super Potion (keeps only 20 maximum)
[00:17:14] Server seems to be busy or offline - try again - 1/5
[00:17:22] Server seems to be busy or offline - try again - 1/5
[00:17:32] Server seems to be busy or offline - try again - 1/5
[00:17:42] Server seems to be busy or offline - try again - 1/5
[00:17:51] Server seems to be busy or offline - try again - 1/5
[00:17:56] Server seems to be busy or offline - try again - 1/5
[00:18:00] Server seems to be busy or offline - try again - 1/5
[00:18:05] Server seems to be busy or offline - try again - 1/5
[00:18:11] Server seems to be busy or offline - try again - 1/5
[00:18:17] Server seems to be busy or offline - try again - 1/5
[00:18:26] Server seems to be busy or offline - try again - 1/5
[00:18:31] Server seems to be busy or offline - try again - 1/5

[MFizz]

Could that happen because of niantic throttling (look at #2171)? Because I can't recreate.

[xorinzor]

I have this happen occasionally, it could very well be due to rate limiting as @MFizz suggests

[Thieund]

It happens to me only on Windows server 2012, while running OK on windows 8 with same configuration, same account, within same network.

[SamuraiKal]

It looks like the "follow cluster" task relies on the bot's fort cache. The bot currently loses the fort cache when the server responds with no forts in the cell update. You're less likley to run into this issue if you have more forts around you that are being spun by you or have lures being placed or expiring around the time of the "follow cluster" task's tick/update.

If no forts have been updated since your last cell update request, the server's cell response will not include any forts which will currently clear the bot's internal fort data.

If the "follow cluster" task is trying to make a call to the server based on a null fort reference, then the server is going to time-out or reject the request.

I fixed this in #2269

It seems like the failure to retain fort data is causing several issues.