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

Teamsite suddenly gets crashed

ridzi

We are receving this typical error evrytime the teamsite goes down:
ERROR:5000068: Unable to establish connection with server,

iwstat --> command

we have gone through multiple logs like,
error.log,servletd.log,iwtrace.log,iwjoberrors.log ,iwevents.log but we are still not able to pin point the root cause.

what could be the possible reasons of this sudden crash?
1) too many files for deployment?
2) CPU/Memory of linux server
3) any other cause?

version is 6.2
appreciate any qucik help/comments.thanks

Find more posts tagged with

Comments

Adam Stoller

Wow, 6.2 is pretty old, but I think all the applications logs are in IWHOME/local/logs and IWHOME/local/logs/iwui by default, so if you cannot find anything in those logs (or even if you can) you should probably look at OS logs (e.g.: /var/log/* or wherever Linux stores such things - check with your local SysAdmin)

In terms of causes:

Rick Poulin

ERROR:5000068: Unable to establish connection with server

The cause could be any number of things, but the above error implies that it's your iwserver process that's dying and not (necessarily) any of the related services. As such, you should concentrate your efforts on monitoring the health of that process and keeping a close eye on iwserver.log + iwtrace.log. Use the timestamp of the death of that service to check across all other logs for activity immediately prior. You should also run an iwfsck to check the integrity of your content store.

mart2001

Was there ever a version 6.2 release? You can use the command "top" on a linux box to monitor the cpu and memory usage. Are you adding the files to your workflow through external task? There are kb articles about setting file listing if your line is too long. For other causes, it could be a number of things.

We are receving this typical error evrytime the teamsite goes down:
ERROR:5000068: Unable to establish connection with server,

iwstat --> command

we have gone through multiple logs like,
error.log,servletd.log,iwtrace.log,iwjoberrors.log ,iwevents.log but we are still not able to pin point the root cause.

what could be the possible reasons of this sudden crash?
1) too many files for deployment?
2) CPU/Memory of linux server
3) any other cause?

version is 6.2
appreciate any qucik help/comments.thanks

Adam Stoller

Was there ever a version 6.2 release? .

Good question - I thought that sounded odd.

There were 6.2.x releases for OpenDeploy - but not TeamSite. I believe TeamSite jumped from 6.1.0 to 6.5.0

nipper

Good question - I thought that sounded odd.

There were 6.2.x releases for OpenDeploy - but not TeamSite. I believe TeamSite jumped from 6.1.0 to 6.5.0

Correct, there was no 6.2 for TeamSite, only OpenDeploy

ridzi

Thanks a lot for your responses. I tried to get as much information as I could and below they are.

The Interwoven Teamsite version we are using is 6.5 not 6.2 as mentioned earlier.

•CPU and Memory (as you indicated)?
You didn't indicate how many CPUs nor how much memory you have on the server)
Ans: There are 8 CPU's being used for this with 1200 Mhz Capacity.
Memory size: 8192 Megabytes

•Is this a physical standalone server or a virtual server?
Ans: It's physical standalone server.

•What else, besides TeamSite (and OpenDeploy) is running on the server in terms of enterprise / application software?
Ans: This is a dedicated server for Teamsite.

•Any antivirus programs running?
I could not get this info.

•How many users are beating on the box?
Ans: The user login during Pick hours is close to 200.

•How many deployments do you tend to run concurrently (ball-park)?
Ans: I have seen not more than 10 deployment concurrently going on.

•How many target nodes are there per deployment (ball-partk)?
Ans: The target nodes are different for diferent environments. For each non-prod environment we have 2 target nodes. For Prod we have 3 target nodes.

When this error occurs, iwstat does not give an results and shows the error as mentioned earlier. At the same time, users can not login to the UI which displays the same details.
So far the resolution has been to reboot the servers.

Please let me know what else can be a reason for this issue. This application is really critical for us. Any help in this regard would be appreciated.

Thanks

Adam Stoller

The server sounds like it's sized well - so I don't think it's a [basic] resource issue. You should probably also check how many inodes are allocated to the file system - but my guess is that's okay too.

If you haven't already, you should open a case with Support.

There might be something simple, but then again, you may need to re-install some or all of the application since it's clear that something isn't very happy.

rpoulin's suggestion of closely monitoring the log files - including OS system logs for around the period of time when the server goes down - is very good advice.

mart2001's reference to external tasks in workflows, while good advice, probably doesn't have anything to do with this issue.

You probably should run an iwfsck -d on your backing store - it may not uncover the problem, but it could uncover additional issues that were caused by the problem - and which need to be taken care of.

I'd still recommend finding out if there's any anti-virus software running on the system.

Lastly - for completeness sake if nothing else - what OS are you running (including version information)?

nipper

With the amount of detail you have provided, there is little we can do here to help debug.

I hope you are talking to support.

If you want more help from DevNet you need to provide more information.

I do not believe you say what OS you are running. That may be the problem, 6.5 is very old, it may not be supported on the OS you are running (if you have done OS upgrades to the server or patches).

Put some logs on dropbox or other sharing server and provide the link. Trace and iwserver are the most important. Or trim them down to under 1 meg and post them here. Also, run TOP (if unix) and post the output.

The last point is that 6.5 is EOL (end of life), having been release in 2006 or so, upgrading may be your only choice.