› Clovertech Forums › Cloverleaf › How do we access hciserveradmin with PuTTy?
I need to access the Server Admin, but am telneting in with no X11 display set.
How can one access hciserveradmin without XWindows running on AIX?
I had previously got mobaXterm to work, but today I get the error: Can’t open display.
When you log in with MobaXterm with SSH, you should get a message like this:
┌────────────────────────────────────────────────────────────────────┐
│ • MobaXterm 12.1 • │
│ (SSH client, X-server and networking tools) │
│ │
│ ➤ SSH session to dbarr@mkifmgrt.Valleymed.net │
│ • SSH compression : (check) │
│ • SSH-browser : (check) │
│ • X11-forwarding : (check) (remote display is forwarded through SSH) │
│ • DISPLAY : (check) (automatically set on remote server) │
│ │
│ ➤ For more info, ctrl+click on help or visit our website │
└────────────────────────────────────────────────────────────────────┘
Is that what you see when you log in?
Make sure you have “Enable X11 Forwarding” enabled in the PuTTY config (Connection->SSH->X11). This should configure the DISPLAY env var for you.
If you are telneting in and need to set DISPLAY manually, try something like
export DISPLAY=<your-host-name>:0
Rob Abbott
Cloverleaf Emeritus
Thanks Rob, I did exactly that in MobaXterm and didn’t get any more display errors.
However, when I ran the command I got an XWindows error that said:
“The Server Administrator GUI only runs on a local machine in local mode. Remote mode was attempted…..”
I found the client.ini on the AIX Cloverleaf Server and removed all sections except the general section. Still, got the error.
============
In short I am just trying to get Global Monitor (6.2) to connect to CL 19.1.0.1, which I was able to do by manually setting the following in server.ini:
[general]
global_monitoring_enabled=true
[web]
web_server_autostart=true
I then ran hciss (no switches) and it restarted the web server.
I then found the port its communicating on in client.ini (on AIX)
[host_ourservername_cl_srv]
url=//ourservername:13023/RMI_CloverleafServer_1.0
===========
Rob/etc,
I got this far and only have one last question. It would be super cool if you (or anyone) could respond.
Why in Global Monitor do 10% of the sites show as Unknown?
I see no major errors relating to this in the logs of the GM Server.
“The Server Administrator GUI only runs on a local machine in local mode. Remote mode was attempted…..”
That error probably means that your DISPLAY wasn’t set to localhost. You may need to do SSH tunneling to get this to work. MobaXterm should do that automatically if you use SSH instead of Telnet.
Unfortunately we don’t have SSH installed on our AIX box. Only Telnet.
a couple of thoughts..
confirm that X11FORWARDING is set to yes in /etc/ssh/sshd_config
also, you may need to add this to your .profile.local.end
export DISPLAY=”yourlocalmachineIP”:0.0
will hciaccess run?
Yes! hciaccess did run!
Wonder if anyone saw the section where I have 4 sites that are listed as ‘Unknown’ in Global Monitor.
Why does that happen? What is making it list as Unknown?
i have a similar issue. hciaccess will run but hciserveradmin will not.
I was able to resolve my issue… try this fix:
navigate to $HCIROOT/client
you will modify the client.ini, so you may want to make a backup copy. While in client.ini, change “last_remote=true”, too “last_remote=false”.
save client.ini modifications then relaunch hciserveradmin
let us know?
as is not sure about your globalmonitor issue. looking in your server.ini, located in $HCIROOT/server, are your sites listed under ENVIRONS?
Ok wow nice! That client.ini modification worked and I can now load hciserveradmin.
Thank you for noticing the other issue also! Yes I checked the environments yesterday and also checked them in hciserveradmin today. We are basically testing GM 6.2.0.0 with CL 19.1.0.1. Every site works except 3. There should be no difference between the sites.
So far I have tried:
– restarting MonitorD, restarting the host server, restarting the GM service
Off hand, i don’t have a solution. I’d recommend upgrading your GM to the latest release. 6.2.1 appears to be the latest, and see if that fixes the issue.
Great response! We did that and… it did fix the issue!
Great suggestion Dustin. FYI, the GM 6.2.1 patch is required to properly monitor Cloverleaf 19.1 environments.
Rob Abbott
Cloverleaf Emeritus