Urgent: Accessing “/iwmnt/default”

Urgent: Accessing “/iwmnt/default”

This is very urgent due to time constraint and strict project deadline.

I am using TS 6.1 on Solaris 9.
When I am trying to access "/app/mass1/teamsite/iwmnt/default" through console or telnet, it give me error "Permission denied".

Permission of /app/mass1/teamsite/iwmnt/default is "drw-------" (600).
I am not facing any problem through GUI.
I am able to create Branch, Workarea, file and folder through GUI. I have not tested Workflow and templating yet.

I want to know is it bug of TS6.1 or it is normal behavior on Solaris 9.

If it is normal behavior then how can I access "/app/mass1/teamsite/iwmnt/default" through console or telnet.

However, I am able to access "/app/mass1/teamsite/iwmnt/default" on Solaris 8 with TS 6.1

My second problem is:

I have 2 disks.
"APP" is my second disk and all installation are done in "APP" partition.

Mount point for "iwmnt" is "/app/mass1/teamsite/iwmnt/".
When I am doing df -k it show me disk usage of "/" (root) partition for "/iwserver/default".

When I am mounting it in "app". Ideally it should show me disk usage of "app" partition.
Please help me out.

I am attaching output of "df -k" command and log files
(iwtrace.log, iwserver.log,iwevents.log and 014201262005install.properties)

Please let me know if you need more information.

df -k output
===============================

Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 3626444 1370881 2219299 39% /
/proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
fd 0 0 0 0% /dev/fd
swap 2213800 24 2213776 1% /var/run
swap 2213792 16 2213776 1% /tmp
/dev/dsk/c0t0d0s7 11994877 2638621 9236308 23% /app2
/dev/dsk/c0t8d0s6 17413250 1468509 15770609 9% /app
techsun:/iwserver/default
3626444 1370881 2219299 39% /app/mass1/teamsite/iwmnt/default
techsun:/iwserver/default
3626444 1370881 2219299 39% /app/mass1/teamsite/.iwmnt/default

014201262005install.properties
=========================================
#
#Wed Jan 26 01:40:45 IST 2005
wsport=81
WORKGROUP=interwoven
IW_LOG=/app/mass1/teamsite/iwinstall/log/124801262005install_log.log
STORELOCATION=/app/mass1/teamsite/iw-store
RMI_PORT=1099
IW_HOME_4DISPLAY=/app/mass1/teamsite
tomcatport=8080
INSTALLER_UI=CONSOLE
https=443
IW_PRODUCT_DIR=/app/mass1/teamsite/iw-home
vaemail=rajesh.pal@india.techspan.com
HTTPCONFDIR=/usr/local/apache/conf
PCN=0
IW_RESULT=/tmp/install.dir.1726/MyWorkingSpot/install_result.xml
SAM=1
IW_PRODUCT_DIR_4DISPLAY=/app/mass1/teamsite/iw-home
LOGLOCATION=/app/mass1/teamsite/ts_logs
proxyport=1080
HTTPBIN=/usr/local/apache/bin
IW_DEBUG=false
IW_MODULES=/app/mass1/teamsite/iwinstall/modules
IW_HOME=/app/mass1/teamsite
IWINSTALL=/app/mass1/teamsite/iwinstall
http=80
APA=1
IW_INSTALL_MODE=IW_INSTALL_MODE_INSTALL
MOUNTLOCATION=/app/mass1/teamsite/iwmnt
IW_PRODUCTS=/app/mass1/teamsite/iwinstall/products
IW_TSHOME=/app/mass1/teamsite/iw-home
IW_UPGRADE=false

