From 23685502f3f923930cc9c24a1e2e99b5173d2a37 Mon Sep 17 00:00:00 2001 From: David Luevano Alvarado Date: Thu, 15 Jun 2023 04:26:29 -0600 Subject: fix typos on arch logs entry, add temp jellyfin entry --- db/db_blog.psv | 2 +- live/blog/a/arch_logs_flooding_disk.html | 7 ++-- live/blog/rss.xml | 6 ++-- src/blog/a/arch_logs_flooding_disk.md | 6 ++-- .../temp/jellyfin_server_with_sonarr_radarr.md | 41 ++++++++++++++++++++++ 5 files changed, 52 insertions(+), 10 deletions(-) create mode 100644 src/blog/temp/jellyfin_server_with_sonarr_radarr.md diff --git a/db/db_blog.psv b/db/db_blog.psv index fb22107..ea3e806 100644 --- a/db/db_blog.psv +++ b/db/db_blog.psv @@ -23,4 +23,4 @@ a/al_fin_tengo_fibra_opticona.md|1683622740.1853704|0.0|949b8fd2aca929d74d821747 a/learned_go_and_lua_hard_way.md|1685763137.7581403|0.0|493f86ce317f7b182b62c3438e5f7a8a|english,rant,short,tools a/updating_creating_entries_titles_to_setup.md|1685764004.1478639|0.0|2bcf247ed5c2aa9fd5f4b542043123fe|english,short,update a/manga_server_with_komga.md|1686425767.8936074|1686653315.6535006|7c33a7604565de1300710ce0add53944|code,english,server,tools,tutorial -a/arch_logs_flooding_disk.md|1686824540.5338242|0.0|fcd1990de048be002380aea9a92333fe|code,english,server,short,tools,tutorial +a/arch_logs_flooding_disk.md|1686824540.5338242|1686824666.933781|261eeee98ecbb22399f1253697b12353|code,english,server,short,tools,tutorial diff --git a/live/blog/a/arch_logs_flooding_disk.html b/live/blog/a/arch_logs_flooding_disk.html index 4b8bd19..8903f85 100644 --- a/live/blog/a/arch_logs_flooding_disk.html +++ b/live/blog/a/arch_logs_flooding_disk.html @@ -91,13 +91,13 @@

It’s been a while since I’ve been running a minimal server on a VPS, and it is a pretty humble VPS with just 32 GB of storage which works for me as I’m only hosting a handful of services. At some point I started noticing that the disk keept filling up on each time I checked.

Turns out that out of the box, Arch has a default config for systemd‘s journald that keeps a persistent journal log, but doesn’t have a limit on how much logging is kept. This means that depending on how many services, and how aggresive they log, it can be filled up pretty quickly. For me I had around 15 GB of logs, from the normal journal directory, nginx directory and my now unused prosody instance.

For prosody it was just a matter of deleting the directory as I’m not using it anymore, which freed around 4 GB of disk space. -For journal I did a combination of configuring SystemMaxUse and creating a Namespace for all “email” related services as mentioned in the Arch wiki: systemd/Journal; basically just configuring /etc/systemd/journald.conf (and /etc/systemd/journald@email.con with the comment change) with:

-
[Journal]
+For journal I did a combination of configuring SystemMaxUse and creating a Namespace for all “email” related services as mentioned in the Arch wiki: systemd/Journal; basically just configuring /etc/systemd/journald.conf (and /etc/systemd/journald@email.conf with the comment change) with:

+
[Journal]
 Storage=persistent
 SystemMaxUse=100MB # 50MB for the "email" Namespace
 

 
And then for each service that I want to use this “email” Namespace I add:

-
[Service]
+
[Service]
 LogNamespace=email
 

 
Which can be changed manually or by executing systemctl edit service_name.service and it will create an override file which will be read on top of the normal service configuration. Once configured restart by running systemctl daemon-reload and systemctl restart service_name.service (probably also restart systemd-journald).

@@ -142,6 +142,7 @@ LogNamespace=email
   

     
By David Luévano

     
Created: Thu, Jun 15, 2023 @ 10:22 UTC

+      
Modified: Thu, Jun 15, 2023 @ 10:24 UTC

     

   
Tags:
 code, english, server, short, tools, tutorial  

diff --git a/live/blog/rss.xml b/live/blog/rss.xml
index 9c7de3e..d96d238 100644
--- a/live/blog/rss.xml
+++ b/live/blog/rss.xml
@@ -37,13 +37,13 @@
       It’s been a while since I’ve been running a minimal server on a VPS, and it is a pretty humble VPS with just 32 GB of storage which works for me as I’m only hosting a handful of services. At some point I started noticing that the disk keept filling up on each time I checked.

 
Turns out that out of the box, Arch has a default config for systemd‘s journald that keeps a persistent journal log, but doesn’t have a limit on how much logging is kept. This means that depending on how many services, and how aggresive they log, it can be filled up pretty quickly. For me I had around 15 GB of logs, from the normal journal directory, nginx directory and my now unused prosody instance.

 
For prosody it was just a matter of deleting the directory as I’m not using it anymore, which freed around 4 GB of disk space.
-For journal I did a combination of configuring SystemMaxUse and creating a Namespace for all “email” related services as mentioned in the Arch wiki: systemd/Journal; basically just configuring /etc/systemd/journald.conf (and /etc/systemd/journald@email.con with the comment change) with:

