This server's files are stored in an older format
[Moved from bugzilla] Reporter: email@example.com (Peter Palfrader) Description: Opened: 2003-10-19 23:46
After copying the mixminiond.conf config file from the etc directory of the tarball and modifying it to set local settings, when one tried to start the server one is told to run server-upgrade.
weasel@valiant:~/mixminion/bin$ ./mixminion server-start -f
Mixminion version 0.0.5.1 This software is for testing purposes only. Anonymity is not guaranteed. Reading configuration from ../etc/mixminiond.conf Oct 19 23:44:42.841 [WARN] Mode specification is not yet supported. Oct 19 23:44:42.842 [WARN] Dangerously low MixInterval This server's files are stored in an older format, and are not compatible with this version of the mixminion server. To upgrade, run: 'mixminion server-upgrade'.
Same happens with current CVS.
Maybe the shipped sample mixminiond.conf file should have a current format.
------- Additional Comments From Nick Mathewson 2003-10-20 20:47 -------
Actually, this is not the bug you think it is. The problem isn't with mixminiond.conf, but with a file named 'version' in your server's homedir: it is supposed to contain the current version of the directory layout. Currently, this is the string "1001". It has been "1001" since about 0.0.4, IIRC.
One of two things is the case:
- You are upgrading from 0.0.3. (Not too likely.)
- You somehow managed to get a directory created with no version file. (More likely; I'll try to figure out how this could happen.)
Also, it is definitely the case that you got an error message not helpful to you. Can you suggest a more useful one?
------- Additional Comments From Peter Palfrader 2003-10-20 21:01 -------
Ah, now I know what I was doing.
I was starting from scratch, so there was nothing in that dir before. Only a bin, lib and etc file. I didn't realize that mixminion expected an empty dir as its homedir.
Here's transcript of what I did: weasel@valiant:~$ mkdir mixminion2 weasel@valiant:~$ ( cd projects/mixminion/src/minion; make install PREFIX=/home/weasel/mixminion2 ) (...) weasel@valiant:~$ cd mixminion2 weasel@valiant:~/mixminion2$ mkdir etc weasel@valiant:~/mixminion2$ cp ~/projects/mixminion/src/minion/etc/mixminiond.c etc weasel@valiant:~/mixminion2$ grep !^Homedir etc/mixminiond.conf Homedir: /home/weasel/mixminion2 weasel@valiant:~/mixminion2$ bin/mixminion server-start -f etc/mixminiond.conf Mixminion version 0.0.6alpha1 This software is for testing purposes only. Anonymity is not guaranteed. Reading configuration from etc/mixminiond.conf This server's files are stored in an older format, and are not compatible with this version of the mixminion server. To upgrade, run: 'mixminion server-upgrade'. weasel@valiant:~/mixminion2$ ls -l total 12 drwxr-xr-x 2 weasel weasel 4096 Oct 20 20:52 bin/ drwxrwxr-x 2 weasel weasel 4096 Oct 20 20:54 etc/ drwxr-xr-x 3 weasel weasel 4096 Oct 20 20:52 lib/
Maybe mixminion should say that it expects an empty directory as serverhome, or a directory with a version file if none is found.
------- Additional Comments From Nick Mathewson 2004-02-21 01:45 -------
Okay. The bug seemed to be: 1 User configures server. 2 User creates home directory for server. 3 User starts server for the first time. 4 Server starts, notices that the directory doesn't have a "version" file 5 Server decides that it is looking at an obsolete directory. 6 Server freaks out and tells user to upgrade. 7 Recursively, user freaks out.
Now, there is a new step: 4.5 Since there is no version file, the server checks for "work" and "keys" directories. If they were there, it would decide that it had an obsolete direcotry. But since thay aren't, it decides that it just has an uninitialized empty directory. 5' The server goes on to initialized a new file layout.
So I can't make the bug happen anymore, and I think it's gone.
[Automatically added by flyspray2trac: Operating System: All]