Platform: Linux
TeamSite Version: 6.7.1
Content Store: Located on a NFS Share mounted on version 2

I was involved in a project where the UNIX team said they do not support nfs version 2.  This was seen as a major problem as on an Interwoven article it clearly states only nfs version 2 is fully supported by Interwoven.

After speaking with Interwoven Support and Engineering, they confirmed NFS version 3 is supported on Linux

Platform: Linux
TeamSite Version: 6.7.1
Content Store: Located on a NFS Share mounted on version 2

I was involved in a project where TeamSite reported the following warning in the iwtrace.logs

Warning: disk low    “/local/data/interwoven/iw-store/workflow”    Less than 50000 inodes (0 free of 0 inodes).

Cause:

This was diagnosed, and the following diagnosis was made

- The server reported a low number of inodes.
– ‘df -i’ showed that there were inodes at all (available, used and free) on the interwoven nfs share.
- This issue was triggered during diagnosis of a nfs lock (refer to content store lock article)
- netapp filer is confused when NFS share is mounted both as nfs v2 and nfs v3.

Solution:

Mounting the interwoven nfs share under nfs v3

I was recently involved in a upgrade of TeamSite 6.1 to 6.7.1, and had to migrate the old 6.1 content store to the new 6.7.1 content store format.  To do this I decided I would add a new 6.7.1 format content store to TeamSite, and thereafter run my migrate commands.

To add an additional Content Store to TeamSite, you need to execute the following;

1. Browse to the file iw.cfg (On  Solaris/Linux this is located in /etc/.  On Windows iw-home/etc/)
2. Add the following lines to the file under the [iwserver] section
   

   store_directory_new-store=/local/data/interwoven/new-store
   store_comment_new-store=New TeamSite Store

   The 1st line names the store and points to the location of the new store.  The 2nd line is optional, but adds comments to the store

3. Save the file and do a iwreset
4. Navigate to iw-home/bin and run the command iwstoreadm -a new-store (new-store is the name of the content store name inputted in point 2)

5. You should now get a message appearing store has been added.
   
6. You can further verify this by running the command,
   
   iwstoreadm -l (This will display all active stores TeamSite are pointing to with comments)
   
7. You now have another content store added to TeamSite
   

I experienced a situation where I found my TeamSite Content Store locked.  This meant that TeamSite would not start if it was pointed to the locked content store.

The Solution:

1. Stop TeamSite (May already be out of service due to the lock Content Store)
2. Remove ‘LOCKFILE’ files in the Content Store sub-directories (e.g. C:\iw-store)
3. Point to the Content Store.  To do this you have 2 options;
   • Set the Content Store as the Default Content Store.  For this browse to iw-home/etc/.  Edit the file defaultiwstore to point to the content store location.  On Solaris/Linux you would browse to /etc/
   • Add a Content Store – Refer to Add Content Store Blog Article
4. Start the TeamSite Service – You should now have you content store unlocked and working in TeamSite

If you get the below issue when trying to edit or view a page in LiveSite then check whether the server has run out of disk space:

“An error occurred while getting the page”

In the servlet_out.log file you may also see the following:

"Caused by: com.interwoven.livesite.common.business.BusinessException: Failed to get page //snt2k020/default/main/UK/WORKAREA/Content/sites/one/home.page
 
        at com.interwoven.livesite.business.BusinessPage.getTemplate(BusinessPage.java:771) 
        at com.interwoven.livesite.business.BusinessPage.getPage(BusinessPage.java:636) 
        at com.interwoven.livesite.business.BusinessPage.verifyChecksum(BusinessPage.java:188) 
        ... 40 more 
Caused by: java.io.EOFException 
        at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2228) 
        at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2694)

and in the /var/adm/eventsubd.log you may see the following

"Error: CRITICAL: page header magic for block 1 not OK 0"

The most likely cause is a problem with the /iw-home/eventsubsystem/openjms.db file.

Move this file to another area (it may be very large and have taken up 100% disk space under iw-home – you can check this by doing a ‘df -k’ command and looking at the results)

Also delete openjms.lock and openjms.lg in the same folder.

Re-start TeamSite and it should re-create this file (it may be the same size when you “ls -la” but on disk iw-home is no longer at 100%.

We think this is due to the service “reserving” the space that was previously used.)

If you want to reduce the amount of “claimed” disk space you should delete any “.0″ files under “/iw-home/loacl/logs/iwevents” folder and restart TeamSite (/etc/init.d/iw.server stop) and then (/etc/init.d/iw.server start).

