Henrik Feldt
Oh I see. Well, the norm would be that the platforms are all pushed to the same image, so it doesn't really solve my use-case, but it's great that it's...
https://en.wikipedia.org/wiki/Crash-only_software - this is a reference to a very sane way of building software - where you auto-correct faults by restarting at different levels.
If the connectivity to redis is a problem, a restart will trigger a retry of the connection
If it's done using a liveness probe in k8s it would have solved my problem. If you've solved the bug from the stacktrace in the original post in this thread,...
We moved away from n8n for now, let's see if we come back.
Another stacktrace: ``` .venv/lib/python3.11/site-packages/playwright/_impl/_connection.py:296, in Connection.cleanup(self, cause) 294 ws_connection._transport.dispose() 295 for callback in self._callbacks.values(): --> 296 callback.future.set_exception(self._closed_error) 297 self._callbacks.clear() 298 self.emit("close") ``` With `anyio`: ```py async with ( async_playwright() as...
You may be experiencing a replica that has desynced; the WAL might grow because it's keeping to-be-synchronised transactions.
So after discussions in the other thread, it would seem the bucket retention policy deleted the file. **How do I make postgres-operator reinitialise the stanza?**
When creating a new `repo`: > time="2022-10-21T07:51:21Z" level=error msg="unable to create stanza" error="command terminated with exit code 47: ERROR: [047]: unable to create path '/var/lib/pgbackrest/archive': [30] Read-only file system\n" file="internal/controller/postgrescluster/pgbackrest.go:2580"...