[Bug] Login queue wont work properly on reconnect

#1

hi ryan,

it seems that the login queue does not work properly with several bind-IP’s when the bots are reconnecting.

i got 9 bots on one machine. 3 of each got the same bind-IP. lets say a dc comes and all bots get back to the login-process, two of each bind-IP’s are logging in where one of them is waiting due to login-limit reached. that means, no one of them uses the login queue although this option is checked to all.

yes, this time i checked if the interface exists :slight_smile:

regards

1 Like

#2

Only with bind IPs? Seems a bit odd that it would only not work correctly with that option.

0 Likes

#3

might even be, that the queue does not work at all. i am even not sure if this issue happens on initial login. unfortunately its a little tricky to check this couz iSRO has huge waiting time on login :frowning:

0 Likes

#4

anyway. right now i got the following situation:

IP1
|_ char1: logging
|_ char2: logging
|_ char3: connection closed by remote due to too many login trials -.-

IP2
|_ char1: logging
|_ char2: logging
|_ char3: botting

IP3
|_ char1: botting
|_ char2: botting
|_ char3: botting

i expected only one char per IP-set in logging state. so something is going wrong here.

0 Likes

#5

@Ryan

v21.7.7

  • SOCKS / bind IP settings will no longer save if the bot is started from the Manager

is this point related to this thread? trying to say: should i keep an eye on it if my issue got fixed now?

0 Likes

#6

No. By save I mean inside phBot.ini so it doesn’t overwrite those settings when another bot is started through the Manager.

0 Likes

#7

ok i c. thanks

0 Likes

#8

still got that issue and it appears on first login as well (not just on reconnecting).

i updated to v21.8.2. i use wine on that server. all bots got terminated before.

  1. started bot1: all good and as expected. its connecting.
  2. started bot2: all good as well: Another bot is currently trying to connect, waiting 60 seconds again
  3. started bot3: here we got an issue. its connecting anyway.

thats a strange behavior. 2nd one cares about the queue, 3rd one does not.
all use the same bindip and all have queue checked in the options.
here is the process list (ps aux | grep phBot on my terminal):

root 28628 86.2 0.4 1836156 156224 ? Sl 11:14 2:17 /root/phBot/phBot.exe --username user1 --password pass1 --server Feronia --character char1 --passcode 123456 --bindip x.x.x.229 --startbot --relogdc --locale isro --disabletray --wine

root 28747 21.7 0.4 1829228 135568 ? Sl 11:15 0:16 /root/phBot/phBot.exe --username user2 --password pass2 --server Feronia --character char2 --passcode 123456 --bindip x.x.x.229 --startbot --relogdc --locale isro --disabletray --wine

root 28777 30.3 0.4 1829228 135708 ? Sl 11:15 0:15 /root/phBot/phBot.exe --username user3 --password pass3 --server Feronia --character char3 --passcode 123456 --bindip x.x.x.229 --startbot --relogdc --locale isro --disabletray --wine

regards

0 Likes

#9

edit: i was waiting until each bot got started before starting the next one to prevent that they dont see each other.

(i was not able to edit my post before. got “body is to similar” message … o_O)

0 Likes

#10

I’m not sure if you’re using the random gateway or not. It also looks at that for the queue. If they are different IPs then it uses a different mutex.

1 Like

#11

thats it - thank you! i use remote random with switch gateway after 1 attempts to prevent that the bot stands still when one the login server might got a problem.

why does it use a different mutex? do i need to decide between random gateway and properly use of the bot’s queue then or is there some chance that u gonna change that?

0 Likes

#12

Because Joymax won’t ban you if you login two accounts on two different gateway IPs.

0 Likes

#13

How does the queue button work. I’m currently using 1 proxy for 2 characters and I get ip ban once in a while. If I use the que button on a account does the queue appli only to the other account that is using the same proxy?

0 Likes

#14
  1. Locale
  2. Gateway IP
  3. SOCKS IP
  4. Bind IP
0 Likes

#15

What does that mean? I’m sorry if I dont understand.
I have x-trap set to locale.
Gateway ip I have set to random
I have a socks ip set up
And I dont know what bind ip mean and I dont see that option on the bot menu.

0 Likes

#16

It’s in phBot.ini. If SOCKS / bind IP are blank they are not used.

  1. You don’t have to worry about this one. It’s just iSRO.
  2. It does not use “random”. It uses what it will connect to.
  3. It’s used in your case.
  4. Not used in your case.
