-
Notifications
You must be signed in to change notification settings - Fork 38
run Gratipay 194 #508
Comments
Having an issue pulling down from GitHub atm, debugging |
@rohitpaulk is this expected? |
Backup completed and verified. |
payday.sh is still running but the log file hasn't updated in awhile...? |
Yeah, payday.sh is hung. cc @whit537 @rohitpaulk Current status is capturing cards |
Here's the partial log file https://github.com/gratipay/logs/blob/master/payday/gratipay-194.log-partial |
Maybe @rohitpaulk is incommunicado? @clone1018 Sec, digging up previous payday ticket ... |
It had to do with a network error leading to a wedged process in Postgres ... |
I think it was the first week that @rohitpaulk ran payday last month ... |
Here it is, @clone1018: #477 (comment). Any update on our situation? How can I help? |
This could be a red herring, but I did make a seemingly minor configuration change at Mandrill: I verified our domain. I mention it because it looks from the log like we made it through card captures, but stopped short of sending notifications (I didn't receive one, e.g.). |
The log ends with a capture. Did we make it through all captures? |
@whit537 we did 59 captures last week and 69 so far in the partial log |
I'm not sure how to check how many captures we should have done |
Well, it's okay to rerun because the captures shouldn't be recaptured. I was asking more to say—where did we actually die? And why? |
I have no idea, straced the process at the end and it was just hung. I'll return and monitor with strace to see what it's hanging on |
|
Did get a
|
Interesting! |
I see $1152 posted on Braintree, that seem about average? |
@clone1018 Yeah, seems likely that captures worked. Did we hang up in a Postgres call? Did you follow the #477 (comment) thread at all? |
It could have been related to the network, I do Payday on my laptop on an aircard but it seemly worked fine the past two times and I don't see any obvious errors? |
I can do the droplet thing in the future if this doesn't work |
#508 (comment) indicates that exchange 80448 is what we died in the middle of. |
@whit537 there's an SSL error in 80448's exchange_routes |
There we go. Sounds like a network connectivity issue in an API call to Braintree. The little-used |
So I guess we need to make sure a) that everyone after 80448 worked properly, and b) that whoever 80448 was for had a second charge in the re-run. Sound right? |
In the re-run. |
I moved the error into the
|
Looks like we have 6's |
We want to run #!/usr/bin/env python2
from __future__ import absolute_import, division, print_function, unicode_literals
import sys
from gratipay import wireup
from gratipay.models.exchange_route import ExchangeRoute
wireup.db(wireup.env())
for route_id in sys.argv[1:]:
ExchangeRoute.from_id(route_id).update_error('') |
|
This look right, @clone1018?
Here's Here's from __future__ import absolute_import, division, print_function, unicode_literals
import sys
from gratipay import wireup
from gratipay.models.exchange_route import ExchangeRoute
wireup.db(wireup.env())
for route_id in sys.argv[1:]:
ExchangeRoute.from_id(route_id).update_error('')
print("cleared", route_id) |
Local test looks okay:
|
Here goes ... |
Looks good to me |
!m @clone1018 gratipay::MAROON=> select id, error from exchange_routes where id in (9051, 9136);
┌──────┬─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ id │ error
├──────┼─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ 9051 │ ReadTimeout(ReadTimeoutError("HTTPSConnectionPool(host='api.braintreegateway.com', port=443): Read timed out. (read timeout=
│ 9136 │ SSLError(SSLError(SSLEOFError(8, u'EOF occurred in violation of protocol (_ssl.c:590)'),),)
└──────┴─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
(2 rows)
gratipay::MAROON=> select id, error from exchange_routes where id in (9051, 9136);
┌──────┬───────┐
│ id │ error │
├──────┼───────┤
│ 9051 │ │
│ 9136 │ │
└──────┴───────┘
(2 rows) |
OMG for the first time in my payday experience, fee's and totals match up on the first try! |
I think you've earned it this week, @clone1018. :-) |
POSTed MassPay back to Gratipay for 51 users. |
Verified:
|
Decline rate = 13.92 EEP! |
1152 * 5 = 5760, paypal says we have 4,077.82, gonna add $2000? |
@clone1018 Sounds good. I'm winding down hear, gonna go find a bus. I will try to check in later tonight but I might not get to until tomorrow. Good work! :-) !m @clone1018 |
!m @whit537 thanks for the help with the explosion! |
Added $2000USD |
Interesting note about https://github.com/gratipay/logs/commit/956b9a96c68dc30aa89756c249dfd927c9de9a76#diff-094c93b75ab960c9d1f51dcb9ec35469R168 I didn't see that in my shell, maybe when I was running payday.sh stderr went nowhere? |
I think we're done, I've finished all the normal tasks, gonna leave open until @whit537 confirms his cleanup is done |
My cleanup is done. !m @clone1018 |
Done |
!m @whit537 @clone1018. I forgot about Payday 😑, I've set a recurring reminder, hopefully won't happen again :) |
No worries @rohitpaulk. As long as you don't forget and everything doesn't explode during #314! :) |
#500
The text was updated successfully, but these errors were encountered: