Oct 12, 2016 14:22:05.129 [0x7fc98d3ff700] DEBUG - CloudSync: Finished uploading /apps/plexmediaserver/MediaLibrary/Plex Media Server/Cache/Transcode/Sync+/11961923/65/8393.mp4 to https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication with status 429 Oct 12, 2016 14:22:05.129 [0x7fc98d3ff700] DEBUG - CloudSync: Upload failure response body: {“logref”:“6e2db5df-9033-11e6-a03d-3dba4cddc570”,“message”:“Rate exceeded”,“code”:""}
Oct 12, 2016 14:22:05.129 [0x7fc98d3ff700] DEBUG - CloudSync: Retrying after failed upload. Retry count is now 3
Oct 12, 2016 14:22:05.129 [0x7fc98d3ff700] DEBUG - CloudSync: Uploading /apps/plexmediaserver/MediaLibrary/Plex Media Server/Cache/Transcode/Sync+/11961923/65/8393.mp4 to https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication
seems to get itself into a retry loop, been running for a few days before I started to look further into it
anyone else experiencing this issue? or shed any light on how I could find out what limit I am hitting?
‘429’ is the same error being seen in the Plex Cloud beta and is part of the Amazon-side problem trying to get resolved.
I’ve asked other Ninjas and until Amazon fixes their side, we can only let PMS do its thing and retry, unfortunately at longer intervals between each upload attempt failure, until it does.
I wish there was more to share but that’s all we know at this point until Amazon tells us.
Unfortunately no. We’re completely at Amazon’s mercy at this point. It would take some serious knowledge of how Plex works to reach in, grab the files and push them up exactly how they have to be at Amazon and then trick the database into thinking PMS did the upload. Very Non-trivial.
Sounds like they can’t deal with the increased traffic, might have to flick back to dropbox or google drive, did they sort the time out issue with google drive yet?
I looked at the release notes for my Synology NAS after updating Cloud Sync. They just came out with an update which includes handling the same problem so it’s clearly egg on Amazon’s face at this point.
have they acknowledged it in any form as yet? I’m afraid it might be one of these “just wait the ball is in there court” type issues and they never do anything…
While I’m not ‘Official Plex’, I can tell you that is a big problem. It shows up in the CloudPMS log files. Engineering is on it (and probably a fair amount of management too)
I hope you are right, I’ve seen a lot of water pass under the Plex bridge in my nearly 8 years of continued use and support, however this would be the single biggest impacting problem I’ve experienced and it does force me to think about alternative solutions where the outcome of such a system is more under my own control
DEBUG - CloudSync: Upload failure response body: {“logref”:“dd1974b1-9589-11e6-9fda-035d8d81a1a5”,“message”:“Token has expired”,“code”:""}
What I don’t get after trolling the logs again this morning, is that Plex sets up the the transfer, we tell Amazon how much data we are about to send it and the other particulars, check that we have quota and that everything is ok, proceed with the transfer and then at the end of the transfer we get told to piss off? It’s too late Amazon, we’ve already sent you the data, your chance to rate limit me was when I first asked you to setup the transfer not at the freaking end!??
No, I have not. I’ve not heard anything yet. I’ve also been swamped on another issue and not been able to go hunting answers. If I don’t get called in to do another “hat trick” tomorrow, I’ll have time to go ask more.
May I have the log file you found that in (whole file) ?
Thanks for your help on this @ChuckPa . I’ve seen the same error messages mentioned by @izy . On top of those two errors, I just saw a new one today after attempting another upload.
No. There is nothing that I know of. I do know there is an update to PMS in QA right now. I don’t know any details but based on what I hear… we should see it really quickly. I just wish ‘quickly’ had a number assigned to it… haha
@amccook said:
Thanks for your help on this @ChuckPa . I’ve seen the same error messages mentioned by @izy . On top of those two errors, I just saw a new one today after attempting another upload.
Sorry for being slow getting back to you on your logs.
I do see where you’re getting the ‘multipart incomplete’ error, responds with
“Oct 19, 2016 23:43:59.691 [8328] DEBUG - CloudSync: Retrying after failed upload. Retry count is now 1” then retries and actually does complete.
Can you help me find an instance where PMS thought it uploaded one thing but you didn’t get it or what you got was damaged? If so, and we can reproduce it… We’ll turn on Verbose logging and I’ll write it up.
The multipart upload failure is different… How different is something I need to go research more
updated to Version 1.2.3.2914 last night, no change still error 429 among others, just about time to write Plex Sync off I think for the foreseeable future
CloudSync: Upload failure response body: {“logref”:“6bf62715-9b7d-11e6-acb1-e16ec7918885”,“message”:“Node with the name e-bv4fwczreh0id1k5l9oxy1-xc\u003d.mp4 already exists under parentId tkQUO-jQQOy2LkpKFp1-Ow conflicting NodeId: x1LmE_8iSGiXKd6YPbdy2A”,“code”:“NAME_ALREADY_EXISTS”,“info”:{“nodeId”:“x1LmE_8iSGiXKd6YPbdy2A”}}
CloudSync: Upload failure response body: {“logref”:“bfb8c6fb-9b77-11e6-8d76-5b4d6a2267bc”,“message”:“Token has expired”,“code”:""}’
Oddly enough, I’m seeing the progress bar update when files are uploading, it will attempt a file a few times, and then sometimes (appears to be random) files will show up in Amazon Cloud Drive. But Plex doesn’t seem to ever make the link when I try and find that media in the web player.
I see you’re still running 1.1.3. Have you tried stepping up to PMS 1.1.4 or 1.2.3 (currently in Plex Pass) and verifying it’s not something already addressed ?
While you check that, I’ll go check a few things.
