Fw: SWISH-e on OS X - not completing.

Just to lift any clouds - bad router took server off line, not Swish-e....

Any other thoughts re:  swish-e on this OS X box?

Thanks,

WB

----- Original Message ----- 
From: "Worth Bishop" <[email protected]>
To: <[email protected]>
Sent: Wednesday, October 18, 2006 10:03 AM
Subject: Fw: SWISH-e on OS X - not completing.


> Well, I allowed swish-e to continue to run, just to see whether a longer 
> time in process would allow the economy mode to complete it's indexing and 
> write out the index file. It seems that the server is now down. Could it 
> be due to swish-e?
>
> While I'm waiting for someone at that remote location to intervene with 
> the server, I thought I'd pose this question again to the list.
>
> Thanks again for any help!
>
> ----- Original Message ----- 
> From: "Worth Bishop" <[email protected]>
> To: "Bill Moseley" <[email protected]>
> Sent: Tuesday, October 17, 2006 4:59 PM
> Subject: Re: SWISH-e on OS X - not completing.
>
>
>> By "finish," I mean that swish-e continues to run (have allowed as long 
>> as a weekend) but does not ever write the output file. I don't know why, 
>> although it doesn't appear to run out of memory or freeze - may be in a 
>> loop, I don't know.  Top shows it continues to use CPU time...
>>
>>
>> Here's the gdb back trace output:
>>
>> (gdb) bt
>> #0  0x90002b48 in strcmp ()
>> #1  0x000085c8 in getentry (sw=0x2522e7a0, word=0x1803400 "Ñu") at 
>> index.c:1090
>> #2  0x00008de8 in addword (word=0x1803400 "Ñu", sw=0x1800400, 
>> filenum=1137, structure=73, numMetaNames=1, metaID=0xd1750066, 
>> word_position=0xbffff784) at index.c:2217
>> #3  0x0000ae68 in indexstring (sw=0x1800400, s=0xbfffdb5c 
>> "\001\232ø:\001\232ø", filenum=1137, structure=73, numMetaNames=1, 
>> metaID=0x1803800, position=0xbffff784) at index.c:2525
>> #4  0x00016e6c in flush_buffer (parse_data=0xbffff738, clear=46589) at 
>> parser.c:1567
>> #5  0x00017c6c in start_metaTag (parse_data=0xbffff738, tag=0xbfffe4b9 
>> "_n", endtag=0xbfffe4b9 "_n", meta_append=0xbfffdcd8, 
>> prop_append=0xbfffdcdc, is_html_tag=-780861338) at parser.c:998
>> #6  0x000182dc in start_hndl (data=0xbffff738, el=0x19adfe4 "_n", 
>> attr=0x418ba0) at parser.c:656
>> #7  0x92cc36b4 in htmlParseCharRef ()
>> #8  0x92cc5398 in htmlCreateMemoryParserCtxt ()
>> #9  0x92cc5c5c in htmlParseChunk ()
>> #10 0x00018540 in parse_chunks (parse_data=0xbffff738) at parser.c:338
>> #11 0x000186fc in parse_HTML (sw=0x1800400, fprop=0x31ea4, fi=0xbffff85c, 
>> buffer=0x80808080 <Address 0x80808080 out of bounds>) at parser.c:256
>> #12 0x000099e0 in do_index_file (sw=0x8, fprop=0x41dc70) at index.c:961
>> #13 0x0000c238 in printfile (sw=0x1800400, filename=0x41dc70 
>> "\001\230ü¼") at fs.c:609
>> #14 0x0000c564 in indexadir (sw=0x1800400, dir=0x405420 
>> "/Library/Tomcat/blojsom_root/webapps/ROOT/blojsom_resources/meta/klandini") 
>> at fs.c:649
>> #15 0x0000c5ec in indexadir (sw=0x1800400, dir=0x401e28 
>> "/Library/Tomcat/blojsom_root/webapps/ROOT/blojsom_resources/meta") at 
>> fs.c:687
>> #16 0x000035a8 in cmd_index (sw=0x1800400, params=0x33358) at 
>> swish.c:1388
>> #17 0x000045ac in main (argc=623044512, argv=0xbffffca4) at swish.c:200
>> (gdb)
>>
>> And 5 minutes later:
>>
>> (gdb) bt
>> #0  CompressCurrentLocEntry (sw=0x1800400, e=0x14890820) at 
>> compress.c:691
>> #1  0x00009ce4 in do_index_file (sw=0x1800400, fprop=0x305978) at 
>> index.c:1045
>> #2  0x0000c238 in printfile (sw=0x1800400, filename=0x41dc70 
>> "\001\230ü¼") at fs.c:609
>> #3  0x0000c564 in indexadir (sw=0x1800400, dir=0x405420 
>> "/Library/Tomcat/blojsom_root/webapps/ROOT/blojsom_resources/meta/klandini") 
>> at fs.c:649
>> #4  0x0000c5ec in indexadir (sw=0x1800400, dir=0x401e28 
>> "/Library/Tomcat/blojsom_root/webapps/ROOT/blojsom_resources/meta") at 
>> fs.c:687
>> #5  0x000035a8 in cmd_index (sw=0x1800400, params=0x33358) at 
>> swish.c:1388
>> #6  0x000045ac in main (argc=25166848, argv=0xbffffca4) at swish.c:200
>> (gdb)
>>
>> Thanks for your help!
>>
>> Worth
>> ----- Original Message ----- 
>> From: "Bill Moseley" <[email protected]>
>> To: "Worth Bishop" <[email protected]>
>> Cc: "Multiple recipients of list" <[email protected]>
>> Sent: Tuesday, October 17, 2006 12:37 PM
>> Subject: Re: SWISH-e on OS X - not completing.
>>
>>
>>> On Tue, Oct 17, 2006 at 08:39:30AM -0700, Worth Bishop wrote:
>>>> Problem:  SWISH-E does not seem to complete indexing large directory 
>>>> (2.1
>>>> Gb, 252 subdirectories, mostly MP3, MP4, m4a files of 1 to 15Mb) on Mac 
>>>> OS X
>>>> box.
>>>
>>> What do you mean by finish?  It keeps running forever?  Is that due to
>>> running out of memory during indexing, or from swish getting stuck in
>>> a loop?  Can you attach with gdb and get a back trace?
>>>
>>> -- 
>>> Bill Moseley
>>> [email protected]
>>>
>>> Unsubscribe from or help with the swish-e list:
>>>   http://swish-e.org/Discussion/
>>>
>>> Help with Swish-e:
>>>   http://swish-e.org/current/docs
>>>   [email protected]
>>>
>>
>