trading works for 2 days, then just stops and "entry" is lost all of a sudden

[Wladastic]

I have to restart the bot every now and then because it stops trading and stops sending signals. I don't see any exceptions there in the logs, it just stops showing signals and doesn't execute trades

[ghost]

I would say this is because its using SQLite. Which it should be using mysql. SQLite will lose data if restarted its like a temp DB.

https://stackoverflow.com/questions/28773847/sqlite-loses-data-insert-update-after-restarting-app

[Wladastic]

hm, why don't we use mongodb instead?

[Haehnchen]

there is nothing wrong with SQLite its not a "temp DB" :)

Maybe the external lib handling the signals stopped working at some point, just replaced it with using core functions https://github.com/Haehnchen/crypto-trading-bot/commit/9c31f4d0d73cac9a9a3bf0c6385c1e5fddbdf1af

But i have no problem "since years" now. The only problem that happends from time is a breaking exchange down time. where the exchange connection is not able to recover. which is also now logged, when the candles are possible outdated.

a helpful context would be what exchange is taken here.

[Wladastic]

just noticed that now the trades stay after docker-compose restart, thank you Haehnchen! :)

[Wladastic]

I figured it "freezes" the trades once my router restarts, which is getting super annoying, have to figure something out there, as my provider is forcing me to restart it.

[Haehnchen]

@Wladastic which exchange are you connected to? So that i can check maybe the reconnection is not working there.

[Wladastic]

Binance Spot