Re: [freenet-support] Sometimes can't get to my own node's data
My goof in my email... Q to Y, of course. (Which is what I actually did.) - Original Message - From: Roger Hayter To: [EMAIL PROTECTED] Sent: Friday, December 12, 2003 12:17 AM Subject: Re: [freenet-support] Sometimes can't get to my own node's data In message <[EMAIL PROTECTED]>, Art Charbonneau <[EMAIL PROTECTED]> writes>Thanks for the suggestion, Kevin, but I've been running with>"max-connections" set to 200, and "max-connections-per-server" set to>100. So that shouldn't be the problem, right?> >Someone else suggested setting "threadFactory" to "Q", rather than the>default. I'm trying that.If you look back I think you will see they actually suggested changing it from Q (default) to Y. Also, have you got "dontLimitClients=yes", this exempts connections to your browser from bandwidth limiting?> - Original Message -> From: Kevin Steen> To: [EMAIL PROTECTED]> Sent: Thursday, December 11, 2003 9:37 PM> Subject: Re: [freenet-support] Sometimes can't get to my own node's> data>> On Fri, 2003-12-12 at 04:49, Art Charbonneau wrote:> > I'm running 5050 on ADSL, 2.4 GHz, with Outgoing set to 30,7200> B/s,> > CPU set to normal priority, and store set to 1 gig.> > > > Sometimes Freenet starts up quite normally (for this period in> time)> > and I can get to a few freesites (mainly using bookmarks, in> Netscape> > 7.1), but then I'll go back to the Web Interface to look at info> and> > stats, and I can't get to my own node (like right now).>> This sounds most like you're hitting the limit of connections in> your> browser. If you have one browser window open trying to retrieve> images> for a page (e.g. The Freedom Engine) then your browser will wait for> those connections to finish before trying to download the web> interface> page.>> If you are running Opera or a Mozilla-based browser, there are> instructions in the Freenet README file on how to extend the number> of> connections your browser uses per server.>> -Kevin>> ___> Support mailing list> [EMAIL PROTECTED]> http://news.gmane.org/gmane.network.freenet.support>___>Support mailing list>[EMAIL PROTECTED]>http://news.gmane.org/gmane.network.freenet.support-- Roger Hayter___Support mailing list[EMAIL PROTECTED]http://news.gmane.org/gmane.network.freenet.support ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
Re: [freenet-support] Sometimes can't get to my own node's data
In message <[EMAIL PROTECTED]>, Art Charbonneau <[EMAIL PROTECTED]> writes Thanks for the suggestion, Kevin, but I've been running with "max-connections" set to 200, and "max-connections-per-server" set to 100. So that shouldn't be the problem, right? Someone else suggested setting "threadFactory" to "Q", rather than the default. I'm trying that. If you look back I think you will see they actually suggested changing it from Q (default) to Y. Also, have you got "dontLimitClients=yes", this exempts connections to your browser from bandwidth limiting? - Original Message - From: Kevin Steen To: [EMAIL PROTECTED] Sent: Thursday, December 11, 2003 9:37 PM Subject: Re: [freenet-support] Sometimes can't get to my own node's data On Fri, 2003-12-12 at 04:49, Art Charbonneau wrote: > I'm running 5050 on ADSL, 2.4 GHz, with Outgoing set to 30,7200 B/s, > CPU set to normal priority, and store set to 1 gig. > > Sometimes Freenet starts up quite normally (for this period in time) > and I can get to a few freesites (mainly using bookmarks, in Netscape > 7.1), but then I'll go back to the Web Interface to look at info and > stats, and I can't get to my own node (like right now). This sounds most like you're hitting the limit of connections in your browser. If you have one browser window open trying to retrieve images for a page (e.g. The Freedom Engine) then your browser will wait for those connections to finish before trying to download the web interface page. If you are running Opera or a Mozilla-based browser, there are instructions in the Freenet README file on how to extend the number of connections your browser uses per server. -Kevin ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support -- Roger Hayter ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
Re: [freenet-support] Sometimes can't get to my own node's data
Thanks for the suggestion, Kevin, but I've been running with "max-connections" set to 200, and "max-connections-per-server" set to 100. So that shouldn't be the problem, right? Someone else suggested setting "threadFactory" to "Q", rather than the default. I'm trying that. - Original Message - From: Kevin Steen To: [EMAIL PROTECTED] Sent: Thursday, December 11, 2003 9:37 PM Subject: Re: [freenet-support] Sometimes can't get to my own node's data On Fri, 2003-12-12 at 04:49, Art Charbonneau wrote:> I'm running 5050 on ADSL, 2.4 GHz, with Outgoing set to 30,7200 B/s,> CPU set to normal priority, and store set to 1 gig.> > Sometimes Freenet starts up quite normally (for this period in time)> and I can get to a few freesites (mainly using bookmarks, in Netscape> 7.1), but then I'll go back to the Web Interface to look at info and> stats, and I can't get to my own node (like right now).This sounds most like you're hitting the limit of connections in yourbrowser. If you have one browser window open trying to retrieve imagesfor a page (e.g. The Freedom Engine) then your browser will wait forthose connections to finish before trying to download the web interfacepage. If you are running Opera or a Mozilla-based browser, there areinstructions in the Freenet README file on how to extend the number ofconnections your browser uses per server.-Kevin___Support mailing list[EMAIL PROTECTED]http://news.gmane.org/gmane.network.freenet.support ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
Re: [freenet-support] Sometimes can't get to my own node's data
Thanks, s... I don't even have a clue what "threadFactory" is, but I'll give "Q" a shot. It can't hurt ...much. ;-) - Original Message - From: S To: [EMAIL PROTECTED] Sent: Thursday, December 11, 2003 9:14 PM Subject: Re: [freenet-support] Sometimes can't get to my own node's data On Thu, 11 Dec 2003 20:49:11 -0800"Art Charbonneau" <[EMAIL PROTECTED]> wrote:> I'm running 5050 on ADSL, 2.4 GHz, with Outgoing set to 30,7200 > B/s, CPU set to normal priority, and store set to 1 gig.> > Sometimes Freenet starts up quite normally (for this period in time)> and I can get to a few freesites (mainly using bookmarks, in Netscape> 7.1), but then I'll go back to the Web Interface to look at info and> stats, and I can't get to my own node (like right now).> > If I try 'Node Status Interface', or 'Recent logs', or 'Failure Table',> etc, (even the 'README file'), all I get is 'Waiting for...'. How can> it be that I cannot get to my own node??Your node is probably hitting periods of severe overload. Mine used toconstantly stay at 100% load and die with Out of Memory errors after afew hours. I changed the threadFactory from Q to Y in freenet.ini andthat helped immensely. Even when it's at 100%, I can still pull up theweb interface. Give it a shot and see if it helps you out.-s___Support mailing list[EMAIL PROTECTED]http://news.gmane.org/gmane.network.freenet.support ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
Re: [freenet-support] Sometimes can't get to my own node's data
On Fri, 2003-12-12 at 04:49, Art Charbonneau wrote: > I'm running 5050 on ADSL, 2.4 GHz, with Outgoing set to 30,7200 B/s, > CPU set to normal priority, and store set to 1 gig. > > Sometimes Freenet starts up quite normally (for this period in time) > and I can get to a few freesites (mainly using bookmarks, in Netscape > 7.1), but then I'll go back to the Web Interface to look at info and > stats, and I can't get to my own node (like right now). This sounds most like you're hitting the limit of connections in your browser. If you have one browser window open trying to retrieve images for a page (e.g. The Freedom Engine) then your browser will wait for those connections to finish before trying to download the web interface page. If you are running Opera or a Mozilla-based browser, there are instructions in the Freenet README file on how to extend the number of connections your browser uses per server. -Kevin ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
Re: [freenet-support] Sometimes can't get to my own node's data
On Thu, 11 Dec 2003 20:49:11 -0800 "Art Charbonneau" <[EMAIL PROTECTED]> wrote: > I'm running 5050 on ADSL, 2.4 GHz, with Outgoing set to 30,7200 > B/s, CPU set to normal priority, and store set to 1 gig. > > Sometimes Freenet starts up quite normally (for this period in time) > and I can get to a few freesites (mainly using bookmarks, in Netscape > 7.1), but then I'll go back to the Web Interface to look at info and > stats, and I can't get to my own node (like right now). > > If I try 'Node Status Interface', or 'Recent logs', or 'Failure Table', > etc, (even the 'README file'), all I get is 'Waiting for...'. How can > it be that I cannot get to my own node?? Your node is probably hitting periods of severe overload. Mine used to constantly stay at 100% load and die with Out of Memory errors after a few hours. I changed the threadFactory from Q to Y in freenet.ini and that helped immensely. Even when it's at 100%, I can still pull up the web interface. Give it a shot and see if it helps you out. -s ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
[freenet-support] Sometimes can't get to my own node's data
I'm running 5050 on ADSL, 2.4 GHz, with Outgoing set to 30,7200 B/s, CPU set to normal priority, and store set to 1 gig. Sometimes Freenet starts up quite normally (for this period in time) and I can get to a few freesites (mainly using bookmarks, in Netscape 7.1), but then I'll go back to the Web Interface to look at info and stats, and I can't get to my own node (like right now). If I try 'Node Status Interface', or 'Recent logs', or 'Failure Table', etc, (even the 'README file'), all I get is 'Waiting for...'. How can it be that I cannot get to my own node?? Usually I quit Netscape, do a stop-start on Freenet, then reopen Netscape, and then usually I can get into my node again. Sometimes after a few minutes (like right now! I just checked) access is restored. Why does this happen, and are there any settings (in Configuration, or in freenet.ini) that I can change to prevent it? ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
