Synology DS415Play - Failed to install Serviio

Hi,

I originally had Serviio installed on my old DS212 and working. I shifted the disks from there to my new DS415Play and it still worked, but not completely.

I decided to uninstall and reinstall (various reasons), but now the package installation simply fails. (dialog box pops up and says "failed to install Servo.")

I am running DSM 5.1-5022 Update 3.

I installed jdk-7u75-linux-i586 using the java manager.

Tried Java 6, but that made no difference. ( have stopped/started the NAS).

Ironically, I was just getting going with the API and had paid for the Pro version when this happened.

Any suggestions how I can start to troubleshoot this?

Andy

I sent the logs to Synology, but there is nothing being written in the general logs when the installation fails so I have no clue why it is failing and they could not help.

Does anyone know where I can log to start troubleshooting?

A.

Hello,

Did you manage to resolve this eventually? I'm having similar issues.

Hi,

Sadly, no. I have left it alone for a while so no progress.

A.

Sadly this is still an issue.

I have used find and deleted every reference to 'serviio*' in an attempt to make sure nothing is stopping the installation because of old files.

I have made sure the public folder is wide open in case the permissions on that folder were an issue.

Anyone got any bright ideas?

All I need is some sort of guidance on where to check for problems and I'll follow the trail myself.

Andy

[patters]

Old package files would be in /var/packages/Serviio
Before you delete that, navigate to /var/packages/Serviio/target which is a symbolic link to the parts of the package that live in the @appstore folder (this could be on any volume, so the sym link allows a consistent way of referencing it). Delete the files and folders in there. Then remove the Serviio user account and its home folder if it still exists. That should clean up all traces of a previous install.

You can troubleshoot package issues by checking the main system log after the failure. E.g.:

  Code:

tail -n 30 /var/log/messages

You will often get some idea of the line number in the script causing the issue.