Jump to content

Issue with sync (Google Drive)


WonkoTheSane
Go to solution Solved by WonkoTheSane,

Recommended Posts

WonkoTheSane

Hi everyone,

 

I'm running Emby 4.2.0.40 and since 2-3 days syncing to my Google Drive doesn't

seem to work anymore.

 

Extract from my log follows:

 

2019-07-30 19:42:28.112 Info TaskManager: Executing Cloud & Folder Sync2019-07-30 19:42:28.112 Info HttpServer: HTTP Response 204 to 192.168.1.66. Time: 5ms. http://192.168.1.114:8096/emby/ScheduledTasks/Running/9c4589c712196c27894f665a58cc42e32019-07-30 19:42:28.119 Info HttpServer: HTTP GET http://192.168.1.114:8096/emby/ScheduledTasks?isHidden=false. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.02019-07-30 19:42:28.120 Info HttpServer: HTTP Response 200 to 192.168.1.66. Time: 2ms. http://192.168.1.114:8096/emby/ScheduledTasks?isHidden=false2019-07-30 19:42:28.582 Error App: Error transferring sync job file	*** Error Report ***	Version: 4.2.0.40	Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3	Operating system: Unix 4.19.56.0	64-Bit OS: True	64-Bit Process: True	User Interactive: True	Runtime: file:///system/System.Private.CoreLib.dll	Processor count: 4	Program data path: /config	Application directory: /system	SharpCifs.Smb.SmbAuthException: SharpCifs.Smb.SmbAuthException: Access is denied.	   at SharpCifs.Smb.SmbTransport.CheckStatus(ServerMessageBlock req, ServerMessageBlock resp)	   at SharpCifs.Smb.SmbTransport.Send(ServerMessageBlock request, ServerMessageBlock response)	   at SharpCifs.Smb.SmbSession.Send(ServerMessageBlock request, ServerMessageBlock response)	   at SharpCifs.Smb.SmbTree.TreeConnect(ServerMessageBlock andx, ServerMessageBlock andxResponse)	   at SharpCifs.Smb.SmbFile.DoConnect()	   at SharpCifs.Smb.SmbFile.Connect()	   at SharpCifs.Smb.SmbFile.Connect0()	   at SharpCifs.Smb.SmbFile.QueryPath(String path, Int32 infoLevel)	   at SharpCifs.Smb.SmbFile.Exists()	   at Emby.Server.Implementations.IO.SharpCifsFileSystem.AssertFileExists(SmbFile file, String path)	   at Emby.Server.Implementations.IO.SharpCifsFileSystem.OpenRead(String path)	   at Emby.Server.Sync.MediaSync.SendFile(SyncJob job, String originalMediaPath, IServerSyncProvider provider, String inputPath, Boolean isMedia, String[] pathParts, SyncTarget target, SyncOptions options, IProgress`1 progress, CancellationToken cancellationToken)	   at Emby.Server.Sync.MediaSync.GetItem(IServerSyncProvider provider, SyncTarget target, SyncJobItem jobItem, IProgress`1 progress, CancellationToken cancellationToken)	Source: Emby.Server.Implementations	TargetSite: Void CheckStatus(SharpCifs.Smb.ServerMessageBlock, SharpCifs.Smb.ServerMessageBlock)	2019-07-30 19:42:28.597 Error App: Error transferring sync job file	*** Error Report ***	Version: 4.2.0.40	Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3	Operating system: Unix 4.19.56.0	64-Bit OS: True	64-Bit Process: True	User Interactive: True	Runtime: file:///system/System.Private.CoreLib.dll	Processor count: 4	Program data path: /config	Application directory: /system	SharpCifs.Smb.SmbAuthException: SharpCifs.Smb.SmbAuthException: Access is denied.	   at SharpCifs.Smb.SmbTransport.CheckStatus(ServerMessageBlock req, ServerMessageBlock resp)	   at SharpCifs.Smb.SmbTransport.Send(ServerMessageBlock request, ServerMessageBlock response)	   at SharpCifs.Smb.SmbSession.Send(ServerMessageBlock request, ServerMessageBlock response)	   at SharpCifs.Smb.SmbTree.TreeConnect(ServerMessageBlock andx, ServerMessageBlock andxResponse)	   at SharpCifs.Smb.SmbFile.DoConnect()	   at SharpCifs.Smb.SmbFile.Connect()	   at SharpCifs.Smb.SmbFile.Connect0()	   at SharpCifs.Smb.SmbFile.QueryPath(String path, Int32 infoLevel)	   at SharpCifs.Smb.SmbFile.Exists()	   at Emby.Server.Implementations.IO.SharpCifsFileSystem.AssertFileExists(SmbFile file, String path)	   at Emby.Server.Implementations.IO.SharpCifsFileSystem.OpenRead(String path)	   at Emby.Server.Sync.MediaSync.SendFile(SyncJob job, String originalMediaPath, IServerSyncProvider provider, String inputPath, Boolean isMedia, String[] pathParts, SyncTarget target, SyncOptions options, IProgress`1 progress, CancellationToken cancellationToken)	   at Emby.Server.Sync.MediaSync.GetItem(IServerSyncProvider provider, SyncTarget target, SyncJobItem jobItem, IProgress`1 progress, CancellationToken cancellationToken)	Source: Emby.Server.Implementations	TargetSite: Void CheckStatus(SharpCifs.Smb.ServerMessageBlock, SharpCifs.Smb.ServerMessageBlock)	2019-07-30 19:42:28.731 Info TaskManager: Cloud & Folder Sync Completed after 0 minute(s) and 0 seconds

 

 

