[ic] Interchange on FreeBSD
Karl M. Joch
k.joch@kmjeuro.com
Thu, 7 Dec 2000 11:37:15 +0100
i would encourage you to upgrade. there was lot of good changes between 3.4
and 4.2. but for sure only after finding why it crashes. i descided to do a
cvsup/buildworld on the testbox today and investigate the problem. i have
one xxx shop running and there the traffic is really very high. upgrading
mysql to 3.23.x and rebuilding all tables with mysqldump/reload brought some
advantages and exra speed (14 Mio record at the moment).. The out of memory
error i only had when doing a wrong query on a big table. but you can set
the resources in login.conf to not affect the whole system. crashing with
out of memory sometimes also destroys the mysql key file with mysql 3.22. on
3.23 i never had that since now. running isamcheck -s in crontab helps you
to see this problem as soon as possible.
the crashes i have here results in a core dump without logging anything. so
its a little bit hard to debug. i hate debugging production boxes. and on
the test box its hard to have that effect. at the moment i know that the
lycos spider crashes MV when running down the pages. furthermore there is
alexa.com which has a really bad configured spider. since i blocked the
whole class C of alexa.com crashes are less.
will let you know when finding out more.
regards,
karl
-----Ursprüngliche Nachricht-----
Von: jojo@buchonline.net <jojo@buchonline.net>
An: interchange-users@minivend.com <interchange-users@minivend.com>
Datum: Donnerstag, 7. Dezember 2000 10:18
Betreff: Re: [ic] Interchange on FreeBSD
>On 7 Dec, Karl wrote:
>> Actually there was some changes in FreeBSD 4.2 compared to 4.1.1 and <. I
>> found out the on the Boxes witch hat Minimate included MV 3.x crashes.
>> Installing 4.6.1 had some troubles. but i still havnt found out the
problem.
>> I also have a 5.0 box (also known as -current). Here it is more or less
>> impossible to install IC. (got it to run, but ....).
>>
>> since 4.2 MV 3.x crashes alot on all 5 servers running MV. i am working
on
>> checking the diffs between 4.1.1 and 4.2 to find a solution.
>>
>> best regards,
>>
>> karl
>
>I use FreeBSD 3.4-STABLE, MV 3.xx, MV 4.04 and IC 4.6.1. If I use
>LowTraffic and not HighTraffic, all MV and IC stuff run stable without
>any trouble or problem. But if I use HighTraffic, IC crash under high
>traffic. I try to find out the cause of this crash. After removing # to
>get "::logGlobal..." working and setting the DEBUG on. I noticed a
>message like
>
>--------snip------------
>..
>..
>main:debug: arg is
>main:debug: 5 - session name='94qAspmZ:192.168.1.10'
>main:debug: 6 - session name='94qAspmZ:192.168.1.10'
>main:debug: end dispatch: 0.015625 0.0546875 0 0
>main:debug: 6 - session name='94qAspmZ:192.168.1.10'
>main:debug: 7 - session name='94qAspmZ:192.168.1.10'
>main:debug: closed all: 0.015625
>main:debug: end dispatch: 0.03125 0.046875 0 0
>main:debug: 6 - session name='u94qAspm:192.168.1.10'
>main:debug: 7 - session name='u94qAspm:192.168.1.10'
>main:debug: closed all: 0.03125
>
>ge in malloc(): warning: recursive call.
>ge in malloc(): warning: recursive call.
>Out of memory!
>ge in free(): warning: recursive call.
>ge in free(): warning: recursive call.
>ge in free(): warning: recursive call.
>ge in malloc(): warning: recursive call.
>Out of memory!
>ge in malloc(): warning: recursive call.
>Out of memory!
>Callback called exit.
>END failed--cleanup aborted.
>ge in free(): warning: recursive call.
>ge in free(): warning: recursive call.
>ge in free(): warning: recursive call.
>ge in free(): warning: recursive call.
>..
>..
>..
>ge in free(): warning: recursive call.
>ge in free(): warning: recursive call.
>ge in free(): warning: recursive call.
>ge in malloc(): warning: recursive call.
>Out of memory!
>main:debug: session='' cookie='' chost=''
>main:debug: befor newsession
>Vend::Session:debug: new session id= name=
>Vend::Session:debug: 0 - open_session: File_sessions= Sub=
>Vend::Session:debug: 2 - open_session: File_sessions=1 Sub=CODE(0x84277e4)
>Vend::Session:debug: 6 - open_session: File_sessions=1 Sub=CODE(0x84277e4)
>Vend::Session:debug: 7 - open_session: File_sessions=1 Sub=CODE(0x84277e4)
>Vend::Session:debug: 1 - new session id=4qAspmZz name=
>Vend::Session:debug: 2 - new session id=4qAspmZz name=
>Vend::Session:debug: 3 - new session id=4qAspmZz name=
>Vend::Session:debug: 4 - new session id=4qAspmZz
name=4qAspmZz:192.168..1.10
>Vend::Session:debug: init session
>Vend::Session:debug: end init session
>Vend::Session:debug: 5 - new session id=4qAspmZz
name=4qAspmZz:192.168..1.10
>main:debug: session name='4qAspmZz:192.168.1.10'
>main:debug: 1 - session name='4qAspmZz:192.168.1.10'
>main:debug: 2 - session name='4qAspmZz:192.168.1.10'
>main:debug: 4 - session name='4qAspmZz:192.168.1.10'
>main:debug: arg is
>main:debug: 5 - session name='4qAspmZz:192.168.1.10'
>main:debug: 6 - session name='4qAspmZz:192.168.1.10'
>main:debug: end dispatch: 0.0234375 0.046875 0 0
>main:debug: 6 - session name='4qAspmZz:192.168.1.10'
>main:debug: 7 - session name='4qAspmZz:192.168.1.10'
>main:debug: closed all: 0.0234375
>--------snip------------
>
>and then, all of MV or IC Servers exit at the first exit(0) in the sub
>function server_both (Server.pm) and $! and $? has "No such process".
>
>I try to debug interchange with "perl -d bin/interchange -u". But I get
>problem to get it working, because the debugger don´t know which tty
>should the debugger print the output? If after starting the debugger
>and typing the command "O TTY=tty" or "O TTY=/dev/tty", the first
>Server ist starting and then, the next problem at the second fork. The
>debugger has trouble to get the TTY by DB::fork_TTY().
>
>Are there a way to debug the IC programs at the real time like "perl -d
>...." ?
>
>Thanks!
>
>Joachim
>
>--
>Hans-Joachim Leidinger
>buch online jojo@buchonline.net
>Munscheidstr. 14 FAX: +49 209 1671441
>45886 Gelsenkirchen FAX: 0209 1671441
>
>
>_______________________________________________
>Interchange-users mailing list
>Interchange-users@www.minivend.com
>http://www.minivend.com/mailman/listinfo/interchange-users