Custom Query (26254 matches)


Show under each result:

Results (4 - 6 of 26254)

1 2 3 4 5 6 7 8 9 10 11 12
Ticket Resolution Summary Owner Reporter
#5 Fixed Can't start new server-- get fatal exception while configuring server nickm weasel

[Moved from bugzilla] Reporter: geckox@… Description: Opened: 2003-07-31 02:22

Linux system, Python 2.3, Openssl 0.9.7

Here's the traceback:

root@xxx:/home/minion/etc# /etc/rc.d/mixminion.init start root@xxx:/home/minion/etc# This software is for testing purposes only. Anonymity is not guaranteed. Reading configuration from /home/minion/etc/mixminiond.conf Jul 30 19:17:13.979 [FATAL] Exception while configuring server Jul 30 19:17:13.989 [FATAL] Traceback (most recent call last):


"/usr/local/lib/python2.3/site-packages/mixminion/server/", line 1031, in runServer

mixminion.Common.LOG.configure(config, keepStderr=1) File "/usr/local/lib/python2.3/site-packages/mixminion/", line 722,

in configure

self.addHandler(_FileLogHandler(logfile)) File "/usr/local/lib/python2.3/site-packages/mixminion/", line 629,

in init

self.reset() File "/usr/local/lib/python2.3/site-packages/mixminion/", line 638,

in reset

createPrivateDir(parent) File "/usr/local/lib/python2.3/site-packages/mixminion/", line 305,

in createPrivateDir

raise MixFatalError("Unable to create directory %s: %s" % d, e)

TypeError: not enough arguments for format string

Jul 30 19:17:13.990 [FATAL] Shutting down because of exception: exceptions.TypeError


This is fixed in CVS---or at least, the error message is better. It's a symptom

of an underlying problem -- for some reason, you don't have permissions or

ability to create the directory the log files are supposed to be in.

[Automatically added by flyspray2trac: Operating System: Linux]

#6 wontfix Confused server clocks can screw up timing nickm weasel

[Moved from bugzilla] Reporter: nickm@… (Nick Mathewson) Description: Opened: 2003-08-29 20:44

Some users have reported that the mixminion server has a nasty failure mode when a server's clock moves backwards by a large interval. When the server asks "when did we last (do something)", the answer "tomorrow" can cause crashes or weird behavior.

I'm deferring this for a while, because (a) I want to get 0.0.5 put to bed, and (b) the workaround is trivial: keep your clock set right.

[Automatically added by flyspray2trac: Operating System: All]

#7 Fixed client 'flush' takes too much memory nickm weasel

[Moved from bugzilla] Reporter: qumqats@… (Joel M. Baldwin) Description: Opened: 2003-09-19 13:43

I there any way you can reduce the memory used by by the client 'flush' command?

When I have thousands of messages in my client queue the 'flush' command creates such a large memory footprint that the process causes my system to starts swapping.

This should be fixed in 0.0.6 CVS; we now lazy-load queued messages as we flush them. [We still use space proportional to the number of pending messages to compute which messages are going where, but this should now be a few dozen bytes per message, not 32KB per message.]

[Automatically added by flyspray2trac: Operating System: FreeBSD]

1 2 3 4 5 6 7 8 9 10 11 12
Note: See TracQuery for help on using queries.