bug: summary of your issue

[leomerkl]

Describe the bug
eRPC does not handle correctly cases where postgreSQL cache loop restarts because it goes out of disk space.

To Reproduce
Steps to reproduce the behavior:

1. Use erpc version 0.0.63

2. Use basic erpc.yaml config with postgreSQL cache enabled and limit postgreSQL cache disk size to 10MB.

3. Make enough requests to fill the postgres cache (e.g. getLogs on big contracts on multiple ranges should do).

Expected behavior
Once postgreSQL crash with out of disk space, eRPC should ignore it and continue to serve requests based on other caches and upstreams.

Screenshots

Additional context
Sorry I don't have a lot of logs/background on this issue as it append on a weekend overnight and I couldn't recover the logs of eRPC. Hope this is enough to isolate a cause.

[aramalipoor]

@leomerkl what are the erpc logs at that point? is it panic-ing, or slowing down, or bad/wrong responses?