[bedevtalk] Zeta trouble

[Zaranthos]

*This message was transferred with a trial version of CommuniGate(tm) Pro*
I've had problems with uptime if I leave terminals or tracker windows 
open. My uptime goes up drastically if don't leave terminal or tracker 
windows running. I easily get 6+ months uptime from Zeta RC2? (never 
installed 1.2x).

Mark Hellegers wrote:
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
>   
>> Mark Hellegers wrote:
>>     
>>> Hi all,
>>>       
>
> [snip my problem]
>
>   
>> Imagine finding you here.. :-)
>>     
>
> Well, I do more than scan the Themis mailinglist for messages. ;)
>
>   
>> Although my days of being a BeOS
>> expert are long gone and I never had a copy of Zeta, it sounds like
>> either an out of memory error (due to a memory leak most likely) or a
>> trip to KDL. I've noticed that somethings will continue to run and
>> respond normally after a KDL, or at least they think they're running
>> normally. I'd bet on the out of memory error though.
>>     
>
> Hmm, according to ps, I still have plenty of memory free.
> Stopping the webserver and the database also don't seem to help.
> I will give it a try though.
>
>   
>> Try this: type the following in a terminal window or in a telnet session
>> before running the web server and postgresql.
>>
>> export NEW_LEAK_CHECK=1
>> export MALLOC_LEAK_CHECK=1
>>
>> That should turn on the memory leak detection. Then start the web server
>> and postgresql from that terminal. Let them run for a while, then shut
>> them down separately. If there's a memory leak, you'll be able to
>> determine it from the output. It'll indicate the number of memory
>> allocations and the type (new/malloc) and a list of stack traces that
>> should help you identify where the memory was allocated, and potentially
>> where it should be freed. You can pop the addresses into a certain dialog
>> in bdb to take a peek. Of course, this is only useful if you have the
>> sources for the web server and postgresql, but it might help. It might
>> not though, because there are/were some memory leaks in BeOS itself, and
>> I'm sure inherited by Zeta...
>>     
>
> Thanks for the explanation. I will try it this weekend.
> I do have the sources to both the webserver and the database, but I hope I
> don't have to go through the postgresql source. if there is a problem.
>
> [snip example output]
>
> Thanks,
>
> Mark
>
>