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; } } }

TS Server going down when create/save file in workarea

GomathiP

TS Server is going down, host also not reachacle when save workarea file from editor (not from UI). Restarting all the services again and server is cuming up. We face same issue when execute code also.

Recently we migrated content store to new server from existing server. All functions are working fine except this. It's completly stopping our work. Please let us know whether we missed to do any operation in new server.

Warm Regards,
Gomathi

Find more posts tagged with

Comments

nipper

This will take a lot of looking. No clue. What OS ? What version of TS ? What version/OS did the backingstore come from ? Was iwmigrate run ? Were users migrated ? What type of users/groups (OS/LDAP/TS)

Where would I look ? Permissions of iwts/iwui, all logs

Bhargav Coca

TS Server is going down, host also not reachacle when save workarea file from editor (not from UI). Restarting all the services again and server is cuming up. We face same issue when execute code also.

Recently we migrated content store to new server from existing server. All functions are working fine except this. It's completly stopping our work. Please let us know whether we missed to do any operation in new server.

Warm Regards,
Gomathi

First of all Open a support case, seems like there is lot more than one issue here.

When you said All functions are working except this (Doing something not from UI) see whats happening if you work only frm UI?

Thanks

GomathiP

Existing Server Detail
--------------------
OS : Solaris 10 (Generic_139555-08)
TeamSite : 7.2.0 Build 1653 Interwoven 20100617

New Server Detail
-----------------
OS : Solaris 10 (Generic_142909-17)
TeamSite : 7.2.0 Build 1653 Interwoven 20100617

Created tar of iw-store in old server and extracted the same in target server to migrate content store. We don't run iwmigrate. User are OS & TS users. Yes all users are migrated from existing to new server, group mapping also done.

I created support case also, meanwhile I raised quiery here also. I may get some useful information here also, that's why I raised query in devnet also.

I don't get useful information in any of the log. I don't get any issue when i save non workarea files, so I don't know what I have to fix.

Any clues on this issue will help me to solve this ASAP.

Warm Regards,
Gomathi

Adam Stoller

Existing Server Detail
--------------------
OS : Solaris 10 (Generic_139555-08)
TeamSite : 7.2.0 Build 1653 Interwoven 20100617

New Server Detail
-----------------
OS : Solaris 10 (Generic_142909-17)
TeamSite : 7.2.0 Build 1653 Interwoven 20100617

Created tar of iw-store in old server and extracted the same in target server to migrate content store.

GomathiP

* Root created & extrated tar
* I'm not sure whether users & groups permissions set properly, pls let me know how to validate that
* And I didn't run "iwfsck -d" in existing & new server. Whether this create issue?

Warm Regards,
Gomathi

Adam Stoller

* Root created & extrated tar
* I'm not sure whether users & groups permissions set properly, pls let me know how to validate that
* And I didn't run "iwfsck -d" in existing & new server. Whether this create issue?

Warm Regards,
Gomathi

[As root] Look at the owner and group permissions of the files within the backing store on both servers and verify that they look identical.

At your earliest convenience, run iwfsck -d on both systems, capturing the output in log files, and compare the results.

The goal of the above is to try to identify or rule-out variables that may be involved in the issue.

kailash1

You mentioned "TS Server is going down". You need to be more specific here. Did you take a look what services of TS Server is going down. Is it iwserver or UI services (Jboss). Please start with iwtrace.log then look at server.log and content center.log to start with.