1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85
|
* The index is huuuuge ! How can I make it smaller ?
The format of Xapian indexes is optimized for writing. Once all documents
have been indexed, compacting the index may reduce its size quite
significantly. If you have Xapian >= 1.0.6, xapian-compact will let you do
that. Stop the daemon and run the following commands :
$ mv ~/.pinot/daemon ~/.pinot/backup-daemon
$ xapian-compact ~/.pinot/backup-daemon ~/.pinot/daemon
This may take a little while. Once xapian-compact has completed, restart
the daemon with :
$ pinot-dbus-daemon -i
The -i parameter instructs the daemon to ignore the index version number,
which may not have been set in the compacted index.
You may also want to disable support for spelling and enable stopwords
removal. See the README for more details.
* Memory usage is too high ! How can I reduce it ?
Since 0.92, Pinot hints at the OS that it can reclaim unused memory on a
regular basis. This works on Linux but maybe not on other OSes.
If your system is memory constrained, you can :
- increase the frequency at which memory is returned to the OS by setting
MALLOC_TRIM_THRESHOLD_ to a value lower than 128kb (the default) :
$ export MALLOC_TRIM_THRESHOLD_=65536
- reduce the number of documents Xapian buffers in memory before changes
are flushed to the disk (default is 10000) :
$ export XAPIAN_FLUSH_THRESHOLD=1000
Note that the daemon explicitely flushes the index once it has crawled one
of the directory configured in Preferences.
If the above doesn't help and there is a large number of big documents to
index, you may want to configure Pinot to index your corpus in stages.
* Pinot doesn't use my favourite browser XYZ to open HTML documents
Even if you have set XYZ as your favourite Web browser in your desktop
environment, it may not be setup as the default application for HTML files.
In Gnome for instance, one has to select XYZ as default for all HTML files
using Nautilus (Properties dialog, Open With tab). This applies to
applications for any other file type.
* If you experience segfaults at startup and you are on Fedora, chances are
it's because of libxml++/libsigc++. See this Bugzilla entry :
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=178592
The latest version seems to fix this issue.
* If the daemon crashes with a backtrace pointing at boost::pool_allocator<>,
rebuild with the configure option "--enable-mempool=no".
* If the daemon crashes seemingly randomly while indexing, it may be because
SQLite wasn't built thread-safe. I have witnessed this mostly on dual CPU
machines, but others are not immune. Try rebuilding SQLite by passing
"--enable-threadsafe --enable-threads-override-locks" to configure.
* If you have built Pinot from source, make sure you have done a "make install".
Pinot will fail to start if it can't find stuff it needs, its icon for
instance.
* If "make install" fails with an error about Categories in pinot.desktop
and you have desktop-file-utils 0.11, either downgrade to 0.10 or upgrade
to 0.12 if possible, or edit the top-level Makefile and replace the line
@desktop-file-install --vendor="" --dir=$(DESTDIR)$(datadir)/applications pinot.desktop
with
$(INSTALL_DATA) pinot.desktop $(DESTDIR)$(datadir)/applications/pinot.desktop
and run "make install" again.
* On FreeBSD, threading issues may cause the daemon to crash unexpectedly.
A fix is to add the following lines to /etc/libmap.conf (which may not exist) :
[/usr/local/bin/pinot-dbus-daemon]
libpthread.so.2 libc_r.so.6
libpthread.so libc_r.so
[/usr/local/bin/pinot]
libpthread.so.2 libc_r.so.6
libpthread.so libc_r.so
* If you are using KDE 3.* and pinot-dbus-daemon does not autostart, symlink
the file /etc/xdg/autostart/pinot-dbus-daemon.desktop to either
$(kde-config --prefix)/share/autostart (for all users) or ~/.kde/Autostart
(current user only).
* If you suspect search failed to find a particular document, you may take
a closer look with
pinot-index --check --showinfo --backend xapian --db ~/.pinot/daemon/ /path/to/file
This will output metadata about the document for the given file, including
a document ID. Xapian's delve utility will let you take a peek at the list
of terms this document holds with
xapian-delve -r DOCUMENT_ID ~/.pinot/daemon/
|