Re: RoundUp stopped creating tickets

Lee Higginbotham <[email protected]>
Newsgroups gmane.comp.bug-tracking.roundup.user
Message-ID <20151117130038.Horde.LWjb_XR3hbhnojzzo7dhsoV@webmail.riverainc.com>
  David,

Thank you for your assistance.  I've been beating my head against this
issue since the 9th of November.  I've confirmed that all traffic is
flowing the way it should.  The only problem seems to be the
roundup-mailgw is not working properly all the time.  The only thing in my
mail_gateway.log are all the notices that the "Mail Gateway Ran" with an
occasional error of this nature:

[2015-11-09 09:01:01.828927] Mail Gateway Error: <class 'ssl.SSLError'>
[2015-11-09 06:25:10.279796] Mail Gateway Error: <class
'poplib.error_proto'>
[2015-11-09 05:56:01.444671] Mail Gateway Error: <class
'poplib.error_proto'>
[2015-11-09 06:01:01.798850] Mail Gateway Error: <class 'ssl.SSLError'>
[2015-11-09 05:26:02.084608] Mail Gateway Error: <class
'poplib.error_proto'>
[2015-11-08 19:06:02.093787] Mail Gateway Error: <class 'ssl.SSLError'>

  An coincidentally, since the errors on the 9th, I have received no Mail
Gateway Errors at all.  However when the roundup-mailgw command in run, I
receive the following in the roundup.log:
 
  2015-11-17 22:55:01,913 ERROR POP server error
  Traceback (most recent call last):
    File "/usr/local/lib/python2.7/dist-packages/roundup/mailgw.py", line
1330, in _do_pop
      server = klass(server)
    File "/usr/lib/python2.7/poplib.py", line 360, in __init__
      self.sslobj = ssl.wrap_socket(self.sock, self.keyfile,
self.certfile)
    File "/usr/lib/python2.7/ssl.py", line 381, in wrap_socket
      ciphers=ciphers)
    File "/usr/lib/python2.7/ssl.py", line 143, in __init__
      self.do_handshake()
    File "/usr/lib/python2.7/ssl.py", line 305, in do_handshake
      self._sslobj.do_handshake()
  error: [Errno 104] Connection reset by peer

I have checked all the certificates and they are all valid and have no
issues that I can tell, however, every 5 minutes, I receive these messages.

Again, I inherited these systems and am learning about roundup, so, thank
you again for your assistance.  Hopefully, someone else will chime in and
provide assistance.

Sincerely,
Lee

Quoting "R. David Murray" <[email protected]>:

> On Tue, 17 Nov 2015 07:48:22 -0500, Lee Higginbotham wrote:
>> Thank you for your reply.  I too am using POP3 and am using the
>> roundup-mailgw with a cron job to pull everry 5 minutes.
>
> [...]
>
>> This file has an time date stamp of Aug 20 2013, so it hasn't changed
>> in a
>> long time.  I do get several Mail Gateway Errors, but looking back at
>> the
>> historical logs, we have been receiving these errors for quite some time
>> and that doesn't appear to be the issue.
>
> Yes, roundup-mailgw is part of the roundup software, and ideally you
> wouldn't make any local changes to it.
>
> You are on an older version of roundup than I'm using, so I don't
> know that I can give you much help.  Basically, you want to correlate
> the entries in the roundup mail log with the submissions from your
> server that are failing, and see if you can figure out where things
> are going wrong.  If roundup is processing the messages but not
> updating the issue, and there's no corresponding error in the
> mail gateway log, you may need to start adding some logging to the
> roundup code to track it down.  But I'm guessing you'll find
> something before you get to that point.
>
> People with experience with your version of roundup may have additional
> suggestions, once you complete the initial investigation.
> --David
  Sincerely,
   Lee Higginbotham
    Systems Administrator | Rivera Group | [email protected][1]
Office: (812) 246-4055

www.riverainc.com[2]

"We strive to do great things!"


Links:
------
[1]
[2] http://www.riverainc.com/

------------------------------------------------------------------------------

_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.