Hey Slav,

I've got a interesting question. Maybe others can benefit from it too if a solution can be found.

I noticed alot of disturbance within my internet connection provider lately, so there are days when the connection is down for more than 10 minutes maybe even an hour or so. Since I don't check on the bots that often (maybe once or twice a day when they're mining) what happens is that when the internet connection reastablish, the bot keeps doing the stuff it should be but the client is not responding i.e. the ship is not moving, lasers are not powering etc. so it's practically stuck.

Is there a way for bot to somehow recognize the connection problem with the internet and restart the client?

That way if internet connection goes and then reastablish itself after a while, the client gets restarted and the bot is working again. Otherwise, the client get stuck and bot's command are not making any effect.

Now I understand this might potentially cause a situation that the bot restarts the client that has logged off because of the damage or something else. So is there a way to implement the feature and make it optional?

Keep up the good work man.

vvulic wrote:
Hey Slav,

I've got a interesting question. Maybe others can benefit from it too if a solution can be found.

I noticed alot of disturbance within my internet connection provider lately, so there are days when the connection is down for more than 10 minutes maybe even an hour or so. Since I don't check on the bots that often (maybe once or twice a day when they're mining) what happens is that when the internet connection reastablish, the bot keeps doing the stuff it should be but the client is not responding i.e. the ship is not moving, lasers are not powering etc. so it's practically stuck.

Is there a way for bot to somehow recognize the connection problem with the internet and restart the client?
That way if internet connection goes and then reastablish itself after a while, the client gets restarted and the bot is working again. Otherwise, the client get stuck and bot's command are not making any effect.

Now I understand this might potentially cause a situation that the bot restarts the client that has logged off because of the damage or something else. So is there a way to implement the feature and make it optional?

Keep up the good work man.Please record log and send me for detailed look. Need to find what function cannot finish its run by timeout. Restarting of a client in case of some problem is already here and this restart initiated by errorhandler block.

Hmm, yeah, my friend told me the function should be there and I think it was even working in one of the previous versions (2.x). I have this kind of problem occasionally. But lately my provider is doing who knows what and it got more frequent last couple of weeks so I wanted to ask you about this.

I sent the logs to your email. Please, let me know. Thanks.

vvulic wrote:
Hmm, yeah, my friend told me the function should be there and I think it was even working in one of the previous versions (2.x). I have this kind of problem occasionally. But lately my provider is doing who knows what and it got more frequent last couple of weeks so I wanted to ask you about this.

I sent the logs to your email. Please, let me know. Thanks.You have 30 minutes as a max time in belt. There is no stuck situation, there is a big timeout in settings. How much time you need to fill your cargohold? If you have 17000 cargohold, 1350 m^3/cycle and 3 lasers, you need 12 minutes to fill cargohold (ideally). Lets increase this time by factor of 1.5 = 1080 seconds is time you should put as max time while in belt. After this time if miner still mining something, program will force it to go to station. After warp initiation timeout program will restart client.

I know what you mean Slav, but that is not it. Like I said, it's not the problem when the bot is sitting in the belt. It's the problem I noticed when I check after the internet connection outage. So after the outage, it's not that the bot is sitting and doing nothing. The bot is doing all that it should, for example I seen it give the ship the command to warp to station but it doesn't cause the client is not responding. I even pause the client and try to do it myself but it doesn't work. I have to shut down that client and restart the bot program then start it again. The bot then starts up the client, ship warps in from the safe location he goes by default and the bot continues to work normally. But only after i restart it by force and start the bot program again.

I'll look at the situation next time a little deeper. Maybe when I check the bot it haven't been able to establish the timeout error because the max time in belt is not reached. I'll see next time if the client restart after that time or not so I will let you know for sure.

Thanks..

vvulic wrote:
I know what you mean Slav, but that is not it. Like I said, it's not the problem when the bot is sitting in the belt. It's the problem I noticed when I check after the internet connection outage. So after the outage, it's not that the bot is sitting and doing nothing. The bot is doing all that it should, for example I seen it give the ship the command to warp to station but it doesn't cause the client is not responding. I even pause the client and try to do it myself but it doesn't work. I have to shut down that client and restart the bot program then start it again. The bot then starts up the client, ship warps in from the safe location he goes by default and the bot continues to work normally. But only after i restart it by force and start the bot program again.Program will shut down client because warptostation will fail to initiate warp after several attempts. Another method to detect that miner is in desynchronized, for example by speed of cargohold load, not implemented. You have to wait for "max time in belt" timeout.