iwserver.log
=======================================
iw.server: ---------- STARTING: Wed Jan 26 06:06:05 IST 2005
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
iwetcboot: Running iwstart /app/mass1/teamsite/iw-store in /app/mass1/teamsite/iw-home
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
iwstart: The events log file is /app/mass1/teamsite/ts_logs/iwevents.log
iwstart: resetting wfs queue state ... done
iwstart: Resetting aborted state of kernel queue
iwstart: checking for standard services
iwstart: nfsd running
iwstart: mountd running
iwstart: Starting iwprocdstart script (log file: /var/adm/iwprocessd.log)...couldn't set locale correctly
DONE
iwstart: Spawning iwserver.sol (trace file: /app/mass1/teamsite/ts_logs/iwtrace.log)...
couldn't set locale correctly
iwstart: Waiting up to 60 seconds for iwserver to come up...couldn't set locale correctly
couldn't set locale correctly
READY
couldn't set locale correctly
couldn't set locale correctly
iwmount: Mounting /app/mass1/teamsite/iwmnt/default...
iwmount: Mounting /app/mass1/teamsite/.iwmnt/default...
iwmount: Mounted /app/mass1/teamsite/iwmnt/default and /app/mass1/teamsite/.iwmnt/default.
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
Interwoven OpenAPI starting ...
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
couldn't set locale correctly
Interwoven Web Daemon starting ...
Interwoven Proxy Server starting ...
Interwoven Servlet Engine starting ...
couldn't set locale correctly
astcgi.c is already added, skipping
/app/mass1/teamsite/iw-home/iw-webd/bin/iw.webd start: iwwebd started
iwuiboot: ---------- STARTED: Wed Jan 26 06:06:41 IST 2005
iw.server: ---------- STARTED: Wed Jan 26 06:06:42 IST 2005

iwevents.log
========================================
[Wed Jan 26 06:06:09 2005] root master StartUp
[Wed Jan 26 06:15:13 2005] iwui master ModifyEntity
[Wed Jan 26 06:15:17 2005] iwui master ModifyEntity
[Wed Jan 26 06:20:32 2005] iwui master ModifyEntity
[Wed Jan 26 06:20:33 2005] iwui master ModifyEntity
[Wed Jan 26 06:20:57 2005] iwui master ModifyEntity
[Wed Jan 26 06:21:19 2005] iwui master ModifyEntity
[Wed Jan 26 06:21:22 2005] iwui master ModifyEntity
[Wed Jan 26 06:21:23 2005] iwui master ModifyEntity
[Wed Jan 26 06:21:36 2005] iwui master ModifyEntity
[Wed Jan 26 06:22:59 2005] iwui master ModifyEntity
[Wed Jan 26 06:23:00 2005] iwui master ModifyEntity
[Wed Jan 26 06:23:01 2005] iwui master ModifyEntity
[Wed Jan 26 06:23:03 2005] iwui master ModifyEntity
[Wed Jan 26 06:23:05 2005] iwui master Mo

Entered By: Nitin Jain 1/25/2005 9:06:52 AM

difyEntity
[Wed Jan 26 06:23:07 2005] iwui master ModifyEntity
[Wed Jan 26 06:23:09 2005] iwui master ModifyEntity
[Wed Jan 26 06:39:43 2005] iwui master ModifyEntity

iwtrace.log
========================================
STARTING: Wed Jan 26 06:06:06 IST 2005
[Wed Jan 26 06:06:06 2005] iwserver: 6.1.0 Build 33333 Interwoven 20040311
[Wed Jan 26 06:06:06 2005] Sys SunOS Node techsun Release 5.9 Ver Generic_112233-10 Machine sun4u
[Wed Jan 26 06:06:06 2005] TeamSite Executable Version checked OS 5 Exe 5
[Wed Jan 26 06:06:06 2005] TeamSite Executable Version checked OS 9 Exe 9
ERROR: no valid submit config file found in the current configuration (/app/mass1/teamsite/iw-home/conf/events/submit.conf, /app/mass1/teamsite/iw-home/local/config/submit.cfg, /app/mass1/teamsite/iw-home/config/submit.cfg, /app/mass1/teamsite/iw-home/local/config/submit.cfg) (2)
ERROR: no valid autoprivate file found in the current configuration (/app/mass1/teamsite/iw-home/conf/events/autoprv.txt, /app/mass1/teamsite/iw-home/local/config/autoprivate.cfg, /app/mass1/teamsite/iw-home/config/autoprivate.cfg, /app/mass1/teamsite/iw-home/local/config/autoprivate.cfg) (2)
[Wed Jan 26 06:06:06 2005] *** IWServer Locale is --> English_UnitedStates.US-ASCII@Binary
[Wed Jan 26 06:06:06 2005] SMS disabled
[Wed Jan 26 06:06:06 2005] Hopi disabled
[Wed Jan 26 06:06:06 2005] Reading users and groups...
[Wed Jan 26 06:06:06 2005] done. 4 users and 12 groups read.
[Wed Jan 26 06:06:06 2005] New webserver_uid nobody (60001)
[Wed Jan 26 06:06:06 2005] New vannotate_uid iwui (1002)
[Wed Jan 26 06:06:06 2005] Cache size: 30000
[Wed Jan 26 06:06:06 2005] TEnvironment: fd limit 65536 max 65536
[Wed Jan 26 06:06:08 2005] TEnvironment: fd limit 65536 max 65536
[Wed Jan 26 06:06:09 2005] TFSEnvironment: inode cache 30000
[Wed Jan 26 06:06:09 2005] Batch Jobs Thread started
[Wed Jan 26 06:06:09 2005] Initializing workflow query cache...
[Wed Jan 26 06:06:09 2005] Finished initializing workflow query cache
[Wed Jan 26 06:06:09 2005] Started 2 FS threads
[Wed Jan 26 06:06:09 2005] /etc/iw.cfg: rpc_threadcount=64
[Wed Jan 26 06:06:09 2005] SCI Base Thread 19 started (max thread count 64)

