TeamSite732 Installation (Linux) Failure

Hello,

despite seemingly have all the pre-requisites in place and applying some learnings from the previous installation, my TeamSite732 Installation still failed. Sigh.

I got through all the questions in the Installer UI and it started installing, but failed with error:

The install processing was unsuccessful
Install doc file does not exist:
/usr/nlm/iw/iw-home/TeamSite/install/TeamSite_7.3.2.0.0_INSTALL.xml
see /usr/nlm/iw/iw-home/iwinstall/logs/installer.log for more information

There were other errors in the installer.log, the first of which was:

2014-09-10 13:32:09,785 INFO  com.interwoven.wcm.install.util.Iwinstall - iwinstall location is not present
2014-09-10 13:32:09,790 ERROR com.interwoven.wcm.install.framework.InitialPhase - Unable to parse inventory document

...although there was an iwinstall directory created in the 'base directory' entered in the UI, which was /usr/nlm/iw/iw-home (I created iw-home to preserve pathing).

BUT what I noticed was that the "TeamSite" directory was not created under the base directory, AND all the directories that would normally be placed under "TeamSite" dir (iw-webd, bin, eventsubsystem etc) were instead created directly under the base dir, as per following ls -l. So not sure why it would create other directories (eg TeamSiteUI) but not TeamSite - only difference I can see looking at my previous installation is that TeamSite should be owned by iwts:iwts, and we pre-created iwts user & group to make sure we have the same IDs.

I have 2 questions:

1. Has anyone seen this before, and knows the cause?

2. I will need to uninstall as what has been created is unworkable, but when I bring up the Installer to try and do this, it is stuck in "Final Configuration" stage, so doesn't offer me to uninstall. Does anyone know a way where I can reset or trick the installer back to an initial stage where I have the Uninstall option?

Here is an ls -l of the 'base directory' with the mish-mash of directories:

l /usr/nlm/iw/iw-home/
drwxrwxr-x 9 root root     4096 Sep 17 10:56 ApplicationContainer/
drwxrwxr-x 2 root root    16384 Sep 17 10:59 bin/
drwxrwxr-x 5 root root     4096 Sep 17 10:58 CommonServices/
drwxrwxr-x 7 root root     4096 Sep 17 10:58 CommonServicesClient/
drwxrwxr-x 3 root root     4096 Sep 17 10:59 conf/
drwxrwxr-x 3 root root     4096 Sep 17 10:57 CoreFramework/
drwxrwxr-x 7 root root     4096 Sep 17 10:59 cssdk/
drwxrwxr-x 4 root root     4096 Sep 17 10:59 etc/
drwxrwxr-x 4 root root     4096 Sep 17 10:59 eventsubsystem/
drwxrwxr-x 3 root root     4096 Sep 17 10:59 examples/
drwxrwxr-x 5 root root     4096 Sep 17 10:55 FoundationLibraries/
drwxrwxr-x 6 root root     4096 Sep 17 10:59 httpd/
drwxrwxr-x 7 root root     8192 Sep 17 10:59 install/
drwxrwxr-x 3 root root     4096 Sep 17 11:01 InterwovenAdministrationConsole/
drwxrwxr-x 6 root root     4096 Sep 17 11:02 iwinstall/
drwxrwxr-x 7 root root     4096 Sep 17 10:59 iw-perl/
drwxrwxr-x 11 root root     4096 Sep 17 10:59 iw-webd/
drwxrwxr-x 3 root root     4096 Sep 17 10:59 kernel/
drwxrwxr-x 3 root root     8192 Sep 17 11:00 lib/
drwxr-x--- 6 root root     4096 Sep 17 11:00 local/
drwxrwxr-x 2 root root     8192 Sep 17 11:00 msg/
drwxrwxr-x 25 root daemon   4096 Sep 10 12:03 OpenDeployNG/
drwxrwxr-x 6 root root     4096 Sep 17 10:59 private/
drwxrwxr-x 3 root root     4096 Sep 17 10:59 report/
drwxrwxr-x 3 root root     4096 Sep 17 10:59 servletd/
drwxrwxr-x 2 root root     4096 Sep 17 11:00 sharedll/
drwxrwxr-x 3 root root     4096 Sep 17 10:59 src/
-rw-rw-r-- 1 root root   359547 Sep 17 10:59 TeamSiteInstaller.jar
drwxrwxr-x 3 root root     4096 Sep 17 11:02 TeamSiteUI/
drwxrwxr-x 2 root root     4096 Sep 17 10:59 tmp/
drwxrwxr-x 6 root root     4096 Sep 17 10:59 tools/
drwxrwxr-x 6 root root     4096 Sep 17 10:59 tsreport/
drwxrwxr-x 3 root root     4096 Sep 17 10:59 winnt/

