metalfiiish / ts-gw2-verifybot Goto Github PK

After a few days, the bot seems to become unresponsive and stops answering verifyme requests (I can see it is still connected). I have been unsuccessful in getting it to log any errors. So far, restarting the script occasionally has been the only solution.

Users currently need to give the bot their Account Name and their API-Key upon registration. Shockingly, a good lot of people don't know their own account name or fail to write it down correctly, resulting in staff having to guide users through the registration process in excruciating detail only to find out that user TCWarrior.5463 is actually TCWarrior.5436.

Since having acquired an API-Key gives you easy access to the account name through websites like https://mygw2.wvwintel.com/, having to enter the account name doesn't serve as additional security feature to prevent stolen keys from being used in a malicious way either.

I therefore suggest dropping the prompt for the account name altogether to improve usability for users and reduce support time for staff.

Is it possible to use a query acct that server admins can create from rented instance?

Edit: wrong repo. Pls delete

How to fix that? pip3 install keepalive not existing?

python3 TS3Bot.py
Initializing script....
Connecting to Teamspeak server...
Traceback (most recent call last):
File "TS3Bot.py", line 359, in
ts3conn.keepalive(interval=250)
AttributeError: 'TS3Connection' object has no attribute 'keepalive'

I have now for a while tried to battle the timeouts on the bot.

BOT now idle, waiting for requests.
Exception in thread Thread-2:
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/home/ts3bot/.local/lib/python3.6/site-packages/ts3/query.py", line 528, in recv
    b"\n\r", timeout=poll_intervall)
  File "/usr/lib/python3.6/telnetlib.py", line 327, in read_until
    return self.read_very_lazy()
  File "/usr/lib/python3.6/telnetlib.py", line 403, in read_very_lazy
    raise EOFError('telnet connection closed')
EOFError: telnet connection closed

which unfortunately has this follow-up exception that prevents self-healing:

It appears the BOT has lost connection to teamspeak. Trying to restart connection in 30 seconds....
Connecting to Teamspeak server...
Loaded User Database...
BOT loaded into server (377) as botgart (33). Nickname 'Botgart'
Traceback (most recent call last):
  File "TS3Bot.py", line 378, in <module>
    ts3conn.clientupdate(client_nickname=BOT.nickname)
  File "/home/ts3bot/.local/lib/python3.6/site-packages/ts3/commands.py", line 1583, in clientupdate
    return self._return_proxy("clientupdate", cparams, uparams, options)
  File "/home/ts3bot/.local/lib/python3.6/site-packages/ts3/query.py", line 655, in _return_proxy
    self, command, common_parameters, unique_parameters, options)
  File "/home/ts3bot/.local/lib/python3.6/site-packages/ts3/query.py", line 632, in send
    return self.wait_for_resp(query_id, timeout)
  File "/home/ts3bot/.local/lib/python3.6/site-packages/ts3/query.py", line 461, in wait_for_resp
    raise TS3QueryError(resp)
ts3.query.TS3QueryError: error id 513: nickname is already in use

It happens with:

• Local bot to localhost TS-Server
• Local bot to remote TS-Server
• Bot on remote server to another remote TS-Server

I have already tried changing the keepalive value in https://github.com/metalfiiish/ts-gw2-verifyBot/blob/master/TS3Bot.py#L364 to no avail.

I realise that this seems to be a problem with the underlying library, but I just wanted to check if there is perhaps a known solution to this.