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

/.iwmnt not getting automatically created

bscott1

I have a new install of TS 5.5.2 on Solaris and am not seeing the /.iwmnt being created. It is also not included in the /etc/mnttab file. Isn't this mount supposed to automatically be generated? I can forceably mount it but I thought it was automatically put by the Teamsite system files over a stop and start of Teamsite. Any help anyone could provide would be appreciated. I have attached an excerpt from the iwserver.log over a shutdown and startup.
Thanks!

Find more posts tagged with

Comments

gwen1

This mount point should be automatically created when TeamSite is started. Did you reboot your server following the installation? TeamSite will not start properly if not. If server was rebooted, are there any errors being generated in your iwtrace.log file or your system logs?

Gwen

bscott1

yes, we rebooted the machine after the install. The only weird behavior I am seeing is in the iwserver.log which states that /iwmnt is busy while trying to mount it but the /iwmnt mount gets mounted anyway. There is nothing anywhere regarding the /.iwmnt or any errors regarding that mount. Very unusual. I have opened a case as well. but as far as I know this shouldn't be happening. Does anyone know what IW files govern the mounting of both /.iwmnt and /iwmnt so I can see if it is there as a Teamsite mount? Here is the excerpt from the iwserver log:
iwmount: Mounting /iwmnt/default...
iwmount: Mounting /iwmnt/default...
nfs mount: mount: /iwmnt/default: Device busy
iwmount: Mounted /iwmnt/default and /iwmnt/default.

Adam Stoller

This sounds like TeamSite never got shut down properly - and that despite saying it was unmounting /iwmnt - it may never have done so.

Try stopping the TeamSite services again (Something like: /etc/init.d/iw.server stop [if memory serves me correctly]) - and then see if /iwmnt is still there. If so, try unmounting it manually (either as root or via sudo): umount /iwmnt

If it doesn't go away - then it sounds like something is holding it there and you need to do a bit more investigation to figure out what. (though one would think a reboot would fix that ...) perhaps there's something else going wrong during startup? Have you checked all the TeamSite-related log files?

--fish
(Interwoven Senior Technical Consultant)

gwen1

After stopping TeamSite, try running the command:
iw-home/private/bin/iwetcboot stop
before starting TeamSite. When we have had nfs issues in the past this has helped. Another option may be to restart nfs.
Gwen

bscott1

After doing some more troubleshooting...
What is interesting about this is that
Teamsite doesn't seem like to know that it is "supposed" to mount /.iwmnt.
The only error I am seeing in the TS logs is the one I listed above in my post:
"device busy"
After I stop Teamsite then try to execute ./iwetcboot I get this:
# ./iwetcboot stop
iwmount: Unmounting /iwmnt/default...
umount: warning: /iwmnt/default not in mnttab
umount: /iwmnt/default no such file or directory
iwmount: Failed to umount /iwmnt/default ...
iwmount: Unmounting /iwmnt/default...
umount: warning: /iwmnt/default not in mnttab
umount: /iwmnt/default no such file or directory
iwmount: Failed to umount /iwmnt/default ...
RPC connection failure:00930: RPC connection failure
iwetcboot: Running iwstop ...
iwstop: Looking for the wfs kernel module id ... already stopped.
I think this is because TS is already stopped and the /iwmnt is not there.
I tried stopping and starting the nfs server as well with no change in result
I bring up TS and still it only mounts /iwmnt after telling me /iwmnt "device busy"
Where is the listing for /.iwmnt???
What in TS tells the system it has to mount /.iwmnt?

tvaughan

Look in your /etc/mntab file

Do you see something like this?


reNunxOPQ:/iwserver/default     /iwmnt/default  nfs     vers=2,dev=47400311044968753
reNunxOPQ:/iwserver/default     /.iwmnt/default nfs     vers=2,noac,dev=4740032 1044968753

Now check your /etc/dfs/dfstab

Do you have something like this:


share -F nfs -d "IW Server" -o nosuid /iwserver

Tom

bscott1

