[SOLVED] Cannot add network drive to Serviio 1.5

[SOLVED] Long story short, access permissions on NAS were fubar. No clue why. Enabling/disabling guest account seemed do the trick.[/SOLVED]

I am getting the following error when I add my network drives to the library in Serviio 1.5. This worked previously in version 1.4. I have the Serviio service setup to run as my user. The drives are mounted and working as usual.

  Code:

[RepositoriesStatus] Repository '\\DISKSTATION\video' is not currently available. Deferring all operations for later.

  Code:

2015-01-25 12:04:39,147 INFO  [MediaServer] ------------------------------------------------------------------------
2015-01-25 12:04:39,147 INFO  [MediaServer] Serviio DLNA media streaming server v 1.5 (rev. 19ceb8acec8c)
2015-01-25 12:04:39,147 INFO  [MediaServer] Petr Nejedly 2009-2015
2015-01-25 12:04:39,147 INFO  [MediaServer] http://www.serviio.org
2015-01-25 12:04:39,147 INFO  [MediaServer]
2015-01-25 12:04:39,147 INFO  [MediaServer] Java 1.8.0_20-Oracle Corporation x86
2015-01-25 12:04:39,147 INFO  [MediaServer] OS Windows 8 6.2
2015-01-25 12:04:39,147 INFO  [MediaServer] File encoding: windows-1252
2015-01-25 12:04:39,147 INFO  [MediaServer] Headless mode enabled: true
2015-01-25 12:04:39,147 INFO  [MediaServer] User: Adam
2015-01-25 12:04:39,147 INFO  [MediaServer] User home dir: C:\Users\Adam
2015-01-25 12:04:39,147 INFO  [MediaServer] Temp dir: C:\Users\Adam\AppData\Local\Temp\
2015-01-25 12:04:39,147 INFO  [MediaServer] ------------------------------------------------------------------------

[zip]

Check the access rights again. The message means that the drive is not available to Serviio when it starts, meaning it's either disconnected or not 'readable' (ie the user has no access to it)

Check the access rights again. The message means that the drive is not available to Serviio when it starts, meaning it's either disconnected or not 'readable' (ie the user has no access to it)

The access rights are definitely OK. Is it possible that Serviio is starting up before the drives are mounted? The mounts and the server both start at log in.

[atc98092]

Check the access rights again. The message means that the drive is not available to Serviio when it starts, meaning it's either disconnected or not 'readable' (ie the user has no access to it)

The access rights are definitely OK. Is it possible that Serviio is starting up before the drives are mounted? The mounts and the server both start at log in.

That's a possibility. You appear to be running Windows. Is it Windows 7 or 8? if so, you can go into the Services applet and change the Serviio startup to "Automatic (Delayed)". This should give the drives enough time to mount.

Also, you mentioned log in. Does your computer log in automatically on boot, or do you have to log in? If it's not automatic, network drive mappings do not exist until you log in. If you want to connect to a network share, you need to use a UNC, not a drive letter. Of course, that error you show is a UNC, so this may not be the issue.

[DenyAll]

Is it possible that Serviio is starting up before the drives are mounted? The mounts and the server both start at log in.

Yes, but in version 1.5 once the drive is mounted this should then be detected and the drive scanned. Does that happen later in the log?

What happens after a Forced Refresh. If still nothing double check access rights, and post detailed log showing the period when the drive mounts (you may have to manually mount it).

[zip]

yes, in 1.5 it should check every 10 seconds and when the drive becomes available it'll start the delta scan. It will not run the manual scan at this point, so you'd need a force refresh.

If this is happening, you'd see something like this in the detailed log

  Code:

Repository XXXXXX has become available

