Question

I changed the user searchbox runs as in focuseek.cfg and searchbox no longer starts [Linux and OS X only].

Answer 1

If you change the user searchbox runs as the old data files are probably no longer writable by searchbox (they still belong to the old user). The solution is simple: as root run.

# chown -R newuser.newgroup datadir

Where datadir is the path to your searchbox data directory and newuser and newgroup are respectively the new user and group you configured searchbox to run as.

Answer 2

This is most certainly due to incorrect proxy settings: searchbox clients on windows use explorer proxy settings and most proxies don't handle well SOAP calls. Add the server you are trying to connect to the explorer proxy exception list.

Answer 3

searchbox soon after starting, changes the effective user id to the one specified in focuseek.cfg, usually daemon:daemon. If the import directory or any directory leading to it is not readable by that user, as it may happen if, for example, you exported the configuration to root home directory, then searchbox cannot access it and complains.

Answer 4

check your default domain search path on host A. If some domain D is used by default on A and not on B then write X hostname as X.D

Answer 5

check if the file, as well as the directory containing it and any parent directories, are accessible to the user searchbox is running as. The user is specified in focuseek.cfg on linux and osX and in the service properties in windows control panel service manager in windows.

Answer 6

The Control Panel try to avoid misconfigured filter configuration forcing the user to add almost a default filter that let searchbox perform a complete crawling of all configured seeds. To avoid Control Panel adding the default filter you have to:

"cover" all the seeds with at least an include filter
use a stricter filter than the default
if all above does not solve your problem, add an include filter that exactly matches each seed

14.1. Startup problems
I changed the user searchbox runs as in focuseek.cfg and searchbox no longer starts [Linux and OS X only]. I try to connect to searchbox server using a windows client but I get the following error: An error occurred while talking to the server. The error is: SOAP fault: Unknown tag in SOAP Envelope: [an HTML tag]
	I changed the user searchbox runs as in `focuseek.cfg` and searchbox no longer starts [Linux and OS X only].
	If you change the user searchbox runs as the old data files are probably no longer writable by searchbox (they still belong to the old user). The solution is simple: as root run. `# chown -R newuser.newgroup datadir` Where `datadir` is the path to your searchbox data directory and `newuser` and `newgroup` are respectively the new user and group you configured searchbox to run as.
	I try to connect to searchbox server using a windows client but I get the following error: `An error occurred while talking to the server. The error is: SOAP fault: Unknown tag in SOAP Envelope: [an HTML tag]`
	This is most certainly due to incorrect proxy settings: searchbox clients on windows use explorer proxy settings and most proxies don't handle well SOAP calls. Add the server you are trying to connect to the explorer proxy exception list.
14.2. Import/Export problems
I'm using --import and searchbox complains "Path not found: /my/export/dir" but such directory exists (linux os only)
	I'm using --import and searchbox complains "Path not found: `/my/export/dir`" but such directory exists (linux os only)
	searchbox soon after starting, changes the effective user id to the one specified in `focuseek.cfg`, usually daemon:daemon. If the import directory or any directory leading to it is not readable by that user, as it may happen if, for example, you exported the configuration to root home directory, then searchbox cannot access it and complains.
14.3. Crawling problems
I can crawl host X from my server A but not from server B I'm trying to crawl the filesystem and the crawl log says "file not found" but the file exist I want to remove the default filter but controlpanel keeps adding it
	I can crawl host X from my server A but not from server B
	check your default domain search path on host A. If some domain D is used by default on A and not on B then write X hostname as X.D
	I'm trying to crawl the filesystem and the crawl log says "file not found" but the file exist
	check if the file, as well as the directory containing it and any parent directories, are accessible to the user searchbox is running as. The user is specified in `focuseek.cfg` on linux and osX and in the service properties in windows control panel service manager in windows.
	I want to remove the default filter but controlpanel keeps adding it
	The Control Panel try to avoid misconfigured filter configuration forcing the user to add almost a default filter that let searchbox perform a complete crawling of all configured seeds. To avoid Control Panel adding the default filter you have to: "cover" all the seeds with at least an include filter use a stricter filter than the default if all above does not solve your problem, add an include filter that exactly matches each seed

Prev
Chapter 13. Engine administration	Home

Chapter 14. Troubleshooting

14.1. Startup problems

14.2. Import/Export problems

14.3. Crawling problems