Open carolyncole opened 8 years ago
@cam156 the fetch error is for a user whose email doesn't resolve when going to SHARE.
It looks like LDAP may be getting cranky being hit too much, becuase if I run these jobs individually they run.
Weird. Why would they fail on the same record? Can you get the job to run with https://scholarsphere.psu.edu/files/8623j753j ? But, now that I check, it was successfully sent to Share... so who knows.
on 2016/01/29 there were about 600 errors There were around 20 on the other days.
Not sure what all the errors are about but it seems bad that there were so many. Does anyone else remember?
Worker ssjobs1prod:14923 on id_based at 2016/01/29 09:32:15 -0500 Retry or Remove Class Sufia::Resque::MarshaledJob Arguments --- 'BAhvOhNTaGFyZU5vdGlmeUpvYgY6CEBpZEkiDngzNDZkbjU0cAY6BkVU
' Exception Timeout::Error Error execution expired
ssjobs1prod:32718 on id_based at 2016/02/14 07:27:04 -0500 Retry or Remove Class Sufia::Resque::MarshaledJob Arguments --- 'BAhvOhNTaGFyZU5vdGlmeUpvYgY6CEBpZEkiDjg2MjNqNzUzagY6BkVU
' Exception NoMethodError Error undefined method `fetch' for #Net::LDAP::Entry:0x007fb479906e58
ssjobs1prod:8990 on id_based at 2016/04/04 07:26:14 -0400 Retry or Remove Class Sufia::Resque::MarshaledJob Arguments --- 'BAhvOhNTaGFyZU5vdGlmeUpvYgY6CEBpZEkiDjg2MjNqNzUzagY6BkVU
' Exception NoMethodError Error undefined method `fetch' for #Net::LDAP::Entry:0x007f66f0f49300