Christopher S

@Atem18 Just a small report. First time it ran about 24h after that the socket.send() was raised again. Unfortunately I had forgot to reset the log level (updating overwrote my...

> @Kiessar Any news ? @Atem18 It crashed again, but some time ago and I hadn't had the time to check on it. I will try to let it run...

> I pushed a new version with an updated version of websockets. Maybe it will help. Ok I started in the morning but crashed caused by an error of my...

@Atem18 Unfortunately error still persists. Set all the timeouts to 10 and still gettingthe error: socket.send() raised exception.

@Atem18 Yes, one time I got an memory error, but I thought it was caused by my own implementation.

@Atem18 Because I'm starting to need the functionality more and more I will start to dive in more and try to solve the issue. My latest debug log is the...

@Atem18 Sorry didn't make that clearly enough. It goes repeating the line "socket.send() raised exception." for about 500mB (so thousands of lines repeated). So the number of lines was just...

@Atem18 New error and it crashed my server due to overload and diskspace consumption: ``` 2022-06-20 01:54:53,144 kraky.ws DEBUG WebSockets connection closed error - retrying connection in 20 sec. 2022-06-20...

@Atem18 Script: https://pastebin.com/scZ0qA27 Command: `nohup python WSDataFetcher.py -p RARI/EUR,ADA/EUR,PAXG/ETH,SOL/EUR,RARI/XBT,XBT/EUR,ADA/USD -s 10 &` My best guess is still, that it runs into rate limits. Therefore it highly depends on the current...

@Atem18 Are you sure thats not my code whats causing the memory consumption? Just don't want to waste your time. If you like I could strip down everything regarding storing...