Amahi 12 with fedora 34 and platform 11.9
These are the notes for Amahi 12 on Fedora 34.
The f34 public repo has been populated.
So far, after some amount of recompiling, it exhibits the following issues:
- hda-install seems to work ok
- upon rebooting, hda-ctl is not running
- web interface is not working by IP address, despite httpd and puma services being running
- the /etc/httpd/conf.d/01-platform.conf file has an unexploded line: ServerAlias hda.
It's clear in F34 we have to use the systemd-resolved service, since there are new layers in DNS resolution.
It appears that the best thing is to use something like a /etc/systemd/resolved.conf.d/hda.conf file, though the directory does not exist by default and it appears it's hard for the system to accept it.
There is also the issue that the dnsmasq files are not generated, so that has to be rooted out first.
I upgraded my backup HDA to Fedora 34. Easy as you said and didn't take too long.
Issues so far is cannot access dashboard. I used IP Address and it says:
Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
I will play with it more once I can get the dashboard working with IP address.
#9 Updated by cpg about 4 hours ago
OK, update on hda-ctl.
I found that hda-ctl apparently gets killed unceremoniously with a SIGTERM signal when trying to connect to the DB (even if the DB server is running) and the DB is there.
This is weird. It should instead .. get an error and we'd see quickly the DB is not set up, and the code could try again after some time (which is what the code does), until the install is ready. Killing it is just crazy.
This abrupt TERMination took a while to dig into, and I am not sure why this happens yet.
Also available in: Atom