channel for peer is 100 full #758

Closed
opened 2025-11-20 05:17:03 -05:00 by saavagebueno · 4 comments
Owner

Originally created by @TSJasonH on GitHub (Apr 1, 2024).

Describe the problem

The management server logs are filling with these messages:

{"log":"2024-04-01T16:00:15Z WARN management/server/updatechannel.go:57: channel for peer co3f52c11epm9isopqog is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:15.784777769Z"}
{"log":"2024-04-01T16:00:17Z WARN management/server/updatechannel.go:57: channel for peer co2ncgk11epihjcugs60 is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:17.053787974Z"}
{"log":"2024-04-01T16:00:17Z WARN management/server/updatechannel.go:57: channel for peer co2k3r411epihjcae8mg is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:17.282480806Z"}
{"log":"2024-04-01T16:00:17Z WARN management/server/updatechannel.go:57: channel for peer co3d69411epm9isopqd0 is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:17.502299348Z"}
{"log":"2024-04-01T16:00:17Z WARN management/server/updatechannel.go:57: channel for peer co3f52c11epm9isopqog is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:17.740944392Z"}
{"log":"2024-04-01T16:00:19Z WARN management/server/updatechannel.go:57: channel for peer co1dpes11epihjcae72g is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:19.805896303Z"}
{"log":"2024-04-01T16:00:20Z WARN management/server/updatechannel.go:57: channel for peer co2nqjk11epihjcugs90 is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:20.992513478Z"}
{"log":"2024-04-01T16:00:21Z WARN management/server/updatechannel.go:57: channel for peer co3f52c11epm9isopqog is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:21.231520654Z"}
{"log":"2024-04-01T16:00:22Z WARN management/server/updatechannel.go:57: channel for peer co2ncgk11epihjcugs60 is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:22.35452314Z"}
{"log":"2024-04-01T16:00:22Z WARN management/server/updatechannel.go:57: channel for peer co3f52c11epm9isopqog is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:22.579961274Z"}
{"log":"2024-04-01T16:00:22Z WARN management/server/updatechannel.go:57: channel for peer co2k3r411epihjcae8mg is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:22.793095308Z"}
{"log":"2024-04-01T16:00:24Z WARN management/server/updatechannel.go:57: channel for peer co1dpes11epihjcae72g is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:24.632213485Z"}
{"log":"2024-04-01T16:00:25Z WARN management/server/updatechannel.go:57: channel for peer co3f52c11epm9isopqog is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:25.35770735Z"}
{"log":"2024-04-01T16:00:25Z WARN management/server/updatechannel.go:57: channel for peer co3d69411epm9isopqd0 is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:25.607771243Z"}

To Reproduce

Start server and lets users connect.

Expected behavior

Normal operation

Are you using NetBird Cloud?

self-hosted

NetBird version

0.26.7

Additional context

It's a busy environment but I hadn't seen this before the upgrade to 0.26.7.

Originally created by @TSJasonH on GitHub (Apr 1, 2024). **Describe the problem** The management server logs are filling with these messages: {"log":"2024-04-01T16:00:15Z WARN management/server/updatechannel.go:57: channel for peer co3f52c11epm9isopqog is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:15.784777769Z"} {"log":"2024-04-01T16:00:17Z WARN management/server/updatechannel.go:57: channel for peer co2ncgk11epihjcugs60 is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:17.053787974Z"} {"log":"2024-04-01T16:00:17Z WARN management/server/updatechannel.go:57: channel for peer co2k3r411epihjcae8mg is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:17.282480806Z"} {"log":"2024-04-01T16:00:17Z WARN management/server/updatechannel.go:57: channel for peer co3d69411epm9isopqd0 is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:17.502299348Z"} {"log":"2024-04-01T16:00:17Z WARN management/server/updatechannel.go:57: channel for peer co3f52c11epm9isopqog is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:17.740944392Z"} {"log":"2024-04-01T16:00:19Z WARN management/server/updatechannel.go:57: channel for peer co1dpes11epihjcae72g is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:19.805896303Z"} {"log":"2024-04-01T16:00:20Z WARN management/server/updatechannel.go:57: channel for peer co2nqjk11epihjcugs90 is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:20.992513478Z"} {"log":"2024-04-01T16:00:21Z WARN management/server/updatechannel.go:57: channel for peer co3f52c11epm9isopqog is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:21.231520654Z"} {"log":"2024-04-01T16:00:22Z WARN management/server/updatechannel.go:57: channel for peer co2ncgk11epihjcugs60 is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:22.35452314Z"} {"log":"2024-04-01T16:00:22Z WARN management/server/updatechannel.go:57: channel for peer co3f52c11epm9isopqog is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:22.579961274Z"} {"log":"2024-04-01T16:00:22Z WARN management/server/updatechannel.go:57: channel for peer co2k3r411epihjcae8mg is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:22.793095308Z"} {"log":"2024-04-01T16:00:24Z WARN management/server/updatechannel.go:57: channel for peer co1dpes11epihjcae72g is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:24.632213485Z"} {"log":"2024-04-01T16:00:25Z WARN management/server/updatechannel.go:57: channel for peer co3f52c11epm9isopqog is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:25.35770735Z"} {"log":"2024-04-01T16:00:25Z WARN management/server/updatechannel.go:57: channel for peer co3d69411epm9isopqd0 is 100 full\n","stream":"stderr","time":"2024-04-01T16:00:25.607771243Z"} **To Reproduce** Start server and lets users connect. **Expected behavior** Normal operation **Are you using NetBird Cloud?** self-hosted **NetBird version** 0.26.7 **Additional context** It's a busy environment but I hadn't seen this before the upgrade to 0.26.7.
saavagebueno added the waiting-feedbacktriage-needed labels 2025-11-20 05:17:03 -05:00
Author
Owner

@TSJasonH commented on GitHub (Apr 2, 2024):

Ok, so I rolled back to 0.26.6 just to be sure and these WARN messages are still present so it's not specific to 0.26.7. Still don't know what to do about them or how to identify those peers.

@TSJasonH commented on GitHub (Apr 2, 2024): Ok, so I rolled back to 0.26.6 just to be sure and these WARN messages are still present so it's not specific to 0.26.7. Still don't know what to do about them or how to identify those peers.
Author
Owner

@mlsmaycon commented on GitHub (Apr 17, 2025):

@TSJasonH can you confirm if the issue happens on the latest version?

@mlsmaycon commented on GitHub (Apr 17, 2025): @TSJasonH can you confirm if the issue happens on the latest version?
Author
Owner

@TSJasonH commented on GitHub (Apr 17, 2025):

I cannot confirm on the latest version. We are currently running 0.28.4 with no such issues.

@TSJasonH commented on GitHub (Apr 17, 2025): I cannot confirm on the latest version. We are currently running 0.28.4 with no such issues.
Author
Owner

@mlsmaycon commented on GitHub (Apr 17, 2025):

Thanks for the feedback. The issue might happen if the system is overloaded.

I will close the issue for now.

@mlsmaycon commented on GitHub (Apr 17, 2025): Thanks for the feedback. The issue might happen if the system is overloaded. I will close the issue for now.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#758