Installing Nextcloud on SmartOS was waaayyy easier than expected, I hit fewer issues than on Linux, and mostly I'm impressed that everything, every single php extension, was in the package repos (unlike on some Linux distros)
This post saved me again
Omfg I am dumb. While creating the zone I omitted the "ram" field, thinking that omitting it means there are no memory restrictions. Turns out, it defaults to 256mb. Which is too little for ffmpeg, and causes it to throw a Bus error instead of printing something useful
...which is especially strange since it is "just" ffmpeg
The transcoder is throwing a "Bus error, core dumped" and I'm not yet sure if this is Plex' fault or SmartOS fault (or my fault)
The even better news: Of course it's an error that nobody on the internet ever had
It wouldn't be true homelab maintenance without Plex breaking for no reason...
I only found this because it prevented the SSH service from starting.
...one year ago, March 24. Seems like I tend to do homelab maintenance every year on March 24th.
Found some problems with my ZFS array while switching OSs:
I have a dataset called poolname/nextcloud. You can guess what's in it. I just wanted to mount all datasets on the new OS, with a different ZFS implementation, and get the error that dataset/nextcloud is not empty! Turns out, there was a (normal) folder called poolname/nextcloud, that I never got to see because on Linux you can just mount the poolname/nextcloud dataset "over" it. The best part? The old nextcloud version in there is from *exactly*
#SmartOS people (esp. @brbennett), I come to you for help again:
Is there any particular reason I can load/install/activate 20230309T001400Z just fine, but the newest build, 20230323T000605Z, gives me those errors?
The medium I'm booting from is the one released today/yesterday, I just cannot activate it.
Can someone check for me please? raw.githubusercontent.com presents an incorrect cert (*.githubassets.com) with no alternative names. Tried three different connections/browsers/DNS/...
The servers are off for the first time this year and the absolute silence is killing me
It's always DNS (I mistyped the domain name and blame it on DNS)
Let’s try what happens, when you put 4 nerds in a Stellwerk and let them code on FOSS. #HedgeDoc
Das Programm für die O-Phase nächste Woche ist endlich draußen: https://oh14.de/op/schedule
Mit Führungen und Vorträgen und Diskussionen (u. a. mit @Eisfunke)
Und natürlich dem Streik von 🚌 🚂 am Montag.
Jetzt noch anmelden unter oh14.de/ophase
Hach ja, Domain geändert, damit ich nicht direkt Teile meines Namens veröffentliche und natürlich passt der dns Eintrag nicht mehr. Dyndns sagt beim update, dass die alte Domain nicht gefunden wird. No shit, Sherlock. Hab die Apps ja migriert und die alte Domain gelöscht.
-> Abriss und frisch mit der neuen Domain aufbauen. Bei der Gelegenheit mach ich gleich Subdomains, damit der unschöne Pfad wegkommt.
