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/libstdc++.so.6.0.9).
>
>
> 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
	libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00000033c5700000)
	libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x00000033bfa00000)
	libswish-e.so.2 => /opt/pij/lib/libswish-e.so.2 (0x0000002a95577000)
	libz.so.1 => /usr/lib64/libz.so.1 (0x00000033bf800000)
	libm.so.6 => /lib64/tls/libm.so.6 (0x00000033bf600000)
	libc.so.6 => /lib64/tls/libc.so.6 (0x00000033bf100000)
	/lib64/ld-linux-x86-64.so.2 (0x00000033bef00000)

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

-- 
Peter Karman  .  http://peknet.com/  .  peter(at)not-real.peknet.com
_______________________________________________
Users mailing list
Users(at)not-real.lists.swish-e.org
http://lists.swish-e.org/listinfo/users