4 ms·
Anyone else only get: <html><head><title>Processing Failed</title></head><body><b>Processing Failed</b></body></html>
by skrowl 13y ago
Anyone else only get:
<html><head><title>Processing Failed</title></head><body><b>Processing Failed</b></body></html>
- deleted 13y ago[deleted]
- lvh 13y agoYep. Too many open file descriptors. I'm trying to figure out how to fix that without taking the site down now. EDIT: It should be hopefully slightly better right now...
- Mithrandir 13y agoWebsite: https://archive.is/fG4Fb https://archive.is/fG4Fb Book: https://9d0df72831e4b345bb93-4b37fd03e6af34f2323bb971f72f0c0d.ssl.cf5.rackcdn.com/Crypto101March2014.pdf https://9d0df72831e4b345bb93-4b37fd03e6af34f2323bb971f72f0c0...
- deleted 13y ago[deleted]
- kmtrowbr 13y agoThe "processing failed" banner is quite ironic considering our recent collective experiences with cryptography. Why the Mt.Gox failure and so many other hackings and exposures of supposedly-private data? "Processing Failed"
- marshray 13y agoI don't read "Processing Failed" as an indication of hacking or a data breach. Sounds to me more like an overloaded website falling back to a small static error page.
- lvh 13y agoYep, that's exactly what happened. Combination of: 1) me not understanding docker and forgetting to increase the host nofiles; 2) me not understanding upstart (because I don't normally use ubuntu...) and not realizing that it conveniently ignores /etc/security/limits.conf :) It's obviously not a data breach: I don't actually store anyone's data :)