Ruby error uploading to Photoshelter

[owen-b]

Hiya,

Got a frequent error when uploading to Photoshelter. Didn't used to happen, but has been happening a lot recently, screenshot attached, seems to be a Ruby/openssl/syswrite/broken pipe thing. Or something.

Running PM 5.0 for Mac, build 13764 (7b2b451) on 10.8.2 on a late 2012 iMac.

Cheers,
Owen

[attachment deleted by admin]

[Kirk Baker]

Owen,

Got a frequent error when uploading to Photoshelter. Didn't used to happen, but has been happening a lot recently, screenshot attached, seems to be a Ruby/openssl/syswrite/broken pipe thing. Or something.

Running PM 5.0 for Mac, build 13764 (7b2b451) on 10.8.2 on a late 2012 iMac.

Sounds like your connection to PhotoShelter (or the internet in general) is not very reliable, or PhotoShelter is having an issue on their end.

-Kirk

[owen-b]

Okay, that's possible, I noticed I was having issues in Lightroom with a plugin I was trying the other day. I didn't like the plugin, PM is more user friendly especially when uploads fail.

Okay, I'll email them. It shouldn't be my connection to the internet, unless something freaky is happening in the router that frazzles uploads somehow, but it's a solid 30 down and 2 up cable line normally.

I know it looks like it's outside your responsibility but from a more knowledgeable-about-Ruby man to a lesser one, are there any other things I might look for in system reports or the Console that could identify if it's my end or theirs?

EDIT: Just noticed I happen to have a Backblaze backup running as well - actually that's something that can happen any time, and right now it's uploading the JPGs I just created in LR which I'm using PM to send to PS... So that's a lot of uploading. Perhaps that was screwing with the PS connection. I've turned it off for an hour to see what happens...

[Kirk Baker]

Okay, that's possible, I noticed I was having issues in Lightroom with a plugin I was trying the other day. I didn't like the plugin, PM is more user friendly especially when uploads fail.

Okay, I'll email them. It shouldn't be my connection to the internet, unless something freaky is happening in the router that frazzles uploads somehow, but it's a solid 30 down and 2 up cable line normally.

I know it looks like it's outside your 'responsibility' but from a more knowledgeable-about-Ruby man to a lesser one, are there any other things I might look for in system reports or the Console that could identify if it's my end or theirs?

Sure.  Open up the Console application (Applications/Utilities) and view the console.log and system.log for clues.  Photo Mechanic has it's own log file (PM.log) which is stored in the same place as Photo Mechanic's Disk Cache (you can view the path in the Caching section of the Photo Mechanic Preferences dialog, under Disk Cache).

There could be more information in each of these three places.  Feel free to post excerpts here and I'll look them over.

-Kirk

[owen-b]

Okay, here's a little snippet from the tail end of the PM.log:

(eval):569:in `eval'
    (eval):3919:in `value'
    (eval):3919:in `sandbox_with_user_abort'
    (eval):3877:in `image_upload'
    (eval):579:in `create_sandbox_binding'
    (eval):579:in `create_sandbox_binding'
    (eval):541:in `run'
    (eval):628:in `dispatch_new_contexts'
    (eval):628:in `dispatch_new_contexts'
    (eval):618:in `run'
    (eval):2508
[Thu Feb-28-2013 16:45:36.956][b0a8b000] ruby-bridge: exception: #<Errno::EPIPE: /Applications/Photo Mechanic 5/Photo Mechanic 5.app/Contents/ruby/lib/ruby/1.8/openssl/buffering.rb:178:in `syswrite': Broken pipe>
    (eval):569:in `eval'
    (eval):3919:in `value'
    (eval):3919:in `sandbox_with_user_abort'
    (eval):3877:in `image_upload'
    (eval):579:in `create_sandbox_binding'
    (eval):579:in `create_sandbox_binding'
    (eval):541:in `run'
    (eval):628:in `dispatch_new_contexts'
    (eval):628:in `dispatch_new_contexts'
    (eval):618:in `run'
    (eval):2508