The below script will look through all the branches in a TeamSite file system and simply list only the branches, not workareas or files and so on.

This script is by no means optimised and could run alot faster by doing checks in the “wanted” sub routine, but it does the job

This is useful when running ‘iwmigrate’ and other such tools recursively.

From the command line run the script passing the parameter of the top level branch to search from

Example Usage:

c:\temp\find_all_branches.ipl y:\default\main

#!C:\Perl\bin\perl.exe -w
 
use strict;
use File::Find;
 
my ($area) = @ARGV;
my(@branches, $branch, $directory, @allDirectories);
 
find(\&wanted, $area);
		foreach $directory(@allDirectories){
			if (-d $directory){
				next if ($directory =~ "WORKAREA" || $directory =~ "STAGING" || $directory =~ "EDITION");
					push @branches, $directory;
				}
			}
 
foreach $branch(@branches){
					print "Branch: $branch\n";
				}
 
sub wanted {
	push @allDirectories, $File::Find::name;
	return @allDirectories;
}

The output the script produces is a list of every branch it finds, such as:

Branch: c:\TEMP\branches
Branch: c:\TEMP\branches/default
Branch: c:\TEMP\branches/default/main
Branch: c:\TEMP\branches/default/main/test
Branch: c:\TEMP\branches/default/main/test/sub-branch

TeamSite 6.7.1 has some nice new URL Commands that give quite a
detailed view of various elements in the tool:

The master list of these can be found by placing the following in the
browser address bar, replacing ‘servername‘ with the name of your TeamSite server.

The Master List

URL to use:
http://servername/iw-cc/command/iw.base.show_command_descriptors

This command shows the below and very long list..

I have picked out a few useful examples below from the above master list:

Show Performance

URL to use:
http://servername/iw-cc/command/iw.base.show_performance

Returns the below results:

JSP Snoop

URL to use:

http://servername/iw-cc/command/iw.show_snoop

This command returns useful environment information just like ‘show_env.cgi’ does:

Show Loggers

URL to use:

http://servername/iw-cc/command/iw.base.loggers

Returns the below type results to the browser

The above allows you visual easy control of the log4j level settings on all the objects
in TeamSite. Remember to always check this is in ‘default’ setting when running the
server under Production so as to not add unnecessary overhead to the system.

There are lots of other commands, use the master list mentioned first in this article
to play around and find the others you like.

The below are some further useful ones:

http://servername/iw-cc/command/iw.admin.teamsite.iwserver_stats

http://servername/iw-cc/command/iw.admin.teamsite.jvm_memory

http://servername/iw-cc/command/iw.base.caches

http://servername/iw-cc/command/iw.ping

Enjoy!

On UNIX servers it is useful to have ’sudo’ setup in order to not always have to use or get ‘root’ access.

The below lists should help with the kind of commands you typically want to setup to be run under ’sudo’.

Interwoven Commands for TeamSite and OpenDeploy Base Server:

/etc/rc3.d/S99iw.local stop
/etc/rc3.d/S80iwod60 stop
/etc/rc3.d/S50iw.samba stop
/etc/rc3.d/S16iw.server stop
/etc/rc3.d/S16iw.server start/etc/rc3.d/S50iw.samba start
/etc/rc3.d/S80iwod60 start
/etc/rc3.d/S99iw.local start
/etc/init.d/iwod60 stop
/etc/init.d/iwod60 start
/etc/init.d/iw.server start
/etc/init.d/iw.server stop
/path to apache/bin/apachectl start(for the machine in question)
/usr/iw-home/bin/iwreset
/usr/iw-home/bin/iwstoreadm
/usr/iw-home/bin/iw* (all scripts would be very useful if possible)

Commands for OpenDeploy Receiver Server

/etc/rc3.d/S80iwod60 stop
/etc/rc3.d/S80iwod60 start
/etc/init.d/iwod60 stop
/etc/init.d/iwod60 start

The below commands may already be setup for ’sudo’ but it is worth checking:

File
view
ps
Netstat
Prstat
last -a
Vmstat
Iostat
Nfsstat

Hi

I installed TS6.5 on a box last month, and every thing was fine, people were installed bits, and building up the Y drive, except now, that I’m checking it I find a problem.

IIS has not installed the Y mount, or any IIS setup ?

Have you seen anything like this before, and is it just a matter of creating a ‘website’ and linking to the Y drive ?
Thanks

Frank