New error on longstanding Laravel server - stderr to vsock zero copy err: Broken pipe (os error 32)

Questions / Help
1

I have a machine that has been running Laravel for months that is suddenly showing a new error in the logs. It appears once every minute. As far as stderr goes, I have followed the configuration in the fly.io docs here which has been working great up until now. I’m not aware of anything else that could be affecting stderr.

I’ve tried destroying and recreating the machine. The machine has plenty of spare resources CPU, memory, and volume wise.

I’m really just not sure how to debug from here. Any suggestions at all would be much appreciated!

2024-09-13T19:24:41.429 app[7815123c94ddd8] sea [info] ERROR stderr to vsock zero copy err: Broken pipe (os error 32)
2024-09-13T19:25:41.132 app[7815123c94ddd8] sea [info] ERROR stderr to vsock zero copy err: Broken pipe (os error 32)
2024-09-13T19:26:41.165 app[7815123c94ddd8] sea [info] ERROR stderr to vsock zero copy err: Broken pipe (os error 32)
2024-09-13T19:27:41.113 app[7815123c94ddd8] sea [info] ERROR stderr to vsock zero copy err: Broken pipe (os error 32)
2024-09-13T19:28:41.158 app[7815123c94ddd8] sea [info] ERROR stderr to vsock zero copy err: Broken pipe (os error 32)
2024-09-13T19:29:41.115 app[7815123c94ddd8] sea [info] ERROR stderr to vsock zero copy err: Broken pipe (os error 32)
2

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.