I did check the he JPG with timestamp 2013-12-07 15:34:21 and it is a single image.
I turned off Settings / Server / Library / Update my Library Automatically, deleted the images remaining in the upload folder, and retried enabling Camera Upload on the client. To my amazement, the process restarted immediately, and continued through all 435 images and .MOV videos without any errors. During this time, I watched the temp upload folder, and the only filename in the folder was the currently-downloading image name with .inProgress appended. The file was immediately moved before the next file upload began, and there was never more than one file in the folder at a time.
It appears that the issue lies with Automatic Library Updates conflicting with the upload and database.
I noted one more issue: Although disabling Update My Library Automatically, and then deleting any images that remained in the temp folder, allowed the Camera Upload feature to resume and complete, if the upload process was interrupted (due to loss of wireless signal, etc.) the following behavior was noted:
The image file in the temporary upload folder with the .inProgress extension would remain
After some amount of time (between 15 and 30 minutes) the image file would be renamed, removing the .inProgress extension
The Camera Upload would not resume while that file remained in the temporary upload folder
Deleting the file from the temporary upload folder allowed the Camera Upload to resume again
I too am seeing the same behavior. The camera upload was working initially and 300+ photos and videos (out of about 1400) were uploaded, but now the iPhone is stuck waiting to upload with around a 1000 still left to go. Iām not seeing the files in the upload folder like Daship is seeing so it may not be the same issue. I have attached the server and client logs, would appreciate any help on getting this working.
I did verify that āUpdate My Library Automaticallyā is disabled. Restarting the Server didnāt solve the issue. On the client, I have tried turning off camera upload and turning it back on, though I didnāt actually reset it. Iād like to avoid resetting it completely since it has been very slow to upload the initial 300 photos, so Iād prefer to not restart from zero if there is any other option.
@andycarver said:
I am having a similar/same issue on OS X. Where can I find the temporary upload folder to try and clear it?
I suggest you get diagnostic logs first to establish if the issue is really similar to what was seen before.
Screenshots and logging from both sides : server and iOS app and trying the upload after restarting the server having ensured debug logging is enabled. For this test please also enable verbose logging on the server.
@andycarver said:
I am having a similar/same issue on OS X. Where can I find the temporary upload folder to try and clear it?
I suggest you get diagnostic logs first to establish if the issue is really similar to what was seen before.
Screenshots and logging from both sides : server and iOS app and trying the upload after restarting the server having ensured debug logging is enabled. For this test please also enable verbose logging on the server.
Iām having the same waiting to upload issues. I canāt seem to figure which of these solutions I need to try. Can you help please? Hereās the debug from my phone. Thanks
@mike8itall said:
Iām having the same waiting to upload issues. I canāt seem to figure which of these solutions I need to try. Can you help please? Hereās the debug from my phone. Thanks
with sync and camera upload issues it is necessary to get logs from both ends: the mobile app and the server
For camera upload issues, please ensure both debug and verbose logging are enabled on the server
Save changes and restart the server
Then reproduce the problem, get screenshot from the app and collect logs from both the app and the server and upload here
So, I got it to work. Not the way I wanted to do it, but it did work.
Apparently plex needs execute permissions, just to write files?
As soon as I gave it execute permissions, everything worked.
Is there no way to convince plex it is allowed to write, with āwriteā permissions?
I am kind of uncomfortable leaving the folder in a state which can be used to attack my server.
@mike8itall said:
So, I got it to work. Not the way I wanted to do it, but it did work.
Apparently plex needs execute permissions, just to write files?
As soon as I gave it execute permissions, everything worked.
Is there no way to convince plex it is allowed to write, with āwriteā permissions?
I am kind of uncomfortable leaving the folder in a state which can be used to attack my server.
Finally figured this out on my windows server. Apparently a file gets hung some times causing the issue. If you go to C:\Users\nameOfProfile\AppData\Local\Temp\Plex\Upload there will be a directory. Inside of that directory you should see a jpg, video etc from your upload device. Delete it/them and the upload should resume. Hope this helps someone.
I have exactly the same problem.
Using latest server and iOS app versions.
Have tried various combinations of stopping/restarting server.
Checked permissions and disk space.
Changed from Upload automatically to manual/Upload-now.
Shows 400 uploaded and 3500 remaining.
No errors listed in the console however from time to time, there is a SLOW QUERY message, but this is intermittent.
I still intermittently experience this problem. Iāve found that if I just do nothing it clears up on its own. Its probably happened three or four times and resolves/catches up within one to two weeks. Hardly ideal but Iāve stopped caring. @Plex doesnāt fix ā ā ā ā . They just pump out new features.
I have plex installed on Synology(software only) a virtual machie (VmWare) in a normal PC.
I started uploading photos taken with my iPhone 6s.
The uploading hangs at the same photo (I think) and I donāt know how to debugg.
Iāve read your suggestions but the path to files is different in Synology than your examples (in Windows).
I tried also to reset the upload but no scuccess.
Can you please have a look at the logs and give me a hint how to fix this.