Thanks for your time!

Link to comment
Share on other sites

Hi, did you look at the error? This looks like a permissions error in your file system:

SharpCifs.Smb.SmbAuthException: SharpCifs.Smb.SmbAuthException: Access is denied.
Link to comment
Share on other sites

WonkoTheSane

Hi Luke,

 

yes, I saw that. I didn't know what to make of it, though. This looks like something related to samba, I don't really

see how accessing a network share would come into play here. I'm running an emby-docker on an unraid server. My

TV shows and movies are located on the same server and mounted into the container. I can stream stuff

using emby without a problem, so accessing the mounted media folders works. Can I provide additional

info to sort this out?

Link to comment
Share on other sites

Perhaps at certain times of day it becomes unavailable?

 

Anyway I think you will get a better experience if you instead mount the network share to a local path in the OS and then add that local path into emby, instead of smb directly.

Link to comment
Share on other sites

WonkoTheSane

Luke, I think I may not have made that clear, but that is exactly what I'm doing.

I even removed the (Optional) Shared network folder entry from the library that

I'm using so Kodi can directly access my media even though that never caused

any issues before. I don't see why samba comes into the picture here.

 

To reiterate: In the docker config I'm making my media folders, which are located

on the unraid host, available to the emby docker.

Edited by WonkoTheSane
Link to comment
Share on other sites

But somewhere you still have an smb path or unc path configured into Emby because that's the only reason it would be trying to use it's built-in smb protocol support. That could either be a library path setting or perhaps a temp folder path setting.

Link to comment
Share on other sites

WonkoTheSane

I'm at a loss here. I'm trying to sync a movie. This is the only folder have configured for my movie library:

 

"/media/movies"

 

No SMB path here.

 

In the logs I see the following with debug logging enabled:

 

 

Sending \\LOCHNAS\movies\hd\SciFi\whatever.mkv to Google Drive. Remote path: Videos/whatever/whatever.mkv

 

Where could the SMB path come from if not from the library configuration?

Link to comment
Share on other sites

I'm guessing you added this folder into your emby library?

\\LOCHNAS\movies\hd

The server no longer has access to this folder and that is the reason for the error in  your log. If you can resolve this then your problem should go away.

 

However, you will also get a better experience by mounting this unc path to a local path in your OS, and then adding that local path to Emby, instead of the unc path directly.

Link to comment
Share on other sites

WonkoTheSane

Thanks for your patience.

 

The only point where this path came into play with my library configuration was

as the optional shared network folder. According to the explanation provided

with this setting:

 

 

If this folder is shared on your network, supplying the network share path can allow Emby apps on other devices to access media files directly.

 

Why would the server use this path? It has direct access via the Folder /media/movies in my case.

Link to comment
Share on other sites

Yes you're right. The server is using that when it should not be. We'll be releasing 4.2.1 in the coming days and it will have this fix included. Thanks.

Link to comment
Share on other sites

  • Solution
WonkoTheSane

Just reporting back: Sync is working for me again. Thanks for the quick fix.

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...