>>>>> "Christian" == Christian Grothoff <[EMAIL PROTECTED]> writes: > I wonder how you managed to restart gnunetd without gnunet-update -- > the code does check. The only way I can think of this happening is > that you might have started gnunetd with a different directory / > configuration.
Running gnunet-update, I just saw the following message: Jul 10 22:55:45 ERROR: `mysql_query' failed at mysql.c:1542 with error: Lost connection to MySQL server during query I also remember having seen the same message when running gnunetd v0.7.2a the first time. Does this point to a specific problem? > If you want to force a run of gnunet-update, remove the first > character of "$GNUNETD_HOME/state.sdb/GNUNET-VERSION", that should > cause gnunet-update to actually do stuff (and equally cause gnunetd to > force you to run gnunet-update). gnunet-update does quite some extensive checks, even if I run it three times in a row. GNUNET-VERSION now contains the string "0.7.2a\0..." unfortunately I didn't check what was in there before running gnunet-update. Manually chaning GNUNET-VERSION back to "0.7.2\0.." really makes gnunetd issue an error on startup. hmmm. -- GnuPG public key: http://user.cs.tu-berlin.de/~dvdkhlng/dk.gpg Fingerprint: B17A DC95 D293 657B 4205 D016 7DEF 5323 C174 7D40 _______________________________________________ Help-gnunet mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-gnunet