I see this in mnttab file:
dubsun6:/iwserver/default /iwmnt/default nfs vers=2,dev=2d40004
1045079103
No other entries (after starting Teamsite server)
In dfstab I see this:
share -Fnfs -d "IW Server" /iwserver
no other entries.
On my 5.01 Teamsite server I see the same entry in the dfstab file but I see what looks like the correct entry in the mnttab file. See below from mnttab:
dubsun65:/iwserver /iwmnt nfs vers=2,dev=2d40002 1044764729
dubsun65:/iwserver /.iwmnt nfs vers=2,noac,dev=2d40003 1044764730

What does this mean?

tvaughan

Well, the mnttab is modified by the OS at runtime (you shouldn't edit it yourself).

Yours looks like there's no "/.iwmnt" which is a problem that will affect your ability to preview any content.

Your dfstab is correct -- that got written during your installation.

I looked around in my $TS_HOME/private/bin directory, and couldn't find where it tries to mount "/.iwmnt". No luck in /etc/init.d either. . . .sorry, but I'm out of ideas for you. Put the pressure on IWOV support and see if they can help you out. Let us know what the resolution is.

Thanks, and good luck
Tom

bscott1

Thanks for trying. I have a case open with support as well. I looked at all that to. I can't seem to find where it is writing the /.iwmnt or even why it might not be. I can manually mount the /.iwmnt drive after I bring up TS (which is what I have been doing) to render web assets but that is just a work around. If anyone out there has any further ideas they are always appreciated. I will post resolution if it comes from IW Support.

bscott1

The problem was discovered and it was related to the cgi mount being set in iw.cfg for /iwmnt. This will cause the /.iwmnt to not mount. This has brought up another problem however, now our CGI menu items cannot find the files as they are looking at /.iwmnt (and obviously the file is not there at the /.iwmnt point) If anyone has a quick way to get around this problem with CGI item in iw.cfg required to be referenced at /.iwmnt to auto mount /.iwmnt over a TS start but also needing the CGI mount to be /iwmnt so that files can be found by the CGI programs let me know. Thanks!

Adam Stoller

What CGI's fail? How do they fail?
Can you post (as an attachment) an example of a CGI script that doesn't work when iwcgimount=/.iwmnt ?

--fish
(Interwoven Senior Technical Consultant)

bscott1

without posting a lot of code here is what happens, in a nutshell. If you take, for example, the menu_item_test.ipl that ships with TS and executes as a CGI menu item you will see that with the iwcgimount in the iw.cfg set to /.iwmnt (which I understand is required to ensure that both /iwmnt and /.iwmnt start automatically over TS stop and start) that this ipl returns /.iwmnt in all path variables. If you change the iw.cfg setting to have the CGI mount set to /iwmnt then it returns all paths with /iwmnt preceeding them. Now if you attempt to execute say /iw-home/bin/ iwextattr -l $file name. The path starting with /.iwmnt will error out giving ERROR:02005: Error locating /.iwmnt/blah/blah/blah. The path starting with /iwmnt will give the correct response listing the extended attributes on the file in question. Please let me know any thoughts out there on a quick way to resolve this problem without changing too much code.

Adam Stoller

What menu_item_test.ipl that ships with TeamSite? Do you mean show_env.ipl ?

If you've read any of the various threads about the CLTs you'll realize that the path given to iwextattr is supposed to be a vpath and not a file system path - and therefore, technically, both /.iwmnt/default/blah and /iwmnt/default/blah are "wrong" and always have been, it's just the latter happened to work more by accident than anything else.

The quickest way to strip this off with the minimum of code would probably be to create your own little subroutine that you can call in various places:

[not tested - but should be pretty close to functional if not already there]

use TeamSite::Config;
sub fpath_to_vpath{
    my $p = $_[0];
    my $iwmount = TeamSite::Config::iwgetmount();
    $p =~ s|^$iwmount||;
    if ($^O ne "MSWin32"){
        $iwmount =~ s|^/|/.|;
        $p =~ s|^$iwmount||;
    }
    return($p);
}

Hopefully that will help a bit

--fish
(Interwoven Senior Technical Consultant)