Trac keeps crashing. Doesn't happen every time but is happening multiple times a day.

[jon@…]

If you think this really should work and you can reproduce it, you should consider reporting this problem to the Trac team.

Go to ​http://trac.edgewall.org/ and create a new ticket where you describe the problem, how to reproduce it. Don't forget to include the Python traceback found below.

TracGuide — The Trac User and Administration Guide Python Traceback

Traceback (most recent call last):
  File "/usr/local/python/lib/python2.5/site-packages/trac/web/main.py", line 393, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/python/lib/python2.5/site-packages/trac/web/main.py", line 243, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/local/python/lib/python2.5/site-packages/trac/ticket/web_ui.py", line 302, in process_request
    get_reporter_id(req, 'author'))
  File "/usr/local/python/lib/python2.5/site-packages/trac/ticket/web_ui.py", line 627, in _insert_ticket_data
    change['localdate'] = format_datetime(parse_date(change['date']), tz=req.session.get_timezone())
  File "/usr/local/python/lib/python2.5/site-packages/trac/util/datefmt.py", line 136, in parse_date
    raise ValueError, '%s is not a known date format.' % text
ValueError: 10/30/07 17:36:23 EST is not a known date format.

[ThurnerRupert]

is this related to r5188?

[sid]

Which version of Trac are you using? Can you give us any instructions on how we might be able to reproduce this? Any additional info you can give will help us solve this faster. Thanks!

[anonymous]

Powered by Trac 0.10.3

Currently I have not found a common pattern. It happens when we enter a ticket or save a ticket (although it does save the changes). The same incident can fail and then the next time I try to enter it I don't get the error.

[sid]

Can you include the relevant date format section from your trac.ini file? This might be the same problem as #2182

[anonymous]

Not sure I can as we use a hosted version of Trac. The host is CVSDUDE. Not that I have taken a large amount of time on this I have to imagine I am not going to be able to get to conf/trac.ini file.

[anonymous]

You can get hold of your trac.ini file from cvsdude by simply emailing them. Also, CVSDude have timezone support added to trac 0.10 so there's a high probability this isn't a standard trac issue.

[anonymous]

Already emailed them. They haven't responded yet.

[Christian Boos]

Most probably a "CVSDUDE" specific issue. Also, the installation seems to be very much the same as in #6406.