Project

General

Profile

Support #1337

Amahi/SuperSync Integration

Added by bigfoot65 almost 5 years ago. Updated over 3 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
Apps
Target version:
-
Start date:
04/04/2014
Due date:
05/09/2014
% Done:

0%


Description

I started testing the app. Client has a lot of features. I selected the option to sync the music to my HDA. It did not go as I expected.

Transfer was quick, but it put a new folder in /var/hda/files/music entitled Music. The other issue is the folder and it's contents are owned by root:root.

That is bad for Amahi as it needs to have the ownership permissions of the /var/hda/files/music folder. For Amahi, it's 1st Admin user.

The next step that needs to be tested is how it plays with Greyhole. Can SuperSync handle symbolic links? If not, this could be a hindrance as many users have Greyhole enabled on their server.

I will pass on additional info as I continue testing.

History

#1 Updated by bigfoot65 almost 5 years ago

I noticed that the client defaults to the iTunes library. Recommend we change it to default to the Amahi Music share.

\\HDA\Music

Since the point of this integration is to use the HDA Music, makes more sense than using iTunes.

I also noticed that when it's set to use the iTunes library, it automatically opens iTunes in the background. This is annoying in my opinion. Is it possible to use the iTunes library, but not open the actual iTunes application?

#2 Updated by darshin almost 5 years ago

  • Due date set to 05/09/2014
  • Status changed from New to Assigned
  • Assignee set to bigfoot65
  • Priority changed from Normal to High

Hi,

The SuperSync team is working on fixing the issues mentioned. In the next beta update thats due in two week's time, we aim at fixing the root issue, the default directory issue.

Regarding Greyhole, we would try to incorporate this by GA.

#3 Updated by fvicente almost 5 years ago

  • Priority changed from High to Medium

installed SuperSync from apps list. service doesn't want to start. If I run the startup.sh from the /opt/supersync directory I get:
Starting SuperSync Server 1.0.7 (build 20140513)
Starting SuperSync 5.4.4 build 20140513 jvm 1.7.0_55 64
config: /opt/supersync/supersync.config exists=false
Fatal SuperSync error: java.lang.NulPointerException
java.lang.NullPointerException
at ss.headless.Headless.setFilePaths(Headless.java:316)
at ss.supersync.CommandLine.startupProcess(CommandLine.java:598)
at ss.headless.Headless.main(Headless.java:196)
at SuperSyncServer.main(SuperSyncServer.java:13)

and pointing to hda:5360 or supersync.home.local yields service unavailable error message.

#4 Updated by bigfoot65 almost 5 years ago

Thanks for the feedback. There is a service which runs the app.

As root user, try:

systemctl start supersync.service

It should have started on it's own, but something may not have worked correctly. Did you also check /var/log/amahi-app-installer.log for errors?

#5 Updated by fvicente almost 5 years ago

the amahi app-install log shows the installation, with no errors.

"systemctl start supersync.service" starts the service, but it stops and restarts several times until it reaches the start-limit and then fails. is there another log I can check?

this is a bone-stock install off the express cd, on a vmware ESX 5.5 server, with just supersync and amahi time machine installed. I rebuilt it fresh yesterday before I submitted the update just to make sure something hadn't gone wrong with the initial install.

#6 Updated by bigfoot65 almost 5 years ago

  • Priority changed from Medium to Normal

I am afraid it appears to be broken. I will try to contact the vendor and see if they know of the issue. They are supposed to be coming out with a new release soon.

#7 Updated by bigfoot65 almost 5 years ago

The error being reported is:

Starting SuperSync Server 1.0.7 (build 20140513)
Starting SuperSync 5.4.4 build 20140513 jvm 1.7.0_55 64
config: /opt/supersync/supersync.config exists=false
Fatal SuperSync error: java.lang.NullPointerException
java.lang.NullPointerException
at ss.headless.Headless.setFilePaths(Headless.java:316)
at ss.supersync.CommandLine.startupProcess(CommandLine.java:598)
at ss.headless.Headless.main(Headless.java:196)
at SuperSyncServer.main(SuperSyncServer.java:13)

#8 Updated by fvicente almost 5 years ago

i see they pushed out an update, but I don't see an update button anywhere in the amahi control panel. tried "yum update supersync" but it doesn't have the source repository. should i remove and reinstall or is there a smoother way to update?

#9 Updated by bigfoot65 almost 5 years ago

There is no update button for apps unless it's integrated into the app itself. The only way to update is to uninstall, clean up any leftovers, then reinstall.

To cleanup the RPM after uninstall, do the following as root user:
yum erase supersync
rm -rf /opt/supersync

That should remove all the trash. Once you reinstall, give it a minute for the service to start before trying to access the app URL.

#10 Updated by fvicente almost 5 years ago

got it!
uninstalled, removed, installed 1.0.8, restarted. Service was still start-limit stopped. Had to run start.sh from the /opt/supersync to get it to run. but i can now access the web interface for supersync.

...update: it ran for 60 seconds before it stopped again.
...update 2. ran ./upgrade.sh from the /opt/supersync directory, app updated itself again, now web interface working. hasn't shut down in 10 minutes of use, will report later tonight if it's still up.

#11 Updated by bigfoot65 almost 5 years ago

The app is still not working right. Should not have to run the upgrade.sh script as it should work on install.

The service still does not work, even after running the upgrade.sh script. When you reboot, the service will not start successfully.

The author is working on a solution I believe.

#12 Updated by fvicente almost 5 years ago

still working 24hrs later but I haven't migrated music yet. I have to add another VHD to the VM first.

#13 Updated by bigfoot65 almost 5 years ago

App updated and service now works. Uninstall, then as root user do:
yum erase supersync

Once uninstalled, reinstall and the app service will work correctly.

#14 Updated by fvicente almost 5 years ago

removed and reinstalled, did run immediately after install. will check reboot autostart once library re-indexes. Have obtained activation keys for my desktops, will be trying those out shortly.

#15 Updated by fvicente over 3 years ago

any update for amahi 8? I installed a fresh Amahi server instead of upgrading. The install doesn't give errors, but systemctl start supersync yields a "supersync.service failed to load: No such file or directory."

#16 Updated by bigfoot65 over 3 years ago

  • Tracker changed from Bug to Support
  • Status changed from Assigned to Feedback
  • Assignee deleted (bigfoot65)
  • Target version deleted (amahi-7-2)

There is no estimate as to when this will be available for Amahi 8. The vendor has not released a Fedora 21 version.

We have reached out to them and hope to hear something soon. Until then, this app will not work for Amahi 8. Checking the app status at http://www.amahi.org/apps will reflect it's not LIVE.

Also available in: Atom