Roundup Tracker - Issues

Message6304

Author rouilj
Recipients aparcar, rouilj, schlatterbeck
Date 2018-11-28.02:17:50
Message-id <20181128021748.5F5EF4C030E@itserver6.localdomain>
In-reply-to <1543231495.96.0.788709270274.issue2551014@psf.upfronthosting.co.za>
Hello Paul:

In message
<1543231495.96.0.788709270274.issue2551014@psf.upfronthosting.co.za>,
Paul Spooren writes:

>The interface works fine except when sending emails by putting entries
>to the nosy list. The interface loads until it times out, no matter what
>timeout I set in the proxy.
>
>Receiving emails via mailgw works just fine.
>
>The error message looks like that:
>
>127.0.0.1 - - [26/Nov/2018 11:18:18] "POST /support/issue4 HTTP/1.0" 500 -
>----------------------------------------
>Exception happened during processing of request from ('127.0.0.1', 46082)
>Traceback (most recent call last):
>  File "/usr/lib/python2.7/SocketServer.py", line 571, in process_request
>    self.finish_request(request, client_address)
>  File "/usr/lib/python2.7/SocketServer.py", line 331, in finish_request
>    self.RequestHandlerClass(request, client_address, self)
>  File "/usr/lib/python2.7/SocketServer.py", line 654, in __init__
>    self.finish()
>  File
>"/usr/local/lib/python2.7/dist-packages/roundup/scripts/roundup_server.py",
>line 683, in finish
>    RoundupRequestHandler.finish(self)
>  File "/usr/lib/python2.7/SocketServer.py", line 713, in finish
>    self.wfile.close()
>  File "/usr/lib/python2.7/socket.py", line 283, in close
>    self.flush()
>  File "/usr/lib/python2.7/socket.py", line 307, in flush
>    self._sock.sendall(view[write_offset:write_offset+buffer_size])
>error: [Errno 32] Broken pipe
>----------------------------------------

Sorry you are having an issue (so to speak) with roundup.

Assuming your diagnosis is correct, how have you configured outbound
email for the tracker? This is configured in the [mail] section of the
tracker's config.ini.

Can you connect to the configured host and port (try using telnet or
netcat to verify a connection)?

Are you using tls? If so, do you have a local certificate?

Are you using a username and password to authenticate?

If you look at the mail logs on the mail server, do you see a
connection from the roundup server?

If you are logged into the roundup server, do you see a connection
from that server to the email port on the mail server (use

   netstat -an | grep 25

or what value (465 if using tls maybe) you set for the port.

If you try to reset your password, is email sent?

Are you using the normal nosyreaction.py script to send nosy messages?
If so rename/move detectors/nosyreaction.py from your tracker's home
directory and restart the roundup server. In this state can you update
an issue without it hanging?

Hopefully this will give us some idea what's going on. Also you may
want to try posting to the roundup-user's mailing list as more people
are on that list than there are watching issues.
History
Date User Action Args
2018-11-28 02:17:52rouiljsetrecipients: + rouilj, schlatterbeck, aparcar
2018-11-28 02:17:52rouiljlinkissue2551014 messages
2018-11-28 02:17:50rouiljcreate