Old Java 7

[deefdragon]

It appears that the current versions of java 7 are not able to work with idrac6. It may be necessary to specify a verison of java7 in the dockerfile that is known to work. I have gotten mine working with 7_80, and apperently 7_79 also works.

[DomiStyle]

Interesting, will take a look. Thanks for the tip!

[z3dm4n]

Confirmed.

[DomiStyle]

@deef0000dragon1 @z3dm4n Do you already have trouble building the image? The current Java version in the image is 1.7.0_95, there is no other version available in the OpenJDK repo for Ubuntu 16.04. 18.04 only has 1.8.0 and upward, which won't work anyway.

I just built the image locally and the latest version available worked with no issues.

[z3dm4n]

Hi Dominik,
image works smoothly, but connection to the remote console fails after some seconds. At first the connection is successful. After connecting via WebUI or VNC, the connection fails with "Login failed with access denied error." Hence I suspected, that @deef0000dragon1 experienced a similar issue as I did.
As there is no PPA archive where we could get prehistoric OpenJDK packages from, I am not sure how to address this, if this is caused by newer versions of this package.

[DomiStyle]

@z3dm4n Interesting, I couldn't reproduce that issue yet. Using domistyle/idrac6:latest and building the image fresh both work just fine for a longer period.

Does the same thing happen when you run the Java console on another machine?

[z3dm4n]

I'll re-check this issue on another server once I have time for this.

[deefdragon]

To specify the "not able to work with idrac6" bit, I was able to get the container started, and was easily able to get into the container. Unfortunately, The only thing that I would be greeted by once I was in was a pair of java notification boxes. One saying connecting, and the other saying connection failed.

This was the same issue that I was encountering with a local version of java. Downgrading to 7_80 allowed me to access the console.

It might be possible to get the required jre it from https://snapshot.debian.org/package/openjdk-7/
specifically here ? but I wouldnt know for sure.

[ipv6freely]

I ran into the same issue trying to connect to an iDRAC 6 session: the connection fails with "Login failed with access denied error."

[ptmorris1]

I had the same issue on windows as well using newer java 7. I was able to get this working by installing the Java JDK 7_80 and making it default inside the image. Have to commit the image which increases the size a bit but it works for me. Great container, thank you.

[ssmoss]

@ptmorris1 @ipv6freely @deefdragon @z3dm4n does this solve your issue #47 ?

[deefdragon]

I have deprecated my idrac6 system & upgraded unfortunately, so I can not confirm functionality.

[ssmoss]

I have deprecated my idrac6 system & upgraded unfortunately, so I can not confirm functionality.

No worries, thanks.

[second2falcon]

@ssmoss I know that this issue is quite old, but I think the problem is related to this.

My iDRAC cert recently expired, so now the IPMI KVM and the docker container stopped working.
Using JRE 6u45 on Windows it seems to work fine using the script from the ipmi-starter repo.

Is there maybe a way we could get the SSL expired error fixed (maybe with another version of Java)?

[ssmoss]

@second2falcon I have been using the Amazon Corretto Java, version 1.8.0 along with OpenWeb Start version 1.6.0 and I haven't had any issues. Are you using that?

[second2falcon]

@second2falcon I have been using the Amazon Corretto Java, version 1.8.0 along with OpenWeb Start version 1.6.0 and I haven't had any issues. Are you using that?

@ssmoss do you mean on the machine where I am using ipmi-starter or on the docker-idrac6 host?

[ssmoss]

I am running a Linux Virtual machine. Inside that virtual machine I am using Amazon Corretto Java and OpenWeb Start to connect.

In the end it was easier than trying to mess around with the docker container.