<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Serveradministration on WebWork Blog</title><link>https://webwork.blog/en/tags/serveradministration/</link><description>Recent content in Serveradministration on WebWork Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 11 May 2024 16:33:06 +0000</lastBuildDate><atom:link href="https://webwork.blog/en/tags/serveradministration/index.xml" rel="self" type="application/rss+xml"/><item><title>Server migration with dd over SSH</title><link>https://webwork.blog/en/server-migration-with-dd-over-ssh/</link><pubDate>Wed, 24 Apr 2024 20:37:06 +0000</pubDate><guid>https://webwork.blog/en/server-migration-with-dd-over-ssh/</guid><description>Every so often I want to migrate a server "whole", as if I were pulling the disk out of the old server and plugging it into the new one. This is not only very convenient (no need to migrate each application's data individually), it is often faster than a manual migration.</description></item><item><title>CLI command "w" on Linux/Unix</title><link>https://webwork.blog/en/cli-command-w-on-linux-unix/</link><pubDate>Tue, 28 Mar 2023 10:00:00 +0000</pubDate><guid>https://webwork.blog/en/cli-command-w-on-linux-unix/</guid><description>Even with years of experience in IT you keep running into something new. Recently I came across the CLI command w.
w gives a quick overview of which users are currently logged in to the system and what they are doing.</description></item><item><title>Upgrade Debian 10 (Buster) to Debian 11 (Bullseye)</title><link>https://webwork.blog/en/upgrade-debian-10-buster-to-debian-11-bullseye/</link><pubDate>Thu, 06 Jan 2022 21:32:42 +0000</pubDate><guid>https://webwork.blog/en/upgrade-debian-10-buster-to-debian-11-bullseye/</guid><description>Debian releases a new stable version about every two years. The current version 11 (Bullseye) was released on August 14, 2021. Debian 10 (Buster) was released on July 6, 2019 and is expected to be updated until August 2022. After that, Debian 10 Buster is EOL ("</description></item><item><title>Change Docker subnets</title><link>https://webwork.blog/en/change-docker-subnets/</link><pubDate>Tue, 04 May 2021 20:34:25 +0000</pubDate><guid>https://webwork.blog/en/change-docker-subnets/</guid><description>Docker is wasteful with IP subnets by default. On hosts with many networks, this sooner or later leads to the following error:
Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network Looking at the created networks, the following pattern becomes apparent:</description></item><item><title>Install Contabo VPS from ISO</title><link>https://webwork.blog/en/reinstall-contabo-vps-from-iso/</link><pubDate>Mon, 05 Apr 2021 13:00:21 +0000</pubDate><guid>https://webwork.blog/en/reinstall-contabo-vps-from-iso/</guid><description>I recently rented a small storage VPS at Contabo. On my request (left as a comment during the order) it was provisioned in Munich, giving me a reasonable level of geo-redundancy against Nuremberg, where my other servers are hosted. The ~150 km between the two sites is already close to the BSI recommendation of 200 km for geo-redundant data centres — plenty for my needs.</description></item><item><title>Server snapshots with dd over SSH</title><link>https://webwork.blog/en/server-snapshots-with-dd-over-ssh/</link><pubDate>Sat, 03 Apr 2021 15:53:18 +0000</pubDate><guid>https://webwork.blog/en/server-snapshots-with-dd-over-ssh/</guid><description>A snapshot is an image of a disk or a system captured at a specific point in time. Depending on the environment, snapshots can be taken "online" (while the system is running) or "offline". Offline snapshots are generally preferable because they guarantee a consistent data set.</description></item><item><title>Timezones in Docker containers</title><link>https://webwork.blog/en/timezones-in-docker-containers/</link><pubDate>Tue, 23 Mar 2021 20:00:00 +0000</pubDate><guid>https://webwork.blog/en/timezones-in-docker-containers/</guid><description>While reviewing logs from various Docker containers I ran into an issue: some containers were running with the host's local timezone (CET), others with UTC. While debugging I even spotted a third timezone in another container. The reason: every developer can pin an arbitrary timezone in their Dockerfile in 1–2 lines — definitely not a best practice, but it happened in one of the containers I was using.</description></item></channel></rss>