[Thu Feb-28-2013 16:46:48.721][b0a8b000] ruby-bridge: exception: #<Errno::EPIPE: /Applications/Photo Mechanic 5/Photo Mechanic 5.app/Contents/ruby/lib/ruby/1.8/openssl/buffering.rb:178:in `syswrite': Broken pipe>

I'm not quite sure what's pertinent in system.log but there's a lot of this:


Feb 28 16:06:56 DarthVader.local sandboxd[5409] ([5408]): mdworker(5408) deny mach-lookup com.apple.ls.boxd
Feb 28 16:06:56 DarthVader kernel[0]: Sandbox: sandboxd(5409) deny mach-lookup com.apple.coresymbolicationd
Feb 28 16:08:56 DarthVader.local mdworker[5413]: Unable to talk to lsboxd
Feb 28 16:08:56 DarthVader.local sandboxd[5414] ([5413]): mdworker(5413) deny mach-lookup com.apple.ls.boxd
Feb 28 16:08:57 DarthVader kernel[0]: Sandbox: sandboxd(5414) deny mach-lookup com.apple.coresymbolicationd
Feb 28 16:10:57 DarthVader.local mdworker[5417]: Unable to talk to lsboxd
Feb 28 16:10:57 DarthVader kernel[0]: Sandbox: sandboxd(5418) deny mach-lookup com.apple.coresymbolicationd
Feb 28 16:10:57 DarthVader.local sandboxd[5418] ([5417]): mdworker(5417) deny mach-lookup com.apple.ls.boxd

(yeah my computer is called DarthVader...)

I don't appear to have a console.log.

[Kirk Baker]

I'm not quite sure what's pertinent in system.log but there's a lot of this:


Feb 28 16:06:56 DarthVader.local sandboxd[5409] ([5408]): mdworker(5408) deny mach-lookup com.apple.ls.boxd
Feb 28 16:06:56 DarthVader kernel[0]: Sandbox: sandboxd(5409) deny mach-lookup com.apple.coresymbolicationd
Feb 28 16:08:56 DarthVader.local mdworker[5413]: Unable to talk to lsboxd
Feb 28 16:08:56 DarthVader.local sandboxd[5414] ([5413]): mdworker(5413) deny mach-lookup com.apple.ls.boxd
Feb 28 16:08:57 DarthVader kernel[0]: Sandbox: sandboxd(5414) deny mach-lookup com.apple.coresymbolicationd
Feb 28 16:10:57 DarthVader.local mdworker[5417]: Unable to talk to lsboxd
Feb 28 16:10:57 DarthVader kernel[0]: Sandbox: sandboxd(5418) deny mach-lookup com.apple.coresymbolicationd
Feb 28 16:10:57 DarthVader.local sandboxd[5418] ([5417]): mdworker(5417) deny mach-lookup com.apple.ls.boxd

mdworker is a daemon for Spotlight.  Does Spotlight work well on your system?

The PM.log output is expected given the errors the Upload progress dialog was showing you.

-Kirk

[owen-b]

Yeah thought so. I think it's just because I was uploading to Backblaze actually - the same JPGs that I was also uploading to PS. Backblaze just starts whenever it notices new stuff, have paused it for now and restarted uploading and LO! No errors.

Spotlight, well, I never use it myself so I have no idea. I use Alfred, which employs the Spotlight database. Is that something that should definitely not be happening or just one of those myriad things that system logs throw out all the time that I shouldn't lose sleep over?

[Kirk Baker]

Yeah thought so. I think it's just because I was uploading to Backblaze actually - the same JPGs that I was also uploading to PS. Backblaze just starts whenever it notices new stuff, have paused it for now and restarted uploading and LO! No errors.

Spotlight, well, I never use it myself so I have no idea. I use Alfred, which employs the Spotlight database. Is that something that should definitely not be happening or just one of those myriad things that system logs throw out all the time that I shouldn't lose sleep over?

If it were me, I'd want it fixed.  Here is one possible solution:

http://www.princeton.edu/~jcjb/docs/osx_error_fix/

HTH,

-Kirk