Here's the relevant part of the wrapper.log (at least I think it's the right part, as it's the one that's different from old entries when the node was running fine):
INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: Error in WrapperListener.start callback. java.lang.NumberFormatException: For input string: "4329173579036400079" INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: java.lang.NumberFormatException: For input string: "4329173579036400079" INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: at java.lang.NumberFormatException.forInputString(Unknown Source) INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: at java.lang.Integer.parseInt(Unknown Source) INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: at java.lang.Integer.parseInt(Unknown Source) INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: at freenet.node.updater.UpdateOverMandatoryManager$13.accept(UpdateOverMandatoryManager.java:1287) INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: at java.io.File.listFiles(Unknown Source) INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: at freenet.node.updater.UpdateOverMandatoryManager.removeOldTempFiles(UpdateOverMandatoryManager.java:1269) INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: at freenet.node.updater.NodeUpdateManager.<init>(NodeUpdateManager.java:157) INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: at freenet.node.updater.NodeUpdateManager.maybeCreate(NodeUpdateManager.java:263) INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: at freenet.node.Node.<init>(Node.java:1879) INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: at freenet.node.NodeStarter.start(NodeStarter.java:152) INFO | jvm 1 | 2008/12/11 12:31:13 | WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:2979) Other than that, running update.cmd updated the node and solved the startup issues. There's still that infamous message present: "Probably a bug: please report: 3 peers forcibly disconnected due to not acknowledging packets. 3 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or to the support mailing list support at freenetproject.org. Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are:[...]" But the number of peers shown there is now lower than it was earlier. Should I be worried about this message: "Connection problems: Please forward UDP port XXXX (you may have already done this). Your node appears to be behind some sort of NAT (see the connectivity page for details). You should forward UDP (not TCP) port XXXX if possible to improve connectivity. It is possible you have already done this; it takes a while for Freenet to detect a port forward. See here for some more information." The port in question is portforwarded correctly, though.