I am running Windows 8.1 and I manually log into my account. I removed the folder from my library and bounced the Serviio service and server. I verified that the folder is readable and writeable for my user account. I then added the folder back to the library. I saw the same behavior as before. I then manually refreshed the library. Here is the detailed log (http://pastebin.com/XmCD6iDp).

[snowflake7]

Just wondering, your post states that you are trying to connect to a network drive. I noticed that the log posting references "\\diskstation\video..." By chance is this a NAS device. If so you will need to be sure that there is an account on the NAS that is exactly the same (Username and password) as the windows account that you are using to run the serviio service. Otherwise you will never see the repository on the NAS. I run a couple of Synology NAS devices and use this configuration successfully.

Just wondering, your post states that you are trying to connect to a network drive. I noticed that the log posting references "\\diskstation\video..." By chance is this a NAS device. If so you will need to be sure that there is an account on the NAS that is exactly the same (Username and password) as the windows account that you are using to run the serviio service. Otherwise you will never see the repository on the NAS. I run a couple of Synology NAS devices and use this configuration successfully.

It is a NAS and the account name and password are identical on my Windows machine and the Synology. As I said before, this all worked on 1.4. I'm wondering if this is a Java 8 issue. A lot has changed from 6 to 8. Maybe some kind of security settings?

[DenyAll]

But is it the same account as is used for the Serviio Service?

On your windows machine, run services.msc. Double click on the Serviio Service, and go to the Log On tab.
Is this using the same user account as is used on the NAS (in the "This account" area)? When you upgraded to 1.5 it may have reverted to the standard Local System account.

But is it the same account as is used for the Serviio Service?

On your windows machine, run services.msc. Double click on the Serviio Service, and go to the Log On tab.
Is this using the same user account as is used on the NAS (in the "This account" area)? When you upgraded to 1.5 it may have reverted to the standard Local System account.

The Serviio service is already running as my account. I manually did this after upgrading to 1.5.

[DenyAll]

Based on what is not in your log, the drive is never detected as becoming available by Serviio. One of two things - there is an issue with Serviio not detecting it becoming active, or more likely imo, the condition that is preventing it being read initially doesn't change (hence why everyone is thinking access rights, but we seem to have covered that).

This goes against all best practice but what happens if you map the drive? If this works it would suggest an issue with Serviio's handling of URL's.
Can you make the drive/folder accessible by everyone (ie. without login credentials - the Everyone or Anonymous user)? If this works it would suggest an issue with access rights still.
ps. are non-networked drives working?

Based on what is not in your log, the drive is never detected as becoming available by Serviio. One of two things - there is an issue with Serviio not detecting it becoming active, or more likely imo, the condition that is preventing it being read initially doesn't change (hence why everyone is thinking access rights, but we seem to have covered that).

This goes against all best practice but what happens if you map the drive? If this works it would suggest an issue with Serviio's handling of URL's.
Can you make the drive/folder accessible by everyone (ie. without login credentials - the Everyone or Anonymous user)? If this works it would suggest an issue with access rights still.
ps. are non-networked drives working?

Changing it to a mapped drive makes no difference (I used V:). Local drives are working just fine so that leaves the access rights...

So I enabled the Guest account (with no password) on my NAS and gave it read permissions to the video folder. I then removed the folder from the library and stopped the Serviio service. I switched the service to run as the local system account (not as a user). I then started up the service and added the same folder back to the library. This time it worked. It started to index the network folder. So it is an access rights issue, but I'm just not sure what the issue is. I've triple checked the permissions to that folder and to my user account. Unfortunately, leaving the Guest account on with no password isn't an option since I have my NAS open to the interwebs.

[DenyAll]

Strange indeed. A few thoughts:

• Try sharing a new Video_1 folder on the NAS with a couple of video files. If that works, move all video files to the new folder, delete the old and rename the new. This would indicate something got screwed up in the security attributes on the original folder.
• Maybe re-instate your user rights on the original video folder and propagate to all files (once again, re-establishing the attributes but also on all files and sub-folders)
• What happens if you set up a dedicated user account for Serviio?

These are all just stabs in the dark though....

Strange indeed. A few thoughts:

• Try sharing a new Video_1 folder on the NAS with a couple of video files. If that works, move all video files to the new folder, delete the old and rename the new. This would indicate something got screwed up in the security attributes on the original folder.
• Maybe re-instate your user rights on the original video folder and propagate to all files (once again, re-establishing the attributes but also on all files and sub-folders)
• What happens if you set up a dedicated user account for Serviio?

These are all just stabs in the dark though....

So I disabled the Guest account and switched the service back to my user......and it is working fine now. I think you are right about the permissions being screwy. Thanks everyone for the help.

Sent from my LG-LS980 using Tapatalk