<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Debian on The Gnu Pit</title><link>https://gnupit.net/debian/</link><description>Recent content in Debian on The Gnu Pit</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 12 Aug 2025 07:12:15 -0500</lastBuildDate><atom:link href="https://gnupit.net/debian/index.xml" rel="self" type="application/rss+xml"/><item><title>Upgrading to Debian 13 Trixie</title><link>https://gnupit.net/posts/upgrading_to_debian13/</link><pubDate>Tue, 12 Aug 2025 07:12:15 -0500</pubDate><guid>https://gnupit.net/posts/upgrading_to_debian13/</guid><description>&lt;p&gt;Ah, the trials and tribulations of upgrading Debian 12 Bookworm to Debian 13 Trixie! I learned a valuable lesson this weekend with the update - always read the apt listchanges email. Always.&lt;/p&gt;
&lt;p&gt;The upgrade itself went smoothly with no errors during the packages upgrading/installing. I run three main services on my server - nginx, exim, and dovecot. On reboot, all three had issues with the upgraded packages.&lt;/p&gt;
&lt;h3 id="nginx"&gt;nginx&lt;/h3&gt;
&lt;p&gt;I received the following error in my nginx error.log:&lt;/p&gt;</description></item><item><title>Nginx, OCSP stapling, booting, systemd and Debian 9</title><link>https://gnupit.net/posts/systemd_nginx_fix/</link><pubDate>Sun, 10 Dec 2017 18:26:24 -0500</pubDate><guid>https://gnupit.net/posts/systemd_nginx_fix/</guid><description>&lt;p&gt;Noticed these lines in journalctl when nginx didn&amp;rsquo;t start after a reboot:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Dec 10 17:43:30 mail1 nginx[3485]: nginx: [warn] &amp;#34;ssl_stapling&amp;#34; ignored, host not found in OCSP responder &amp;#34;ocsp.int-x3.letsencrypt.org&amp;#34; in the certificate &amp;#34;/etc/letsencrypt/live/www.example.com/fullchain.pem&amp;#34;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Dec 10 17:43:30 mail1 nginx[3485]: nginx: [emerg] bind() to [&amp;lt;IPv6 address&amp;gt;]:80 failed (99: Cannot assign requested address)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Dec 10 17:43:30 mail1 nginx[3485]: nginx: configuration file /etc/nginx/nginx.conf test failed
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Dec 10 17:43:30 mail1 systemd[1]: nginx.service: Control process exited, code=exited status=1
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Dec 10 17:43:30 mail1 systemd[1]: nginx.service: Unit entered failed state.
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Dec 10 17:43:30 mail1 systemd[1]: nginx.service: Failed with result &amp;#39;exit-code&amp;#39;.
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Dec 10 17:52:35 mail1 systemd[1]: nginx.service: Failed to read PID from file /run/nginx.pid: Invalid argument
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Hmmm&amp;hellip;&lt;/p&gt;</description></item></channel></rss>