wierd ignite behaviour

[Fabian Briseño]

Hello.
Guys I have a weird problem with an ignite server.
im getting this message when running an ignite session in my client.


Permission denied
ERROR: Unable to mount or write
ignk260:/var/opt/ignite/recovery/archives/smxpqs
On ignk260 you may need to:
mkdir -p /var/opt/ignite/recovery/archives/smxpqs
chown bin:bin /var/opt/ignite/recovery/archives/smxpqs

vi /etc/exports (add or modify an entry). The /etc/exports file on
"ignk260" should contain the entry:
"/var/opt/ignite/recovery/archives/smxpqs -anon=2,access=smxpqs".
After editing the /etc/exports file, run exportfs -av

If you need to change the owner of the directory,
you will also need to re-export the directory.

See make_net_recovery(1M) for more information.
ERROR: Failed to Create NFS mount Archive directory.

I must point out that I have already made everything that the previous error message states.

I have made the directory, vi/etc/exports and changed the ownership of the directory.


my exports file looks like this
"/var/opt/ignite/recovery/archives/smxpqs -anon=2,access=smxpqs"


and the ignite session fails.

but if edit the exports file and put:
"/var/opt/ignite/recovery/archives/smxpqs -anon=2,root=smxpqs"

The ignite runs well, if I leave the the file this way with the "root" does it pose a security risk ?

any help you can provide would be appreciated.

[Steven E. Protter · Accepted solution]

Shalom,

Ignite due to its reliance on the r-protocols and not openssh is a security risk.

I in general did modifications to the inetd.conf file or kept a second copy which was only put into use during ignite backup windows.

The risk is low unless you are exposed to the public internet or unruly, unstrustworthy users, then its unacceptable.

There is nothing to do but ask HP to start supporting a ssh based model. This I asked about 3 years ago.

SEP

[Fabian Briseño]

Thaks for the response steven.

I apreciate your input on this matter.

have a nice day

[Stijn V]

I do have the same issue .... only for one new server that I just added. Does anybody knows why? Thanks.

[Fabian Briseño]

I could never find the reason for this problem, putting the anon=root instead of anon=2, fixed the problem and I left it like that.