Amahi Forums

Hi

Upgraded today as per the wiki, uninstalling apps then updating etc.
Everything looked quite promising until i tried to stop and disable the rolekit (could not find the rolekit.service)

Tried to access the had - dashboard failure:

The Dashboard has encountered an exception!
Woopsie. Sorry about that!

It could be due to a bug, or very low memory, or very low disk in the root (/) partition.

If your disk or memory are not critical, it's likely a bug.

If this persists, please file a bug report with as much detail as you can.

You will be redirected to a debug page with more information shortly.

For Troubleshooting visit here Troubleshoot

Here is the info gathered so far:

[anders@hda ~]$ systemctl status hda-ctl.service
● hda-ctl.service - Amahi HDA controller
Loaded: loaded (/usr/lib/systemd/system/hda-ctl.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2018-11-25 19:06:18 CET; 15min ago
Process: 1340 ExecStart=/usr/bin/hda-ctl $HDA_CTL_OPTIONS (code=exited, status=2)

Nov 25 19:06:18 localhost.localdomain systemd[1]: hda-ctl.service: Unit entered failed state.
Nov 25 19:06:18 localhost.localdomain systemd[1]: hda-ctl.service: Failed with result 'exit-code'.
Nov 25 19:06:18 localhost.localdomain systemd[1]: hda-ctl.service: Service hold-off time over, scheduling restart.
Nov 25 19:06:18 localhost.localdomain systemd[1]: Stopped Amahi HDA controller.
Nov 25 19:06:18 localhost.localdomain systemd[1]: hda-ctl.service: Start request repeated too quickly.
Nov 25 19:06:18 localhost.localdomain systemd[1]: Failed to start Amahi HDA controller.
Nov 25 19:06:18 localhost.localdomain systemd[1]: hda-ctl.service: Unit entered failed state.
Nov 25 19:06:18 localhost.localdomain systemd[1]: hda-ctl.service: Failed with result 'exit-code'.




● dnsmasq.service - DNS caching server.
Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2018-11-25 19:06:17 CET; 11min ago
Main PID: 1336 (dnsmasq)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/dnsmasq.service
└─1336 /usr/sbin/dnsmasq -k

Nov 25 19:12:20 hda.home.p4 dnsmasq-dhcp[1336]: DHCPREQUEST(enp6s0) 10.0.0.234 38:80:df:e7:6a:18
Nov 25 19:12:20 hda.home.p4 dnsmasq-dhcp[1336]: DHCPACK(enp6s0) 10.0.0.234 38:80:df:e7:6a:18 android-96f28f6d271b31e6
Nov 25 19:12:20 hda.home.p4 dnsmasq-dhcp[1336]: not giving name localhost.home.p4 to the DHCP lease of 10.0.0.219 because the name exists in /etc/hosts with address 127.0.0.1
Nov 25 19:12:20 hda.home.p4 dnsmasq-dhcp[1336]: not giving name localhost to the DHCP lease of 10.0.0.219 because the name exists in /etc/hosts with address 127.0.0.1
Nov 25 19:14:55 hda.home.p4 dnsmasq-dhcp[1336]: DHCPREQUEST(enp6s0) 10.0.0.254 60:38:e0:dc:4b:84
Nov 25 19:14:55 hda.home.p4 dnsmasq-dhcp[1336]: DHCPACK(enp6s0) 10.0.0.254 60:38:e0:dc:4b:84 NCAGSPC19
Nov 25 19:14:55 hda.home.p4 dnsmasq-dhcp[1336]: not giving name localhost.home.p4 to the DHCP lease of 10.0.0.219 because the name exists in /etc/hosts with address 127.0.0.1
Nov 25 19:14:55 hda.home.p4 dnsmasq-dhcp[1336]: not giving name localhost to the DHCP lease of 10.0.0.219 because the name exists in /etc/hosts with address 127.0.0.1
Nov 25 19:16:40 hda.home.p4 dnsmasq-dhcp[1336]: DHCPINFORM(enp6s0) 10.0.0.254 60:38:e0:dc:4b:84
Nov 25 19:16:40 hda.home.p4 dnsmasq-dhcp[1336]: DHCPACK(enp6s0) 10.0.0.254 60:38:e0:dc:4b:84 NCAGSPC19

● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/httpd.service.d
└─php-fpm.conf
Active: active (running) since Sun 2018-11-25 19:06:17 CET; 14min ago
Docs: man:httpd.service(8)
Main PID: 890 (httpd)
Status: "Running, listening on: port 80"
Tasks: 239 (limit: 4915)
CGroup: /system.slice/httpd.service
├─ 890 /usr/sbin/httpd -DFOREGROUND
├─1013 /usr/sbin/httpd -DFOREGROUND
├─1014 Passenger watchdog
├─1017 Passenger core
├─1026 Passenger ust-router
├─1042 /usr/sbin/httpd -DFOREGROUND
├─1043 /usr/sbin/httpd -DFOREGROUND
└─1044 /usr/sbin/httpd -DFOREGROUND

Nov 25 19:06:16 localhost.localdomain systemd[1]: Starting The Apache HTTP Server...
Nov 25 19:06:16 localhost.localdomain httpd[890]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using localhost.localdomain. Set the 'ServerName' directive globally to suppress this message
Nov 25 19:06:17 localhost.localdomain httpd[890]: Server configured, listening on: port 80
Nov 25 19:06:17 localhost.localdomain systemd[1]: Started The Apache HTTP Server.


Gathering system info ...............................Uploading (9.7KiB)...
https://paste.fedoraproject.org/paste/S ... cAOZeTqpiA


What to do next??
Any help appreciated

Br
Anders

Have you rebooted since the upgrade?

Looks like the Fedora 25 Kernel was still listed even though you are running Fedora 27.

Also recommend you do an OS update to ensure you have all packages updated.

Yes I have rebooted , also done a system update with "nothing to do" result
As for the kernels, both 25 and 27 are present, but isn't that for rollback reasons?

As far as i am able to see the system has rebooted with f27 kernels the last 8 times

https://paste.fedoraproject.org/paste/G ... oXB~Yi-sFg

@

Please provide the output of the following:

Here it goes:

total 4
drwxr-xr-x. 8 apache apache 129 Nov 25 18:10 .
drwxr-xr-x. 19 apache apache 4096 Nov 25 18:11 ..
drwxr-xr-x. 7 apache apache 152 Nov 25 18:11 010-users
drwxr-xr-x. 7 apache apache 153 Nov 25 18:10 020-shares
drwxr-xr-x. 7 apache apache 152 Nov 25 18:10 030-disks
drwxr-xr-x. 8 apache apache 163 Nov 25 18:11 040-apps
drwxr-xr-x. 6 apache apache 144 Nov 25 18:10 050-network
drwxr-xr-x. 7 apache apache 155 Nov 25 18:10 080-settings
-rw-r--r-- 1 apache apache 0 Nov 6 12:28 .gitkeep


@

The directory contents look good.

Please take a look at /var/hda/platform/html/log/production.log for errors.

Hoping there is something there.

Also check hda-ctl is running:

Thanks
Did the output of the hda-ctl service showing the same error as in my first post and title indicates
Clearly something wrong here, but i have no clue how to do anything about it

● hda-ctl.service - Amahi HDA controller
Loaded: loaded (/usr/lib/systemd/system/hda-ctl.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2018-11-26 08:15:21 CET; 16h ago
Process: 1367 ExecStart=/usr/bin/hda-ctl $HDA_CTL_OPTIONS (code=exited, status=2)

Nov 26 08:15:21 hda.home.p4 systemd[1]: hda-ctl.service: Unit entered failed state.
Nov 26 08:15:21 hda.home.p4 systemd[1]: hda-ctl.service: Failed with result 'exit-code'.
Nov 26 08:15:21 hda.home.p4 systemd[1]: hda-ctl.service: Service hold-off time over, scheduling restart.
Nov 26 08:15:21 hda.home.p4 systemd[1]: Stopped Amahi HDA controller.
Nov 26 08:15:21 hda.home.p4 systemd[1]: hda-ctl.service: Start request repeated too quickly.
Nov 26 08:15:21 hda.home.p4 systemd[1]: Failed to start Amahi HDA controller.
Nov 26 08:15:21 hda.home.p4 systemd[1]: hda-ctl.service: Unit entered failed state.
Nov 26 08:15:21 hda.home.p4 systemd[1]: hda-ctl.service: Failed with result 'exit-code'.

Also found errors in the platform.log, however not sure what it actually means

I, [2018-11-26T20:59:55.406477 #4808] INFO -- : [9b746da9-dedf-469d-8e84-b87ab50f4adf] Completed 500 Internal Server Error in 7ms (ActiveRecord: 0.8ms)
F, [2018-11-26T20:59:55.407113 #4808] FATAL -- : [9b746da9-dedf-469d-8e84-b87ab50f4adf]
F, [2018-11-26T20:59:55.407151 #4808] FATAL -- : [9b746da9-dedf-469d-8e84-b87ab50f4adf] JSON::ParserError (765: unexpected token at '^D^H{
I"^Osession_id^F:^FETI"%8d6199cc32adf6e99875b345fcaf2093^F;'):
F, [2018-11-26T20:59:55.407182 #4808] FATAL -- : [9b746da9-dedf-469d-8e84-b87ab50f4adf]
F, [2018-11-26T20:59:55.407230 #4808] FATAL -- : [9b746da9-dedf-469d-8e84-b87ab50f4adf] app/controllers/application_controller.rb:166:in `current_user_session'
[9b746da9-dedf-469d-8e84-b87ab50f4adf] app/controllers/application_controller.rb:171:in `current_user'
[9b746da9-dedf-469d-8e84-b87ab50f4adf] app/controllers/application_controller.rb:175:in `login_required'
[9b746da9-dedf-469d-8e84-b87ab50f4adf] app/controllers/application_controller.rb:190:in `admin_required'
I, [2018-11-26T20:59:59.561730 #4808] INFO -- : [b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2] Started GET "/tab/debug" for 10.0.0.254 at 2018-11-26 20:59:59 +0100
I, [2018-11-26T20:59:59.562372 #4808] INFO -- : [b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2] Processing by DebugController#index as HTML
D, [2018-11-26T20:59:59.563544 #4808] DEBUG -- : [b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2] ESC[1mESC[36mSetting Load (0.2ms)ESC[0m ESC[1mESC[34mSELECT `settings`.* FROM `settings` WHERE `settings`.`name` = 'domain' ORDER BY `settings`.`id` ASC LIMIT 1ESC[0m
D, [2018-11-26T20:59:59.564207 #4808] DEBUG -- : [b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2] ESC[1mESC[36mSetting Load (0.2ms)ESC[0m ESC[1mESC[34mSELECT `settings`.* FROM `settings` WHERE `settings`.`name` = 'theme' ORDER BY `settings`.`id` ASC LIMIT 1ESC[0m
D, [2018-11-26T20:59:59.566954 #4808] DEBUG -- : [b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2] ESC[1mESC[36mSetting Load (0.2ms)ESC[0m ESC[1mESC[34mSELECT `settings`.* FROM `settings` WHERE `settings`.`name` = 'advanced' ORDER BY `settings`.`id` ASC LIMIT 1ESC[0m
D, [2018-11-26T20:59:59.568102 #4808] DEBUG -- : [b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2] ESC[1mESC[36mUser Load (0.2ms)ESC[0m ESC[1mESC[34mSELECT `users`.* FROM `users` WHERE `users`.`id` = 1 LIMIT 1ESC[0m
I, [2018-11-26T20:59:59.569265 #4808] INFO -- : [b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2] Completed 500 Internal Server Error in 7ms (ActiveRecord: 0.7ms)
F, [2018-11-26T20:59:59.569880 #4808] FATAL -- : [b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2]
F, [2018-11-26T20:59:59.569919 #4808] FATAL -- : [b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2] JSON::ParserError (765: unexpected token at '^D^H{
I"^Osession_id^F:^FETI"%8d6199cc32adf6e99875b345fcaf2093^F;'):
F, [2018-11-26T20:59:59.569954 #4808] FATAL -- : [b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2]
F, [2018-11-26T20:59:59.569989 #4808] FATAL -- : [b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2] app/controllers/application_controller.rb:166:in `current_user_session'
[b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2] app/controllers/application_controller.rb:171:in `current_user'
[b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2] app/controllers/application_controller.rb:175:in `login_required'
[b6cbfd9b-9c0c-441f-b73c-8c59ebcc52b2] app/controllers/application_controller.rb:190:in `admin_required'

Looks like the upgrade didn’t go well.

I had the same issues on a upgrade. It was unfixable, meaning a reinstall from scratch was required.

I’m sorry to say I believe that’s your case. Only way to get things working is via new install.

Upgrade goes well for most, but some have experienced issues that could not be resolved.

Ok, thanks for the help - had hoped to avoid a new install

@

Yea I know. Most would rather not have to start over.

Not sure if it will help with the new install, but you might check out the HDA OS Migration Guide.

I presume we can mark this topic closed.