Custom Query (332 matches)


Show under each result:

Results (262 - 264 of 332)

Ticket Resolution Summary Owner Reporter
#277 fixed "database locked" issue bas thomas.moschny@…

I thought I'd ask per mail first, before creating a ticket; maybe this
is a (configuration) error on our side, or something like that.

Here's the issue: Occasionally we lose mails in our email2trac -> Trac
setup, and get trackbacks like this in the syslog:

Oct 26 11:35:00 <hostname> email2trac <prjname>: subject: u'#4951: XXX'
Oct 26 11:35:11 <hostname> email2trac <prjname>: Traceback (most recent call
Oct 26 11:35:11 <hostname> email2trac <prjname>:   File
"/opt/trac/bin/email2trac", line 2553, in ?     tktparser.parse(sys.stdin)
Oct 26 11:35:11 <hostname> email2trac <prjname>:   File
"/opt/trac/bin/email2trac", line 1689, in parse     if not
self.ticket_update(m,'reply')[:-1], spam_msg):
Oct 26 11:35:11 <hostname> email2trac <prjname>:   File
"/opt/trac/bin/email2trac", line 985, in ticket_update
tkt.save_changes(, body_text, when, None, str(cnum))
Oct 26 11:35:11 <hostname> email2trac <prjname>:   File
packages/Trac-0.11.8dev_r10236-py2.4.egg/trac/ticket/", line 293, in
save_changes     db.commit()
Oct 26 11:35:11 <hostname> email2trac <prjname>:   File
"/usr/lib64/python2.4/site-packages/sqlite/", line 540, in commit
Oct 26 11:35:11 <hostname> email2trac <prjname>: OperationalError: database
is locked

As you can see, we are using Python 2.4 (well, we are on Centos5),
Trac 0.11.8dev and email2trac 2.4.0 (I know there's a later version,
will try it, but couldn't find anything relevant in the changelog).

It seems clear that email2trac might not be causing the issue, but is
suffering from it: something else might be blocking the DB while
email2trac tries to insert or update a ticket.

So the question is: Can email2trac repeat and try again for a while, or
else save the message somewhere so it doesn't get lost?

Best regards,
#278 fixed Conditional workflow bas Chris.Nelson@…

I'd like an email2trac workflow to only be invoked when the e-mail sender is the ticket owner. Is there any way to configure this restriction?

#279 wontfix email2trac 2.4.5 with sendmail 8.14.4-8 and 0.12.1-4 on CentOS 6.0 bas anonymous


I'd like to use email2trac with my trac installation but sendmail gives only this error:

to="|run_email2trac", ctladdr=<> (8/0), delay=00:00:01, xdelay=00:00:00, mailer=prog, pri=30840, dsn=5.3.0, stat=unknown mailer error 254

I tried to turn off selinux. The message does not change.

I had a look at the source. Is the problem that caller is not the same user as mta is running?

  if ( caller !=  MTA->pw_uid ) {    if ( DEBUG ) printf("Invalid caller UID (%d)\n",caller);
    return -2;     /* 254 : Invalid caller */

cheers Andi

Note: See TracQuery for help on using queries.