Closed Bug 856717 Opened 13 years ago Closed 13 years ago

Pulsetranslator died with "connection timed out"

Categories

(Webtools :: Pulse, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jgriffin, Assigned: jgriffin)

Details

Attachments

(1 file)

Pulsetranslator died again, this time with this stack trace: Traceback (most recent call last): File "/home/webtools/apps/pulsetranslator/bin/runtranslator", line 8, in <module> load_entry_point('pulsetranslator==0.1', 'console_scripts', 'runtranslator')() File "/home/webtools/apps/pulsetranslator/src/pulsetranslator/pulsetranslator/runservice.py", line 35, in main service.start() File "/home/webtools/apps/pulsetranslator/src/pulsetranslator/pulsetranslator/pulsetranslator.py", line 54, in start self.pulse.listen() File "build/bdist.linux-i686/egg/mozillapulse/consumers.py", line 136, in listen File "/home/webtools/apps/pulsetranslator/lib/python2.6/site-packages/carrot-0.10.7-py2.6.egg/carrot/messaging.py", line 446, in wait it.next() File "/home/webtools/apps/pulsetranslator/lib/python2.6/site-packages/carrot-0.10.7-py2.6.egg/carrot/backends/pyamqplib.py", line 300, in consume self.channel.wait() File "build/bdist.linux-i686/egg/amqplib/client_0_8/abstract_channel.py", line 95, in wait File "build/bdist.linux-i686/egg/amqplib/client_0_8/connection.py", line 202, in _wait_method File "build/bdist.linux-i686/egg/amqplib/client_0_8/method_framing.py", line 221, in read_method socket.error: [Errno 110] Connection timed out
Assignee: jgriffin → nobody
Borrowed some code from the pulsesbuildmonitor for this.
Assignee: nobody → jgriffin
Status: NEW → ASSIGNED
Attachment #739557 - Flags: review?(mcote)
Comment on attachment 739557 [details] [diff] [review] Make the pulsetranslator reconnect on network error Review of attachment 739557 [details] [diff] [review]: ----------------------------------------------------------------- Nice. This bug means that the translator would stop receiving messages, but its process would keep running, right? Just want to make sure, since when I've reset it before, I've noticed that it's still running, just not doing anything.
Attachment #739557 - Flags: review?(mcote) → review+
Yes, exactly.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Jonathan, just a question for this landing. I assume we are safe in not missing any pulse notification giving that we run the daemon with --durable by default, right?
Yes, that's correct. Since we run with --daemon, all messages are queued when the translator goes down, and are delivered when it gets restarted.
s/--daemon/--durable/
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: