You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I have an issue random down on the web service posthog and I check to log. I see error (32: Broken pipe) on web service. Check my resources, all services not peak resources used.
I don't know what caused this and I haven't been able to reproduce this error. but this often happens during productive hours UTC+7. in one day it can be up to 3x, but at night it has never happened.
Additional context
For fixing at this time I usually restart the posthog web service and wait a few minutes for it to return to normal.
my posthog image uses the tag: posthog/posthog:26e3e0eac315f021bdcfbdaf9394ff05cabfff70
Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables or https://eu.posthog.com/settings/project-details#variables]
- [✅] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
The text was updated successfully, but these errors were encountered:
Bug Description
Bug description
Hi, I have an issue random down on the web service posthog and I check to log. I see
error (32: Broken pipe)
on web service. Check my resources, all services not peak resources used.full log on my VM:
How to reproduce
I don't know what caused this and I haven't been able to reproduce this error. but this often happens during productive hours UTC+7. in one day it can be up to 3x, but at night it has never happened.
Additional context
For fixing at this time I usually restart the posthog web service and wait a few minutes for it to return to normal.
my posthog image uses the tag: posthog/posthog:26e3e0eac315f021bdcfbdaf9394ff05cabfff70
Debug info
The text was updated successfully, but these errors were encountered: