My Windows-based host crashes every once in a while, causing the host to go offline. The problem comes, normally the host crash restarts, but the annoying windows host generates a new SID after each run, and the original bot does not have the original SID online and can not stop updating the parameters to replace the host, it must be deleted, the original bot has a lot of parameters, the robot also records a lot of data locally with _(G, delete re-create there must be a lot.
Mr. HoAs long as the database of the host robot is not lost, the logs are not important. However, it is best to re-run the SID of the host without changing it is best, so as not to have so much trouble operating, sometimes without a phone outside to operate too much is really inconvenient.
Mr. HoThanks little dream, I'm using a desktop host, there's no way to take a screenshot, I think it might be related to the server's operating environment, I have a cloud server in Japan that runs the same strategy and it doesn't crash, whereas the machine in the US crashed twice, all Ali Cloud servers.
The Little DreamOK, I've recorded this problem, and I'm going to use your handy words here: 359706687, and then I'm going to take a screenshot of the crashed Windows Administrator (if it's a command line version). Can you send me the code of the crashed strategy, so that we can determine if the problems were caused by it? If the host appears to be down, just delete the host in Control Center, then restart the host, restart the bot (no need to create a new one), the bot's database remains the same, the logs are still available, unless you delete all files from the host directory on your computer and re-download a host program, the previous bot's database will not exist, and the bot will re-create the database. So if you plan to replace the program, you need to back up the db3 robot database under the Logs folder before replacing it, the file name of the host is the corresponding bot, back up.
The Little DreamI can't see the log, so I filter it directly.
Mr. HoIs it possible to see the wrong logs in the logs below the robot?
Mr. HoThat's not a bad idea, thank you.
The Little DreamYesterday I specifically consulted the following, you can use this function SetErrorFilter, in the API documentation: https://www.botvs.com/api#SetErrorFilter, you can see that the error log type filtered by this function will not be written to the database.
Mr. HoThe reason you are saying should be the root cause, the logs are not my policy written, but the error that the exchange has reported during this time, the administrator wrote in, so I can only deal with LogReset ((5000) for now.
The Little DreamSome logs are not output by you, for example, you get the behavior, and if you report an error after the deadline, an error log will be generated.
Mr. HoIt is strongly recommended that you store the database separately from log tables and status tables, configuration key value tables, etc., so that you can improve the efficiency of access to the database, but also enhance the security of the profile file. The configuration information is read and written every time the policy is run, but the log content is desirable, as we currently do not have much data in the actual key value tables, but because the logs are so large, they cause a slow reading, no wonder I feel that these days your website is slow, I open the robots for a long time, because the logs cause a problem with the database and the content also causes problems with reading the status information.
Mr. HoI'm not exporting logs at all, I'm just exporting LogProfit and LogStatus, logs that are just normal when I'm executing buy and sell, and I haven't run many buy and sell for half a month.
The Little DreamYou can do this by calling LogReset ((5000) or setting the parameter to 10000 at each interval of a certain time period in the program, periodically clearing some logs. This allows the DB database files to be kept without over-inflating.
The Little DreamYou filtered the logs with SetErrorFilter to display, or you deleted the logs with LogReset.
The Little DreamRecently, many exchanges have been walled up, and if accessed by a domestic custodian, there could be a large amount of overtime error reporting, resulting in frequent write-ins to the database, a long time, and log data volumes that can be surprising.
Mr. HoIs the log and the local key value pairs stored in the DB3 file, so that the log file explodes on the hard drive and you don't have to do anything, you can't delete DB3, and you can't export DB3 to a new library, on the one hand the hard drive has exploded, on the other hand you export this much content?
Mr. HoMy robot had already deleted all the logs, and while it was running normally, there was basically no log output except for the status bar, so why did it have to make such a big log file?
Mr. HoI'm scared to death, there's 27 G's in the log, the hard drive's blown, the database files are broken.
The Little Dream> Addition of knowledge points: In the process of using a loop operation, you can see that a temporary file of XXX.db3-journal is generated in the database file directory, and the size changes at any time. This can't be deleted.
The Little DreamIf there is another software that has opened the data file, you can try restarting the system where the host is located and see if this works.
Mr. HoI found a.db3-journal file in the bot directory of the Log directory, and I moved it outside to run the bot, but the admin program kept reporting the following error, [Log] database disk image is malformed
Mr. HoRun the version of the command line again, which indicates that the database is locked and cannot be successfully run[Log] 2018/03/26 10:17:12 This is the first time I've seen this.
Mr. HoYou're not going to pass.