iw.server will not start on a ControlHub server that was just upgraded to 3.0

I did not see a ControlHub or CAPs forum so I am posting here, it's my understanding that TS and CH are similar products....

iw.server will not start on a ControlHub server that was just upgraded from 2.1 to 3.0

ERROR found in the iwtrace.log
ERROR: iwm_UnRunWFS: Could not open device driver /dev/iwovwfs; errno
= 13
ERROR: iwm_UnRunWFS: Could not set close-on-exec on fd to device
driver /dev/iwovwfs; errno = 9
ERROR: iwm_UnRunWFS: ioctl WFS_SYS_COMMAND to device driver failed
with error =-1

Any ideas I have tried a few things...
NFS seems good:

bash-2.05# share
- /iwserver rw=tx8sdint01 "IW Server"
bash-2.05# share /tmp
bash-2.05# share
- /iwserver rw=tx8sdint01 "IW Server"
- /tmp rw ""
bash-2.05# mkdir /mnt/foo
bash-2.05# mount -o vers=2 localhost:/tmp /mnt/foo
bash-2.05# share
- /iwserver rw=tx8sdint01 "IW Server"
- /tmp rw ""
bash-2.05#

Find more posts tagged with

Comments

nipper

Is this Linux ? It looks like the IWOV filesystem needs to be upgraded, they usually have that as part of the install instructions.

mattbryant

The server is Solaris 9, we are going to try on Solaris 10. It was determined that NFS needed to be enabled with ControlHub 3.0. This is a new requirement for this version as it was not needed in 2.1. We tried enabling NFS and ADB packages per Iwov's recommendations but we still were not able to bring the app up. We are going to try the upgrade on another box.

mattbryant

Found resolution we were missing prereqs.

Make sure this package is installed (and the mdbx pkg).
bash-2.05# pkginfo | grep 'SUNWmdb'

Ensure NFS is installed and working:
# share /tmp
# share <-- confirm /tmp is really shared
# mkdir /mnt/foo
# mount –o vers=2 localhost:/tmp /mnt/foo <-- see if mount fails
# share <--- /tmp is still shared or not
also do this:
ps -ef |grep nfs