Amahi Forums

Posted: **Wed Aug 05, 2015 2:07 pm**

Hi

I hope you can help me

a couple of weeks ago I started receiving "The Dashboard has encountered an exception!" I've also noticed today that when I sign in to the Amahi website and go to my server's control pannel my server status is showing as stopped.

Does this mean I need to reinstall everything or is there a way to resolve this issue?

Thanks

Posted: **Wed Aug 05, 2015 5:18 pm**

Can you provide some more details?

Is this a default setup (Express CD)?

Are there apps installed?

Did you do any modifications to the OS after installing Amahi?

Can you ping the internet from the machine?

Did you try a reboot?

Posted: **Thu Aug 06, 2015 4:59 am**

Thanks bigfoot65 for the quick response

Please find answers below

Can you provide some more details?

Sure, the server is running on an old IBM laptop and has been running with no issues for the best part of two years

Is this a default setup (Express CD)?

It was a manual installation - Fedora 19 + Amahi. I don't remember why it was manual but the Fedora express CD did not run on my hardware

Are there apps installed?

yes
From Amahi app store: SABNZBD, Sick Beard and a few others
Manually: castget, google-drive-ocamlfuse

Did you do any modifications to the OS after installing Amahi?

no, apart for installed apps

Can you ping the internet from the machine?

yes. Also Amahi is the DHCP server and seems to be in operation

Did you try a reboot?

several times... No change.

The system is up to date, I run yum update all every few weeks. running it now comes up with nothing to do.

Disk space seems to be fine:

Code: Select all