Edited by r_pal007 on 01/25/05 09:10 AM (server time).

Find more posts tagged with

Comments

fiquebem

We have TS 6.5 + Search + SP1 + Patch on Solaris 9.

We're experiencing the same frustrating problem:

# cd /iwmnt
# ls -al
total 6
drwxr-xr-x 3 root other 512 Aug 25 10:35 .
drwxr-xr-x 29 root root 1024 Aug 25 10:35 ..
drw------- 4 root root 512 Aug 24 16:22 default

Same story with /.iwmnt.

This way one can't Preview files from content web server either.

This is a new installation.

Here's how /usr/iw-store looks:

ls -al
total 18
drwxr-xr-x 6 root root 512 Aug 25 10:35 .
drwxr-xr-x 46 root sys 1024 Aug 24 14:27 ..
-rw------- 1 root root 4 Aug 22 19:00 STOREID
-rw------- 1 root root 4 Aug 22 19:00 STOREID_
-rw------- 1 root root 22 Aug 25 10:35 StoreRegistry
-rw-r--r-- 1 root other 0 Aug 25 10:35 TSRunning
drw------- 5 root root 1024 Aug 25 10:34 default
drw------- 5 root root 512 Aug 22 19:00 events
drwxr-xr-x 2 root root 512 Aug 22 14:58 lost+found
drw------- 4 root root 512 Aug 25 10:34 workflow

Any suggestions?

Thanks,

S.

nipper

do a

df -k

and send the results

Also, have you thought of looking in the log files ?

amar_maheshwary

Guys ..
check for
/etc/rc3.d/S15nfs.server ... this file is hardlink for /etc/init.d/nfs.server

if this link is missing then reinstate tht ..I hope this would help :-)

regds
-Amar

fiquebem

Thanks, men! The link to start nfs.server is there.

The iwserver.log doesn't seem to have any errors.

Below is the output of df -h.

Any other ideas?

Thanks,

S.

