Weird error showing up (socket.error: (65, 'No route to host'))

Periodic scanner was hung up for about 4 hours there by a strange socket error "no route to host". Not sure if Tim changed something in the routing tables, or if a router somewhere blew up. Going to have to alter the code to gracefully handle the condition. No big deal, just generalise which errors it considers indications of "offline" status somewhat.


Comments are closed.


Pingbacks are closed.