On 01/03/2015 10:38 AM, Евгения Карпова wrote: > Hello, I have and old node and it seems to be broken/misconfigured (I see > too few peers, comparing to a fresh node install on the next box, though > all security configs are the same, and also it suffered from strange > reindex/db loss sometimes).
I am sorry to hear you're running into trouble. purge-db4o should solve these problems and is continuing to make progress toward release, but I don't have a timeframe for it yet. There are testing versions of it out, but it's not ready for a stable release yet. > I want to stay on new node, but also migrate all data from old node to new > one to not break network and to not loose others's people data. Thanks for that! > Is it possible, and is it is, which files/keys/dbases should i copy to a > fresh node? You should be able to copy enough to keep your node's datastore configuration and its contents. Two options come to mind, and it depends on whether your want the new node to get the old darknet reference. In either case, replace the "/datastore/" directory of the new node with that of the old one. If you want to keep the same reference, copy the "node-<darknet port number>" file to the new node. Then replace the "node.opennet.listenPort" and "node.listenPort" lines in the new freenet.ini with those in the old. I do not recommend running both nodes after doing this because I expect them to conflict with one another. If you do not want to keep the same reference, replace the "location" line in the new "node-<darknet port number>" with that from the old. - Steve
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
