# sysadmin Published articles for sysadmin. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Git para sysadmins: control de versiones DevFeed: [Git para sysadmins: control de versiones]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-02-16T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Git](), [Linux](), [Ansible](), [nginx](), [Firewall](), [Terraform](), [Command-line interface](), [Script](), [Terminal](), [Gitea](), [GitHub](), [GitLab]() Tags: [ansible](), [env-file-security](), [firewall](), [git](), [github](), [gitlab](), [linux](), [scripts](), [sysadmin](), [sysadmins](), [terminal](), [terraform]() ### AI overview A practical Spanish-language guide explains how sysadmins can use Git to version server configurations, infrastructure-as-code files, and maintenance scripts. It covers repository setup, commits, branches, remotes, collaboration, and avoiding secrets in version control. ### Source excerpt Guía práctica de Git para sysadmins: versiona configuraciones, gestiona infraestructura como código y colabora en equipo sin miedo a romper nada. ## Why Sysadmins Should Learn Automation with Ansible, Terraform, and Git in 2026 DevFeed: [Why Sysadmins Should Learn Automation with Ansible, Terraform, and Git in 2026]() Original publisher: [Read original article]() Author: Alois Published: 2026-01-20T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Ansible](), [Terraform](), [Git](), [ssh](), [Prometheus](), [Grafana](), [systemd]() Tags: [ansible](), [git](), [grafana](), [prometheus](), [ssh](), [sysadmin](), [systemd](), [terraform](), [yaml]() ### AI overview This Spanish article argues that automation is an essential skill for sysadmins managing growing infrastructure. It explains how Ansible playbooks can coordinate tasks such as kernel patching and staged server reboots, while monitoring and scheduled maintenance can automate remediation and preventive work. ### Source excerpt Por qué la automatización con Ansible, Terraform y Git dejó de ser opcional para un sysadmin, y por dónde empezar sin agobiarte. ## 10 scripts Bash útiles para sysadmins DevFeed: [10 scripts Bash útiles para sysadmins]() Original publisher: [Read original article]() Author: Alois Published: 2026-01-14T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Scripting, bash](), [Bash](), [backups](), [monitor](), [rsync]() Tags: [backups](), [bash](), [logs](), [rsync](), [script](), [scripts](), [shell](), [sysadmin](), [sysadmins]() ### AI overview A Spanish-language tutorial presents ten practical Bash scripts for system administrators, including disk monitoring, rotating backups, log cleanup, and other routine tasks. It notes that Bash scripts suit focused tasks on individual machines but are not a replacement for configuration-management tools when managing many servers. ### Source excerpt Colección de scripts Bash prácticos para monitorización, backups, limpieza de logs y tareas comunes de administración de sistemas. ## IA en sysadmin: ¿oportunidad o amenaza? DevFeed: [IA en sysadmin: ¿oportunidad o amenaza?]() Original publisher: [Read original article]() Author: Alois Published: 2026-01-13T00:00:00Z Content type: opinion Language: es Sources: [tengoping.com]() Topics: [AIOps](), [datacenter](), [Infrastructure as code](), [Terraform](), [Ansible](), [Command-line interface](), [Post Mortem](), [telemetry]() Tags: [aiops](), [ansible](), [datacenter](), [iac](), [logs](), [post-mortem](), [sysadmin](), [terminal](), [terraform]() ### AI overview This Spanish-language article examines how AI can assist systems administrators with log triage, anomaly detection, IaC manifest generation, incident summaries, runbook drafts, and command suggestions. It argues that AI reduces mechanical work but does not replace human diagnosis, review, or operational judgment. ### Source excerpt Reflexión sobre dónde ayuda la IA al sysadmin, qué riesgos reales conlleva en producción y cómo adaptarse sin perder criterio. ## GIMP 3.0 Released With Updated UI, Wayland Support, Improved File Compatibility, and Plugin API Changes DevFeed: [GIMP 3.0 Released With Updated UI, Wayland Support, Improved File Compatibility, and Plugin API Changes]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2025-03-18T03:45:26Z Content type: release Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Development](), [Linux](), [CSS](), [Wayland](), [API](), [Compression](), [file](), [format](), [export](), [import]() Tags: [api](), [centos](), [compression](), [css](), [debian-linux](), [downloads](), [export](), [file](), [format](), [freebsd](), [gimp](), [import](), [improvements](), [linux](), [linux-news](), [macos](), [new-features](), [open-source](), [plugins](), [release](), [sysadmin](), [unix](), [upgrades](), [version]() ### AI overview GIMP 3.0 was released on March 16, 2025. The release adds a GTK3 interface, HiDPI and tablet improvements, Wayland support, CSS-based themes, updated icons, broader file-format compatibility, painting and text improvements, and updates to the core plugin API. ### Source excerpt Wow! After years of hard work and countless commits, we have finally reached a huge milestone: GIMP 3.0 is officially released! I am excited as I write this and can't wait to share some incredible new features and improvements in this release. GIMP 2.10 was released in 2018, and the first development version of GIMP 3.0 came out in 2020. GIMP 3.0 released on 16/March/2025. Let us explore how to download and install GIMP 3.0, as well as the new features in this version. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post Download of the day: GIMP 3.0 is FINALLY Here! appeared first on nixCraft. ## Ubuntu to Explore Rust-Based "uutils" as Potential GNU Core Utilities Replacement DevFeed: [Ubuntu to Explore Rust-Based "uutils" as Potential GNU Core Utilities Replacement]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2025-03-16T12:17:36Z Content type: article Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Ubuntu](), [canonical](), [Linux](), [Rust](), [Memory Safety](), [Operating system](), [Command-line interface]() Tags: [developer](), [devops](), [linux](), [linux-news](), [memory-safety](), [open-source](), [rust](), [sysadmin](), [ubuntu]() ### AI overview Canonical is exploring Rust-based uutils as a potential replacement for GNU Core Utilities in Ubuntu, with possible changes beginning in Ubuntu 25.10 and extending to Ubuntu 26.04 LTS. The article explains the role of core utilities and discusses possible memory-safety and performance benefits. ### Source excerpt In a move that has sparked significant discussion within the Ubuntu Linux fan-base and community, Canonical, the company behind Ubuntu, has announced its intention to explore the potential replacement of GNU Core Utilities with the Rust-based "uutils" project. They plan to introduce new changes in Ubuntu Linux 25.10, eventually changing it to Ubuntu version 26.04 LTS release in 2026 as Ubuntu is testing Rust 'uutils' to overhaul its core utilities potentially. Let us find out the pros and cons and what this means for you as an Ubuntu Linux user, IT pro, or developer. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post Ubuntu to Explore Rust-Based "uutils" as Potential GNU Core Utilities Replacement appeared first on nixCraft. ## Rsync Versions 3.3.0 and Earlier Affected by Multiple Security Vulnerabilities DevFeed: [Rsync Versions 3.3.0 and Earlier Affected by Multiple Security Vulnerabilities]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2025-01-15T18:04:24Z Content type: news Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [rsync](), [Vulnerabilities](), [Exploit](), [Linux](), [Command-line interface](), [Unix](), [backups]() Tags: [backups](), [buffer-overflow](), [centos](), [client](), [command-line](), [debian-linux](), [exploit](), [freebsd](), [linux](), [linux-news](), [open-source](), [race-condition](), [rsync](), [security](), [server](), [sysadmin](), [unix](), [vulnerability]() ### AI overview Rsync versions 3.3.0 and earlier are affected by multiple security vulnerabilities, including heap-based buffer overflow, information disclosure, symbolic-link race conditions, and path traversal. The document recommends patching rsync on both client and server systems. ### Source excerpt Rsync is a opensource command-line tool in Linux, macOS, *BSD and Unix-like systems that synchronizes files and directories. It is a popular tool for sending or receiving files, making backups, or setting up mirrors. It minimizes data copied by transferring only the changed parts of files, making it faster and more bandwidth-efficient than traditional copying methods provided by tools like sftp or ftp-ssl. Rsync versions 3.3.0 and below has been found with SIX serious vulnerabilities. Attackers could exploit these to leak your data, corrupt your files, or even take over your system. There is a heap-based buffer overflow with a CVSS score of 9.8 that needs to be addressed on both the client and server sides of rsync package. Apart from that info leak via uninitialized stack contents defeats ASLR protection and rsync server can make client write files outside of destination directory using symbolic links. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post Critical Rsync Vulnerability Requires Immediate Patching on Linux and Unix systems appeared first on nixCraft. ## lnav - Awesome terminal log file viewer for Linux and Unix DevFeed: [lnav - Awesome terminal log file viewer for Linux and Unix]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-06-16T11:04:42Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Terminal](), [Command-line interface](), [Linux](), [Unix](), [SQLite](), [SQL](), [Regular expression](), [ssh](), [OpenSSH](), [Databases]() Tags: [centos](), [debian-linux](), [developer](), [devops](), [facebook](), [filter](), [freebsd](), [how-to](), [install](), [linkedin](), [linux](), [open-source](), [reddit](), [reports](), [sql](), [sqlite](), [sysadmin](), [systems](), [terminal](), [unix]() ### AI overview A tutorial on lnav, a terminal-based log viewer for Linux and Unix. It explains how lnav identifies log details, combines files by time, supports colorized error highlighting, regular-expression filtering, SQLite queries, JSON formatting, remote access, and installation across several operating systems. ### Source excerpt It is no secret that whether you are a developer or sysadmin, you need to use log files to troubleshoot errors on your Linux and Unix systems. You use tools like grep, tail, cat, or journalctl to view log files. However, you may need help with so many log files. These essential Unix tools are suitable for basic text but fall short when dealing with many log files. You can get tired from sifting through endless lines of log files. The lnav utility is here to the rescue! It is a powerful log file viewer that goes beyond the basics. It understands your logs by identifying timestamps, log levels, and other vital details. You can run SQLite SQL queries against your standard log files and build reports for your needs. Let us see how to install and use the lnav tool quickly. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post lnav - Awesome terminal log file viewer for Linux and Unix appeared first on nixCraft. ## How to find out AWS EC2 instances type over SSH DevFeed: [How to find out AWS EC2 instances type over SSH]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-05-26T11:51:12Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Amazon EC2](), [Amazon Web Services](), [ssh](), [Linux](), [freebsd](), [Unix](), [Cloud]() Tags: [amazon-cloud-computing](), [aws](), [bash](), [commands](), [curl](), [curl-command](), [easy](), [ec2](), [freebsd](), [how-to](), [linux](), [ssh](), [sysadmin](), [systems](), [tutorial](), [unix]() ### AI overview A quick tutorial showing how to identify the instance type of an AWS EC2 or Lightsail virtual machine over SSH. It covers commands using dmesg, instance metadata, system files, dmidecode, Bash, and ec2-metadata on Linux, FreeBSD, and Unix systems. ### Source excerpt AWS offers various instance types, and sometimes, you need to know which one you are using or which one has been deployed by someone else (another developer or sysadmin) for a project. Don't worry. Here are some commands to find the EC2 instance type over SSH without logging into the AWS console. These commands works with any Linux distro or FreeBSD Unix systems. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post How to find out AWS EC2 instances type over SSH appeared first on nixCraft. ## How to find ulimit for user on Linux DevFeed: [How to find ulimit for user on Linux]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-05-16T21:57:31Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Linux](), [Processes](), [systems]() Tags: [account](), [bash-shell](), [centos](), [command](), [debian](), [debian-linux](), [developers](), [easy](), [file](), [firefox](), [how-to](), [limits](), [linux](), [nginx](), [php](), [process](), [python](), [red-hat-enterprise](), [redhat-and-friends](), [rhel](), [suse](), [sysadmin](), [ulimit](), [unix-linux](), [user]() ### AI overview A Linux tutorial explaining how to inspect ulimit resource limits for user accounts and running processes. It covers soft and hard limits, relevant configuration sources, and finding limits for services such as nginx. ### Source excerpt How can I find the correct ulimit values for a user account or process on Linux systems? Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post How to find ulimit for user on Linux appeared first on nixCraft. ## Sysadmin friendly high speed ethernet switching DevFeed: [Sysadmin friendly high speed ethernet switching]() Original publisher: [Read original article]() Author: ben@benjojo.co.uk Published: 2024-04-18T10:05:46Z Content type: article Language: en Sources: [benjojo blog]() Topics: [Ethernet](), [networking](), [Debian](), [Software](), [SDK]() Tags: [debian](), [drivers](), [ethernet](), [networking](), [patches](), [sdk](), [sysadmin]() ### AI overview A sysadmin describes deploying a Mellanox SN2010 high-speed Ethernet switch with open mlxsw drivers and stock Debian. The approach aims to reduce dependence on vendor software updates while accepting responsibility for bugs and maintenance. ### Source excerpt Sysadmin friendly high speed ethernet switching I've been on the lookout for a ethernet switch that I don't hate, the problem with a lot of higher ## Who is squatting IPv4 addresses? DevFeed: [Who is squatting IPv4 addresses?]() Original publisher: [Read original article]() Author: ben@benjojo.co.uk Published: 2022-02-17T11:30:04Z Content type: article Language: en Sources: [benjojo blog]() Topics: [Network](), [Internet](), [BGP](), [Cloudflare](), [1.1.1.1]() Tags: [bgp](), [cloudflare](), [dns](), [internet](), [ip](), [ipv4](), [ipv6](), [network](), [routers](), [sysadmin]() ### AI overview This article examines the practice of using IPv4 address space that is neither RFC1918 private space nor address space assigned by a regional Internet registry. It discusses IPv4 scarcity, Cloudflare's 1.1.1.1 resolver addresses, and large Department of Defense BGP announcements as possible indicators of unused address space being squatted on. ### Source excerpt Who is squatting IPv4 addresses? It's an established fact on the internet that we have ran out of IP(v4) addresses, and we are st ## Things I Do To My Every Rails Code Base DevFeed: [Things I Do To My Every Rails Code Base]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-09-18T11:20:00Z Content type: article Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Documentation](), [Development](), [DevOps](), [Markdown](), [Shell]() Tags: [code](), [development](), [devops](), [documentation](), [markdown](), [rails](), [shell](), [sysadmin](), [tooling]() ### AI overview A personal developer article describes practices the author applies to Rails projects and, more broadly, to Python, PHP, and other languages. It emphasizes keeping project documentation in a local docs directory and using tools and automation to make development and operations easier. ### Source excerpt NOTE: This is written in a Rails context but I've applied these techniques to Python and PHP as well as other languages. This isn't Rails specific as much as it is a development best practice. My very first rails codebase was a project called eduFire which was a C2C (consumer to consumer) marketplace for educators who wanted to sell online tutoring in language instruction. This let an instructor: build a profile advertise their services to people who wanted to learn conduct video tutoring sessions make a decent side income eduFire was a lightly funded startup (seed an then an A round) where all ops tasks were done by the engineers who built the product. And, yes, there were only two of us with about 90% of the ops tasks falling on my shoulders. From a technical perspective, we were doing DevOps although we certainly: didn't call it that didn't use today's generation of automated tooling much save shell scripting What that project did for me though was force me to figure out an approach to my Rails projects that centered around: Documentation Making things easy for myself eduFire was built and deployed from 2007 to 2009. Now this was a time when Rails applications where harder to deploy and keep running. And that instability was actually good for me. I went through a period in Summer of 2008 when I was constantly on call and my kids, now over a decade later, can tell the tale of my work Mac laptop intoning: "eduFire IS DOWN" loudly, in the voice of god at 3 am or some such ridiculous hour. What I learned from this was that you can fix anything from a dead sleep if you have: Documentation Tools Each of these is discussed below. Documentation The first thing I do with any rails app, right after the rails new command is this: mkdir docs And in that directory I place markdown files of any documentation that I might need. Here's an example of what's in the docs directory for the Covid Near Me app: ❯ ls -l docs total 80 -rw-r--r--@ 1 sjohnson staff 1192 Mar 24 07:29 api_jo ## When Postgres Won't Start DevFeed: [When Postgres Won't Start]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-09-12T11:05:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [PostgreSQL](), [upgrade](), [postgresql clusters]() Tags: [install](), [logs](), [postgres](), [postgresql](), [server](), [sysadmin](), [upgrade]() ### AI overview A PostgreSQL installation was upgraded from version 11 to 12.4 without upgrading its data directory, preventing the database server from starting. The article explains how to diagnose the incompatibility through PostgreSQL logs and lists commands used to resolve it. ### Source excerpt TLDR Somehow my postgres installation was upgraded. When postgres is upgraded its data is NOT upgraded. This means postgres won't start BUT it will be a silent failure; you can only confirm this via the logs. tail -n 10 /usr/local/var/log/postgres.log The Long Version I went through a situation the other day where I would start and stop postgres and the database would NEVER be available for connection. Here is the error that I kept getting: ❯ psql psql: error: could not connect to server: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.5432"? This blog posts lists all the commands I used for reference and how I fixed it: brew services restart postgres brew services stop postgres brew services start postgres rm -f /usr/local/var/postgres/postmaster.pid brew uninstall postgresql brew install postgresql brew reinstall postgresql brew upgrade postgres ls -l /usr/local/var/postgres/postmaster.pid ls -l /usr/local/var/postgres/ tail -n 10 /usr/local/var/log/postgres.log brew postgresql-upgrade-database tail -n 10 /usr/local/var/log/postgres.log As is always the case with this type of low level issue, the answer is ALWAYS IN THE DAMN LOGS and it is always the near to last command you use that finds it. Here's what I found: ❯ tail -n 10 /usr/local/var/log/postgres.log 2020-09-10 16:17:49.566 EDT [85169] FATAL: database files are incompatible with server 2020-09-10 16:17:49.566 EDT [85169] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 12.4. 2020-09-10 16:17:59.589 EDT [85170] FATAL: database files are incompatible with server 2020-09-10 16:17:59.589 EDT [85170] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 12.4. 2020-09-10 16:18:09.617 EDT [85172] FATAL: database files are incompatible with server 2020-09-10 16:18:09.617 EDT [85172] DETAIL: The data ## Building a Home Server DevFeed: [Building a Home Server]() Original publisher: [Read original article]() Author: Christian Hollinger Published: 2019-04-11T00:00:00Z Content type: article Language: en Sources: [Christian Hollinger]() Topics: [Homelab](), [backups](), [Computing](), [Hardware](), [Pi-hole](), [Monitoring](), [Internet](), [cpu](), [Virtual Private Network](), [Amazon S3](), [DDR4](), [Git]() Tags: [article](), [aws-s3](), [backups](), [bash](), [big-data](), [centos](), [computing](), [debian](), [encryption](), [git](), [hardware](), [headless](), [home-server](), [linux](), [luks](), [nas](), [networking](), [privacy](), [security](), [server](), [smb](), [storage](), [sysadmin](), [windows]() ### AI overview A practical account of building a home server or NAS for local storage, SMB drives, backups, processing, Git repositories, CD rips, and other headless computing. It discusses privacy, cloud-storage limitations, local services, and the hardware used. ### Source excerpt In this article, I'll document my process of building a home server - or NAS - for local storage, smb drives, backups, processing, git, CD-rips, and other headless computing... ## 'Twas the night before Christmas - SysAdmin Edition DevFeed: ['Twas the night before Christmas - SysAdmin Edition]() Original publisher: [Read original article]() Published: 2018-12-24T03:07:02Z Content type: opinion Language: en Sources: [Signs of Triviality]() Topics: [Cloud]() Tags: [allowed](), [christmas](), [cloud](), [pager](), [sysadmin]() ### AI overview A SysAdmin-themed Christmas poem describes a cloud environment under a deployment moratorium, with no pager alerts and deploys not allowed. ### Source excerpt 'Twas the night of the moratorium, and all through the cloud not a pager was beeping: no deploys were allowed... ## Tales of a Part-time Sysadmin: Dogfooding Docker to test Docker DevFeed: [Tales of a Part-time Sysadmin: Dogfooding Docker to test Docker]() Original publisher: [Read original article]() Published: 2015-06-07T01:10:30Z Content type: article Language: en Sources: [Jessie Frazelle]() Topics: [Docker](), [Testing](), [ci](), [Jenkins](), [Server]() Tags: [ci](), [docker](), [dogfooding](), [jenkins](), [sysadmin](), [testing]() ### AI overview This article describes how Docker's core team uses Docker to run and test Docker. It explains the CI infrastructure, including Jenkins in a Docker container, storage-driver and Linux distribution matrices, and testing across multiple servers, kernels, Docker Windows clients, and pull requests. ### Source excerpt This is a tale about how we use Docker to test Docker. Yes, I am familiar with the meme. Puhlease. Many of you are familiar with the fact I work on the Docker core team. Which consists of fixing bugs, doing releases, reviewing PRs, hanging out on IRC, mailing lists etc etc etc. But what you may not know is that in addition to all these things I also manage our testing infrastructure. Now really this in itself could be a fulltime job. However it is not my fulltime job, nor would I ever want it to be. [insert gif about yak shaving here] This blog post is going to be about how I manage ~50 servers but don't do anything at all. Of course, I have my angry sysadmin moments when everything breaks and I could punch a whole in a wall... but who doesn't? Our CI First let me take a chance to familiarize you with how we test Docker. Docker's tests run in a Docker container. We use Jenkins as our CI mostly because we needed a lot of flexibility and control. Obviously everything in our infrastructure runs in Docker, so that even goes for Jenkins. We use the official image for our Jenkins container. Docker itself has 6 different storage driver options. These are aufs, btrfs, devmapper, overlay, vfs, and zfs. We have servers that use each of these hooked up to our Jenkins instance for testing. Along with all the storage driver options, Docker also runs on any linux distro and a world of different linux kernel versions. In order to be able to try and test all this differentiation, each server runs a different kernel and all major linux distros are accounted for. With every push to master on the docker/docker repo, we run tests on the entire storage driver matrix. We also trigger builds to test the unsupported lxc execdriver for Docker. And we trigger builds to test the Docker Windows client. Right there is three different jobs running on 8 different servers just for 1 push to master. Did I mention we have 9 Windows servers and 9 linux remote hosts paired with those servers for testing ## Developer services offline DevFeed: [Developer services offline]() Original publisher: [Read original article]() Published: 2013-11-25T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Hardware](), [upgrade](), [servers]() Tags: [crashes](), [developer](), [free](), [git](), [hardware](), [open-source](), [os](), [react](), [reactos](), [recovery](), [server](), [sysadmin](), [upgrade](), [uptime](), [win32](), [winapi]() ### AI overview ReactOS developer services went offline after an unstable host server followed an attempted hypervisor upgrade. The outage affected virtual machines and services including mail, mailing lists, SVN, Git, buildbot, Testman, Jira, the old ReactOS website, and secondary DNS. The team was working to restore services on a new server, with mail issues and recovery timing still unresolved. ### Source excerpt Updated at 13h21 CET: We are trying to restore all the services at the moment, on a new server. Everything should be working again. Let's hope it will be a stable server this time... Except issues with mail server and delays with mails for the moment. Dear all, On Saturday, we attempted an upgrade of one of our old hypervisor. If the upgrade went fine, it appears that the new server provided by our hoster is totally unstable. ## Setting up Monit on Ubuntu DevFeed: [Setting up Monit on Ubuntu]() Original publisher: [Read original article]() Author: Graham King Published: 2010-02-28T23:18:23Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [monitor](), [Monitoring](), [Ubuntu](), [servers](), [MySQL](), [Replication](), [Python](), [Django]() Tags: [django](), [monit](), [monitor](), [monitoring](), [mysql](), [mysql-replication](), [python](), [replication](), [server](), [software](), [sysadmin](), [ubuntu]() ### AI overview A tutorial on setting up Monit on Ubuntu to monitor server processes, network responsiveness, system resources, files, Apache, services, and MySQL replication. It covers configuration, email alerts, the HTTP interface, service control, and a Python-based Django management command for replication monitoring. ### Source excerpt "Monit: Your server's vigilant guardian and problem-solver."