March 3:
See this post:
December 16:
More logs, this time in 1.3.3.3148.
Same issue as before with nothing uploading.
Soon after it finishes the conversion process, it will attempt to upload, but only getting as far as 1% before stopping. Multiple instances of it failing can be seen within the log files.
Dec 16, 2016 03:02:49.503 [10508] DEBUG - CloudSync: Uploading D:\Users\Sean\AppData\Local\Plex Media Server\Cache\Transcode\Sync+\9428839\10\467493.mp4 to https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication
Dec 16, 2016 03:02:49.503 [10508] DEBUG - HTTP requesting POST https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication
Dec 16, 2016 03:02:49.696 [10508] DEBUG - HTTP 400 response from POST https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication
Dec 16, 2016 03:02:49.696 [10508] DEBUG - CloudSync: Finished uploading D:\Users\Sean\AppData\Local\Plex Media Server\Cache\Transcode\Sync+\9428839\10\467493.mp4 to https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication with status 400
Dec 16, 2016 03:02:49.696 [10508] DEBUG - CloudSync: Upload failure response body: {“message”:“Multipart request is incomplete: Content required.”}
Dec 16, 2016 03:02:49.696 [10508] DEBUG - CloudSync: Retrying after failed upload. Retry count is now 2
Even though it does say “Finished uploading”, looking at the drive itself shows there is nothing new actually added from that session.
December 15:
After about a week of uploading things normally with minimal issues in 1.1.4, I decided to update to 1.3.2.3112…
The latest version of PMS still does not allow any content to upload to Amazon.
Again: This was after a week of uploading while in the build that was PRE-“STREAMING BRAIN”.
The only issues that I have had uploading was one of an older issue wherein a file that takes too long to upload will not sync (in my case, files that are above 6.5GB after conversion). Not sure if that was fixed in builds post-1.1.4, but cannot check for obvious reasons.
I was able to upload / sync over 30 files with no issue and without “bad duplicates” (ones that are missing thumbnails and not associated with any synced content) on the Amazon Drive itself while in 1.1.4.
There are of course the files that did not sync, but were uploaded that were greater than 6.5GB. That bug has been described in detail within the above link.
Logs can be found in this post:
November 10:
Build 1.2.7.2987 will not allow any content to upload.
Last build to at least sync some content was 1.1.4.2757 which can be found here:
https://downloads.plex.tv/plex-media-server/1.1.4.2757-24ffd60/Plex-Media-Server-1.1.4.2757-24ffd60-en-US.exe
For steps on how to downgrade PMS, please see this post:
Logs from the latest build (1.2.7.2987) can be found within this post:
The issue of only a small fraction of content being synced still occurs within any previous build.
Additionally, Roku 3s are unable to play any content synced to the cloud.
Locally streamed content plays fine.
This also is regardless of PMS build, and appears tied to a Roku update.
September 30:
For a couple days now, it seems that most of what I try to upload to my Amazon Drive appears to be constantly failing for some reason. I haven’t changed anything on my end and the files that are failing is very inconsistent.
I don’t mean this is giving a “Failure to Upload” message, I just mean that I’ll watch a file hit 100% only for it to repeat the same file. Then that will finally have it moving on to the next one, but with the previous file still saying “Waiting to be Uploaded”.
I’m seeing a lot of the following within the logs:
Sep 30, 2016 04:57:06.378 [10840] DEBUG - HTTP 429 response from POST https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication
Sep 30, 2016 04:57:06.378 [10840] DEBUG - CloudSync: Finished uploading D:\Users\Sean\AppData\Local\Plex Media Server\Cache\Transcode\Sync+\9428839\fe\347335.mp4 to https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication with status 429
Sep 30, 2016 04:57:06.378 [10840] DEBUG - CloudSync: Upload failure response body: {“logref”:“ddd26ae4-86eb-11e6-be4a-1b5304a9d318”,“message”:“Rate exceeded”,“code”:""}
Sep 30, 2016 04:57:06.378 [10840] DEBUG - CloudSync: Retrying after failed upload. Retry count is now 3
Sep 30, 2016 04:57:06.379 [10840] DEBUG - CloudSync: Uploading D:\Users\Sean\AppData\Local\Plex Media Server\Cache\Transcode\Sync+\9428839\fe\347335.mp4 to https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication
Sep 30, 2016 04:57:06.379 [10840] DEBUG - HTTP requesting POST https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication
Sep 30, 2016 04:57:06.796 [10840] DEBUG - HTTP 409 response from POST https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication
Sep 30, 2016 04:57:06.797 [10840] DEBUG - CloudSync: Finished uploading D:\Users\Sean\AppData\Local\Plex Media Server\Cache\Transcode\Sync+\9428839\fe\347335.mp4 to https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication with status 409
Sep 30, 2016 04:57:06.797 [10840] DEBUG - CloudSync: Upload failure response body: {“logref”:“de3d61ee-86eb-11e6-ac4e-fdf1ac1bef97”,“message”:“Node with the name rl2godef5isexbx60fx1pejwnra\u003d.mp4 already exists under parentId b7TLV015SACNRn-nO7zFPQ conflicting NodeId: IC_JBLCWQvKZHKj1qmphSA”,“code”:“NAME_ALREADY_EXISTS”,“info”:{“nodeId”:“IC_JBLCWQvKZHKj1qmphSA”}}
Sep 30, 2016 04:57:06.797 [10840] DEBUG - CloudSync: Retrying after failed upload. Retry count is now 2
Each of the files are under 500MB after conversion, so not sure what’s going on here. I’ve even checked the drive itself just to make sure it isn’t still uploading like I’ve seen in the past, and it definitely is not. My settings are still the same from when it worked perfectly.
I am on the current latest version of 1.1.4.2757-24ffd60.
