Host v3.0 release, one hard upgrade, compatible with older versions as of 2016/03/31

Causes of the escalation

• Since BotVS went live, the number of users has increased, as the number of robots has increased, the database servers have become overloaded, and the overall architecture has recently been rebuilt, with 90% of the code being rewritten.
• Hardware upgrades are required to make the old version of the host compatible as of 31/03/2016
• Communication port changed from 9002 to9902Please note the switch.

New features

• [x] Logs are stored entirely locally with no limit on log entries, no host uploads logs to BotVS, only dynamically retrieves from host when retrieved (but not saved)
• [x] Saved locally in the sqlite format, with a suffix in the logs directory as db3, a file named Robot ID, and users can open analytics logs with the sqlite view tool
• [x] Administrators run the robot using a method of actively receiving tasks, making the robot control more fluid
• [x] All communications are encrypted using TLS, which provides a higher level of security.
• [x] LogProfitReset and LogReset, as well as the reset function of the chart add a feature to save the record, which can reset data or save the most recent record
• [x] Added TCP connection reuse functionality to provide faster data access
• [x] Fixes many of the details problems that have been accumulating for over a year.

How to save logs

• After the administrator logs on to BotVS successfully, it creates a logs folder in the directory where the program is located, which generates a log.docker.pidDocuments
• This file stores a 32-bit unique ID, and every bot running on this host is associated with this unique ID.
• Users can create multiple hosted processes, and multiple hosts can share a docker.pid file with the logs directory
• Once a docker.pid file is created, the contents do not change.
• The robot logs are stored in the logs directory, and the file name format is: Robot ID.db3
• 查看机器人日志的时候，服务器会根据机器人关联的托管的docker.pid内容中的唯一ID号来向相应托管者发送命令
• 如果有多个托管者在同一个机器上运行，使用同一个docker.pid文件，获取机器人日志的时候会随机向其中一个托管获取
• lost logs directory or changes to the working directory when the administrator is running will cause lost logs previously associated with the bot

Updated by

http://7xi2n7.com1.z0.glb.clouddn.com/1c9cfbcb394a0051808ee9aff323b58639b09bdc.png

Update Please re-deploy the trustee:https://www.fmz.com/m/add-node

遇到问题可跟贴留言