One more and I'll stop. This was from a fresh set of 200 to upload, and 199 went, one did not, and there was no overt error in the UI. In the log I got:
05/07/2015 18:06:23 DEBUG Wait for render
05/07/2015 18:06:23 DEBUG Render complete: s:\FergusonTemp\4E19CD4D-A2E7-47EF-967B-089EA5E31B94\FGCU v Stetson 01-04-2014 - 20140104_DSC_6892.jpg
05/07/2015 18:06:23 DEBUG SmugMugAPI.callMethod - start
05/07/2015 18:06:23 DEBUG Timestamp Offset: 0
05/07/2015 18:06:23 DEBUG Base: GET&https%3A%2F%2Fapi.smugmug.com%2Fapi%2Fv2%21authuser&_accept%3Dapplicatio...4423a85%26oauth_version%3D1.0
05/07/2015 18:06:23 DEBUG GET: https://api.smugmug.com/api/v2!authuser?_verbosity=1&_accept=application%205/07/2015 18:06:23 DEBUG HTTP Status: none
05/07/2015 18:06:23 DEBUG {"Code":1000,"Message":"A connection with the server could not be established\r\n","stat":"noresponse"}
05/07/2015 18:06:23 DEBUG SmugMugAPI.callMethod - end
I find it interesting how sometimes it gives a UI indication, sometimes it does not.
So far in some spot checks it does keep correct track of what is on Smugmug, i.e. I haven't found any, like my videos, where it shows failed but uploaded or vice versa.
I'll quit now, not sure if any of these are helpful.
It looks like some fluke network issues (I've also seen them on occasion), Both of those errors should have given an indication to you that there were errors. I'll look into the error reporting. Thanks for sending the log info!
Just installed plugin update 2.2.7 and did a run of 92 pics; no rainbow spinning wheel / delay and upload worked perfectly. Fast and no dropped images!
Just installed plugin update 2.2.7 and did a run of 92 pics; no rainbow spinning wheel / delay and upload worked perfectly. Fast and no dropped images!
It's doing it again today, with 2.2.7.0. I didn't have logging on for all of it, but I had dozens of shots that didn't upload, some also gave the null pointer error again.
I will say that it happened while uploading three separate galleries in three separate runs of Publish (I.e. in parallel not consecutively). And I realie 2.2.8 is current now (though not knowing what was in it was kind of waiting to see if I read anything good/bad)
I turned on the log and published again and everything worked. I'll experiment more when I get some time, but 2.2.7 still, at least this afternoon, had some hiccups, including all three situations separately: explicit "authorize" problem, silent failure to publish, and the null pointer issue.
Some of these errors are out of my control and relate to either transient network errors or backend erros from SmugMug's infrastructure. I've made a few minor changes that might help, but in many respects there are a lot of factors that are outside of my control...though I would give my right nut to upload a 2mb file in 1 second.
Some of these errors are out of my control and relate to either transient network errors or backend erros from SmugMug's infrastructure. I've made a few minor changes that might help, but in many respects there are a lot of factors that are outside of my control...though I would give my right nut to upload a 2mb file in 1 second.
Cheers,
David
David, I get that for network errors, but aren't the "unauthorized" ones more under SM's control?
I just ran about 50 images with no errors, then tried about 15 each in three galleries at the same time. Of these the third at first just said "cannot update collection" then I republished and it ran in parallel. The first two rejected 2 and 3 images as "unauthorized" in the UI, and the good news is that is how many did not publish (i.e. all got reported). The third finished fine.
Here's some of the long around one of the files (one with 2137 in the name), not sure if it tells you anything. This is 2.2.7.0 also.
If it's useful to pursue will pull down the latest and can send a full log.
Or do you think that authorization errors can also come from internet glitches?
I can also get a wireshark capture if it's useful, and prune to the relevant portions.
But.... is anyone else seeing the problem again? I had zero problems for several days.
I'm still seeing a similar issue - seems to work fine uploading one gallery at a time but as soon as I run 2+ galleries uploading together I get the 'unauthorized' errors and unfinished images 2.2.8 SM version
I photograph for a commercial food product group and one photoshoot might have items that overlap and are placed in several different galleries.
You probably already know this, but if you publish at a folder level above those galleries, it will do them each consecutively without your needing to publish each one (of course it publishes ALL the galleries contained inside).
You can also highlight all the galleries individually and do one publish which appears to do them consecutively, but I've found that simply does not work - it just skips some. I've never had trouble publishing from a higher level folder though.
You probably already know this, but if you publish at a folder level above those galleries, it will do them each consecutively without your needing to publish each one (of course it publishes ALL the galleries contained inside).
You can also highlight all the galleries individually and do one publish which appears to do them consecutively, but I've found that simply does not work - it just skips some. I've never had trouble publishing from a higher level folder though.
Ahh cool - I actually tried that several editions ago (maybe a year or couple of years ago) and couldn't get it to work and never tried again - doh!
You probably already know this, but if you publish at a folder level above those galleries, it will do them each consecutively without your needing to publish each one (of course it publishes ALL the galleries contained inside).
You can also highlight all the galleries individually and do one publish which appears to do them consecutively, but I've found that simply does not work - it just skips some. I've never had trouble publishing from a higher level folder though.
The only problem with publishing from a folder is that the galleries are queued to publish back to back as you mentioned, but if there is an error with one publish action, it reports that at the end of that gallery instead of at the end of all the galleries...so you end up with a potential blocking issue if left unattended.
I'm still seeing a similar issue - seems to work fine uploading one gallery at a time but as soon as I run 2+ galleries uploading together I get the 'unauthorized' errors and unfinished images 2.2.8 SM version
I somehow missed that this was publishing multiple galleries at the same time...i'll do some testing along those lines.
Uploads are now failing for me in LR 6.01 after updating to 2.2.9. Tried PMing log file to devbobo, but it says the text is too big. I've got 11 files, and it says: "Upload failed(10), gateway Timeout (1)"
Uploads are now failing for me in LR 6.01 after updating to 2.2.9. Tried PMing log file to devbobo, but it says the text is too big. I've got 11 files, and it says: "Upload failed(10), gateway Timeout (1)"
Uploads are now failing for me in LR 6.01 after updating to 2.2.9. Tried PMing log file to devbobo, but it says the text is too big. I've got 11 files, and it says: "Upload failed(10), gateway Timeout (1)"
Not all upload failures are a result of the plugin doing something wrong. I had a look at the upload logs for the past 24 hours. We had 4 successful uploads and 2 uploads that resulted in "Incomplete File" error. These errors typically result when you have some sort of network issue between your location and our servers.
[Edit] I've just confirmed that we had a partial outage with respect to uploading, which should be resolved.
Maybe a little off-topic, but not worth starting a new thread: I just started using LR6, (perpetual license version), and I'd like to use the SM plugin. I don't see a way of installing it without also installing CC, which I do not want on my machine. Am I missing something?
Maybe a little off-topic, but not worth starting a new thread: I just started using LR6, (perpetual license version), and I'd like to use the SM plugin. I don't see a way of installing it without also installing CC, which I do not want on my machine. Am I missing something?
Maybe a little off-topic, but not worth starting a new thread: I just started using LR6, (perpetual license version), and I'd like to use the SM plugin. I don't see a way of installing it without also installing CC, which I do not want on my machine. Am I missing something?
And the auto-update inside of LR (i.e. inside the plugin) will continue to keep it updated, so you can ignore CC there also (I have CC but prefer to use the plugin's own update as I trust David more than Adobe!).
And the auto-update inside of LR (i.e. inside the plugin) will continue to keep it updated, so you can ignore CC there also (I have CC but prefer to use the plugin's own update as I trust David more than Adobe!).
We can also push the auto-updates out a bit faster than Adobe can. Typically using the plugins' auto-update you'll get the update 1-2 days before those getting the updates from Adobe CC.
Comments
It looks like some fluke network issues (I've also seen them on occasion), Both of those errors should have given an indication to you that there were errors. I'll look into the error reporting. Thanks for sending the log info!
Former SmugMug Product Team
aaron AT aaronmphotography DOT com
Website: http://www.aaronmphotography.com
My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations
Nikon | Private Photojournalist
Good to hear
SmugMug API Developer
My Photos
I will say that it happened while uploading three separate galleries in three separate runs of Publish (I.e. in parallel not consecutively). And I realie 2.2.8 is current now (though not knowing what was in it was kind of waiting to see if I read anything good/bad)
I turned on the log and published again and everything worked. I'll experiment more when I get some time, but 2.2.7 still, at least this afternoon, had some hiccups, including all three situations separately: explicit "authorize" problem, silent failure to publish, and the null pointer issue.
Some of these errors are out of my control and relate to either transient network errors or backend erros from SmugMug's infrastructure. I've made a few minor changes that might help, but in many respects there are a lot of factors that are outside of my control...though I would give my right nut to upload a 2mb file in 1 second.
Cheers,
David
SmugMug API Developer
My Photos
David, I get that for network errors, but aren't the "unauthorized" ones more under SM's control?
I just ran about 50 images with no errors, then tried about 15 each in three galleries at the same time. Of these the third at first just said "cannot update collection" then I republished and it ran in parallel. The first two rejected 2 and 3 images as "unauthorized" in the UI, and the good news is that is how many did not publish (i.e. all got reported). The third finished fine.
Here's some of the long around one of the files (one with 2137 in the name), not sure if it tells you anything. This is 2.2.7.0 also.
If it's useful to pursue will pull down the latest and can send a full log.
Or do you think that authorization errors can also come from internet glitches?
I can also get a wireshark capture if it's useful, and prune to the relevant portions.
But.... is anyone else seeing the problem again? I had zero problems for several days.
Nikon | Private Photojournalist
I just won't do that, I guess, but I do think there must be some defect underneath the covers when run in parallel.
Yep, although uploading several galleries at once is usually a part of my daily routine.
I photograph for a commercial food product group and one photoshoot might have items that overlap and are placed in several different galleries.
Nikon | Private Photojournalist
You probably already know this, but if you publish at a folder level above those galleries, it will do them each consecutively without your needing to publish each one (of course it publishes ALL the galleries contained inside).
You can also highlight all the galleries individually and do one publish which appears to do them consecutively, but I've found that simply does not work - it just skips some. I've never had trouble publishing from a higher level folder though.
Ahh cool - I actually tried that several editions ago (maybe a year or couple of years ago) and couldn't get it to work and never tried again - doh!
I'll definitely do that in the future
Nikon | Private Photojournalist
The only problem with publishing from a folder is that the galleries are queued to publish back to back as you mentioned, but if there is an error with one publish action, it reports that at the end of that gallery instead of at the end of all the galleries...so you end up with a potential blocking issue if left unattended.
SmugMug API Developer
My Photos
I somehow missed that this was publishing multiple galleries at the same time...i'll do some testing along those lines.
SmugMug API Developer
My Photos
SmugMug API Developer
My Photos
please email to david at sm
thanks
SmugMug API Developer
My Photos
Not all upload failures are a result of the plugin doing something wrong. I had a look at the upload logs for the past 24 hours. We had 4 successful uploads and 2 uploads that resulted in "Incomplete File" error. These errors typically result when you have some sort of network issue between your location and our servers.
[Edit] I've just confirmed that we had a partial outage with respect to uploading, which should be resolved.
SmugMug API Developer
My Photos
You can follow the instructions for "Install Manually" located on our help page here: http://help.smugmug.com/customer/portal/articles/121321
Former SmugMug Product Team
aaron AT aaronmphotography DOT com
Website: http://www.aaronmphotography.com
My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations
And the auto-update inside of LR (i.e. inside the plugin) will continue to keep it updated, so you can ignore CC there also (I have CC but prefer to use the plugin's own update as I trust David more than Adobe!).
We can also push the auto-updates out a bit faster than Adobe can. Typically using the plugins' auto-update you'll get the update 1-2 days before those getting the updates from Adobe CC.
Former SmugMug Product Team
aaron AT aaronmphotography DOT com
Website: http://www.aaronmphotography.com
My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations