[freenet-support] Freenet 0.7 build 1186

2008-12-01 Thread Matthew Toseland
On Monday 01 December 2008 07:11, Ronald Wiplinger (Lists) wrote:
> How to upgrade?
> 
> Automatic upgrade did not work.
> Now it does not even start anymore.

Please send me your wrapper.log. This will be in the directory you installed 
Freenet to. Thanks.
> 
> bye
> 
> Ronald
> 
> 
> Matthew Toseland wrote:
> > Freenet 0.7 build 1186 is now available. Please upgrade, it will be 
mandatory 
> > on Tuesday. Changes:
> > - Fix a nasty race condition in the message handling code. Impact is 
uncertain 
> > but could be large - it broke an update-over-mandatory between nodes on 
the 
> > same computer in testing.
> > - Implement (long overdue) update over mandatory for freenet-ext.jar. 
Normally 
> > this will fetch both the main jar and the ext jar at the same time, if the 
> > node is too old to update over Freenet, or if it takes more than 3 hours 
to 
> > update. 
> > - Include the earliest compatible version of freenet-ext.jar in the 
manifest 
> > for the main jar. We will use this to ensure compatibility when updating 
in a 
> > near future build.
> > - Limit the size of the auto-detected datastore size to 256GB. This will 
> > ensure the Bloom filter is of a reasonable size (128MB at most), and avoid 
> > some crazy situations. Don't limit the Bloom filter size to 256MB any 
more, 
> > defaults to 1/2048th of the size of the store up to 2GB filter.
> > - Make the datastore size default to 100MB. The first-time wizard will 
> > configure it to a larger size, but the resize will occur online, and this 
> > gains us a few seconds on the first startup by not having to wait so long 
for 
> > preallocating it.
> > - Minor change to plugin loading and a minor bugfix to connection setup.
> >
> > Please upgrade! If you find any bugs, please report them on the bug 
tracker. 
> > The "not acknowledging packets even after 10 minutes" bug is sadly still 
with 
> > us, it will be fixed soon.
> >   
> > 
> >
> > ___
> > Support mailing list
> > Support at freenetproject.org
> > http://news.gmane.org/gmane.network.freenet.support
> > Unsubscribe at 
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
> > Or mailto:support-request at freenetproject.org?subject=unsubscribe
> 
> ___
> Support mailing list
> Support at freenetproject.org
> http://news.gmane.org/gmane.network.freenet.support
> Unsubscribe at 
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
> Or mailto:support-request at freenetproject.org?subject=unsubscribe
> 
> 
-- 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/20081201/afcdb17a/attachment.pgp>


[freenet-support] Probably a bug: please report: 4 peers forcibly disconnected due to not acknowledging packets.

2008-12-01 Thread IOR
4 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 
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:

* 81.210.138.199:28077
* 86.74.177.210:14089
* 85.178.251.99:55164
* 76.182.35.72:36405



Freenet 0.7 Build 1186 r23968
Freenet-ext Build #26 r23771




[freenet-support] Freenet 0.7 build 1186

2008-12-01 Thread Luke771
On Mon, 01 Dec 2008 15:11:07 +0800
"Ronald Wiplinger (Lists)"  wrote:

> How to upgrade?

On Windows:
Click My Computer, Browse to Freenet folder, double click on update.cmd
-or-
Start => (type) cmd [enter] => (type) cd c:\program files\freenet (or wherever 
you installed Freenet)[enter] => (type) update.cmd [enter]

NOTE: If you get 'too many parameters' error, type progra~1 instead of program 
files (cd c:\progra~1\freenet)



On any other OS (including Mac, Ubuntu)
- Open a terminal, cd to the Freenet directory, type ./update.sh ,  hit enter

NOTE: you may need to set execute permission for file update.sh with the 
command chmod +x update.sh


> Automatic upgrade did not work.
> Now it does not even start anymore.

It would be nice to know what happens exactly
Any ERROR lines in wrapper.conf?



[freenet-support] Freenet 0.7 build 1186

2008-12-01 Thread Ronald Wiplinger (Lists)
How to upgrade?

Automatic upgrade did not work.
Now it does not even start anymore.

bye

Ronald


