Project

General

Profile

Bug #2458

Amahi 12 with fedora 34 and platform 11.9

Added by cpg 11 days ago. Updated about 4 hours ago.

Status:
Assigned
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
04/28/2021
Due date:
% Done:

0%


Description

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.HDA_DOMAIN

History

#1 Updated by cpg 11 days ago

There is also a message that reads like this

Apr 28 19:26:28 fedora systemd-resolved[584]: Using degraded feature set TCP instead of UDP for DNS server 192.168.32.20.

while (seemingly) harmless, it is quite annoying, as it's spamming the logs every 6 seconds.

#2 Updated by cpg 9 days ago

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.

#3 Updated by cpg 5 days ago

After some prep, I updated my HDA to F34 and it was surprisingly easy and quick. More than ever.

#4 Updated by bigfoot65 4 days ago

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.

#5 Updated by cpg 3 days ago

Try this work-around to see if the platform works, as root:

cd /var/hda/platform/html/
mkdir -p tmp/pids/
chown apache:apache -R tmp
systemctl restart hda-platform

#6 Updated by cpg 3 days ago

Scratch that. This rpm was pushed to the f34 repo: hda-platform-11.9.1-1.x86_64.rpm and a simple upgrade should fix this issue without the need of a workaround. Please confirm.

#7 Updated by cpg 3 days ago

I cannot seem to build hda-ctl so that it does not crash upon launch on f34. I do not know yet why. The f33 version may work (but I am not sure if that is what is in the repo), i.e. what's in the repo may work or not.

#8 Updated by bigfoot65 3 days ago

I did the work around before I saw the guidance about the upgraded rpm. The dashboard is now working for me using IP address.

Apps appear to be working as well. I will test more and report back.

#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