Public bug reported: Binary package hint: nagstamon
If nagstamon's connection to the nagios server is dropped, it's possible that nagstamon will not notice and get stuck. On the occasions I've noticed this, 'strace'ing the nagstamon process reveals that the threads responsible for talking to the nagios servers are sitting waiting for a "read" call to return on their sockets connected to nagios. According to http://www.voidspace.org.uk/python/articles/urllib2.shtml #sockets-and-layers, there is no default socket timeout set in urllib2. I have applied the workaround in that article to my copy of nagstamon, and it's running OK so far (not had much testing yet though). My patch is attached. It might want some more thought though (I'm no Python programmer). I've just hardcoded a 30s timeout, this may want to become a setting in the preferences dialog. ** Affects: nagstamon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/732544 Title: dropped connections do not time out -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