Filesystem size used avail capacity Mounted on
/dev/vx/dsk/bootdg/rootvol
486M 202M 236M 47% /
/dev/vx/dsk/bootdg/usr
2.0G 1.5G 414M 79% /usr
/proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
fd 0K 0K 0K 0% /dev/fd
/dev/vx/dsk/bootdg/var
2.0G 1.3G 592M 70% /var
swap 20G 24K 20G 1% /var/run
dmpfs 20G 0K 20G 0% /dev/vx/dmp
dmpfs 20G 0K 20G 0% /dev/vx/rdmp
swap 20G 208K 20G 1% /tmp
/dev/vx/dsk/bootdg/opt
4.0G 3.1G 966M 77% /opt
/dev/vx/dsk/appsdg/archivevol
3.0G 2.7G 298M 91% /flasharchive
/dev/vx/dsk/appsdg/homevol
1.0G 578M 419M 58% /home
/dev/vx/dsk/localiwovdg/http20vol
1.0G 17M 944M 2% /usr/HTTPServer20
/dev/vx/dsk/localiwovdg/iwhomevol
15G 1.5G 13G 11% /usr/iw-home
/dev/vx/dsk/localiwovdg/iwinstallvol
5.0G 1.8G 3.0G 39% /usr/iwinstall
/dev/vx/dsk/localiwovdg/mthomevol
5.0G 18M 4.7G 1% /usr/mt-home
/dev/vx/dsk/localiwovdg/crystalvol
5.0G 18M 4.7G 1% /usr/crystal
/dev/vx/dsk/localiwovdg/httpvol
1.0G 30M 932M 4% /usr/HTTPServer
/dev/vx/dsk/localiwovdg/iwsearchvol
5.0G 957M 3.8G 20% /usr/iw-search
/dev/vx/dsk/localiwovdg/odhomevol
5.0G 18M 4.7G 1% /usr/od-home
/dev/vx/dsk/appsdg/dragonvol
100M 1.7M 92M 2% /usr/dragon
/dev/vx/dsk/appsdg/edirvol
5.0G 19M 4.7G 1% /var/nds
/dev/vx/dsk/appsdg/ulocalvol
1.0G 526M 467M 53% /usr/local
/dev/vx/dsk/appsdg/candlevol
512M 42M 440M 9% /opt/candle
/dev/vx/dsk/appsdg/logs1vol
5.0G 19M 4.7G 1% /usr/iwov1-logs
iwovxtapp1:/iwserver/default
486M 202M 236M 47% /iwmnt/default
iwovxtapp1:/iwserver/default
486M 202M 236M 47% /.iwmnt/default
/dev/vx/dsk/iwovdg/iwstorevol
50G 78M 47G 1% /usr/iw-store
/dev/vx/dsk/iwovdg/iwsearchdbvol
15G 3.3G 11G 24% /usr/iw-search-db

nipper

is there anything of interest in ANY of the log files ?

iwtrace ?

fiquebem

We're back in business. Thanks. See the gory details below.

Our TS logs are stored somewhere other than in /var/adm, so I wasn't looking in there. Eventually I found iwwfs.log there. It said:

S70iw.wfs: FATAL ERROR: "iwfs_hijack -s /dev/iwovwfs" returned error 1
S70iw.wfs: FATAL ERROR:"Usage: iwfs_hijack [-r rootPath] -s svcFindAddr path_to_wfs_device
Usage: iwfs_hijack -l|-h|-v
Hijacks native NFS requests to re-route to TeamSite.
This tool should be used with caution, only run
by Interwoven startup scripts.
-r rootPath Path that signifies TeamSite file system.
(Default is /iwserver)
-s svcFindAddr Address of native NFS dispatcher function.
Please be careful with the address you pass in here.
-l Triggers loading of native NFS kernel modules
into memory (required for hijack).
-h Display this usage message.
-v Display version.
path_to_wfs_device Path to the installed wfs device driver.
(example: /dev/iwovwfs)" Exiting..

There's an entry in Interwoven's Bug Database (Bug 59601) titled "iwfs_hijack errors in and incorrect /iwmnt/default permissions on solaris 9 even after verifying all networking services started before TeamSite." That entry refers to the "adb" debugger being called from iw.wfs. It turns out that we didn't have /usr/bin/adb installed. (We didn't have the SUNWmdb package installed at all.)

Cheers,

S.

dazzlad

Did you solve this? I suspect I have the same.

nipper

He said he did,

He needed adb loaded, do you have it ?

/usr/bin/adb

dazzlad

Yes i do have it. I just re-read that and checked it out.

I also found this https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=45861
This looks a possible issue, but my knowledge of solaris isn't sufficient to understand different run-levels (rc.x folders) and how to re-order the items in them. iw.server seems to appear in all of them.

My iwwfs.log seems to inidcate that " iwfs_hijack -l" didn't return anything, and i guess it was supposed to return the info for the -s flag in this call
"iwfs_hijack -s /dev/iwovwfs"

Help!
See below:

