• RE: Intermapper Remote Access Linux Java version problem

    Installed a fresh install of Oracle OpenJDK-11.0.10 in an alternate path, pointed $INTERMAPPER_JAVA at it, it is now working, and doesn't interfere with the system 11.0.9 JRE.

    Thanks for the help.

    Tim

  • RE: Intermapper Remote Access Linux Java version problem

    From your post, I am assuming that Ubuntu 18.04 has updated to java 11.0.10, Debian stable has not. 

    I normally run openjdk-11-jre, but in troubleshooting this problem I have installed the full JDK as well as trying the reference implementation from Oracle.

    I will try a manual install of a later version.  Mixing Ubuntu and Debian repositories on an apt based linux tends to lead to admin headaches, so I will just put a newer version of java in the directory with remote access.  I see that it checks for an environment variable then a local java before trying the system java, so I will give that a try.  I decompiled CIntermapperClientMain.class to look at the java version checker code, I honestly don't see why it doesn't work, unless for some reason the Debian java is returning a non standard value for system property java.version.

    Thanks for the reply

    Tim

  • RE: Intermapper Remote Access Linux Java version problem

    Just an update, I removed all java from my machine, cleanly installed OpenJDK reference implementation (build 11+28), pointed environment variable $INTERMAPPER_JAVA at the location of the java interpreter, and got the same dialogue box as with the Debian OpenJDK version.

    Tim

  • Intermapper Remote Access Linux Java version problem

    I have been running Intermapper Remote Access on various Debian based Liuxes for several years.  Recently have been seeing new installs fail with a dialogue box that says:


    Java 11.0.2 or later is needed to run this application
    You should install OpenJDK JVM: https://openjdk.java.net
    java.vendor = Debian
    java.runtime.name = OpenJDK Runtime Environment
    java.runtime.version = 11.0.9+1-post-Debian-1deb10u2

    This morning I quit IRA and restarted it, and got this dialogue.  This machine is running Linux Mint Debian Edition 4, which is based on Debian 10 (Buster).

    Obviously the java version checker has a broken parser, since the runtime version is 11.0.9, which is definitely later than 11.0.2, and it is the recommended OpenJDK jre.  This behaviour is at least in Intermapper Remote Access 6.3, 6.4, and 6.5, and at least 2 versions of Debian OpenJDK-11. 

    The document at https://static.helpsystems.com/intermapper/pdfs/intermapperinstallation.pdf says that the installer installs a JRE to run the client, however it does not appear to do so.  Just in case the installer only installed a JRE if it could not find one I completely removed Java from my machine and reinstalled the client. It did not install a JRE, and it obviously failed to start with an "unable to locate Java" error.

    Do I need to download and install a clean OpenJDK reference implementation just to run Intermapper Remote Access?  I really try to avoid running multiple Java environments on my machine, especially when they are the same version of Java.

    Thanks for any advice,

    Tim

  • Intermapper server source interface

    Is there a way, by map or device, to send probes from an alternative interface on the intermapper server?

    My specific scenario is using ping tests from a single intermapper server out of multiple network interfaces connected to different points in my network.

    I am attempting to track ping times, primarily to the internet, from the different layers of my firewall architecture, to track the latency the firewalls incur.  What I need to do is what linux ping does with the -b option, it binds to a specified interface instead of using the normal routing table.

    The reason I need to do this is I need to send pings to one IP address from multiple places so there is a valid basis for comparison.

    It is sort of the opposite of directly attaching a subnet to an interface to avoid routing the probes, which I already do for my management network.  I that case the normal routing table works as intended and automatically sends probe for the attached subnet out the correct interface.