joblog_scraper losing its reporter threads...
THe joblog scraper had its reporting threads crashing and stopped actually reporting things, rather just queueing them up for threads that weren't there anymore..
Added some debug in prodution, found an httpd.BadHeaderLine exception I had been
previously unaware of.
Reworking in development so we aren't so dependent on knowing what exceptions we get
#1 Updated by Marc Mengel over 3 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
- First Occurred set to b0_5
Discovered an httplib.BadStatusLine exception that was getting thrown which we
weren't catching... We've been running for 3 days now in production without losing
any reporter threads.