Bug 837239 - The HP Lights Out Management Console Does Not Work with Iced-Tea
Summary: The HP Lights Out Management Console Does Not Work with Iced-Tea
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: icedtea-web
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-03 09:50 UTC by Emmanuel Seyman
Modified: 2013-05-05 08:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-05 08:22:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
firefox output (18.07 KB, application/octet-stream)
2012-07-03 09:50 UTC, Emmanuel Seyman
no flags Details
updated firefox output (15.79 KB, text/plain)
2012-07-09 10:21 UTC, Emmanuel Seyman
no flags Details
Java standard error output (19.67 KB, text/plain)
2012-07-09 10:24 UTC, Emmanuel Seyman
no flags Details

Description Emmanuel Seyman 2012-07-03 09:50:12 UTC
Created attachment 595918 [details]
firefox output

Description of problem:
I'm unable to start an ILO Remote Console on an HP Server using Fedora's Firefox.

Version-Release number of selected component (if applicable):
icedtea-web-1.2-2.fc17.x86_64
firefox-13.0.1-1.fc17.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Login to the Integrated Lights-Out 2 (iLO) on a Hewlett-Packard ProLiant server web page using firefox 
2. Click the remote console tab
3. Click the third choice "Remote Console" to launch the java applet based console.
  
Actual results:
A popup window with: Error saying that the applet not initialized.

Expected results:
A popup window running the console on the server.

Additional info:
Attached is firefox's output with ICEDTEAPLUGIN_DEBUG=true LANG=C

Comment 1 Deepak Bhole 2012-07-04 17:46:02 UTC
Hi Emmanuel.

I thought I had seen a bug about this but cannot find it any more :/

Can you please also post the ~/.icedtea/log/* files from the run when ICEDTEAPLUGIN_DEBUG=true?

Comment 2 Emmanuel Seyman 2012-07-04 21:15:56 UTC
(In reply to comment #1)
> 
> I thought I had seen a bug about this but cannot find it any more :/

Bug #497408, perhaps?

> Can you please also post the ~/.icedtea/log/* files from the run when
> ICEDTEAPLUGIN_DEBUG=true?

I won't be back in the office until Monday. I'll post them then.

Comment 3 Deepak Bhole 2012-07-05 19:14:51 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > 
> > I thought I had seen a bug about this but cannot find it any more :/
> 
> Bug #497408, perhaps?
> 

Ah, that must have been it. So looks like you might be encountering a separate issue. I will wait for the logs. Thanks.

Comment 4 Emmanuel Seyman 2012-07-09 10:21:58 UTC
Created attachment 597034 [details]
updated firefox output

Comment 5 Emmanuel Seyman 2012-07-09 10:24:00 UTC
Created attachment 597035 [details]
Java standard error output

$HOME/.icedtea/log/ contains two files : an empty java.stdout and a java.stderr one. Here it is.

Comment 6 Deepak Bhole 2012-07-09 15:23:34 UTC
Thanks! Looks like a CNFE .. can you please run the following and post the output?

for i in `find ~/.icedtea/cache -name "*.jar"`; do 
  unzip -l $i 2>/dev/null | grep -i hp/ilo2/remcons/remcons && echo $i
done


Also, what does this show?

wget --no-check-certificate https://rac-coeos/com/hp/ilo2/remcons/remcons.class

Comment 7 Emmanuel Seyman 2012-07-10 09:41:14 UTC
(In reply to comment #6)
> 
> for i in `find ~/.icedtea/cache -name "*.jar"`; do 
>   unzip -l $i 2>/dev/null | grep -i hp/ilo2/remcons/remcons && echo $i
> done

The only file I have in ~/.icedtea/cache is ~/.icedtea/cache/0/https/rac-coeos/rc175p06.jar.info . It's empty.


> Also, what does this show?
> 
> wget --no-check-certificate
> https://rac-coeos/com/hp/ilo2/remcons/remcons.class

404 Not Found

Comment 8 Deepak Bhole 2012-07-12 16:59:11 UTC
Odd that there is a .info but no jar. What does this show?

wget --no-check-certificate https://rac-coeos//rc175p06.jar

Comment 9 Emmanuel Seyman 2012-07-13 08:09:31 UTC
(In reply to comment #8)
>
> Odd that there is a .info but no jar. What does this show?
> 
> wget --no-check-certificate https://rac-coeos//rc175p06.jar

404 Not Found

Comment 10 Emmanuel Seyman 2012-07-13 09:04:05 UTC
To be more specific, this is the ouput:


--2012-07-13 10:26:26--  https://rac-coeos//rc175p06.cab
Resolving rac-coeos... 192.168.199.1
Connecting to rac-coeos|192.168.199.1|:443... connected.
WARNING: cannot verify rac-coeos's certificate, issued by `/C=US/ST=Texas/L=Houston/O=Hewlett-Packard Company/OU=ISS/CN=ILOCZ20206438':
  Self-signed certificate encountered.
    WARNING: certificate common name `ILOCZ20206438' doesn't match requested host name `rac-coeos'.
HTTP request sent, awaiting response... 404 Not Found
2012-07-13 10:26:30 ERROR 404: Not Found.

Deepak, couldn't the self-signed certificate be the source of the problem?

Comment 11 Deepak Bhole 2012-07-16 17:36:41 UTC
That should've just been a warning though. Can you load/download the jar with firefox?

Comment 12 Emmanuel Seyman 2012-07-17 12:42:48 UTC
(In reply to comment #11)
>
> Can you load/download the jar with firefox?

No, I get the 404 errors even with Firefox.

Comment 13 Deepak Bhole 2012-07-18 18:09:53 UTC
Ah, just noticed that you tried .cab in comment 10 and thereafter.. can you please try the .jar from comment #8?

Comment 14 Emmanuel Seyman 2012-07-19 12:05:00 UTC
Same thing.

Request Error
HTTP/1.1 404 Not Found

Comment 15 Deepak Bhole 2012-07-19 14:19:35 UTC
Hmm, that is really odd. Do you by any chance know where that jar would/should be?

Comment 16 Emmanuel Seyman 2012-07-19 15:26:48 UTC
(In reply to comment #15)
>
> Hmm, that is really odd. Do you by any chance know where that jar
> would/should be?

Not at all. And the only result Google gives me is this bug report. :-(
I'll keep digging.

Comment 17 Emmanuel Seyman 2013-05-05 08:22:40 UTC
Revisiting this bug on Fedora 18 and against ILO4, I'm able to use ILO without problems.


Note You need to log in before you can comment on or make changes to this bug.