go to post Erik Hemdal · Dec 27, 2017 Robert's suggestion is the answer nearly all the time, but it's interesting that the messages seem to show an SSH server responding on the port you are using. If you want to use SSH, Robert is right: use an external SSH client and open port 22 on the remote server.If you definitely need to use Telnet, you need to have a Telnet server (something like telnetd) running on the remote Ubuntu server and open TCP port 23.If you are stuck, contact the WRC (support@intersystems.com) and an advisor can help you.Erik
go to post Erik Hemdal · Dec 27, 2017 Marco, were you able to resolve this? If Jinho's suggestion does not resolve it, contact the WRC at support@intersystems.com and an advisor can help.Erik
go to post Erik Hemdal · Oct 23, 2017 HP-UX uses initscripts to start processes. So you need an initscript which includes commands to start, stop, and check status of processes.Let's take the Arbiter; it's a standalone process at OS level and is easier:The Arbiter is an instance of ISCAgent, whose initscript is likely at /sbin/init.d/ISCAgent on your HP-UX system.Symlink to that script in the runlevel directory for the runlevels you need this to run; this should be /sbin/rc3.d for runlevel 3 or /sbin/rc4.d for runlevel 4. You can review the HP-UX runlevels by reading the manpage for init (1M) (the command man init should get you there).In those directories, you'll see names starting with S##name and K##name (digits for the #). This signals which services are (S)tarted or (K)illed when the system switches to this runlevel. On my test machine here, in /sbin/rc3.d I see S900ISCAgent, and I can see that it would start afterS870hpsmhd.You would need a similar initscript which would start Cache'. I would expect that the Arbiter would be run on a host distinct from its mirror members. You can review the ISCAgent initscript to get a sense of how these are organized.
go to post Erik Hemdal · Jan 24, 2017 Hello Thomas, Since you are having an issue with a field test, please open a WRC case so we can get you the kit and investigate the trouble. Kind regards, Erik
go to post Erik Hemdal · May 27, 2016 Bear in mind that a container is not exactly the same as a full OS installation, unless you make it so. This can lead to surprising problems. One issue that I have seen is that installations fail when using a CentOS 7 container with an error that gzip is not found -- even though gzip is installed. If you encounter this, make sure that the 'which' command is installed in the container. The installation tool uses which to locate gzip. yum install -y which This may prevent an annoying issue when you are commissioning a new container.
go to post Erik Hemdal · Feb 9, 2016 David, your terminal emulator might also provide logging capability. For instance, in PuTTY, look at Session > Logging on the PuTTY configuration window.
