<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Network on </title>
    <link>https://peng.fyi/tags/network/</link>
    <description>Recent content in Network on </description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>map[name:Peng Zhang]</managingEditor>
    <webMaster>map[name:Peng Zhang]</webMaster>
    <copyright>Peng Zhang</copyright>
    <lastBuildDate>Sat, 01 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://peng.fyi/tags/network/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Apply sysctl before systemd: a lesson from reserving ephemeral ports too late</title>
      <link>https://peng.fyi/post/apply-sysctl-before-systemd/</link>
      <pubDate>Sat, 01 Aug 2026 00:00:00 +0000</pubDate>
      <author>map[name:Peng Zhang]</author>
      <guid>https://peng.fyi/post/apply-sysctl-before-systemd/</guid>
      <description>
        
          
            We run an OpenTelemetry Collector (otel-collector) as a systemd service on Bottlerocket. Its Prometheus metrics endpoint was configured on port 51000, which falls inside the default Linux ephemeral port range. On a small portion of EC2 instances, the otel-collector kept restarting, failing to bind with EADDRINUSE. Sometimes it self-healed, sometimes it kept restarting and we lost logs. This post walks through the fix, which involves a race condition among systemd services and why the sysctl has to be applied before systemd starts.
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
