Categories
Computers Debian deutsch Linux Ubuntu Uncategorized Windows

Mini-PC BMAX B5A Pro im Kurztest

Seit etwa fünf Wochen besitze ich nun meinen ersten “Mini-PC“, einen BMAX B5A Pro, Produktnummer G7R2, nachdem ich bisher immer nur PCs im Standard-Desktop-Format oder im Tower-Gehäuse (Maxi- oder Medi-/Mini-Format) besessen habe, die ich zudem oft selbst gebaut habe. Und ich muss sagen, ich bin begeistert von dem kleinen “Kistchen”.

Warum habe ich mir überhaupt diesen PC gekauft? Ich wollte die Hardware unseres Familien-Intranet-Servers ersetzen, die bisher aus einem alten Dell-Latitude-Laptop bestand. Obwohl dieser ständig nur “idle” läuft, verbraucht er im Durchschnitt etwas mehr als 20 W, was mir einfach zu viel ist. Ein Mini-PC versprach, deutlich weniger Leistung aufzunehmen.

Zum anderen sind meine Ansprüche an die Leistungsfähigkeit eines Intranet-Servers gestiegen, u. a. da ich seit einigen Monaten eine Home Assistant-Instanz auf Docker-Basis betreibe, die zu den bereits bestehenden Anwendungen auf dem Intranet-Server dazu kam. Der Mini-PC verfügt bereits ab Werk über 16 GB RAM (ein Modul mit der Bezeichnung “TDS4CDAG08-32SC22C” des relativ unbekannten Herstellers TWSC, “TechWinSemiConductors”) und eine 500 GB-M.2-SSD (“AirDisk 512GB SSD” des Herstellers “MAXIO Technology (Hangzhou) Ltd.”), was genügend Spielraum für leistungshungrige Anwendungen verspricht. Außerdem ist eine leistungsfähige AMD Ryzen 7 5825U verbaut mit acht Kernen und 16 Threads und einer TDP von lediglich 15(!) Watt.

Categories
Computers Debian English Linux Networking Routers Ubuntu

rsyslog Configuration for remote Logging

I want all the network devices in my house to log to a central location, so that log messages can be

  • stored permanently (if I switch off an access point, normally all logs are gone), and
  • automatically checked for interesting events.

So I needed to set up my internal Ubuntu-based server to receive log messages from these devices via the syslog protocol.

My requirements were:

  • Logs from different devices should go into a dedicated file each.
  • Logs from the local machine should not go into any of these files, but the standard Ubuntu logging should be continued to be observed.

It took me a while to figure out how the “ultimate” configuration should be, but here’s the result in case anybody else has similar requirements:

Categories
Ubuntu

Issues in Ubuntu 13.04 after machine froze…

I recently upgraded from Ubuntu 12.10 to 13.04, and everything seemed to be extremely smooth and painless.

However, a day or two later I suddenly noticed that the fan of my Ubuntu laptop (a Dell Latitude D630) was blowing like hell — the machine had stalled, I couldn’t wake up the desktop again, the screen remained black… I think the hang occurred after I had installed the first updates after upgrading to 13.04… Anyway, I had to hard-reboot the box… And this is when the trouble started… 🙁

Dunno what exactly happened, but the first thing I noticed was boot issues, something like “Cannot mount /boot; ext2: no such filesystem” or something close to that. And indeed the kernel in Ubuntu 13.04 seems to lack support for that admittedly ancient filesystem (cat /proc/filesystems). I fixed that by creating a journal on my /boot filesystem as follows (obviously if you have similar issues, you need to substitute your actual UUID in the command below), thereby migrating the filesystem to ext3:

sudo tune2fs -j UUID=b8ad9dbd-a514-46c8-86af-d2a9cafe3d0c

I also had to update /etc/fstab accordingly, of course:

UUID=b8ad9dbd-a514-46c8-86af-d2a9cafe3d0c /boot           ext3    defaults        0       2

Next thing I noticed that a couple of devices suddenly didn’t work: The touchpad, the touchpoint, my WiFi interface, etc. I quickly found out that obviously the modules required to support the devices weren’t loaded, and it was due to missing/broken modules dependencies. The following file which keeps those dependencies

/lib/modules/3.8.0-19-generic/modules.dep.bin

was truncated (size of 0 bytes).

So I removed it and recreated it by

sudo depmod -a

After I rebooted everything seemed to be fine again.

I hope that this concludes my negative experiences with 13.04, and that the laptop will runs as rock solid again as it used to be under 12.10.