Cheers

Find more posts tagged with

Comments

Adam Stoller

Is this a VM?

If so, I'd advise you to wipe and reload the OS and patches, take a snapshot; then install TS - if successful take a snapshot, ...., take a snapshot, ... etc.

That way if you have to back-track [again], it should be a lot less painful.

Rick Poulin

As for the cause, I would imagine you just didn't set the path for that module correctly when the wizard asked for it. You must've input /blah/iw-home instead of /blah/iw-home/TeamSite.

HurricanesFan

Thanks Ghoti & Rpoulin.

Yes, it is a VM.

Yes I did just put blah/iw-home as the base dir in the Installer UI, but I'm sure that is all that is needed for the 732 install as the default is /interwoven (although I think you have to specify iw-store, which is inconsistent), and TeamSiteUI, ApplicationContainer & CommonServices all got installed under iw-home - they should be at the same level as "TeamSite" I believe.

And yes, I may have to go back to a snapshot (Unix team will be happy...) as the installer is stuck at "Final Configuration" stage and not offering uninstall. I was trying to find out how I could reset the system so the Installer would start at the beginning again - the only clue I got from the manuals was: "The installation program detects Autonomy Registry on your system and the Installation Type dialog box opens". What exactly is "Autonomy Registry" and how could I reset it?

The thing is though, if I do just go back and try to install again the problem is likely to occur again because we haven't identified the cause and it is most likely still there - it must be some permission issue I think.

HP-Aut Support have stuck me with a junior and I am not hopeful of getting a solution from them anytime soon.

Cheers

Rick Poulin

The "registry" is the same thing as "common services". It's a java app that stores information in a database, and it's usually the very first thing you install.

That said, the "state" of the wizard is actually stored in an inventory.xml file within the iwinstall folder. You can make it "forget" it installed some pieces, but then you go down something of a bigger quagmire of fixing stuff as the wizard gets all confused about your half-install.

PageBreak after.PNG

HurricanesFan

Thanks Rpoulin, didn't know about inventory.xml.

For TeamSite itself it has:

    <Component status="INSTALLED" id="TeamSite7.3.2.0.0" operation="INSTALL">
      <name>TeamSite</name>
      <version>7.3.2.0.0</version>
      <visible-name>TeamSite 7.3.2.0.0</visible-name>
      <home>/usr/nlm/iw/iw-home/TeamSite</home>
      <install-date>Wed Sep 17 11:01:06 EDT 2014</install-date>
      <update-date>Wed Sep 17 11:01:06 EDT 2014</update-date>
    </Component>

But obviously <home> is incorrect because /usr/nlm/iw/iw-home/TeamSite doesn't exist, and all the directories that should be under it are instead directly under /usr/nlm/iw/iw-home.

I'm still thinking it may have something to do with creating directories owned by iwts:iwts. Looking at my working TS installation, those dirs are TeamSite itself, .cpan (also not created, but not sure of its raison d'etre) and sub-dirs under "TeamSite" like local, conf & eventsubsystem which were all created as root:root. I do not see why though as iwts user & group is already in the local passwd & group files (inherited from the cloned server).

