Re: [AOLSERVER] Something wrong after 2006-05-12 21:25 (was Re: Weird "memory leak" problem in AOLserver 3.4.2/3.x)
> All versions of AOLserver 3.3 REQUIRED and shipped with their own > special version of Tcl 8.3.x. So unless you took very special steps > to make it do so, it's very unlikely that your AOLserver is using any > other version of Tcl. I tried once to make AOLserver 3.3+ad13 use a > newer version of Tcl - I failed, and I never heard of anyone else > doing it either. I did some googling and it appears you're right. People did get 8.4 working with AOLserver 3.4, but not 3.3 ... -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Something wrong after 2006-05-12 21:25 (was Re: Weird "memory leak" problem in AOLserver 3.4.2/3.x)
Andrew Piskorski wrote: If all you want to know is the Tcl version AOLserver is using, it's trivially easy, just use the Tcl "info patchlevel" command from inside AOLserver. Right; duh. Thanks. So, the version of tcl my 3.3.1+ad13 sites are using is 8.3.2, and they appear to reboot without the VM and scheduled proc problems. FWIW. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Something wrong after 2006-05-12 21:25 (was Re: Weird "memory leak" problem in AOLserver 3.4.2/3.x)
FWIW, on my boxes where aolserver appears to function correctly, the tcl in the aolserver lib is 8.3: I have a what seems reliable test see if aolserver is working properly. copy off your .ini file modify any Library entries and point them to a new location. in the new location put a .tcl file that schedules a number of ns_logs some with threading (I suggest having the procs run ever second or 2 or 3). also kill any lines that have an auxconfigdir bring up the new server using your new .ini file if the logs stop getting written to you know you have a problem. Zach Shaw Web Developer, Library and Technology Services Brandeis University [EMAIL PROTECTED] 781-736-4206 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Something wrong after 2006-05-12 21:25 (was Re: Weird "memory leak" problem in AOLserver 3.4.2/3.x)
On Thu, May 18, 2006 at 10:03:59AM -0700, Stan Kaufman wrote: > On one box I have tcl 8.3.3 installed generally, and on another 8.4.9 > (as revealed by checking [info patchlevel] from tclsh). But I presume > that in both cases, aolserver is still using the tcl in its lib > directory, correct? Since [ns_info patchlevel] isn't implemented in > 3.3.1+ad13, is there some way to tell for sure which tcl aolserver is using? If all you want to know is the Tcl version AOLserver is using, it's trivially easy, just use the Tcl "info patchlevel" command from inside AOLserver. > Anyway, if it is the case that aolserver is using its own version of > tcl, then the "tcl 8.3.x is the problem" theory wouldn't appear to stand. All versions of AOLserver 3.3 REQUIRED and shipped with their own special version of Tcl 8.3.x. So unless you took very special steps to make it do so, it's very unlikely that your AOLserver is using any other version of Tcl. I tried once to make AOLserver 3.3+ad13 use a newer version of Tcl - I failed, and I never heard of anyone else doing it either. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Something wrong after 2006-05-12 21:25 (was Re: Weird "memory leak" problem in AOLserver 3.4.2/3.x)
Cynthia Kiser wrote: Quoting Gustaf Neumann <[EMAIL PROTECTED]>: It seems, as if all problems are in tcl 8.3.*. But just a data point from the "not happening here" side. I have info patchlevel 8.3.2 FWIW, on my boxes where aolserver appears to function correctly, the tcl in the aolserver lib is 8.3: /usr/local/aolserver/lib/tcl8.3/ On one box I have tcl 8.3.3 installed generally, and on another 8.4.9 (as revealed by checking [info patchlevel] from tclsh). But I presume that in both cases, aolserver is still using the tcl in its lib directory, correct? Since [ns_info patchlevel] isn't implemented in 3.3.1+ad13, is there some way to tell for sure which tcl aolserver is using? Anyway, if it is the case that aolserver is using its own version of tcl, then the "tcl 8.3.x is the problem" theory wouldn't appear to stand. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Trojaned Putty? [Was: Something wrong after 2006-05-12 21:25]
CArole Lahaye wrote: > of virtual memory after a certain date. Instead, my first bet is > that this is a new kind of virus/trojan/... > It must have something to do with Putty: ... > - Now I've entered using Putty (0.5.6) and - what a surprise - > everything crashes now. Note that putty 0.56 had a couple security issues - a trojan installer as well as core security issues. See: http://www.chiark.greenend.org.uk/~sgtatham/putty/ Jeff -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Something wrong after 2006-05-12 21:25 (was Re: Weird "memory leak" problem in AOLserver 3.4.2/3.x)
1) ns_info patchlevel 3.3.1+ad13 8.3.2 2) uname -a Linux my.brandeis.edu 2.4.9-e.68smp #1 SMP Thu Jan 19 18:38:50 EST 2006 i686 unknown 3) glibc version [EMAIL PROTECTED] root]# rpm -qa | grep glibc compat-glibc-6.2-2.1.3.2 glibc-common-2.2.4-32.23 glibc-2.2.4-32.23 glibc-devel-2.2.4-32.23 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Trojaned Putty? [Was: Something wrong after 2006-05-12 21:25]
Since we don't use putty, I don't think that has anything to do with the scheduled procs problem, but you seem to having different issues. Might you have some environment differences between the two different means of logging in? -Titi CArole Lahaye wrote: Hi All, Funny stuff. Never seen in 15 years any server sucking up Gigs of virtual memory after a certain date. Instead, my first bet is that this is a new kind of virus/trojan/... It must have something to do with Putty: - I've restarted our AOLServer 3.3.1ad13 using the Linux shell and there were no issues at all. - Now I've entered using Putty (0.5.6) and - what a surprise - everything crashes now. I could imagine that this is a new type of trojan that exploits a vulnerability in Putty and uses it to inject code into a Linux system that in turn infects another Putty. And this injected code would modify the behavious of pThreads and kill our beloved AOLServer. Could somebody try to confirm this? It's just a theory and I haven't found any proof yet, but it sounds more probable to me then a AOLServer suddently going wild. Even if this theory should prove wrong - It might be a good idea to watch out for such a kind of Trojan, don't you think? Cheers, Frank --- Frank Bergmann Dipl.-Ing., MBA Managing Director ]project-open[ Tel: +34 933 250 914 Cell: +34 609 953 751 Fax: +34 932 890 729 mailto:[EMAIL PROTECTED] http://www.project-open.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] Trojaned Putty? [Was: Something wrong after 2006-05-12 21:25]
Hi All,
Funny stuff. Never seen in 15 years any server sucking up Gigs
of virtual memory after a certain date. Instead, my first bet is
that this is a new kind of virus/trojan/...
It must have something to do with Putty:
- I've restarted our AOLServer 3.3.1ad13 using the Linux
shell and there were no issues at all.
- Now I've entered using Putty (0.5.6) and - what a surprise -
everything crashes now.
I could imagine that this is a new type of trojan that exploits
a vulnerability in Putty and uses it to inject code into a
Linux system that in turn infects another Putty.
And this injected code would modify the behavious of pThreads
and kill our beloved AOLServer.
Could somebody try to confirm this? It's just a theory and
I haven't found any proof yet, but it sounds more probable to
me then a AOLServer suddently going wild.
Even if this theory should prove wrong - It might be a good
idea to watch out for such a kind of Trojan, don't you think?
Cheers,
Frank
---
Frank Bergmann
Dipl.-Ing., MBA
Managing Director ]project-open[
Tel: +34 933 250 914
Cell: +34 609 953 751
Fax: +34 932 890 729
mailto:[EMAIL PROTECTED]
http://www.project-open.com/
> -Original Message-
> From: AOLserver Discussion
> [mailto:[EMAIL PROTECTED] On Behalf Of Dossy Shiobara
> Sent: Wednesday, May 17, 2006 10:35 PM
> To: AOLSERVER@LISTSERV.AOL.COM
> Subject: [AOLSERVER] Something wrong after 2006-05-12 21:25
> (was Re: Weird "memory leak" problem in AOLserver 3.4.2/3.x)
>
>
> On 2006.05.17, Zachary Shaw <[EMAIL PROTECTED]> wrote:
> > We're experiancing a similar issue at Brandeis University,
> but we get
> > no error, our scheduled procs just hang. [...] we're
> running aolserver
> > 3.3.1 ad13 [...] if I set the system date to may 12th or
> earilier all
> > the procs will run. otherwise they run for a little then stop.
> >
> > looking at the straces the difference appears to be in how the
> > nanosleep is set for the pids.
> >
> > before may 13th nanosleep was in the form
> > [pid 614] nanosleep({0, 34478},
> >
> > after the 12th there were nanosleeps in the form
> > [pid 614] nanosleep({9, 934211000},
>
> Dave Siktberg seems to have narrowed it down to 2006-05-12 21:25.
>
> What's interesting is I'm running AOLserver 4.0.10 on
> x86/Linux 2.6.15.6 with glibc6 2.3.5 with no OpenACS and all
> my scheduled procs are firing just fine.
>
> Can we get everyone who's experiencing this problem to provide a few
> things:
>
> 1) ns_info patchlevel
> 2) uname -a
> 3) glibc version
>
> I'm betting this is an older Linux or LinuxThreads or glibc
> problem. I could be wrong, of course, but gathering this
> info will help to figure it out.
>
> -- Dossy
>
> --
> Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/
> Panoptic Computer Network | http://panoptic.com/
> "He realized the fastest way to change is to laugh at your own
> folly -- then you can let go and quickly move on." (p. 70)
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to
> <[EMAIL PROTECTED]> with the body of "SIGNOFF
> AOLSERVER" in the email message. You can leave the Subject:
> field of your email blank.
>
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
