LSCS deployment hanging

jsankara

Hi,

We have teamsite 7.2.1 with LSCS authoring on RHEL.
It has one LSDS/LSCS runtime node(on solaris), workflows are getting stuck on the deployment step. screen shows "Executing deployment 3 of 4..." forever. But I saw (File name too long) meesage in OD log. is this the whole issue ?

Runtime machine logs:
lscs.log:
--------
11-19-12 @ 19:06:15 [INFO ] ImportRequestHandler - Starting import.
It keeps printing the below message:
[DEBUG] 19:21:16 IdolSearchDaoRuntimeImpl - Indexing status for job: 726 status:-7

adp.lscs-import.teamsite-areadiff2cbcca4faaa96f1a6f006d91d356e6dd.MYDEFINITIONNAME.authoring.to.runtime.log
----
....
2012-11-19 19:26:52,461 DEBUG url=http://localhost:9090/lscs/v1/import/
2012-11-19 19:26:52,462 INFO ODHOME = /local/Interwoven/OpenDeployNG
2012-11-19 19:26:52,462 DEBUG Start connecting to LSCS runtime server ...


OD receiver log:
------------
ENG: 2012-11-19 19:26:40 MST GMT-07:00
eterNS="null" async="no"/>
ENG: 2012-11-19 19:26:40 MST GMT-07:00 *** Iterating
ENG: 2012-11-19 19:26:40 MST GMT-07:00 *** Class To Instantiate = com.interwoven.wcm.iwrr.deployment.adapter.delivery.ImportDeliveryAdapter
ENG: 2012-11-19 19:26:40 MST GMT-07:00 *** parameter = lscsRuntimeTransport=http; lscsRuntimeHostname=localhost; lscsRuntimePort=9090; lsc
sRuntimeContext=lscs; deploymentContextId=2cbcca4faaa96f1a6f006d91d356e6dd; destinationArea=/shared/OpenDeploy/lscs-store; projectName=//authoring/default/main/App1; lscsRuntimeKeyStore=null; lscsRuntimeKeyStoreType=null; lscsRuntimeKeyStorePassword=null;
lscsRuntimeTrustStore=null; lscsRuntimeTrustStoreType=null; lscsRuntimeTrustStorePassword=null; lscsRuntimeProtoc
olHandler=${StartDeploy_LscsRuntimeProtocolHandler}
ENG: 2012-11-19 19:26:40 MST GMT-07:00 Manifest Path /local/ecm/Interwoven/OpenDeployNG/log/lscs/rcv.teamsite-areadiff2cbcca4faaa96f1a6f006d91d356e6dd.MYDEFINITIONNAME.authoring.to.runtime1.log.mf
ENG: 2012-11-19 19:26:40 MST GMT-07:00 ***WARNING - lscsRuntimeTransport=http; lscsRuntimeHostname=localhost; lscsRuntimePort=9090; lscsRun
timeContext=lscs; deploymentContextId=2cbcca4faaa96f1a6f006d91d356e6dd; destinationArea=/shared/OpenDeploy/lscs-store; projectName=/authoring/default/main/App1; lscsRuntimeKeyStore=null; lscsRuntimeKeyStoreType=null; lscsRuntimeKeyStorePassword=null;
lscsRuntimeTrustStore=null; lscsRuntimeTrustStoreType=null; lscsRuntimeTrustStorePassword=null; lscsRuntimeProtocolHan
dler=${StartDeploy_LscsRuntimeProtocolHandler} (File name too long)
ENG: 2012-11-19 19:26:40 MST GMT-07:00 Start Executing user class class com.interwoven.wcm.iwrr.deployment.adapter.delivery.ImportDeliveryAdapter in Synchronous mode

Adam Stoller

The "File name too long message" can be ignored (it's annoying, but meaningless as far as I've been able to tell).

Better things to check:

Somewhere (I forget where right now) there's also a temp directory that gets used and may have too many sub-directories in it.With 7.2.1 (vanilla) - if you hit the magic number of 32,000 directory entries (including '.' and '..') in LSCSRT-Store (or the temp directory) - the deployments will fail (usually they fail, they might hang) - after that happens you pretty much need to use the DREINIT (or something like that) directive for IDOL ("lscscontent") and then use the startdeploy.sh script to re-deploy all the assets again.My understanding is that the above issue is resolved with Patch 1 (the process of applying it we're currently within - there's both a TeamSite and LiveSite patch - you need to apply both)However, "hanging" is more often than not a disk space issue - something that OpenDeploy never seemed to deal with gracefully