0 Likes

#17

right, but when i got 2 bots with the same bindIP having a DC and remote random is checked, its about 50:50 that both get the same gateway.

in my case i gonna get this then:

[09:27:22] Auto Relog: Starting relog process
[09:27:22] Clientless: Retrying in 30 seconds
[09:27:52] Connecting to the gateway server [45.58.13.127:15779]
[09:27:53] Connected
[09:27:53] Server capacity [Feronia] [Full]
[09:27:58] Login: Sending login credentials
[09:28:04] Login: Secondary passcode has been entered successfully
[09:28:04] Login queue limit has been reached, retrying in 30 seconds
[09:28:04] Auto Relog: Starting relog process
[09:28:04] Clientless: Retrying in 30 seconds
[09:28:34] Connecting to the gateway server [45.58.13.127:15779]
[09:28:34] Connected
[09:28:35] Server capacity [Feronia] [Full]
[09:28:40] Login: Sending login credentials
[09:28:45] Login: Secondary passcode has been entered successfully
[09:28:45] Login queue limit has been reached, retrying in 30 seconds
[09:28:45] Auto Relog: Starting relog process
[09:28:45] Clientless: Retrying in 30 seconds
[09:29:15] Connecting to the gateway server [45.58.13.127:15779]
[09:29:16] Connected
[09:29:17] Server capacity [Feronia] [Full]
[09:29:22] Login: Sending login credentials
[09:29:27] Login: Secondary passcode has been entered successfully
[09:29:27] Login queue limit has been reached, retrying in 30 seconds
[09:29:27] Auto Relog: Starting relog process
[09:29:27] Clientless: Retrying in 30 seconds
[09:29:57] Connecting to the gateway server [45.58.13.127:15779]
[09:29:58] Connected
[09:29:58] Server capacity [Feronia] [Full]
[09:30:03] Login: Sending login credentials
[09:30:09] Login: Secondary passcode has been entered successfully
[09:30:09] Login queue limit has been reached, retrying in 30 seconds
[09:30:09] Auto Relog: Starting relog process
[09:30:09] Clientless: Retrying in 30 seconds
[09:30:39] Connecting to the gateway server [45.58.13.127:15779]
[09:30:39] Connection was closed by the remote host, retrying
[09:30:40] Auto Relog: Starting relog process
[09:30:40] Clientless: Retrying in 30 seconds
[09:30:40] Connecting to the gateway server [45.58.13.127:15779]
[09:30:41] Connection was closed by the remote host, retrying
[09:30:42] Connecting to the gateway server [45.58.13.127:15779]
[09:30:42] Connection was closed by the remote host, retrying
[09:30:43] Connecting to the gateway server [45.58.13.127:15779]
[09:30:43] Connection was closed by the remote host, retrying
[09:30:44] Connecting to the gateway server [45.58.13.127:15779]
[09:30:45] Connection closed repeatedly 5 times, retrying in 60 seconds
[09:31:09] Login: No response from the server, reconnecting
[09:31:09] Clientless: Retrying in 5 seconds
[09:31:14] Connecting to the gateway server [45.58.13.127:15779]
[09:31:14] Connection was closed by the remote host, retrying
[09:31:14] Auto Relog: Starting relog process
[09:31:14] Clientless: Retrying in 30 seconds
[09:31:15] Connecting to the gateway server [45.58.13.127:15779]
[09:31:16] Connection was closed by the remote host, retrying
[09:31:17] Connecting to the gateway server [45.58.13.127:15779]
[09:31:17] Connection was closed by the remote host, retrying
[09:31:18] Connecting to the gateway server [45.58.13.127:15779]
[09:31:18] Connection was closed by the remote host, retrying
[09:31:19] Connecting to the gateway server [45.58.13.127:15779]
[09:31:20] Connection closed repeatedly 5 times, retrying in 120 seconds
[09:31:45] Connecting to the gateway server [45.58.13.127:15779]
[09:31:45] Connection was closed by the remote host, retrying
[09:31:46] Connecting to the gateway server [45.58.13.127:15779]
[09:31:46] Connection was closed by the remote host, retrying
[09:31:47] Connecting to the gateway server [45.58.13.127:15779]
[09:31:48] Connection was closed by the remote host, retrying
[09:31:49] Connecting to the gateway server [45.58.13.127:15779]
[09:31:49] Connection was closed by the remote host, retrying
[09:31:50] Connecting to the gateway server [45.58.13.127:15779]
[09:31:50] Connection closed repeatedly 5 times, retrying in 180 seconds
[09:32:20] Connecting to the gateway server [45.58.13.127:15779]
[09:32:20] Connection was closed by the remote host, retrying
[09:32:20] Auto Relog: Starting relog process
[09:32:20] Clientless: Retrying in 30 seconds
[09:32:21] Connecting to the gateway server [45.58.13.127:15779]
[09:32:22] Connection was closed by the remote host, retrying
[09:32:23] Connecting to the gateway server [45.58.13.127:15779]
[09:32:23] Connection was closed by the remote host, retrying
[09:32:24] Connecting to the gateway server [45.58.13.127:15779]
[09:32:24] Connection was closed by the remote host, retrying
[09:32:25] Connecting to the gateway server [45.58.13.127:15779]
[09:32:26] Connection closed repeatedly 5 times, retrying in 240 seconds
[09:32:55] Connecting to the gateway server [45.58.13.127:15779]
[09:32:56] Connection was closed by the remote host, retrying
[09:32:56] Auto Relog: Starting relog process
[09:32:56] Clientless: Retrying in 30 seconds
[09:32:57] Connecting to the gateway server [45.58.13.127:15779]
[09:32:57] Connection was closed by the remote host, retrying
[09:32:58] Connecting to the gateway server [45.58.13.127:15779]
[09:32:58] Connection was closed by the remote host, retrying
[09:32:59] Connecting to the gateway server [45.58.13.127:15779]
[09:33:00] Connection was closed by the remote host, retrying
[09:33:01] Connecting to the gateway server [45.58.13.127:15779]
[09:33:01] Connection closed repeatedly 5 times, retrying in 300 seconds
[09:33:20] Connecting to the gateway server [45.58.13.127:15779]
[09:33:20] Connection was closed by the remote host, retrying
[09:33:21] Connecting to the gateway server [45.58.13.127:15779]
[09:33:21] Connection was closed by the remote host, retrying
[09:33:22] Connecting to the gateway server [45.58.13.127:15779]
[09:33:23] Connection was closed by the remote host, retrying
[09:33:24] Connecting to the gateway server [45.58.13.127:15779]
[09:33:24] Connection was closed by the remote host, retrying
[09:33:25] Connecting to the gateway server [45.58.13.127:15779]
[09:33:25] Connection closed repeatedly 5 times, retrying in 360 seconds
[09:33:55] Connecting to the gateway server [45.58.13.127:15779]
[09:33:55] Connection was closed by the remote host, retrying
[09:33:55] Auto Relog: Starting relog process
[09:33:55] Clientless: Retrying in 30 seconds
[09:33:56] Connecting to the gateway server [45.58.13.127:15779]
[09:33:57] Connection was closed by the remote host, retrying
[09:33:58] Connecting to the gateway server [45.58.13.127:15779]
[09:33:58] Connection was closed by the remote host, retrying
[09:33:59] Connecting to the gateway server [45.58.13.127:15779]
[09:33:59] Connection was closed by the remote host, retrying
[09:34:00] Connecting to the gateway server [45.58.13.127:15779]
[09:34:01] Connection closed repeatedly 5 times, retrying in 420 seconds
[09:34:30] Connecting to the gateway server [45.58.13.127:15779]
[09:34:31] Connection was closed by the remote host, retrying
[09:34:31] Auto Relog: Starting relog process
[09:34:31] Clientless: Retrying in 30 seconds

and this is really annoying couz i have to terminate the affected bot completely for hours until joymaxx permits this IP to connect again.

and now comes the strange: this example even happened with 2 bots having the same bindIP, queue checked and not using remote random but gateway *.127 instead. so something does not work properly.

could you maybe recheck why this happens here?

and regarding remote random: could you let the bot check if there is already some bot logging in on some gateway that got chosen by remote random of another bot to prevent that both get the same just couz they use remote random?

regards

0 Likes

#18

What is remote random? Are you talking about the gateway IP?

0 Likes

#19

sorry. mixed the name up with openvpn :wink: but yes, i am talking about the random gateway

0 Likes

#20

I’m not sure if I can do anything. Use the Manager and set it up to login one at a time and don’t let the bot relog.

0 Likes