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

Main branch issue in TeamSite 6.7.1 Installation

vasanthi

Hi,

I installed TeamSite 6.7.1 SP 1 in Solaris 10 box.There were no issues during the installation.After the system reboot,the TeamSite UI is up and running.But there were no items found inside the default store.I run the iwstat cmd and found that default,iwadmin & workflow are running.

Attached are the log files.Can anyone please help me out in resolving the issue..

iwserver.log
iwtrace.log
servletd_out.log

Find more posts tagged with

Comments

Adam Stoller

Hi,

I installed TeamSite 6.7.1 SP 1 in Solaris 10 box.There were no issues during the installation.After the system reboot,the TeamSite UI is up and running.But there were no items found inside the default store.I run the iwstat cmd and found that default,iwadmin & workflow are running.

Attached are the log files.Can anyone please help me out in resolving the issue..

iwserver.log
iwtrace.log
servletd_out.log

Was this an upgrade over an existing TS installation (if so what was the old version), a fresh installation on a new box with a copy of an old backing store (from what version) or some other scenario (what)?

It's clear that your log files have lots of errors displayed within them - have you considered trying to work your way through the errors?

For instance, is the backing store on the local disk of the TS server, or is it being mounted from some other device (SAN, NAS, etc.)? - the existence of all those "Stale NFS handle" error messages is a clear indication that something isn't right.

Was the installation performed by someone logged in as 'root', through sudo, or through some other user account?

There are lots of possibilities - but most of them are things that only you can determine because you're in the environment.

vasanthi

Thanks for your response.

Its a fresh installation.
Once I completed my TS, SP and patch installations, I was able to login in TeamSite ContentCenter UI. I could see default and iwadmin stores. But no branches were created in any of the stores. It was not mounted properly.

I deactived a store (default) and created a new store called (default01) using iwstoreadm -a. The store created and mounted properly. I can see the main branch in default01. Moreover, there was no problem in mounting. It happened automatically.

Then I tried to activate default store again. But the same problem persists. It happens only for default and iwadmin stores that had created automatically during installation. Not with manually created stores.

Please throw some lights.

GroupingMultiColumns.zip

buddha1

Hi Vasanthi,
I doubt regarding the path of the mount point during the installation. When this mount path is incorrect or if we give the store and mount path the same, there are the chances of getting this problem. Please verify the path of mount during installation.

Reghunath

Can you check whether the teamsite process got access to read/write files under the mount directory?

tirrudev

Can you check in your iw.cfg what is the value of:

store_directory_default in iw.cfg

vasanthi

Thanks for all your response.

store_directory_=/path/to/backing/store.This line is commented out in iw.cfg.

Aslo, we were able to see the folder main in the /iwserver/default and the main contains the Staging,WORKAREA and Edition inside.

The problem is clear that the default and iwadmin stores were not mounted properly, because inside the cms-store/iwmnt (ie mount path which we have given during installation) there were only default and iwadmin folders but no main folders inside that(both in back-end and in UI).

Mount Path ---- > cms-store/iwmnt
Store Path -----> cms-store/iw-store

Please post your suggestions, which may help us in resolving this issue.

Thanks,

hyperlink.gif

vasanthi

Hi,

Finally we got the solution.The TeamSite was incompatible with the latest OS Solaris patches.We downgraded the patch and then it works good..

Thanks to all for their contribution.

Thanks
Vasanthi P

Grouping Addresses.zip

srosewall

From the Autonomy Support website:

Sun recently released an update to Solaris 10 - 9/10 (update 9) kernel patch 142909-17 which changed the internal structure in nfs. TeamSite's filesystem driver has a dependency to the nfs internal structures causing it to be incompatible with this kernel patch. Autonomy recommends that all customers running TeamSite on Solaris should not apply this kernel patch until a software update is available to address this incompatibility. Please contact Autonomy Technical Support for more information or for availability of the software update to TeamSite.