• users: 1 (just myself)
• following: 254
• timeline_purge_days: 30
• disk: 298m (/var/snac/data)
• ram: 184m (including relayd, httpd, logger, snac itself)

New #blogpost

I have come to share what I've done, some more confessions from a FOSS enthusiast...

https://joelchrono.xyz/blog/more-confessions-from-a-foss-enthusiast/

This is day 53 of #100DaysToOffload

#blogging #selfhosting #degoogle #foss

Looks like not only backups but also my obsession^Wpassion to write detailed entries to my "selfhosting journal" pays back. Any change, I made in my main home server, has a date and a detailed description of changes made. Also, the process of #NetBSD installation and service installation is documented too, alongside with documented list of running services, opened ports, cronjobs, etc.

At one bad day, my main server started to hangup at near 18:00 and at nea 08:00. There weren't any cron (or any another) jobs at this time. In the logs and monitoring the problems with mosquitto (MQTT server) were visible — somehow it eats at near 100% of CPU, then monit restart it, then things become working, then (after some time) the server hangs completely. Investigation showed that write to my second ZFS disk (where the PostgreSQL DB lives) were extremely slowed, so ZFS panicked, crashed and crashes the kernel

[ 204836.661198] wd0d: device timeout writing fsbn 123148477 of 123148477-123148478 (wd0 bn 123148477; cn 122171 tn 1 sn 46), xfer 38, retry 1
[ 204863.837664] wd0: soft error (corrected) xfer 38
[ 206810.672323] wd0: autoconfiguration error: wd_flushcache: status=0x5128<TIMEOU>
[ 212327.420695] SLOW IO: zio timestamp 211326864412007ns, delta 1000556283358ns, last io 211280726737075ns
[ 212327.420695] panic: I/O to pool 'zfs' appears to be hung on vdev guid 1299234741086050345 at '/dev/wd0'.
[ 212327.420695] cpu0: Begin traceback...
[ 212327.420695] vpanic() at netbsd:vpanic+0x183
[ 212327.420695] panic() at netbsd:panic+0x3c
[ 212327.420695] vdev_deadman() at zfs:vdev_deadman+0x15e
[ 212327.420695] vdev_deadman() at zfs:vdev_deadman+0x31
[ 212327.420695] spa_deadman_wq() at zfs:spa_deadman_wq+0xe0
[ 212327.430704] workqueue_worker() at netbsd:workqueue_worker+0xef
[ 212327.430704] cpu0: End traceback...

At the same time, I hear a strange metal noises from server at near 08:00 too, so the destiny of second drive was specified.

The server restoration will take some time, but since anything were written in the log file, I'm able just to replay some actions and get all systems up as soon as possible

#selfhosting #HomeServer

Alt...

Emacs buffer with journal entries (in OrgMode) related to the administrative actions in the server.

Alt...

Emacs buffer with description of NetBSD installation process on the main server and with lists of TODO items, services, opened ports, etc.

Alt...

EGA colored photo of a 2.5 inches HDD

I've been running two degraded ZFS arrays for the last few weeks (Debian host).

Yeah, I know. Whatevs.

One of the pools was basically "scratch" backup space and one of the spindles died (breaking the utility of the mirror). Pulled the drive, wiped the remaining, put back in service with minimum fuss as a single drive. I'll throw another spindle at it when drive prices drop again.

The other array had the SSD cache die and it's been chugging along fine ever since. Not a big deal, but from a "experience" point of view it "feels slow" like a working md array.

New SSD arrived in the mail so that'll get sorted sometime today/tomorrow.

So, what's this post about?

Linux peeps, if you are thinking about md arrays, just stop, take the time, and throw 'yer leg over the zfs horse. It's worth it.

#Linux #RunBSD #zfs #md #mdadm #raid #homelab #SelfHosted #SelfHosting

Here's something really useful I've found.

One of the great things about the Fediverse is being able to follow hashtags.

But.

If someone puts up a post using that hashtag, and no-one on your instance follows that person or anyone who shares it, it won't appear in your feed.

This is particularly common if you're on a small or single-user instance.

Here's the solution.

First, follow @_followback

It will follow you back.

And then tags.pub bot then reshare all of your posts that use hashtags.

So if you do a post with the hashtag #Fediverse, then @fediverse will share your post.

Here's where the magic happens.

The tags.pub bot will do the same thing to everyone else who follows that followback account.

So if you follow @fediverse, then you'll get a feed of everyone who uses #Fediverse on the Fediverse.

And you'll see their posts even if no-one on your instance follows them.

And it works for all hashtags.

Just put the name of the hashtag, followed by @tags.pub

So @tech follows all posts using #tech, for example.

Or @news follows all posts using #news

#relay #relays #selfhosted #selfhosting #Mastodon #feditip #feditips #fedihelp

New post:

"A newbie's guide to self-hosting with #YunoHost. Part 5: Upgrades & Maintenance"

Not exactly the most exciting post I have ever written, but system maintenance is so essential.

And spoiler alert: thanks to a botched #PeerTube upgrade I discovered the wonders of #tmux (thank you @teapot_ben and @drfyzziks for recommending it!)

🔗 : https://blog.elenarossini.com/a-newbies-guide-to-self-hosting-with-yunohost-part-5-upgrades-maintenance/

#SelfHosting #MySoCalledSudoLife #DigitalSovereignty

Self hosters, do you use Cloudflare in front of your hosted services?

#cloudflare #selfhosting #privacy #security

@mastodonmigration We should probably be pushing things like #Friendica and #Pixelfed and other free Fediverse servers over things like Ghost.

Even pushing free wiki software would be a win over a proprietary platform.

But yes, escaping commercial platforms is a critically important idea, and the first step to #selfhosting.

:; jq -r '.id' < $(ag -l 'six thirty twelve meters' ~/sites/schmonz.com/snac/data/user/schmonz/public)
https://schmonz.com/snac/schmonz/p/1743383179.235112

Let's see how this setup pans out: https://schmonz.com/2025/04/15/sensible-basic-minecraft-hosting/

#SelfHosting #s6 #ProcessSupervision