Ignite GUI changing ownersip

[MikeL_4]

I tried to do an Ignite restore to a server and ran into problems due to the ownersip of the directories being root:sys instead of bin:bin. After changing them the restore worked fine.

What I later noticed is that when using the GUI interface the ownership is being changed on these directories.

Has anyone ran into this problem and is there a fix to resolve it ??

[Rick Garland · Accepted solution]

Running HPUX 11.23 on ia64. The /opt/ignite/bin/ignite is staying at bin:bin

On HPUX 11.11 on A500 system, the /opt/ignite/bin/ignite is a link with perms of root:sys. The link is to /opt/ignite/binpa/ignite.10 which has perms of bin:bin.

The perms remain the same when I execute the GUI/TUI and exit out.

What version of Ignite do you have?

[MikeL_4]

HPUX 11.11
Ignite-UX B.5.4.50

[Rick Garland]

Upgrade the Ignite. Version 6.0.109 is what I am running

[Steven E. Protter]

Your version of Ignite may have been recalled.

I think being in the 6.x version number is the way to resolve this problem, though I'm sure that doesn't make the current restore any easier to get done.

SEP

[Rick Garland]

Need to upgrade the Ignite on all other systems as well.

Try to do Ignite accross network and it will complain about version mismatches on other systems.

[MikeL_4]

Can you run multiple version of Ignite then, because there is no way I can get changes in for all servers accessing this Ignite server for the same time ??

[Rick Garland]

If you are going to tape I believe you can. In this instance it is local to the system.

If you are doing Ignites accross the network (make_net_recovery) then there will be complaints from the Ignite application that versions do not match on the Ignite server and the Ignite client. In this case, the Ignite process will error out.

[MikeL_4]

Unfortunately we only do make_net_recovery, we don't have any tape drives..

[MikeL_4]

Thanks