Partition: /dev/mapper/fedora-root
Total size: 34G | Used space: 9.5G | Free space: 22G | Used space percent: 31%
[#######################======================================================]

Partition: /dev/sda1
Total size: 477M | Used space: 81M | Free space: 367M | Used space percent: 18%
[#############================================================================]

Partition: /dev/sdb1
Total size: 1.8T | Used space: 165G | Free space: 1.6T | Used space percent: 10%
[#######======================================================================]

memory status:

Code: Select all

cat /proc/meminfo
MemTotal:        1536464 kB
MemFree:           34160 kB
MemAvailable:    1134712 kB
Buffers:            4620 kB
Cached:          1092468 kB
SwapCached:        10280 kB
Active:           279052 kB
Inactive:        1170960 kB
Active(anon):      74184 kB
Inactive(anon):   279708 kB
Active(file):     204868 kB
Inactive(file):   891252 kB
Unevictable:           0 kB
Mlocked:               0 kB
HighTotal:        658312 kB
HighFree:           2248 kB
LowTotal:         878152 kB
LowFree:           31912 kB
SwapTotal:       3178492 kB
SwapFree:        3039872 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:        346552 kB
Mapped:            21732 kB
Shmem:               976 kB
Slab:              32896 kB
SReclaimable:      22468 kB
SUnreclaim:        10428 kB
KernelStack:        1888 kB
PageTables:         6772 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:     3946724 kB
Committed_AS:    1610448 kB
VmallocTotal:     122880 kB
VmallocUsed:        9760 kB
VmallocChunk:     112472 kB
HardwareCorrupted:     0 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:       24568 kB
DirectMap2M:      880640 kB

Please let me know what other information is requred

Posted: **Thu Aug 06, 2015 1:00 pm**

Manually: castget, google-drive-ocamlfuse

This could cause a problem. have there been any updates to this software?

The system is up to date, I run yum update all every few weeks. running it now comes up with nothing to do.

Fedora is at end-of-life, so there will be no more updates. No point in checking for them in the future.

I don't see anything else that would be causing problems. Have you checked the /var/log/messages for errors? Might run this as root user:

Code: Select all

systemctl status hda-ctl

Is it running? If not, try this next:

Code: Select all

systemctl start hda-ctl

then check the status again.

Posted: **Fri Aug 07, 2015 12:32 am**

The system is running

Code: Select all

hda-ctl.service - Amahi HDA controller
   Loaded: loaded (/usr/lib/systemd/system/hda-ctl.service; enabled)
   Active: active (running) since Wed 2015-08-05 21:00:55 BST; 1 day 11h ago
  Process: 926 ExecStart=/usr/bin/hda-ctl $HDA_CTL_OPTIONS (code=exited, status=0/SUCCESS)
 Main PID: 996 (hda-ctl)
   CGroup: name=systemd:/system/hda-ctl.service
           ├─996 /usr/bin/perl -w /usr/bin/hda-ctl
           └─997 /usr/bin/perl -w /usr/bin/hda-ctl

I am not aware of any updates to the manually installed programs, how can I check if they were recently updated?

Posted: **Fri Aug 07, 2015 9:03 am**

Recommend you check the /var/log/messages or any other system log for errors.

Posted: **Fri Aug 07, 2015 1:15 pm**

Thanks bigfoot65
/var/log/messages hold a lot of information. Anything specific I should be looking for or should I upload the log to the forum for you to review?

Posted: **Fri Aug 07, 2015 2:12 pm**

a few errors from the log:

Code: Select all

Aug  7 21:00:22 localhost mysqld-prepare-db-dir[586]: touch: cannot touch ‘/var/log/mysqld.log’: Permission denied
Aug  7 21:00:22 localhost mysqld-prepare-db-dir[586]: chown: cannot access ‘/var/log/mysqld.log’: No such file or directory
Aug  7 21:00:22 localhost systemd[1]: Failed to read PID from file /run/sm-client.pid: Invalid argument

Code: Select all

Aug 7 21:00:24 localhost systemd[1]: Failed to read PID from file /var/run/openvpn/amahi.pid: Invalid argument

Code: Select all

Aug  7 21:00:25 localhost mysqld_safe[702]: 150807 21:00:25 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Aug  7 21:00:25 localhost mysqld_safe[702]: /usr/bin/mysqld_safe: line 138: /var/log/mysqld.log: Permission denied
Aug  7 21:00:25 localhost mysqld_safe[702]: /usr/bin/mysqld_safe: line 182: /var/log/mysqld.log: Permission denied
Aug  7 21:00:25 localhost mysqld_safe[702]: touch: cannot touch ‘/var/log/mysqld.log’: Permission denied
Aug  7 21:00:25 localhost mysqld_safe[702]: chown: cannot access ‘/var/log/mysqld.log’: No such file or directory
Aug  7 21:00:25 localhost mysqld_safe[702]: chmod: cannot access ‘/var/log/mysqld.log’: No such file or directory
Aug  7 21:00:25 localhost mysqld_safe[702]: 150807 21:00:25 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Aug  7 21:00:25 localhost mysqld_safe[702]: /usr/bin/mysqld_safe: line 138: /var/log/mysqld.log: Permission denied
Aug  7 21:00:25 localhost systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
Aug  7 21:00:25 localhost systemd[1]: mysqld.service: control process exited, code=exited status=1
Aug  7 21:00:25 localhost systemd[1]: Failed to start MariaDB database server.
Aug  7 21:00:25 localhost systemd[1]: Unit mysqld.service entered failed state.

Code: Select all

Aug  7 21:00:26 localhost amahi-anywhere[908]: FATAL: Amahi API key was not found
Aug  7 21:00:26 localhost systemd[1]: amahi-anywhere.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Aug  7 21:00:26 localhost systemd[1]: Unit amahi-anywhere.service entered failed state.
Aug  7 21:00:26 localhost systemd[1]: amahi-anywhere.service holdoff time over, scheduling restart.
Aug  7 21:00:26 localhost systemd[1]: Stopping Amahi Anywhere service...
Aug  7 21:00:26 localhost systemd[1]: Starting Amahi Anywhere service...
Aug  7 21:00:26 localhost systemd[1]: Started Amahi Anywhere service.
Aug  7 21:00:26 localhost amahi-anywhere[918]: PID: 908
Aug  7 21:00:26 localhost amahi-anywhere[918]: PID file exists, but it's stale. Continuing.
Aug  7 21:00:26 localhost amahi-anywhere[918]: FATAL: Amahi API key was not found
Aug  7 21:00:26 localhost systemd[1]: amahi-anywhere.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Aug  7 21:00:26 localhost systemd[1]: Unit amahi-anywhere.service entered failed state.
Aug  7 21:00:26 localhost systemd[1]: amahi-anywhere.service holdoff time over, scheduling restart.
Aug  7 21:00:26 localhost systemd[1]: Stopping Amahi Anywhere service...
Aug  7 21:00:26 localhost systemd[1]: Starting Amahi Anywhere service...
Aug  7 21:00:26 localhost systemd[1]: Started Amahi Anywhere service.
Aug  7 21:00:26 localhost amahi-anywhere[921]: PID: 918
Aug  7 21:00:26 localhost amahi-anywhere[921]: PID file exists, but it's stale. Continuing.
Aug  7 21:00:26 localhost amahi-anywhere[921]: FATAL: Amahi API key was not found
Aug  7 21:00:26 localhost systemd[1]: amahi-anywhere.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Aug  7 21:00:26 localhost systemd[1]: Unit amahi-anywhere.service entered failed state.
Aug  7 21:00:26 localhost systemd[1]: amahi-anywhere.service holdoff time over, scheduling restart.
Aug  7 21:00:26 localhost systemd[1]: Stopping Amahi Anywhere service...
Aug  7 21:00:26 localhost systemd[1]: Starting Amahi Anywhere service...
Aug  7 21:00:26 localhost systemd[1]: Started Amahi Anywhere service.
Aug  7 21:00:26 localhost amahi-anywhere[924]: PID: 921
Aug  7 21:00:26 localhost amahi-anywhere[924]: PID file exists, but it's stale. Continuing.
Aug  7 21:00:26 localhost amahi-anywhere[924]: FATAL: Amahi API key was not found
Aug  7 21:00:26 localhost systemd[1]: amahi-anywhere.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Aug  7 21:00:26 localhost systemd[1]: Unit amahi-anywhere.service entered failed state.
Aug  7 21:00:26 localhost systemd[1]: Mounted /var/hda/files/xstorage.
Aug  7 21:00:26 localhost systemd[1]: amahi-anywhere.service holdoff time over, scheduling restart.
Aug  7 21:00:26 localhost systemd[1]: Stopping Amahi Anywhere service...
Aug  7 21:00:26 localhost systemd[1]: Starting Amahi Anywhere service...
Aug  7 21:00:26 localhost systemd[1]: Started Amahi Anywhere service.
Aug  7 21:00:26 localhost amahi-anywhere[929]: PID: 924
Aug  7 21:00:26 localhost amahi-anywhere[929]: PID file exists, but it's stale. Continuing.
Aug  7 21:00:26 localhost amahi-anywhere[929]: FATAL: Amahi API key was not found
Aug  7 21:00:26 localhost systemd[1]: amahi-anywhere.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Aug  7 21:00:26 localhost systemd[1]: Unit amahi-anywhere.service entered failed state.
Aug  7 21:00:26 localhost systemd[1]: amahi-anywhere.service holdoff time over, scheduling restart.
Aug  7 21:00:26 localhost systemd[1]: Stopping Amahi Anywhere service...
Aug  7 21:00:26 localhost systemd[1]: Starting Amahi Anywhere service...
Aug  7 21:00:26 localhost systemd[1]: amahi-anywhere.service start request repeated too quickly, refusing to start.
Aug  7 21:00:26 localhost systemd[1]: Failed to start Amahi Anywhere service.
Aug  7 21:00:26 localhost systemd[1]: Unit amahi-anywhere.service entered failed state.

Posted: **Fri Aug 07, 2015 3:45 pm**

Have you uninstalled any apps, such as Amahi Anywhere? It looks like a lot of stuff is broken.

Posted: **Sat Aug 08, 2015 1:38 am**

I have not uninstalled anything.

Is there anything worth trying to fix this? Maybe re-install Amahi? or, does it require a full re-installation of everything?

The Fedora platform seems to be working just fine. I've installed Smartmontools and checked the hard drive and it is fine as well.

Amahi Forums

The Dashboard has encountered an exception!

The Dashboard has encountered an exception!

Re: The Dashboard has encountered an exception!

Re: The Dashboard has encountered an exception!

Re: The Dashboard has encountered an exception!

Re: The Dashboard has encountered an exception!

Re: The Dashboard has encountered an exception!

Re: The Dashboard has encountered an exception!

Re: The Dashboard has encountered an exception!

Re: The Dashboard has encountered an exception!

Re: The Dashboard has encountered an exception!