|
|
|
OK thanks. Please the comments in http://issues.knowledgetree.com/browse/KTS-3785 about this issue too.
I have a little more information that may help to solve this indexing issue:
System: KnowledgeTree 3.5.4c fresh Windows install on Windows server 2003. Config: - When Apache is configured to listen on port 80 ( Listen 80 in httpd.conf ) the indexer works fine. - When Apache is configured to listen on any other port that I tried (even 8080) the indexer does not run. Question: - What other parameters need to be changed to allow the indexer to run on ports other than 80? Also: I do not see the specific fields (server:port in server name row) in my MySQL dms database. Could you please clarify this info. Many Thanks! I've added new configuration settings under Admin => General Settings => Server Settings, where the internal and external ip addresses and ports can be set. For installs off the main web root (source installs) the rootUrl must also be set in Admin => General Settings => KnowledgeTree.
12 12 2008. Tested, Passed and Closed
Latest DMS build used: KTDMS 3.5.4a (2008-12-11 142317) Commercial Test for the following upgrades: - 354 Commercial (Win Server 2003, RHEL5) - 353 OSS (Win Server 2003, Ubuntu 8.04) - 352c Commercial (Win Vista, Ubuntu 8.04) - 352c OSS (Win Vista, RHEL 5) - 346 Commercial (Win Server 2003, RHEL 5) Result: Indexing seems to happen out of the box. tested a Word file after upgrade and install and could search for contents. JC | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Setting the correct server:port in Server name row of config table lets the systems working,
It seems that the migration process puts the wrong value in that table.
Thanks.