[AOLSERVER] [ aolserver-Bugs-476328 ] ns_hostbyaddr
Bugs item #476328, was opened at 2001-10-30 03:46 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=103152aid=476328group_id=3152 Category: API: Tcl Group: aolserver3_4 Status: Open Resolution: None Priority: 5 Submitted By: patrick o'leary (pjaol) Assigned to: Nobody/Anonymous (nobody) Summary: ns_hostbyaddr Initial Comment: An system which has no DNS registered with it, will cause the following error [03/Sep/2001:14:44:17][29917.15][-conn5-] Error: could not lookup XX.XXX.XXX.XXX could not lookup XX.XXX.XXX.XXX while executing ns_hostbyaddr [ns_conn peeraddr $conn Under excessive load will cause daemon to fall over. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=103152aid=476328group_id=3152
Re: [AOLSERVER] URGENT AOLSERVER + ACS + SOLARIS
Did you turn on clustering? I think tasks only run on the master in a cluster. Barry Books -Original Message- From: Allan Regenbaum DP [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 30, 2001 8:03 AM To: [EMAIL PROTECTED] Subject: [AOLSERVER] URGENT AOLSERVER + ACS + SOLARIS We are running a production AOLServer 3.3.1 + ad13 on solaris We have 2 machines, duplicates of each other. Machine A suddenly, without error messages stops running scheduled procs !! Machine B continues to perform flawlessly The machine is running acs classic 4.2 tcl, 90% webmail which has been running perfectly well under stress and load for months... Urgent help/suggestions are appreciated .. Allan Regenbaum Digital People
Re: [AOLSERVER] URGENT AOLSERVER + ACS + SOLARIS
Hi Barry .. the machines are decoupled they are in no way dependent upon each other .. I just mentioned that to show that teh setup works perfectly on one machine and is failing on another identical config ... seems that as the production is loade dup something is causing one of our sheculed procs to not return control of the thread, thereby hanging all the other scheduled procs. ? -Original Message- From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Barry Books Sent: Tuesday, October 30, 2001 9:14 AM To: [EMAIL PROTECTED] Subject: Re: [AOLSERVER] URGENT AOLSERVER + ACS + SOLARIS Did you turn on clustering? I think tasks only run on the master in a cluster. Barry Books -Original Message- From: Allan Regenbaum DP [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 30, 2001 8:03 AM To: [EMAIL PROTECTED] Subject: [AOLSERVER] URGENT AOLSERVER + ACS + SOLARIS We are running a production AOLServer 3.3.1 + ad13 on solaris We have 2 machines, duplicates of each other. Machine A suddenly, without error messages stops running scheduled procs !! Machine B continues to perform flawlessly The machine is running acs classic 4.2 tcl, 90% webmail which has been running perfectly well under stress and load for months... Urgent help/suggestions are appreciated .. Allan Regenbaum Digital People
Re: [AOLSERVER] URGENT AOLSERVER + ACS + SOLARIS
I have *always* had a problem with scheduled procs, to the point where I now simply use a cron job and curl to tell AOLserver to do something Michael Allan Regenbaum DP wrote: We are running a production AOLServer 3.3.1 + ad13 on solaris We have 2 machines, duplicates of each other. Machine A suddenly, without error messages stops running scheduled procs !! Machine B continues to perform flawlessly The machine is running acs classic 4.2 tcl, 90% webmail which has been running perfectly well under stress and load for months... Urgent help/suggestions are appreciated .. Allan Regenbaum Digital People
Re: [AOLSERVER] URGENT AOLSERVER + ACS + SOLARIS
Are you exec'ing anything in the scheduled proc? I've seen some weirdness in the past with execs getting hung, although not much recently. I think it was more of an OS (Linux) issue. We've used scheduled procs for years w/o any problems on all of our servers, though we only have a handful (of scheduled procs), like 10. whereas I've read that ACS has lots of them. A suggestion would be to run more complex stuff in detached threads that you launch from the scheduled proc rather than in the scheduled proc itself. Then if it screws up, you won't tie up the scheduler thread. Jim I have *always* had a problem with scheduled procs, to the point where I now simply use a cron job and curl to tell AOLserver to do something Michael Allan Regenbaum DP wrote: We are running a production AOLServer 3.3.1 + ad13 on solaris We have 2 machines, duplicates of each other. Machine A suddenly, without error messages stops running scheduled procs !! Machine B continues to perform flawlessly The machine is running acs classic 4.2 tcl, 90% webmail which has been running perfectly well under stress and load for months... Urgent help/suggestions are appreciated .. Allan Regenbaum Digital People
Re: [AOLSERVER] URGENT AOLSERVER + ACS + SOLARIS
Is this true of detached threads too - no cleanup? We're probably fine, but nice to know when to be extra careful.-Jim Make sure that you explicitly release database handles and ns_sets in scheduled procs. A connection thread has a bunch of cleanup that it does, and none of it gets done from a scheduled proc thread. Pete.
Re: [AOLSERVER] URGENT AOLSERVER + ACS + SOLARIS
On Tue, 30 Oct 2001, Jim Wilcoxson wrote: Is this true of detached threads too - no cleanup? We're probably fine, but nice to know when to be extra careful.-Jim I believe so, but it could just be my paranoia.
Re: [AOLSERVER] nsopenssl page size limit?
Scott Goodwin wrote: This problem was already identified and fixed. I sent Keith an alpha copy of the nsopenssl 2.1 release and he confirmed that it does fix his problem. thanks, Keith! scott, think i could get a copy if it's not too much trouble ? (or point me at one) i think i'm going to exercise this bug soon.. -mike
