Skip to main content.
home | support | download

Back to List Archive

Re: [swish-e] _c is < 0 in uncompress1()

From: at <Peter>
Date: Wed, 01 Aug 2012 10:05:38 -0500
On 8/1/12 9:59 AM, Dr Michael Daly wrote:
> Re: _c is<  0 in uncompress1()
> something went wrong with my cron driven swish-e installation last month.
> This coincided with a reboot of the NAS device its installed on, in the
> process of restoring a C++ library file (/usr/lib/
> Searches of the rebuilt spidered index now produce only this result:
> _c is<  0 in uncompress1()
> (whether searching is via the swish.cgi module or via command line)
> But searches of a non spidered index built prior to the reboot work normally.
> I am hoping there is any easy fix.
> Swish is installed in a chroot environment in /opt, and Cron runs the
> spidering  command overnight:
>   /opt/bin/swish-e -S prog -c
> /share/MD0_DATA/swish-e-files/swish-e-conf/web_2.conf
> I tried recompiling swish, then ran the index command and search worked
> normally...until cron ran overnight. I then found the index file had
> increased in size significanly, and search gave the:
> _c is<  0 in uncompress1() error.

sounds like a problem with your libz (gzip) library being compiled with 
swish-e. I would try re-compiling and verify that you are getting libz 
included. The ./configure output should tell you.

on linux can also ldd the swish-e binary. mine says:

$ ldd swish-e => /usr/lib64/ (0x00000033c5700000) => /lib64/tls/ (0x00000033bfa00000) => /opt/pij/lib/ (0x0000002a95577000) => /usr/lib64/ (0x00000033bf800000) => /lib64/tls/ (0x00000033bf600000) => /lib64/tls/ (0x00000033bf100000)
	/lib64/ (0x00000033bef00000)

^^ notice the path. make sure that is sane on your platform.

Peter Karman  .  .  peter(at)
Users mailing list
Received on Wed Aug 01 2012 - 15:05:46 GMT