Main (#1) - Email notifications not sending, looks like a celery issue? (#49) - Message List

Email notifications not sending, looks like a celery issue?


I've got my test server all set up and running, and can access it on the LAN, and was just starting to set up users for testing, but when it tries to send mail, I get the following:

error at /user/riverside/delegation/sponsor/mail/ [Errno 104] Connection reset by peer Request Method: POST Request URL:  http://localhost/user/riverside/delegation/sponsor/mail/ Django Version: 1.5.1 Exception Type: error Exception Value: [Errno 104] Connection reset by peer Exception Location: /usr/local/lib/python2.7/dist-packages/amqp/ in read_method, line 192 Python Executable: /usr/bin/python Python Version: 2.7.4 Python Path: ['/usr/local/lib/python2.7/dist-packages/psycopg2-2.5.1-py2.7-linux-i686.egg',

'/usr/lib/python2.7', '/usr/lib/python2.7/plat-i386-linux-gnu', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages/PILcompat', '/usr/lib/python2.7/dist-packages/gst-0.10', '/usr/lib/python2.7/dist-packages/gtk-2.0', '/usr/lib/pymodules/python2.7', '/var/django/openPLM/trunk/', '/var/django/openPLM/trunk/openPLM']

Server time: Tue, 6 Aug 2013 15:47:28 -0500

This is the traceback file that generated:

Celery's error log is showing this, repeated many times with different time stamps: [2013-08-05 16:24:25,341: WARNING/MainProcess] celery@… ready. [2013-08-05 16:24:25,397: ERROR/MainProcess] consumer: Cannot connect to  amqp://openplm@ [Errno 111] Connection refused. "w1.log" 888L, 67349C

rabbitmq-server comes back with:

nodes in question: [rabbit@openplm]

hosts, their running nodes and ports:

  • openplm: [{rabbit,57982},{rabbitmqprelaunch5043,59905}]

current node details:

  • node name: rabbitmqprelaunch5043@openplm
  • home dir: /var/lib/rabbitmq

it looks like the wrong port is set, but I'm not that clear on how to change it, or if it even needs to be changed.

Any advice?

Hopefully it's something simple, because from what I see so far, this product is exactly what we need.


  • Message #162


    RabbitMQ logs access in /var/log/*

    It is possible it blocks connections if there is not enough disk space or memory.

    You can check current limits with rabbitmqctl status:

    # rabbitmqctl status
    Status of node rabbit@bebop ...
                            {os_mon,"CPO  CXC 138 46","2.2.5"},
                            {mnesia,"MNESIA  CXC 138 12","4.4.14"},
                            {sasl,"SASL  CXC 138 11",""},
                            {stdlib,"ERTS  CXC 138 10","1.17"},
                            {kernel,"ERTS  CXC 138 10","2.14"}]},
     {erlang_version,"Erlang R14A (erts-5.8) [source] [64-bit] [smp:4:4] [rq:4] [async-threads:30] [kernel-poll:true]\n"},

    To configure limits:

    • Message #163

      Hmmm.... looking at yours, I don't think that's the problem. There's 174 gb free, and the other settings are similar to yours.

      There is another issue I encountered last night when I checked the VPN functionality from home, and it may be related. When I tried to upload a test file, it repeatedly reached 100%, then paused for several seconds before an orange box with "Your upload(s) failed! Try again."

      This was working previously when I was accessing it via localhost, but now even the host machine is exhibiting the same behavior. Any other things I could check?

      • Message #164

        Maybe the broker password is misspelled (BROKER_PASSWORD setting) or maybe a firewall blocks the connection.

        rabbitmqctl report | grep tcp_listeners returns the port that should be set (BROKER_PORT setting).


No attachments created.