-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Nov 24, 2008 at 7:32 AM, Matthew Toseland wrote: > On Monday 24 November 2008 07:26, Juiceman wrote: >> >> On Sat, Nov 22, 2008 at 9:54 PM, Juiceman wrote: >> > -----BEGIN PGP SIGNED MESSAGE----- >> > Hash: SHA1 >> > >> > >> > >> > On Sat, Nov 22, 2008 at 7:08 PM, Dennis Nezic wrote: >> >> On Sat, 22 Nov 2008 16:54:58 +0100, guido >> >> wrote: >> >> >> >>> Am Mittwoch, 19. November 2008 05:32:18 schrieb Dennis Nezic: >> >>> > >> > WARNING - The Wrapper jar file currently in use is version >> >>> > >> > "3.3.1" >> >>> > > while the version of the Wrapper which launched this JVM is >> >>> > > "3.2.3". >> >>> > >> >>> > That looks strange. >> >>> >> >>> I have got that exact same warning in my logs as well. It has been >> >>> like this for quite some time. >> >> >> >> Well, first of all, all of freenet's dependencies, including this >> >> wrapper utility, are bundled "conveniently" in freenet-ext.jar. So you >> >> likely originally launched it with the "older" 3.2.3 wrapper, and later >> >> one freenet-ext got updated. Restarting the wrapper should get rid of >> >> this message, though I don't think it's anything serious, since my >> >> installation is still using 3.2.3. >> > >> > Actually the installer installs 3.3.1 iirc, but we don't have a way >> > currently to update old installs. I manually did mine. >> >> Correction. I just checked and the installer is loading the old >> version. Nextgens should update this as there is a bugfix dealing >> with wrapper restarts. Seems like we went thru this a few months >> ago... yup: https://bugs.freenetproject.org/view.php?id=2564 >> I wonder if the old versions got put back on the website somehow....? > > The new version of the wrapper binary is known to fix the problem??? - From my original bug ticket: "You may remember I changed the Windows update.cmd script to loop during stop until the service was down because the node would not quite be stopped even though the wrapper thought it was. This led to corruption, hence the need for looping. I see in the changelog for one version older than current: "Version 3.3.0: Changes and bug fixes: Fix a problem on Windows where the Windows Service Manager was not waiting the full configured time of the wrapper.jvm_exit.timeout and wrapper.shutdown.timeout properties. This was leading to the net stop command timing out and the system shutting down without the java application having fully stopped. Bug #1582568." This may be the culprit for the occasional datastore corruptions, auto-update failures and the wrapper sometimes not being able to successfully restart the node after a crash/oom" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: http://getfiregpg.org iD8DBQFJKz6r4esu1mlKOs8RAt14AJ9a4vtJsmzFcznnltcCz44Fq4LvcwCghe3W 2VfxXzPMTJtLL1YD7Ecg90U= =siDv -----END PGP SIGNATURE----- _______________________________________________ Support mailing list [email protected] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
