Error 111 Connection refused on new install


#1

I have a development environment set up in a Vm which starts up perfectly, but I have noticed that I am not logged in. when I attempt to login I get the following in my ‘running’ window and still not logged in.

I have read around the forum and although found I page thread on tis it didn’t help. This is a clean install of the latest code as of about 7 days ago.

Error:

rror: [Errno 111] Connection refused

Logged from file cache.py, line 150

Traceback (most recent call last):

File "/home/indico/dev/indico/src/indico/core/logger.py", line 77, in emit

smtp = smtplib.SMTP(self.mailhost, port, timeout=self._timeout)

File "/usr/lib64/python2.7/smtplib.py", line 255, in init

(code, msg) = self.connect(host, port)

File "/usr/lib64/python2.7/smtplib.py", line 315, in connect

self.sock = self._get_socket(host, port, self.timeout)

File "/usr/lib64/python2.7/smtplib.py", line 290, in _get_socket

return socket.create_connection((host, port), timeout)

File "/usr/lib64/python2.7/socket.py", line 571, in create_connection

raise err

error: [Errno 111] Connection refused

Logged from file cache.py, line 144

Traceback (most recent call last):

File "/home/indico/dev/indico/src/indico/core/logger.py", line 77, in emit

smtp = smtplib.SMTP(self.mailhost, port, timeout=self._timeout)

File "/usr/lib64/python2.7/smtplib.py", line 255, in init

(code, msg) = self.connect(host, port)

File "/usr/lib64/python2.7/smtplib.py", line 315, in connect

self.sock = self._get_socket(host, port, self.timeout)

File "/usr/lib64/python2.7/smtplib.py", line 290, in _get_socket

return socket.create_connection((host, port), timeout)

File "/usr/lib64/python2.7/socket.py", line 571, in create_connection

raise err

error: [Errno 111] Connection refused

Logged from file cache.py, line 150

Traceback (most recent call last):


#2

On a restart i am now getting the following, still not loggin in

    self.wfile.write("%s: %s\r\n" % (keyword, value))
IOError: [Errno 32] Broken pipe
Error on request:
Traceback (most recent call last):
  File "/home/indico/dev/indico/env/lib/python2.7/site-packages/werkzeug/serving.py", line 270, in run_wsgi
    execute(self.server.app)
  File "/home/indico/dev/indico/env/lib/python2.7/site-packages/werkzeug/serving.py", line 261, in execute
    write(data)
  File "/home/indico/dev/indico/env/lib/python2.7/site-packages/werkzeug/serving.py", line 227, in write
    self.send_header(key, value)
  File "/usr/lib64/python2.7/BaseHTTPServer.py", line 401, in send_header
    self.wfile.write("%s: %s\r\n" % (keyword, value))
IOError: [Errno 32] Broken pipe
Error on request:
Traceback (most recent call last):
  File "/home/indico/dev/indico/env/lib/python2.7/site-packages/werkzeug/serving.py", line 270, in run_wsgi
    execute(self.server.app)
  File "/home/indico/dev/indico/env/lib/python2.7/site-packages/werkzeug/serving.py", line 261, in execute
    write(data)
  File "/home/indico/dev/indico/env/lib/python2.7/site-packages/werkzeug/serving.py", line 227, in write
    self.send_header(key, value)
  File "/usr/lib64/python2.7/BaseHTTPServer.py", line 401, in send_header
    self.wfile.write("%s: %s\r\n" % (keyword, value))
IOError: [Errno 32] Broken pipe
Error on request:
Traceback (most recent call last):
  File "/home/indico/dev/indico/env/lib/python2.7/site-packages/werkzeug/serving.py", line 270, in run_wsgi
    execute(self.server.app)
  File "/home/indico/dev/indico/env/lib/python2.7/site-packages/werkzeug/serving.py", line 261, in execute
    write(data)
  File "/home/indico/dev/indico/env/lib/python2.7/site-packages/werkzeug/serving.py", line 227, in write
    self.send_header(key, value)
  File "/usr/lib64/python2.7/BaseHTTPServer.py", line 401, in send_header
    self.wfile.write("%s: %s\r\n" % (keyword, value))
IOError: [Errno 32] Broken pipe

#3

The broken pipe errors can be ignored.

The original error indicates that it tried to send an email, but could not connect - likely because you did not start maildump or didn’t set the correct port in the indico config.

Anyway, check the indico log file to see what actually went wrong and caused the error email in the first place.


PS: Please format logs etc. as code when posting them, you can do so using a triple-backtick fence:

```
your stuff here
```