[freenet-support] Sorry to have to report bad bug in 1180

2008-11-24 Thread Juiceman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



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?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: http://getfiregpg.org

iD8DBQFJKlcO4esu1mlKOs8RAhpkAJ9JKFIIB9MiX49YHMS5oZVqCkdrbQCeM5ub
SvKbCxPm/FSViV2XvxhF+Cw=
=MRvj
-END PGP SIGNATURE-



[freenet-support] Sorry to have to report bad bug in 1180

2008-11-24 Thread Matthew Toseland
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???
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/support/attachments/20081124/f9b329d6/attachment.pgp>


[freenet-support] Sorry to have to report bad bug in 1180

2008-11-24 Thread Juiceman
-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-



[freenet-support] Bug report

2008-11-24 Thread toadsfriend
1 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 at [EMAIL PROTECTED] 
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: 24.80.101.100:16145

My node:
Freenet 0.7 Build #1181 r23784
Freenet-ext Build #26 r23771

Hope this helps.

--
Single?
Chat with sexy singles in your area now. Click Here!
http://tagline.hushmail.com/fc/u4MuRdD02Vyd5fLrWa8x5TbtidCV9vLzWQQuOVc30M8iFLKpzudc5/

___
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:[EMAIL PROTECTED]


[freenet-support] report

2008-11-24 Thread Ari Takalo
10 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 at [EMAIL PROTECTED]
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:
79.45.141.64:46423
62.214.215.118:58211
81.107.31.142:9149
75.70.178.124:45478
77.194.193.167:50326
79.138.36.47:46779
38.100.222.92:54774
96.235.40.86:50337
210.170.178.235:33541
76.27.195.133:59946

Freenet 0.7 Build #1181 r23784M
Freenet-ext Build #26 r23771
___
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:[EMAIL PROTECTED]


[freenet-support] Some bug (?) report

2008-11-24 Thread Dsoslglece

Hi,
I had this message, and so I do what was asked for, and send it at one 
of the required addresses
I think that a reason for this may have been the fact that about an hour 
ago, I did send two files to my editor (about 10 MB) each, and the 
traffic may have been a bit strangled since I've got only about 34 Kb/s 
on upload
I've got this information about my version on the home page (I believe 
the last one):


Freenet 0.7 version #1181 r23784
Freenet-ext version #26 r23771

and I'm running OS X 10.4.11


Probably a bug: please report: 7 peers forcibly disconnected due to not 
acknowledging packets.
7 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 at [EMAIL PROTECTED] 
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:


   * 85.177.248.19:24013
   * 88.67.15.46:32035
   * 97.81.131.62:36320
   * 217.122.53.134:1076
   * 78.114.55.212:55062
   * 79.150.234.158:52088
   * 78.46.47.67:6839

___
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:[EMAIL PROTECTED]

Re: [freenet-support] Sorry to have to report bad bug in 1180

2008-11-24 Thread Matthew Toseland
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???


pgpnmU7BJV3VY.pgp
Description: PGP 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:[EMAIL PROTECTED]

Re: [freenet-support] Sorry to have to report bad bug in 1180

2008-11-24 Thread Juiceman
-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
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


Re: [freenet-support] Sorry to have to report bad bug in 1180

2008-11-24 Thread Bill Shutt

Many, many thanks for all your kind help. i reinstalled Freenet which now 
appears to be working OK

warmest regards

bill

> Date: Mon, 24 Nov 2008 18:54:18 -0500
> From: [EMAIL PROTECTED]
> To: support@freenetproject.org
> Subject: Re: [freenet-support] Sorry to have to report bad bug in 1180
> 
> -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
> Support@freenetproject.org
> http://news.gmane.org/gmane.network.freenet.support
> Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
> Or mailto:[EMAIL PROTECTED]

_
Win £1000 John Lewis shopping sprees with BigSnapSearch.com
http://clk.atdmt.com/UKM/go/117442309/direct/01/___
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:[EMAIL PROTECTED]