MAAS@snap on RPi4b doesn't start proxy+syslog

I did a first time test of MAAS@snap on regular x86 Ubuntu and it installed and functioned as expected. Then I tried do the same on RPi4b 8GB, but MAAS refused to start proxy+syslog.

It’s the same on both my pies, before and after wifi-country selection, before and after raspi-updates, Raspbian, Fedora 37, Ubuntu 20.04 and 22.04, with and without 80mm fan for CPU-cooling. With and without snap core installed. MAAS 3.1, 3.2, 3.3 beta and 3.3 RC1 @ snap all give the same result. Apt seems to be built for a specific OS version, so I only tried it once.

No matter what I try of the above the result stays the same: proxy and syslog refuse to start on RPi4b 8GB and 4GB. And every time I doublecheck with any x86 OS it just works there.

Is this a known issue? Are there some common pitfalls I have to cover/fix on a fresh RPi4 before MAAS starts the proxy service?

My intent is to in my homelab use 2x RPi4 at the bottom of the stack with MAAS and other basic services, and then build my other servers and services in layers on top of that. Couse my lab is small, so why use more electricity and hardware on something that have little CPU usage, and just very rare disk activity.

sudo snap list maas

Name  Version                  Rev    Tracking    Publisher   Notes
maas  3.2.6-12016-g.19812b4da  23949  3.2/stable  canonical✓  -

sudo /snap/bin/maas status

bind9                            RUNNING   pid 790, uptime 17:55:16
dhcpd                            STOPPED   Not started
dhcpd6                           STOPPED   Not started
http                             RUNNING   pid 854, uptime 17:55:09
ntp                              RUNNING   pid 792, uptime 17:55:16
proxy                            STOPPED   Not started
rackd                            RUNNING   pid 793, uptime 17:55:16
regiond                          RUNNING   pid 794, uptime 17:55:16
syslog                           STOPPED   Not started

Logs for Raspbian 5.15.76-v8+ #1597 (the last OS I tested with all possible fixes, and the end result is still the same):
https://drive.google.com/file/d/17Ma9G-6kgmCUHRlpEiJtebvSRKKzIyrP/

Just noticed that maas-cli isn’t autoinstalled via snap on Raspbian.

I did a fresh install of Raspbian today. 3.3 RC2 doesn’t start proxy as before, but looks like 3.4 alpha has fixed the issue. (The 3.4 alpha I tried when writing the orig post just crashed on start, so this is a new and improved version.)

Thank you!

sudo snap list maas

Name  Version                         Rev    Tracking     Publisher   Notes
maas  3.4.0~alpha1-13395-g.9034ea581  25400  latest/edge  canonical✓  -

sudo /snap/bin/maas status

bind9                            RUNNING   pid 6066, uptime 0:00:36
dhcpd                            STOPPED   Not started
dhcpd6                           STOPPED   Not started
http                             RUNNING   pid 6289, uptime 0:00:13
ntp                              RUNNING   pid 6216, uptime 0:00:21
proxy                            RUNNING   pid 6249, uptime 0:00:18
rackd                            RUNNING   pid 6069, uptime 0:00:36
regiond                          RUNNING   pid 6071, uptime 0:00:36
syslog                           RUNNING   pid 6219, uptime 0:00:20

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.