[freenet-support] node not self-updating
On Friday 12 September 2008 11:15, Ermanno Baschiera wrote: > Hi, > My node (#1162) is showing this alert: "It seems that your node isn't > running the latest version of the software. Your node will > automatically restart as soon as it has finished downloading and > verifying the new version of Freenet." > Well, it's there since 3 hours at least. Why should it take that long > to upgrade? > Some days ago it was the same with Freenet-ext. The alert stayed on > for several days, until yesterday I ran update.sh. > Note: my node is a seednode. Maybe is seeding preventing the upgrade? > > [could it be useful to add a timestamp to alerts? So I can know > exactly when the alert appeared...] Is it still broken? It seems to work for me, at least with trunk. If it's still broken please send me your wrapper.conf. > > -ermanno -- 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/20080912/d8e25227/attachment.pgp>
[freenet-support] update.sh not working
On Friday 12 September 2008 08:46, Max Giesbert wrote: > hi everyone, > > my node is outdated (build 1160). If I manually run ./update.sh in my > freenet directory I get the message that my node is up-to-date. When i > start it I see it is still build 1160. What's wrong here? You need to manually update your update.sh from downloads.freenetproject.org/alpha/update/ There was a serious bug in update.sh. > > thx > > > max > > P.S. output of: > > $ ./update.sh > Updating freenet > Created temporary download directory. > The SHA1 of sha1test.jar matches > Importing startssl.pem into /tmp/keystore26969.tmp > The CA has been imported into the trustStore > Fetching update.sh > https://checksums.freenetproject.org/latest/update.sh.sha1 > https://checksums.freenetproject.org/latest/update.sh > Downloaded update.sh > Your update.sh is up to date > Importing startssl.pem into /tmp/keystore26581.tmp > The CA has been imported into the trustStore > Fetching freenet-stable-latest.jar > https://checksums.freenetproject.org/latest/freenet-stable-latest.jar.sha1 > https://checksums.freenetproject.org/latest/freenet-stable-latest.jar > Downloaded freenet-stable-latest.jar > Importing startssl.pem into /tmp/keystore43069.tmp > The CA has been imported into the trustStore > Fetching freenet-ext.jar > https://checksums.freenetproject.org/latest/freenet-ext.jar.sha1 > https://checksums.freenetproject.org/latest/freenet-ext.jar > Downloaded freenet-ext.jar > Your node is up to date. > > > > -- 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/20080912/b92f0572/attachment.pgp>
[freenet-support] About Freenet protocol
Hello, I'm a developer from Ukraine. I have to create small Freenet client (file sharing only), but it seems that it is problem to find Freenet protocol specification. Can you tell me, is it closed protocol, or where can I find this specification if it's possible...? Waiting for any news from you. Thank you for your time. With Best Regards, Andrew Surzhenko
Re: [freenet-support] node not self-updating
On Friday 12 September 2008 11:15, Ermanno Baschiera wrote: > Hi, > My node (#1162) is showing this alert: "It seems that your node isn't > running the latest version of the software. Your node will > automatically restart as soon as it has finished downloading and > verifying the new version of Freenet." > Well, it's there since 3 hours at least. Why should it take that long > to upgrade? > Some days ago it was the same with Freenet-ext. The alert stayed on > for several days, until yesterday I ran update.sh. > Note: my node is a seednode. Maybe is seeding preventing the upgrade? > > [could it be useful to add a timestamp to alerts? So I can know > exactly when the alert appeared...] Is it still broken? It seems to work for me, at least with trunk. If it's still broken please send me your wrapper.conf. > > -ermanno pgpX5kUWbPcHd.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]
[freenet-support] node not self-updating
Hi, My node (#1162) is showing this alert: "It seems that your node isn't running the latest version of the software. Your node will automatically restart as soon as it has finished downloading and verifying the new version of Freenet." Well, it's there since 3 hours at least. Why should it take that long to upgrade? Some days ago it was the same with Freenet-ext. The alert stayed on for several days, until yesterday I ran update.sh. Note: my node is a seednode. Maybe is seeding preventing the upgrade? [could it be useful to add a timestamp to alerts? So I can know exactly when the alert appeared...] -ermanno
Re: [freenet-support] update.sh not working
On Friday 12 September 2008 08:46, Max Giesbert wrote: > hi everyone, > > my node is outdated (build 1160). If I manually run ./update.sh in my > freenet directory I get the message that my node is up-to-date. When i > start it I see it is still build 1160. What's wrong here? You need to manually update your update.sh from downloads.freenetproject.org/alpha/update/ There was a serious bug in update.sh. > > thx > > > max > > P.S. output of: > > $ ./update.sh > Updating freenet > Created temporary download directory. > The SHA1 of sha1test.jar matches > Importing startssl.pem into /tmp/keystore26969.tmp > The CA has been imported into the trustStore > Fetching update.sh > https://checksums.freenetproject.org/latest/update.sh.sha1 > https://checksums.freenetproject.org/latest/update.sh > Downloaded update.sh > Your update.sh is up to date > Importing startssl.pem into /tmp/keystore26581.tmp > The CA has been imported into the trustStore > Fetching freenet-stable-latest.jar > https://checksums.freenetproject.org/latest/freenet-stable-latest.jar.sha1 > https://checksums.freenetproject.org/latest/freenet-stable-latest.jar > Downloaded freenet-stable-latest.jar > Importing startssl.pem into /tmp/keystore43069.tmp > The CA has been imported into the trustStore > Fetching freenet-ext.jar > https://checksums.freenetproject.org/latest/freenet-ext.jar.sha1 > https://checksums.freenetproject.org/latest/freenet-ext.jar > Downloaded freenet-ext.jar > Your node is up to date. > > > > pgpkAfJgCaaF3.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]
[freenet-support] update.sh not working
hi everyone, my node is outdated (build 1160). If I manually run ./update.sh in my freenet directory I get the message that my node is up-to-date. When i start it I see it is still build 1160. What's wrong here? thx max P.S. output of: $ ./update.sh Updating freenet Created temporary download directory. The SHA1 of sha1test.jar matches Importing startssl.pem into /tmp/keystore26969.tmp The CA has been imported into the trustStore Fetching update.sh https://checksums.freenetproject.org/latest/update.sh.sha1 https://checksums.freenetproject.org/latest/update.sh Downloaded update.sh Your update.sh is up to date Importing startssl.pem into /tmp/keystore26581.tmp The CA has been imported into the trustStore Fetching freenet-stable-latest.jar https://checksums.freenetproject.org/latest/freenet-stable-latest.jar.sha1 https://checksums.freenetproject.org/latest/freenet-stable-latest.jar Downloaded freenet-stable-latest.jar Importing startssl.pem into /tmp/keystore43069.tmp The CA has been imported into the trustStore Fetching freenet-ext.jar https://checksums.freenetproject.org/latest/freenet-ext.jar.sha1 https://checksums.freenetproject.org/latest/freenet-ext.jar Downloaded freenet-ext.jar Your node is up to date. -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature URL: <https://emu.freenetproject.org/pipermail/support/attachments/20080912/ac374b94/attachment.pgp>
[freenet-support] node not self-updating
Hi, My node (#1162) is showing this alert: "It seems that your node isn't running the latest version of the software. Your node will automatically restart as soon as it has finished downloading and verifying the new version of Freenet." Well, it's there since 3 hours at least. Why should it take that long to upgrade? Some days ago it was the same with Freenet-ext. The alert stayed on for several days, until yesterday I ran update.sh. Note: my node is a seednode. Maybe is seeding preventing the upgrade? [could it be useful to add a timestamp to alerts? So I can know exactly when the alert appeared...] -ermanno ___ 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] update.sh not working
hi everyone, my node is outdated (build 1160). If I manually run ./update.sh in my freenet directory I get the message that my node is up-to-date. When i start it I see it is still build 1160. What's wrong here? thx max P.S. output of: $ ./update.sh Updating freenet Created temporary download directory. The SHA1 of sha1test.jar matches Importing startssl.pem into /tmp/keystore26969.tmp The CA has been imported into the trustStore Fetching update.sh https://checksums.freenetproject.org/latest/update.sh.sha1 https://checksums.freenetproject.org/latest/update.sh Downloaded update.sh Your update.sh is up to date Importing startssl.pem into /tmp/keystore26581.tmp The CA has been imported into the trustStore Fetching freenet-stable-latest.jar https://checksums.freenetproject.org/latest/freenet-stable-latest.jar.sha1 https://checksums.freenetproject.org/latest/freenet-stable-latest.jar Downloaded freenet-stable-latest.jar Importing startssl.pem into /tmp/keystore43069.tmp The CA has been imported into the trustStore Fetching freenet-ext.jar https://checksums.freenetproject.org/latest/freenet-ext.jar.sha1 https://checksums.freenetproject.org/latest/freenet-ext.jar Downloaded freenet-ext.jar Your node is up to date. 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:[EMAIL PROTECTED]
