756444 - Socket exception in pulsebuildmonitor

Status: RESOLVED FIXED

(Webtools :: Pulse, defect)

Description

[Mark Côté [:mcote]]

I got this exception in my pulsebuildmonitor client, after which it appears to have stopped telling me about new builds:

  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/threading.py", line 477, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/Users/mozauto/pulsebuildmonitor/pulsebuildmonitor/pulsebuildmonitor.py", line 90, in listen
    self.pulse.listen()
  File "/Library/Python/2.6/site-packages/mozillapulse/consumers.py", line 136, in listen
    self.consumer.wait()
  File "/Library/Python/2.6/site-packages/carrot/messaging.py", line 446, in wait   
    it.next()
  File "/Library/Python/2.6/site-packages/carrot/backends/pyamqplib.py", line 300, in consume
    self.channel.wait()
  File "/Library/Python/2.6/site-packages/amqplib/client_0_8/abstract_channel.py", line 95, in wait
    self.channel_id, allowed_methods)
  File "/Library/Python/2.6/site-packages/amqplib/client_0_8/connection.py", line 231, in _wait_method
    self.wait()
  File "/Library/Python/2.6/site-packages/amqplib/client_0_8/abstract_channel.py", line 97, in wait
    return self.dispatch_method(method_sig, args, content)
  File "/Library/Python/2.6/site-packages/amqplib/client_0_8/abstract_channel.py", line 115, in dispatch_method
    return amqp_method(self, args)
  File "/Library/Python/2.6/site-packages/amqplib/client_0_8/connection.py", line 378, in _close
    self._x_close_ok()
  File "/Library/Python/2.6/site-packages/amqplib/client_0_8/connection.py", line 398, in _x_close_ok
    self._do_close()
  File "/Library/Python/2.6/site-packages/amqplib/client_0_8/connection.py", line 160, in _do_close
    self.transport.close()
  File "/Library/Python/2.6/site-packages/amqplib/client_0_8/transport.py", line 139, in close
    self.sock.shutdown(socket.SHUT_RDWR)
  File "<string>", line 1, in shutdown
error: [Errno 57] Socket is not connected

Comment 1

[Mark Côté [:mcote]]

Actually I take that back; I think it is still doing new builds... must have just been a while since the last one.

Comment 2

[Jonathan Griffin (:jgriffin)]

If this happened yesterday, it was likely the result of transitioning to the new pulse server.  If it happens again, I'll investigate.

Comment 3

[Mark Côté [:mcote]]

It did indeed happen yesterday. I'll let you know if I see it again.

Comment 4

[Mark Côté [:mcote]]

I can't recall having seen this in a long time.