-
[Journal]
+For journal I did a combination of configuring SystemMaxUse and creating a Namespace for all “email” related services as mentioned in the Arch wiki: systemd/Journal; basically just configuring /etc/systemd/journald.conf (and /etc/systemd/journald@email.conf with the comment change) with:

+
[Journal]
 Storage=persistent
 SystemMaxUse=100MB # 50MB for the "email" Namespace
 

 
And then for each service that I want to use this “email” Namespace I add:

-
[Service]
+
[Service]
 LogNamespace=email
 

 
Which can be changed manually or by executing systemctl edit service_name.service and it will create an override file which will be read on top of the normal service configuration. Once configured restart by running systemctl daemon-reload and systemctl restart service_name.service (probably also restart systemd-journald).

diff --git a/src/blog/a/arch_logs_flooding_disk.md b/src/blog/a/arch_logs_flooding_disk.md
index 6a83e29..226daec 100644
--- a/src/blog/a/arch_logs_flooding_disk.md
+++ b/src/blog/a/arch_logs_flooding_disk.md
@@ -14,9 +14,9 @@ It's been a while since I've been running a minimal server on a VPS, and it is a
 Turns out that out of the box, Arch has a default config for `systemd`'s `journald` that keeps a persistent `journal` log, but doesn't have a limit on how much logging is kept. This means that depending on how many services, and how aggresive they log, it can be filled up pretty quickly. For me I had around 15 GB of logs, from the normal `journal` directory, `nginx` directory and my now unused `prosody` instance.
 
 For `prosody` it was just a matter of deleting the directory as I'm not using it anymore, which freed around 4 GB of disk space.
-For `journal` I did a combination of configuring `SystemMaxUse` and creating a *Namespace* for all "email" related services as mentioned in the [Arch wiki: systemd/Journal](https://wiki.archlinux.org/title/Systemd/Journal#Per_unit_size_limit_by_a_journal_namespace); basically just configuring `/etc/systemd/journald.conf` (and `/etc/systemd/journald@email.con` with the comment change) with:
+For `journal` I did a combination of configuring `SystemMaxUse` and creating a *Namespace* for all "email" related services as mentioned in the [Arch wiki: systemd/Journal](https://wiki.archlinux.org/title/Systemd/Journal#Per_unit_size_limit_by_a_journal_namespace); basically just configuring `/etc/systemd/journald.conf` (and `/etc/systemd/journald@email.conf` with the comment change) with:
 
-```conf
+```ini
 [Journal]
 Storage=persistent
 SystemMaxUse=100MB # 50MB for the "email" Namespace
@@ -24,7 +24,7 @@ SystemMaxUse=100MB # 50MB for the "email" Namespace
 
 And then for each service that I want to use this "email" *Namespace* I add:
 
-```conf
+```ini
 [Service]
 LogNamespace=email
 ```
diff --git a/src/blog/temp/jellyfin_server_with_sonarr_radarr.md b/src/blog/temp/jellyfin_server_with_sonarr_radarr.md
new file mode 100644
index 0000000..fd5055d
--- /dev/null
+++ b/src/blog/temp/jellyfin_server_with_sonarr_radarr.md
@@ -0,0 +1,41 @@
+title: Set up a media server with Jellyfin, Sonarr and Radarr
+author: David Luévano
+lang: en
+summary: How to set up a media server with Jellyfin, Sonarr and Radarr, on Arch. With qBitTorrent and Jackett also.
+tags: server
+	tools
+	code
+	tutorial
+	english
+
+Riding on my excitement of having a good internet connection and having setup my *home server* now it's time to self host a media server for movies, series and anime. Everything here is performed in ==Arch Linux btw== and all commands should be run as root unless stated otherwise, as always.
+
+I'll be exposing my stuff on a personal subdomain, but that's optional depending on your setup.
+
+# Table of contents
+
+[TOC]
+
+# Prerequisites
+
+Similar to my early [tutorial](https://blog.luevano.xyz/tag/@tutorial.html) entries, if you want it as a subdomain:
+
+- An **A** (and/or **AAAA**) or a **CNAME** for `jellyfin` (or whatever you want).
+    - Optionally, another one for all *iso downloading software* (wink).
+- An SSL certificate, if you're following the other entries (specially the [website](https://blog.luevano.xyz/a/website_with_nginx.html) entry), add a `jellyfin.conf` (and optionally the *isos* subdomain config) and run `certbot --nginx` (or similar) to extend/create the certificate.
+- `yay` installed. I mentioned how to install and use it on my previous entry: [Manga server with Komga: yay](https://blog.luevano.xyz/a/manga_server_with_komga.html#yay)
+
+# qBitTorrent
+
+
+# Jellyfin
+
+[Jellyfin](https://wiki.archlinux.org/title/Jellyfin) is a media server "manager", usually used to manage and organize video content (movies, TV series, etc.) which could be compared with [Plex](https://wiki.archlinux.org/title/plex) or [Emby](https://wiki.archlinux.org/title/Emby) for example (take them as possible alternatives).
+
+Install from the AUR with `yay`:
+
+```sh
+pacman -S jellyfin-bin
+```
+
+That's the pre-built binary, but you can build from source with `yay` by installing `jellyfin` (or from the latest `git` commit with `jellyfin-git`).
\ No newline at end of file
-- 
cgit v1.2.3-70-g09d2