Matthew Toseland wrote:
> Freenet 0.7 build 1186 is now available. Please upgrade, it will be mandatory 
> on Tuesday. Changes:
> - Fix a nasty race condition in the message handling code. Impact is 
> uncertain 
> but could be large - it broke an update-over-mandatory between nodes on the 
> same computer in testing.
> - Implement (long overdue) update over mandatory for freenet-ext.jar. 
> Normally 
> this will fetch both the main jar and the ext jar at the same time, if the 
> node is too old to update over Freenet, or if it takes more than 3 hours to 
> update. 
> - Include the earliest compatible version of freenet-ext.jar in the manifest 
> for the main jar. We will use this to ensure compatibility when updating in a 
> near future build.
> - Limit the size of the auto-detected datastore size to 256GB. This will 
> ensure the Bloom filter is of a reasonable size (128MB at most), and avoid 
> some crazy situations. Don't limit the Bloom filter size to 256MB any more, 
> defaults to 1/2048th of the size of the store up to 2GB filter.
> - Make the datastore size default to 100MB. The first-time wizard will 
> configure it to a larger size, but the resize will occur online, and this 
> gains us a few seconds on the first startup by not having to wait so long for 
> preallocating it.
> - Minor change to plugin loading and a minor bugfix to connection setup.
>
> Please upgrade! If you find any bugs, please report them on the bug tracker. 
> The "not acknowledging packets even after 10 minutes" bug is sadly still with 
> us, it will be fixed soon.
>   
> 
>
> ___
> Support mailing list
> Support at freenetproject.org
> http://news.gmane.org/gmane.network.freenet.support
> Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
> Or mailto:support-request at freenetproject.org?subject=unsubscribe




Re: [freenet-support] Freenet 0.7 build 1186

2008-12-01 Thread Matthew Toseland
On Monday 01 December 2008 07:11, Ronald Wiplinger (Lists) wrote:
> How to upgrade?
> 
> Automatic upgrade did not work.
> Now it does not even start anymore.

Please send me your wrapper.log. This will be in the directory you installed 
Freenet to. Thanks.
> 
> bye
> 
> Ronald
> 
> 
> Matthew Toseland wrote:
> > Freenet 0.7 build 1186 is now available. Please upgrade, it will be 
mandatory 
> > on Tuesday. Changes:
> > - Fix a nasty race condition in the message handling code. Impact is 
uncertain 
> > but could be large - it broke an update-over-mandatory between nodes on 
the 
> > same computer in testing.
> > - Implement (long overdue) update over mandatory for freenet-ext.jar. 
Normally 
> > this will fetch both the main jar and the ext jar at the same time, if the 
> > node is too old to update over Freenet, or if it takes more than 3 hours 
to 
> > update. 
> > - Include the earliest compatible version of freenet-ext.jar in the 
manifest 
> > for the main jar. We will use this to ensure compatibility when updating 
in a 
> > near future build.
> > - Limit the size of the auto-detected datastore size to 256GB. This will 
> > ensure the Bloom filter is of a reasonable size (128MB at most), and avoid 
> > some crazy situations. Don't limit the Bloom filter size to 256MB any 
more, 
> > defaults to 1/2048th of the size of the store up to 2GB filter.
> > - Make the datastore size default to 100MB. The first-time wizard will 
> > configure it to a larger size, but the resize will occur online, and this 
> > gains us a few seconds on the first startup by not having to wait so long 
for 
> > preallocating it.
> > - Minor change to plugin loading and a minor bugfix to connection setup.
> >
> > Please upgrade! If you find any bugs, please report them on the bug 
tracker. 
> > The "not acknowledging packets even after 10 minutes" bug is sadly still 
with 
> > us, it will be fixed soon.
> >   
> > 
> >
> > ___
> > 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]
> 
> ___
> 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]
> 
> 


pgp65A1IoeBK0.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] Freenet 0.7 build 1186

2008-12-01 Thread Luke771
On Mon, 01 Dec 2008 15:11:07 +0800
"Ronald Wiplinger (Lists)" <[EMAIL PROTECTED]> wrote:

> How to upgrade?

On Windows:
Click My Computer, Browse to Freenet folder, double click on update.cmd
-or-
Start => (type) cmd [enter] => (type) cd c:\program files\freenet (or wherever 
you installed Freenet)[enter] => (type) update.cmd [enter]

NOTE: If you get 'too many parameters' error, type progra~1 instead of program 
files (cd c:\progra~1\freenet)



On any other OS (including Mac, Ubuntu)
- Open a terminal, cd to the Freenet directory, type ./update.sh ,  hit enter

NOTE: you may need to set execute permission for file update.sh with the 
command chmod +x update.sh

 
> Automatic upgrade did not work.
> Now it does not even start anymore.

It would be nice to know what happens exactly
Any ERROR lines in wrapper.conf?
___
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]