History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: KTS-3882
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Priority Two: Important Priority Two: Important
Assignee: Megan Watson
Reporter: Renato
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
KnowledgeTree Community Edition

Indexer not working

Created: 28/Oct/08 12:32 AM   Updated: 12/Dec/08 11:29 AM
Component/s: Indexing
Affects Version/s: STABLE 3.5.4
Fix Version/s: STABLE 3.5.4a

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: Windows server 2003, Windows server 2000, Windows Vista
Issue Links:
Duplicate
 
This issue is duplicated by:
KTS-3918 indexer tries to connect to apache at... Priority Two: Important Closed
Similar
This issue Similar to:
KTS-3500 Scheduler - Task: Indexing error in l... Priority One: Required Closed
This issue Similar to:
KTS-3785 Indexing does not appear to be happen... Priority Two: Important Closed


 Description  « Hide
Tested windows stack upgrade from 3.4.6 on three different Windows environment and document can't be indexed.
They stay in the queue, the scheduler runs but nothing happens.

The default parameters in System configuration are ok, or they have to be corrected?

Thank you for your help.

 All   Comments   Work Log   Change History      Sort Order:
Renato - [28/Oct/08 08:53 AM ]
Problem solved.
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.

Kevin Fourie - [28/Oct/08 09:09 AM ]
OK thanks. Please the comments in http://issues.knowledgetree.com/browse/KTS-3785 about this issue too.

Craig - [19/Nov/08 08:06 PM ]
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!

Megan Watson - [25/Nov/08 11:37 AM ]
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.

Jarques - [12/Dec/08 11:29 AM ]
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