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

remote backing store does not work

HolgerOstermann

Hi,

After a server move / restart, TS 6.71 SP1 on Solaris cannot start any more and mount the backing store which is on a network storage. The network storage itself is mounted and accessible via the shell.
Are there any timeout or sequence settings for iw.server and iwovwfs or can iwovwfs be restarted with more debug output?

Only the workflow part seems to be initialized, but not the default part of the backing store.
Test-Backing Store Log-Output from iwtrace.log:
Initialized store 0x1 at "/disk_mig_tmp/new_iw_test_store/workflow" (version=300008, next id=0x200).

Thank you.

Find more posts tagged with

Comments

Adam Stoller

Hi,

After a server move / restart, TS 6.71 SP1 on Solaris cannot start any more and mount the backing store which is on a network storage. The network storage itself is mounted and accessible via the shell.
Are there any timeout or sequence settings for iw.server and iwovwfs or can iwovwfs be restarted with more debug output?

Only the workflow part seems to be initialized, but not the default part of the backing store.
Test-Backing Store Log-Output from iwtrace.log:
Initialized store 0x1 at "/disk_mig_tmp/new_iw_test_store/workflow" (version=300008, next id=0x200).

Thank you.

Have you tried running iwstoreadm -a default ?
Are you sure that everything on the new server is correctly pointing to the NAS / SAN for the backing store?
Are you sure that the mount is set up correctly so that it is accessible in read-write mode for 'root' (and/or iwts or iwui - whomever the iwserver process is running as)?