PLC Deployments not getting kicked off - connection timed out with some completely different server?

Adam Stoller

Environment:

TeamSite / LiveSite 6.7.2.0 (yes - old and no longer supported)

Windows

Background:

Unfortunately - upgrading the software is not an option at this point in time.

PLC deployments from this server used to work.

The servers were all cloned / migrated to new IP addresses.

All the servers appear to be up-and-running fine right now.

However the PLC deployments do not work any more.

Issue:

When the deployment is attempted to be kicked off from the PLC workflow - we get connection timed out error messages for an IP address that references a server for a completely different application, and one that - to the best of our knowledge - was not used for TeamSite / LiveSite before to "clone / migration".

I can find no reference to the IP address or its associated hostname in any file within \Interwoven\*

I can find no reference to the IP address or its assoicated hostname in any of the custom java source code that I know about.

The only information I can find is in the sevletd_out.log (see attached)

Can anyone provide a reasonable pointer for where we should be looking / what we should be looking for to fix this?

Additional notes:

The hosts file on the TSServer - has a single entry for "localhost" (127.0.0.1)

The odnodes.xml file has only two entries "MyLocalHost" and "LiveSiteRuntime" - neither of which match the IP address that appears to be timing out.

I've verified that I can connect to the OD WebService from the TeamSite server

Find more posts tagged with

Comments

Rick Poulin

FWIW your stack trace seems to be using IBM's ILOG rules engine to do something and failing to get a session for it. There doesn't appear to be any reference to that in any of the 7.x code. I don't remember what this looked like back in 6.7, but maybe you can scan your directory structure for anything containing "ilog"?

Adam Stoller

Is this likely to be something "OOTB" - or a component (haven't searched the /iwadmin tree) or something else? (I was not involved in the original setup at this site)

nipper

I completely forgot about ILOG, that was included in TS/LS 6.7

There should be an ilog folder in iw-home

Adam Stoller

There is an iLog directory - but what am I looking for in it? If I can trust Windows Search - there's nothing within that directory that references the IP address or hostname that appears to be causing the timeout errors during the PLC workflow - so I'm still rather confused how it's coming to be an issue in the process

nipper

I have not had great luck with windows search, download grep and try it. Also, did you check the windows registry?

jRules is supposed to be installed on the TS server.

Adam Stoller

I might just write my own with iwperl - easy enough to do and allows me to take care of both 'find' and 'grep' (since grep by itself won't really help - and trying to get stuff downloaded on the server is a pain - I hate windows ;-))

As for the registry - I had forgotten about that - and there are two pairs of hits, but they don't seem to make sense to me as being the source of the issue:

HKEY_CURRENT_USER\Software\Microsoft\Search Assistant\ACMru\5604: 000=<HOSTNAME_OF_IP_ADDRESS>
HKEY_CURRENT_USER\Software\Microsoft\Search Assistant\ACMru\5604: 001=<IP_ADDRESS>
HKEY_USERS\{SID}\Software\Microsoft\Search Assistant\ACMru\5604: 000=<HOSTNAME_OF_IP_ADDRESS>
HKEY_USERS\{SID}\Software\Microsoft\Search Assistant\ACMru\5604: 001=<IP_ADDRESS>

I don't see why / how the "Microsoft Search Assistant" software would be getting referenced by a PLC deployment process - do you?

nipper

More likely it remembed you searched for those values.

Can you look at the PLC WFM and see if you can figure out what step is using jRules and how to turn it off ?

The 6.7.2 docs were pretty sparse

Adam Stoller

Doh - that makes sense - but doesn't help in solving the actual issue. Doing a Perl-based search through everything I can think of right now ....