S70iw.wfs: ----------- RUNNING: Thu Dec 8 15:35:44 MET 2005
S70iw.wfs: WFS_DEVICE_PATH is /dev/iwovwfs
S70iw.wfs: Unloading driver before installing new version.
S70iw.wfs: Ensuring nfs daemons(server and client) are not running
S70iw.wfs: Unloading device driver...
S70iw.wfs: Installing TeamSite device driver
S70iw.wfs: Trigger loading of NFS modules...
S70iw.wfs: iwfs_hijack -l output: ""
S70iw.wfs: Looking for the service pointer in the kernel...
S70iw.wfs: Found
S70iw.wfs: Installing device driver...
S70iw.wfs: add_drv iwovwfs succeeded.
S70iw.wfs: Created /dev/iwovwfs.
S70iw.wfs: Patching kernel service pointer...
S70iw.wfs: FATAL ERROR: "iwfs_hijack -s /dev/iwovwfs" returned error 1
S70iw.wfs: FATAL ERROR:"Usage: iwfs_hijack [-r rootPath] -s svcFindAddr path_to_wfs_device
Usage: iwfs_hijack -l|-h|-v
Hijacks native NFS requests to re-route to TeamSite.
This tool should be used with caution, only run
by Interwoven startup scripts.
-r rootPath Path that signifies TeamSite file system.
(Default is /iwserver)
-s svcFindAddr Address of native NFS dispatcher function.
Please be careful with the address you pass in here.
-l Triggers loading of native NFS kernel modules
into memory (required for hijack).
-h Display this usage message.
-v Display version.
path_to_wfs_device Path to the installed wfs device driver.
(example: /dev/iwovwfs)" Exiting..

nipper

I hope you are talking to support

run this command:

ls -l /dev/iwovwfs

It should be a link & then ls -l of the destination

dazzlad

I haven't got onto support yet.
I thought I'd check here first as turnaround times are *much* quicker... Smiley Happy

bash-2.05# ls -l /dev/iwovwfs
lrwxrwxrwx 1 root root 31 Nov 29 14:03 /dev/iwovwfs -> ../devices/pseudo/iwovwfs@0:wfs

bash-2.05# ls -l /devices/pseudo/iwovwfs@0:wfs
crw------- 1 root sys 220, 0 Dec 8 15:35 /devices/pseudo/iwovwfs@0:wfs

Thanks.
D.

nipper

same as what I have,

I will see if I can find iwwfs.log and see whatit differs.

dazzlad

Thanks mate. much appreciated.

Adam Stoller

run this command:

ls -l /dev/iwovwfs

It should be a link & then ls -l of the destination

Or just run: ls -Ll /dev/iwovwfs - the L will follow through the symlink, and the original (lowercase L) l will provide the long-listing.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

dazzlad

fiquebem mentioned a bug in iwov's bug database.

Is this db accessible from the support site? I had a look and I can't see it anywhere....

Thx.
Darren.

Adam Stoller

The bug (and feature request) DB is internal to IWOV only - what you need to do is contact Support - who can access the DB and they can provide you with the ID and description of the bug (or feature request) and *may* be able to provide additional data about it (like "fixed in upcoming SPx" or "fixed in upcoming release x.x)

A number of folks have tried to argue that since the number of customers associated with a bug or feature request is one of the weighting factors for prioritizing when such an item gets addressed - that the DB should be [more] public than it is - however I don't believe this will ever change (for reasons that are obvious, to me at least).

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

dazzlad

Understood.

I have sent an e-mail out with all of the symptoms, and will post here if I manage to resolve.

Cheers.
Darren.

dazzlad

This was the answer from IWOV support that finally got us back on track (in case anyone else hits this issue again):

1. Apparently then the issue is that the OS was installed using the 'End
User Solaris Software Group' and not the 'Developer Solaris Software
Group' when installing for Solaris 9. This makes a big difference in 9
because of some adb / mdb changes in the solaris distribution.

2. A TeamSite Install documentation bug is in process for this and going
forward engineering is also looking into whether to modify TeamSite such
that it will use mdb rather than adb on versions of Solaris 9 and later
as adb no longer exists other than as a symlink (and apparently not a
reliable symlink) to mdb:
http://docs.sun.com/app/docs/doc/816-5165/6mbb0m9b5?a=view

3. Recommendation: Install OS using the 'Developer Solaris Software
Group' bits instead of the 'End User Solaris Software Group' bits and
then re-install TeamSite.

Darren.