Bug #2016

Amahi Time Machine installation Error in Amahi 9

Added by pjcrux about 6 years ago. Updated about 6 years ago.

Target version:
Start date:
Due date:
% Done:



New installation of ATM on fresh installation of A9 yeilds the following error:

======= app install begin @ 2016-04-01 11:45:16 -0500 ==========
Installing app id oxlimkd9bi under /var/hda/platform/html/script/.. ENV=produ$
Unknown operation 'netatalk'.
Redirecting to /bin/systemctl reload monit.service
App: Amahi Time Machine installed ======= app install end @ 2016-04-01 11:45:43 -0500 ==========
uninstall and reinstall results in same error.

manual installation of netatalk shows that netatalk is already installed:

[pjcrux@localhost ~]$ sudo dnf -y install netatalk
Last metadata expiration check: 1:42:19 ago on Fri Apr 1 10:08:58 2016.
Package netatalk-4:3.1.3-4.fc23.x86_64 is already installed, skipping.
Dependencies resolved.
Nothing to do.

manual enablement of netatalk at boot creates symlink:

[pjcrux@localhost ~]$ sudo systemctl enable netatalk.service
Created symlink from /etc/systemd/system/ to /usr/lib/systemd/system/netatalk.service.

after reboot netatalk does not auto enable


#1 Updated by bigfoot65 about 6 years ago

  • Category set to Apps
  • Status changed from New to Feedback
  • Assignee set to pjcrux
  • Priority changed from High to Normal
  • Target version set to amahi-9

Corrected error.

Unknown operation 'netatalk'.

Verified netatalk is enabled after reboot and does start automatically as expected.

Recommend uninstall/reinstall app. If working correctly, please close bug.

#2 Updated by pjcrux about 6 years ago

Just uninstalled and reinstalled the app. Netatalk and Avahi-Daemon are enabled and working.

However, my iMac running 10.11.4 does not see the ATM destination over the network. There is nothing in the logs that shows any error.

What could be causing this?

#3 Updated by bigfoot65 about 6 years ago

  • Status changed from Feedback to Closed

No clue. Might be something specific to the OS version.

Closing bug as the issue has been resolved.

Also available in: Atom