nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

dd service dying with DAS

marcussteiner

Hi all,

got the following DD problem. Got od-dd-sync up an running fine. Got DAS configured fine for certain datatypes. Both on the same TS box running fine quite a while but then out of the blue the DataDeploy Service seems to have died. When author tries to saves a dcr the DAS process does not to be there anymore and we get the following error:

----------------------
Files by type Smiley Tongue

ortal/standard
----------------------
Temp dir name is C:\ddtemp
File list file: \s7g9.
File list:
templatedata/portal/standard/data/portal/allgemein/abc10

filelistname: C:\ddtemp\s7g9.
Area name: /portal/main/allgemein01/WORKAREA/allgemein1
Base area name: /portal/main/allgemein01/STAGING
Table name: PORTAL_PORTAL_STANDARD__MAIN_ALLGEMEIN01_WORKAREA_ALLGEMEIN1
Basetable name: PORTAL_PORTAL_STANDARD__MAIN_ALLGEMEIN01_STAGING
Basetable prefix: PORTAL_PORTAL_STANDARD
Basetable suffix: MAIN_ALLGEMEIN01_STAGING
my_table prefix: PORTAL_PORTAL_STANDARD
my_table suffix: MAIN_ALLGEMEIN01_WORKAREA_ALLGEMEIN1
deployconfig name: Y:/portal/main/allgemein01/WORKAREA/allgemein1/templatedata/portal/standard/standard_dd.cfg
DataDeploy Command=[cfg="Y:/portal/main/allgemein01/WORKAREA/allgemein1/templatedata/portal/standard/standard_dd.cfg" deployment=deltaupdate myarea="/portal/main/allgemein01/WORKAREA/allgemein1" mybasearea="/portal/main/allgemein01/STAGING" mytable=PORTAL_PORTAL_STANDARD__MAIN_ALLGEMEIN01_WORKAREA_ALLGEMEIN1 mybasetable=PORTAL_PORTAL_STANDARD__MAIN_ALLGEMEIN01_STAGING mybasetablenameprefix=PORTAL_PORTAL_STANDARD mybasetablenamesuffix=MAIN_ALLGEMEIN01_STAGING mytablenameprefix=PORTAL_PORTAL_STANDARD mytablenamesuffix=MAIN_ALLGEMEIN01_WORKAREA_ALLGEMEIN1 myfilelist=C:\ddtemp\s7g9 ]
ERROR: connect: Unknown Error

When I run iwddd.ipl from the command line using the deployment specification above (e.g. iwddd.ipl cfg=......) the deployment works fine and the data is in the database. Strange is to me that the DD service is visible in the services section of the box.

Any ideas why its dying and how I could prevent it from doing so?

Plattform is Windows NT with DD 5.5.2.

Find more posts tagged with

Comments

Migrateduser

Can you check your iwddd.log to see why the DAS daemon went down. what was the last deployment and how did it fail. Also check if there is a hs_err_pid file in your ddhome.

stefanmaier

Hi,

no hs_err_pid file on the system and the last entry in iwddd.log is the following:

UPDATE iwtracker SET UPDATETIME='Thu Oct 23 15:03:20 CEST 2003' WHERE NAME='PORTAL_PORTAL_STANDARD__MAIN_MAKLER01_WORKAREA_MAKLER1'
1 row(s) updated.
Committing database [SV50062:3538?database=TeamSite]...
Deployment[submitlist] Table[PORTAL_PORTAL_STANDARD__MAIN_MAKLER01_WORKAREA_MAKLER1]
-----------------------------------
Tuples inserted : 0
Tuples updated : 1
Tuples deleted : 0
Tuples failed : 0
Tuples rolled back : 0
Tuples skipped : 0
-----------------------------------
Files with EA's [1]
Started : Thu Oct 23 15:03:20 CEST 2003
Finished: Thu Oct 23 15:03:20 CEST 2003

### IWDataDeploy DONE ###

TSchemaHelperCacheManager: Cache size is 2 <= 500, Thu Oct 23 15:32:46 CEST 2003
TSchemaHelperCacheManager: Cache size is 2 <= 500, Thu Oct 23 16:02:46 CEST 2003
TSchemaHelperCacheManager: Cache size is 2 <= 500, Thu Oct 23 16:32:46 CEST 2003

We've got no error or warning in either of the logfiles!!
The dd daemon was then shut down around 17h00 ??
Any ideas?

Migrateduser

we get a similar error...it is very confusing since for us the DD service isnt stopped, it just needs restarted then DAS works fine again. check your iwsyncdb.log for errors...

The error message we received is due to a failure trying to connect to the DataDeploy daemon.
ERROR: connect: No connection could be made because the target machine actively refused it.

---------------------
Eric B.
Federated Investors
AOL IM: arthas76

marcussteiner

thanks for the input but we can't accept this. The daemon dies at least twice a day without letting us know...

is this only on NT boxes with dd version 5.5.2 ?

Migrateduser

Could you please file a case with support

Migrateduser

Can you observe if the Daemon is going down when you logoff from the system. If so this was fixed in DD5.6 Can you upgrade to DD5.6 with patches.
or add the following to your iwdd.ipl -> dd_start() routine:

push @vmargs, "-Xrs";
if ( -f $g_jre_bin) {
my @cmdarr =($g_jre_bin,
@vmargs,
"-classpath",
$g_jre_classpath,
$g_dd_appclass,
$g_iwhome_present);

Migrateduser

we are using win2k servers with dd5.6 (no pathes or sp1 applied yet tho) and experience this issue which is quite severe.

will patching or applying sp1 fix this issue for us?

---------------------
Eric B.
Federated Investors
AOL IM: arthas76

Migrateduser

Could you please report your problem to support.

Migrateduser

we experienced this issue again today (which brought down our production environment). any idea why the DD service would stop working, yet still be up? i can resolve this issue by stopping and restarting the service. i have opened a ticket with IW.

---------------------
Eric B.
Federated Investors
AOL IM: arthas76

marcussteiner

the code snippet psank provided in this thread solved our problem completely.
Are you also on a windows plattform using dd 5.5.2 ?

Thaks a lot for the support!!

Migrateduser

we are on win2k server using DD 5.6....no SPs or patches tho. were you getting the same error as us in the iwsyncdb.log?

ERROR: connect: No connection could be made because the target machine actively

im just sort of wary about changing code in the DD scripts manually, im not sure if IW supports this.

---------------------
Eric B.
Federated Investors
AOL IM: arthas76

intel

Hi,
was this ever fixed? we are having the same problem with DD 5.6 SP1. The service appears to be running in services (on Windows) but the log files tell that it has been stopped.

Weirdly this production machine is the same as our development box (TeamSite version-wise) and we've never had the problem with the development box.
The last lines of iwddd.log are:

Started : Fri Mar 05 15:43:09 GMT 2004
Finished: Fri Mar 05 15:43:45 GMT 2004

### IWDataDeploy DONE ###

TWorkItem: Smiley Very Happy

oIt --- sock=2345 id=275
msg [stop-daemon=yes]
*** stop-daemon ***
Exiting...

Any help or experience would be appreciated.

Cheers
Jason

i_like_smile

By looking at the logs, we found out the problem seemed happen right after "PublishStagingArea" event. Basically, this event will create base tables for each edition and it may consume a lot of memory and resources and hence cause the problem.
The solution we implmented was to enable Event Server and filter certain events including 'PublishStagingArea' and 'DestroyEdition' etc.
Hope this may help.