Not sure where to go from here - is this 'installation' beyond trying to fix and do I really need to go back to a backup (if I can't uninstall)?

Cheers

HurricanesFan

I have an update...

I decided to create the "TeamSite" directory myself and moved all the directories that should be in it to there (bin, iw-webd, eventsubsystem etc).

I then brought up the Installer wizard to try to complete the installation. It failed a few times because of missing execute permissions on (in order) iwperlcfg, iw-perl/bin dir, bin & private/bin dirs, tsconfig, and iw scripts in /etc/init.d (that one indicates that the Installer was having general problems creating files and directories with correct permissions).

Eventually after doing all these the Installer went through to completion.

I then tried to stop|start iw.server - found I had to make iw-store iwts:iwts also before iw.server would start. Still some work to do (the Web Daemon didn't start for some reason) but iw.server is running and 2 iwmnt mounts are up.

Now I have to decide if, in view of all these permission problems, this installation is OK to go on with or if I should uninstall and try again - the Installer now gives me the option to uninstall.

If I do uninstall and install again, then I suppose I will have the same problem though... When I run the installer I have set umask to 0002, selinux is disabled and I am sudoed to root. Not sure what else I could do.

What does the panel think?

Adam Stoller

Personally - with that many hand-modified steps, I'd feel a lot better starting over again from scratch.

Good point about the umask - make sure you do that before you start the installation process.

HurricanesFan

BTW what should be the umask for installing TeamSite? I'm asking for 0002 but the Unix team are saying that is too "loose" and they only want to go to 0022.

Rick Poulin

0022 has worked fine for me in the past. It should be sufficient for most cases -- whatever's left over can be fixed manually.

HurricanesFan

Well I went ahead and uninstalled all components with umask 0022, and it ran to completion and said the uninstall was successful.

I see things like the stop|start scripts have been removed but what I noticed is it didn't delete iw-store or the software (ApplicationContainer, TeamSite and everything under it like iw-webd etc).

I've not done an uninstall before, is it normal that it would leave iw-store and the software in place? Should I delete all these myself before I attempt another install?

Adam Stoller

The iw-store should definitely *not* be removed as part of the uninstallation. That should be handled manually. I believe the main home directories for the uninstall may not get removed, but some/most of it may be - I don't think all of it will be because I believe it runs scripts from within that directory tree and thus cannot delete a directory that is being held open by a process.

HurricanesFan

Hmmm.

I think I should probably remove both iw-store and all the software, as I had to intervene in both when I installed (I had to manually make iw-store iwts:iwts, and all sorts of things in TeamSite).

Then run the install again with umask 0022 to see if it can successfully install by itself correctly all the way through, instead of the mess it made last time.

I've remembered to put back the 'pre-created' *iw* groups and users in passwd, group & shadow after the uninstall took some of them out - I need them the same as our working TeamSite server as this is supposed to be a mirror.

Not. Easy.

Thanks Ghoti.

DynamicImageInHeader.zip

HurricanesFan

I'll finish this off as I have successfully installed now, if it helps anyone...

After using the Install Wizard to uninstall, I did the following to finish the uninstallation:

Stop any ”iw” procs, check mounts are down
Delete iw-store – I decided to remove it to give the installer a chance to recreate properly
Save TS.lic to reapply
Delete all dirs & files under iw-home except OpenDeploy [poss rename iwinstall to compare]
Drop all TeamSite, LS, ReportCenter, Search related tables from corresp databases.
Delete all TS-related files under /tmp and /var/tmp (if not sure, delete anyhow)
Delete all /etc/*iw* files
” /usr/bin/iwget & iwgethome
[” /usr/kernel & /dev... iw dir & iwovwfs driver file – Solaris only, Linux TS uses uvfs]
” /etc/init.d/*iw* except iwod*, iw.http (ext apache)
” /etc/rc*.d/*iw* except iwod*, iw.http (ext apache) – mostly links to /ect/init.d
Reboot the server

Then I installed again:

Made sure I had all the *iw* users & groups pre-set up in passwd, shadow & group to mirror their IDs in the TeamSite server this is supposed to mirror.
reset the external instance of apache port to 80 (retrospective - the Installer seems to assume it is 80 and if it is not, it adds rather than changes it)
selinux disabled
Applied a SYSTEM-Wide umask of 0022, as just a session umask of 0022 did NOT work and was shown to be the cause of the initial installation problems (and this thread...).