A macOS bug that causes TCP networking to stop working after 49.7 days
11–20 of 120 posts
Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#12Sounds like it affects every open TCP connection, not just OpenClaw. (It's pretty rare for a TCP connection to live that long, though.)
Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#13Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#14calc_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
#15Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#16Sounds like it affects every open TCP connection, not just OpenClaw. (It's pretty rare for a TCP connection to live that long, though.)
Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#17Sounds 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.
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
#18Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#19Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#20Earlier 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.