Live data from Hacker News

A macOS bug that causes TCP networking to stop working after 49.7 days

photon.codes

11–20 of 120 posts

Re: A macOS bug that causes TCP networking to stop working after 49.7 days

#12
post #7

Sounds like it affects every open TCP connection, not just OpenClaw. (It's pretty rare for a TCP connection to live that long, though.)

Individual TCP connections don't need to live that long. Once a macOS system reaches 49.7 days of uptime, this bug starts affecting all TCP connections.

Re: A macOS bug that causes TCP networking to stop working after 49.7 days

#14
If you want to see exactly when your machine will hit this, I threw together a fish shell function that calculates the precise timestamp, mostly vibe coded.

calc_tcp_overflow_time.fish: https://gist.github.com/daveorzach/64538f82a89fa24e5d134557c...

monitor_tcp_time_wait.fish: https://gist.github.com/daveorzach/0964a7a67c08c50043ff707cf...

Re: A macOS bug that causes TCP networking to stop working after 49.7 days

#17
post #7

Sounds like it affects every open TCP connection, not just OpenClaw. (It's pretty rare for a TCP connection to live that long, though.)

Individual TCP connections don't need to live that long. Once a macOS system reaches 49.7 days of uptime, this bug starts affecting all TCP connections.

Sure they do. They need to live until torn down.

They almost never do live that long, for whatever reason, but they should.

Re: A macOS bug that causes TCP networking to stop working after 49.7 days

#20

Earlier quoted context omitted.

Individual TCP connections don't need to live that long. Once a macOS system reaches 49.7 days of uptime, this bug starts affecting all TCP connections.

Sure they do. They need to live until torn down. They almost never do live that long, for whatever reason, but they should.

I meant that having a connection live that long isn't necessary to trigger this bug. I know that for some workloads, it can be important for connections to live that long.
Post reply on HN