New Tagger install

MT 4.1.1, TS 6.5 Win2K

trying to test the cviewer, added the smf files as required and changed runtime to point to perl.

When I log on cviewer, it complains Subject_lookup.db no such file or directory (did I miss a step ?)

When I try to suggest data foe a sample file I get this error (in error log)

1154037668 lvl0 thread1: [SERVER] failed to execute "C:\Interwoven\MetaTagger\conf\processors\CLT\filePath.pl" -crackedText "C:\Interwoven\MetaTagger\conf\tmp\563216748432" -originalText "C:\Interwoven\MetaTagger\conf\tmp\tmp_15762648"

I tried it from DOS shell, it never finishes, though the file is properly cracked, (it is complete) but the perl process does not return.

Where did I screw up ?

Tips/Pointers/RTFMs appreciated

Andy

Find more posts tagged with

Comments

Migrateduser

Hey Andy,

Between 4.1 and 4.1.1, the stock model names were updated to conform to a new naming syntax. It appears that the CIVIEWER updates were not completely tested. To remedy, do the following steps:

- use the attached metatagger.cfg
- rename Subject.smf.civiewer and Industry.smf.civiewer to Taxonomy.Subject.smf and Taxonomy.Industry.smf

As far as testing filePath.pl on the command, remember that it needs a basic metadata record on stdin:

perl.exe "C:\Interwoven\MetaTagger\conf\processors\CLT\filePath.pl" -crackedText "C:\Interwoven\MetaTagger\conf\tmp\563216748432" -originalText "C:\Interwoven\MetaTagger\conf\tmp\tmp_15762648"
< basic.imd

where basic.imd is:

utf_8
english

Migrateduser

Adding attached metatagger.cfg

nipper

Very strange. I needed to rename the smf files since they were for the old mt.cfg.

However I still get the error that filepath failed. However the cracked file is in the conf/tmp dir and it is accurate.

The only errors I see:

1154110163 lvl3 thread1: OP Command: new_protocol

1154110163 lvl3 thread1: Command: process_content

1154110172 lvl2 thread1: failed to execute "C:\Interwoven\MetaTagger\conf\processors\CLT\filePath.pl" -crackedText "C:\Interwoven\MetaTagger\conf\tmp\308015761760" -originalText "C:\Interwoven\MetaTagger\conf\tmp\tmp_15777112"

1154110172 lvl0 thread1: [SERVER] failed to execute "C:\Interwoven\MetaTagger\conf\processors\CLT\filePath.pl" -crackedText "C:\Interwoven\MetaTagger\conf\tmp\308015761760" -originalText "C:\Interwoven\MetaTagger\conf\tmp\tmp_15777112"

any ideas where to go ?

Thanks

Andy

Migrateduser

Odd that there's a space in "fileP ath.pl". Can you check your metatagger.cfg and runtime.cfg ?

Cheers,
Clark

nipper

Messed up cut and paste. There is not space in the initial log.

However I did notice that in the runtime.cfg it defined ipl files and not pl files. I added iwperl for pl as well.

Now it is thinking (been that way for several minutes), so I am hopeful it will complete. No evidence in the logs about it failing and MTSERVER is dominating the taskmanager, so I think it will work.

Nope, failed:

1154120640 lvl0 thread1: [SERVER] Unknown exception.

2 1154119980: Child on port '9095' died
2 1154119980: This child is being terminated
2 1154119981: Launching: mtserver -port 9095 -pp 604 -logLevel 3

Migrateduser

Be sure to install patch 67000. It improves Classifier and Summarizer performance with the new index format.

nipper

slight difference in performance, Thanks Smiley Very Happy

boskovuk

slight difference in performance, Thanks

hi nipper,
I am curious, did you fix the problem (... failed to execute ...) and how?

I am getting identical issue while building indexes (for a set of documents). This is interesting:

I was able to build these indexes 2-3 weeks ago. Everything worked fine (indexes were generated, etc.)

Last week, we upgraded 4.1 to 4.1.1.

I tried to rebuild some of my indexes now and getting the same errors as you did.

Help appreciated ...