Ignite 7.5.142 GUI and ssh mode

[Tim Nelson]

Wondering if anyone has run into this yet ?

It looks like around Ignite 7.2 there whas an "exhancement" ( I say this with a grin ) to add ssh -X functionality.

I am running into an issue while testing 7.5 that I cannot initiate a make_net_recovery from the GUI as I have been able to in previous version.

The ssh -X option enabled ssh X11 Forwarding, which is great except that it will use the DISPLAY variable of the target and not my current display.

I would like to continue using ssh in lieu of remsh as the method but this is the second time I have tried to upgrade Ignite only to find that some "enhancement" does forces me to stay at my last version.

Any experiences before I put in a call to HP ?

THX

[Armin Kunaschik]

Not a real solution to your problem but:
Why not use make_net_recovery from the machine you want to backup? You don't need either remsh nor ssh (for that purpose).
You have far more options (i.e. include/exclude) and can place the backup to different server.
You're able to write a small script and put in into crontab which removes the need of the gui completely.

My 2 cents,
Armin

[Tim Nelson]

Thanks Armin.

I initially use the Ignite server GUI to do the initial setup, vg inclusion/exclusion, number of archives to retain etc..

Then each server executes make_net_recovery on their own according to schedule.

I have a call open to HP so we will see where it goes. Simply disabling of the -X would be great.

Another issue may be that ssh version 4.7 for hpux seems to have a bug with -X option.

[Matti_Kurkela]

Tim, please allow me to explain how the X11 forwarding of SSH is supposed to work.

When you connect from machine A (with your display) to machine B, the sshd on machine B will act as an X11 proxy and set the DISPLAY variable of the session to machineB:10.0 (or if :10.0 is already in use, then :11.0 etc). That value points to the proxy created by sshd. The sshd will also set up new xauth keys in the ~/.Xauthority file for the connection.

Now the X11 client on machineB will connect to the X11 proxy (aka sshd), which will forward the connection to machineA. There the ssh client on machineA will slightly edit the X11 protocol to make it match the xauth keys used by your session on machineA, and feed the data to the X server of machineA.

When you're using ssh forwarding of X11, you're not supposed to touch the DISPLAY variable in any way on the remote machine. If you, for example, set the DISPLAY variable to a fixed value in your .profile on machineB, it will cause the SSH X11 forwarding to fail.

MK

[Tim Nelson]

I found a solution and will try to nutshell it.

Version 4.7 of ssh does not handle/work with the -X option. ( or at least now returns an error in lieu of silently falling back ).

Edit your ssh_config file for "ForwardX11 yes"

This overrides the -X with -Y until either HP removes the -X from Ignite or the next ssh port works properly.

Attached is the engineering note I got from HP.

[Tim Nelson]

One last solution.

Do not upgrade to ssh 4.7. Older versions do not cause this issue.