Author Topic: runspecvirt.sh not progressing  (Read 12722 times)

tdeneau

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-1
runspecvirt.sh not progressing
« on: December 05, 2016, 12:56:20 PM »
Have set up the server VMs for one tile and also the VM for one client and am following the instructions for starting specvirt from the client VM.

I noticed that for the directions in 5.0:
   cd /opt/SPECvirt
   ./runspecvirt.sh

The runspecvirt.sh and assoicated files are actually in /opt/SPECvirt/helper-sc2013.
But I copied them up to /opt/SPECvirt and continued.

I noticed I also had to have the name client in the client's /etc/hosts file, not just client1 and specdriver.

Anyway, now it looks like client java processes are starting up but I don't see any progress after that.
Below are some of the log files.



primectrl.out

2016-12-05 13:48:53:245 Mon Dec 05 13:48:53 CST 2016
2016-12-05 13:48:53:279 RMI server started: client1:9990
2016-12-05 13:48:53:284 [INFO] This is a perf-only benchmark run. Skipping active idle polling interval.
2016-12-05 13:48:53:284 PrimeControl: preparing client drivers.
2016-12-05 13:48:53:341 PrimeControl: starting clients...
2016-12-05 13:48:53:367 PrimeControl: PTDs not used for this benchmark run!
2016-12-05 13:48:53:367 PrimeControl: starting 4 masters.

Clientmgr1_1088.out

2016-12-05 13:48:33:224 Creating clientmgr using RMI Registry port 1088
2016-12-05 13:48:33:292 client:1088 ready...
2016-12-05 13:48:53:344 Client path: /opt/SPECjAppServer2004/classes
command line is: [java, -jar, specjappclient.jar, -p, 1091]
2016-12-05 13:48:53:356 Client path: /opt/SPECweb2005
command line is: [java, -jar, specwebclient.jar, -p, 1010]
2016-12-05 13:48:53:360 Client path: /opt/SPECimap
command line is: [java, -jar, specimapclient.jar, -p, 1200]
2016-12-05 13:48:53:362 Client path: /opt/SPECbatch
command line is: [java, -jar, specbatchclient.jar, -p, 1902]

Messages from: 10.236.10.156:1091
-> 2016-12-05 13:48:53:531 Creating jappclient using RMI Registry port 1091
-> 2016-12-05 13:48:53:602 client:1091 ready...

Messages from: 10.236.10.156:1010
-> 2016-12-05 13:48:53:552 Creating specwebclient using RMI Registry port 1010
-> 2016-12-05 13:48:53:615 client:1010 ready...

Messages from: 10.236.10.156:1200
-> 2016-12-05 13:48:53:607 SPECvirt-IMAP version SPECvirt-IMAP v1.1
-> 2016-12-05 13:48:53:608 specimapclient: client1:1200 ready...

Messages from: 10.236.10.156:1902
-> Creating specbatchclient using RMI Registry port 1902
-> client:1902 ready...


Clientmgr1_1092.out
2016-12-05 13:48:33:278 Creating clientmgr using RMI Registry port 1092
2016-12-05 13:48:33:316 client:1092 ready...


Clientmgr1_1096.out
2016-12-05 13:48:33:296 Creating clientmgr using RMI Registry port 1096
2016-12-05 13:48:33:327 client:1096 ready...
Mon Dec  5 13:48:52 CST 2016: Starting webInit.sh
Filesystem           1K-blocks     Used Available Use% Mounted on
/dev/mapper/VolGroup-lv_root
                      17938864  2483328  14537624  15% /
Stopping httpd: [  OK  ]
Filesystem           1K-blocks     Used Available Use% Mounted on
/dev/mapper/VolGroup-lv_root
                      17938864  2483328  14537624  15% /
tmpfs                   510064        0    510064   0% /dev/shm
/dev/vda1               487652    38720    423332   9% /boot
/dev/vdb              51475068 33286072  15567556  69% /home/webfiles/downloads



Clientmgr1_1098.out

2016-12-05 13:48:33:287 Creating clientmgr using RMI Registry port 1098
2016-12-05 13:48:33:315 client:1098 ready...
Stopping Appserver (will fail if already stopped)

Stopping Emulator (will fail if already stopped)
Clearing Appserver message queue and log files
Remove postgres transaction logs
Restore the Database
Truncate largeorder table to clear pending requests from previous runs
Starting Appserver
Starting Emulator


« Last Edit: December 05, 2016, 03:01:54 PM by tdeneau »

ChrisFloyd

  • Moderator
  • Jr. Member
  • *****
  • Posts: 52
  • Karma: +2/-0
Re: runspecvirt.sh not progressing
« Reply #1 on: December 05, 2016, 06:21:11 PM »
Tom,

Can you verify that the firewall is off for your master (prime-controller), all of your clients, and SUT VMs?  Also, can you please increase the DEBUG level to 3 in Control.config and then re-run and provide us with the output of those same Client_Mgr*.log files?  It appears that either the webserver or appserver are not starting/initializing properly.

Thanks,

Chris

tdeneau

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-1
Re: runspecvirt.sh not progressing
« Reply #2 on: December 05, 2016, 06:45:07 PM »
firewall is off in all VMs including client.
will collect data with DEBUG level =3

tdeneau

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-1
Re: runspecvirt.sh not progressing
« Reply #3 on: December 05, 2016, 07:01:00 PM »
For some reason, DEBUG=3 is not any more verbose

Here are the logs from the logs directory:
client-10.236.10.156_1010.log
=======
2016-12-05 17:54:46:513 Creating specwebclient using RMI Registry port 1010
2016-12-05 17:54:46:594 client:1010 ready...

client-10.236.10.156_1091.log
=======
2016-12-05 17:54:46:513 Creating jappclient using RMI Registry port 1091
2016-12-05 17:54:46:607 client:1091 ready...

client-10.236.10.156_1200.log
=======
2016-12-05 17:54:46:624 SPECvirt-IMAP version SPECvirt-IMAP v1.1
2016-12-05 17:54:46:642 specimapclient: client1:1200 ready...

client-10.236.10.156_1902.log
=======
Creating specbatchclient using RMI Registry port 1902
client:1902 ready...


And the clientmgr logs from /opt/SPECvirt...

Clientmgr1_1088.out
=======
2016-12-05 17:54:26:262 Creating clientmgr using RMI Registry port 1088
2016-12-05 17:54:26:290 client:1088 ready...
2016-12-05 17:54:46:316 Client path: /opt/SPECjAppServer2004/classes
command line is: [java, -jar, specjappclient.jar, -p, 1091]
2016-12-05 17:54:46:325 Client path: /opt/SPECweb2005
command line is: [java, -jar, specwebclient.jar, -p, 1010]
2016-12-05 17:54:46:331 Client path: /opt/SPECimap
command line is: [java, -jar, specimapclient.jar, -p, 1200]
2016-12-05 17:54:46:339 Client path: /opt/SPECbatch
command line is: [java, -jar, specbatchclient.jar, -p, 1902]

Messages from: 10.236.10.156:1091
-> 2016-12-05 17:54:46:513 Creating jappclient using RMI Registry port 1091
-> 2016-12-05 17:54:46:607 client:1091 ready...

Messages from: 10.236.10.156:1010
-> 2016-12-05 17:54:46:513 Creating specwebclient using RMI Registry port 1010
-> 2016-12-05 17:54:46:594 client:1010 ready...

Messages from: 10.236.10.156:1200
-> 2016-12-05 17:54:46:624 SPECvirt-IMAP version SPECvirt-IMAP v1.1
-> 2016-12-05 17:54:46:642 specimapclient: client1:1200 ready...

Messages from: 10.236.10.156:1902
-> Creating specbatchclient using RMI Registry port 1902
-> client:1902 ready...

Clientmgr1_1092.out
=======
2016-12-05 17:54:26:213 Creating clientmgr using RMI Registry port 1092
2016-12-05 17:54:26:257 client:1092 ready...

Clientmgr1_1094.out
=======
2016-12-05 17:54:26:227 Creating clientmgr using RMI Registry port 1094
2016-12-05 17:54:26:268 client:1094 ready...


Clientmgr1_1096.out
=======
2016-12-05 17:54:26:294 Creating clientmgr using RMI Registry port 1096
2016-12-05 17:54:26:319 client:1096 ready...
Mon Dec  5 17:54:45 CST 2016: Starting webInit.sh
Filesystem           1K-blocks     Used Available Use% Mounted on
/dev/mapper/VolGroup-lv_root
                      17938864  2483328  14537624  15% /
Stopping httpd: [  OK  ]
Filesystem           1K-blocks     Used Available Use% Mounted on
/dev/mapper/VolGroup-lv_root
                      17938864  2483328  14537624  15% /
tmpfs                   510064        0    510064   0% /dev/shm
/dev/vda1               487652    38720    423332   9% /boot
/dev/vdb              51475068 33286072  15567556  69% /home/webfiles/downloads

Clientmgr1_1098.out
=======
2016-12-05 17:54:26:232 Creating clientmgr using RMI Registry port 1098
2016-12-05 17:54:26:277 client:1098 ready...
Stopping Appserver (will fail if already stopped)

Stopping Emulator (will fail if already stopped)
Clearing Appserver message queue and log files
Remove postgres transaction logs
Restore the Database
Truncate largeorder table to clear pending requests from previous runs
Starting Appserver
Starting Emulator


lroderic

  • Moderator
  • Full Member
  • *****
  • Posts: 167
  • Karma: +6/-0
Re: runspecvirt.sh not progressing
« Reply #4 on: December 05, 2016, 07:04:59 PM »
Is this CentOS/RHEL 6 or 7?

Is there a primectrl.out?

tdeneau

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-1
Re: runspecvirt.sh not progressing
« Reply #5 on: December 05, 2016, 07:14:26 PM »
the VMs are all running CentOS 6.8.
The host is running RHEL 7.2

Sorry, forgot to post primectrl.out, it is  a little more verbose

[root@client SPECvirt]# cat primectrl.out
2016-12-05 17:54:46:222 Mon Dec 05 17:54:46 CST 2016
2016-12-05 17:54:46:222 specvirt: maxPreRunTime = 1201
2016-12-05 17:54:46:222 specvirt: runTime = 7200
2016-12-05 17:54:46:222 specvirt: runTime = 7200
2016-12-05 17:54:46:222 specvirt: runTime = 7200
2016-12-05 17:54:46:223 specvirt: runTime = 7200
2016-12-05 17:54:46:223 specvirt: runTime = 600
2016-12-05 17:54:46:223 specvirt: runTime = 600
2016-12-05 17:54:46:223 specvirt: runTime = 600
2016-12-05 17:54:46:223 specvirt: runTime = 600
2016-12-05 17:54:46:254 RMI server started: client1:9990
2016-12-05 17:54:46:258 modVals: [Ljava.lang.String;@157d2287
2016-12-05 17:54:46:258 [INFO] This is a perf-only benchmark run. Skipping active idle polling interval.
2016-12-05 17:54:46:258 PrimeControl: preparing client drivers.
2016-12-05 17:54:46:258 PrimeControl: PRIME_HOST 0 = client1:1098
2016-12-05 17:54:46:258 PrimeControl: PRIME_HOST 1 = client1:1096
2016-12-05 17:54:46:258 PrimeControl: PRIME_HOST 2 = client1:1094
2016-12-05 17:54:46:258 PrimeControl: PRIME_HOST 3 = client1:1092
2016-12-05 17:54:46:259 PrimeControl: Master 1: client1:1098
2016-12-05 17:54:46:259 PrimeControl: Master 2: client1:1096
2016-12-05 17:54:46:260 PrimeControl: Master 3: client1:1094
2016-12-05 17:54:46:260 PrimeControl: Master 4: client1:1092
2016-12-05 17:54:46:260 PrimeControl: adding host client1:1098
2016-12-05 17:54:46:266 PrimeControl: adding host client1:1096
2016-12-05 17:54:46:270 PrimeControl: adding host client1:1094
2016-12-05 17:54:46:277 PrimeControl: adding host client1:1092
2016-12-05 17:54:46:285 First client for 0: 10.236.10.156:1091
client[0][0]: 10.236.10.156:1091
remote client "10.236.10.156" added
2016-12-05 17:54:46:289 PrimeControl: done in client for loop
2016-12-05 17:54:46:292 First client for 1: 10.236.10.156:1010
client[1][0]: 10.236.10.156:1010
2016-12-05 17:54:46:293 PrimeControl: done in client for loop
2016-12-05 17:54:46:307 First client for 2: 10.236.10.156:1200
client[2][0]: 10.236.10.156:1200
2016-12-05 17:54:46:308 PrimeControl: done in client for loop
2016-12-05 17:54:46:311 First client for 3: 10.236.10.156:1902
client[3][0]: 10.236.10.156:1902
2016-12-05 17:54:46:312 PrimeControl: done in client for loop
creating ClientThread-0
2016-12-05 17:54:46:313 PrimeControl: setting job: 0
2016-12-05 17:54:46:313 PrimeControl: client: getting job...done=0
2016-12-05 17:54:46:313 PrimeControl: client: waiting for all done...done=0
2016-12-05 17:54:46:313 PrimeControl: got job: 0
2016-12-05 17:54:46:313 PrimeControl: starting clients...
2016-12-05 17:54:46:313 PrimeControl: clients.length = 4
2016-12-05 17:54:46:313 PrimeControl: clients[0].length = 1
2016-12-05 17:54:46:313 PrimeControl: starting clients[0][0]: 10.236.10.156:1091
2016-12-05 17:54:46:324 PrimeControl: started client: 10.236.10.156:1091
2016-12-05 17:54:46:324 PrimeControl: clients[1].length = 1
2016-12-05 17:54:46:324 PrimeControl: starting clients[1][0]: 10.236.10.156:1010
2016-12-05 17:54:46:330 PrimeControl: started client: 10.236.10.156:1010
2016-12-05 17:54:46:331 PrimeControl: clients[2].length = 1
2016-12-05 17:54:46:331 PrimeControl: starting clients[2][0]: 10.236.10.156:1200
2016-12-05 17:54:46:338 PrimeControl: started client: 10.236.10.156:1200
2016-12-05 17:54:46:338 PrimeControl: clients[3].length = 1
2016-12-05 17:54:46:339 PrimeControl: starting clients[3][0]: 10.236.10.156:1902
2016-12-05 17:54:46:347 PrimeControl: started client: 10.236.10.156:1902
2016-12-05 17:54:46:347 PrimeControl: client: getting job...done=1
2016-12-05 17:54:46:347 PrimeControl: done starting clients
2016-12-05 17:54:46:347 PrimeControl: PTDs not used for this benchmark run!
2016-12-05 17:54:46:347 PrimeControl: starting 4 masters.
2016-12-05 17:54:46:347 PrimeControl: entered startMasters(); remoteMasters.length = 4
2016-12-05 17:54:46:348 PrimeControl: getting job... id=0
2016-12-05 17:54:46:356 PrimeControl: getting job... id=1
2016-12-05 17:54:46:357 PrimeControl: getting job... id=2
2016-12-05 17:54:46:359 PrimeControl: calling primeJob.setJob(10).
2016-12-05 17:54:46:359 PrimeControl: setting job: 10
2016-12-05 17:54:46:359 PrimeControl: got job: 10; id=2
2016-12-05 17:54:46:359 PrimeControl: switch: jobNumber=10; id=2
2016-12-05 17:54:46:359 PrimeControl: got job: 10; id=1
2016-12-05 17:54:46:359 PrimeControl: switch: jobNumber=10; id=1
2016-12-05 17:54:46:361 PrimeControl: getting job... id=3
2016-12-05 17:54:46:361 PrimeControl: got job: 10; id=3
2016-12-05 17:54:46:362 PrimeControl: switch: jobNumber=10; id=3
2016-12-05 17:54:46:362 PrimeControl: getting job... id=3
2016-12-05 17:54:46:363 PrimeControl: got job: 10; id=0
2016-12-05 17:54:46:363 PrimeControl: switch: jobNumber=10; id=0
2016-12-05 17:55:14:535 PrimeControl: getting job... id=2
2016-12-05 17:55:19:730 PrimeControl: getting job... id=0

lroderic

  • Moderator
  • Full Member
  • *****
  • Posts: 167
  • Karma: +6/-0
Re: runspecvirt.sh not progressing
« Reply #6 on: December 06, 2016, 10:12:48 AM »
Tom, please set NUM_WORKLOADS=1 and let's see if we can get db/appserver working by itself.

Lisa

tdeneau

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-1
Re: runspecvirt.sh not progressing
« Reply #7 on: December 06, 2016, 01:12:55 PM »
Lisa --

Just wondering, the Example VM Setup Guide recommends rebooting all VMs before running runspecvirt.sh.  After rebooting is there something that must be done on each VM to get them into a state where they can accept connections?

-- Tom


NUM_WORKLOADS set to 1

SPECvirt/logs/client-1091.log


2016-12-06 11:01:43:497 Creating jappclient using RMI Registry port 1091
2016-12-06 11:01:43:523 client:1091 ready...
Driver Host: client     Tile Number:0
2016-12-06 11:02:36:901 matchOut() messages set ...
2016-12-06 11:02:36:901 Starting rmiregistry; bindWait = 45000
2016-12-06 11:03:21:902 Starting Controller; bindWait = 45000
2016-12-06 11:03:21:912 waiting for: Binding controller to /
rec'd notifyInterrupt(101) call
Binding controller to //client:2098/Controller
Launcher: done in waitMatch(0)
2016-12-06 11:04:07:063 Starting Agents
---------------//client:2098/Controller
Calling switchLog as master
url[0] is : http://specemulator:8080/Emulator/EmulatorServlet?cmd=switchlog
url[1] is : http://specdelivery:8000/Supplier/DeliveryServlet?cmd=switchlog
2016-12-06 11:04:52:110 Exception encountered executing runScript(): java.net.ConnectException: Connection refused (Connection refused)
java.net.ConnectException: Connection refused (Connection refused)


prime_client1_1098.log

2016-12-06 11:02:36:753 Looking up SPECvirt controller: client1
2016-12-06 11:02:36:827 masterID: 0, tile: 0, workload: 0
2016-12-06 11:02:36:828 hostname: client1
Hostname of prime client: client
2016-12-06 11:02:36:848 Tue Dec 06 11:01:43 CST 2016
2016-12-06 11:02:36:869 RMI server started: client1:9900
2016-12-06 11:02:36:870 Total clients: 1
2016-12-06 11:02:36:870 Adding host client1:1091
2016-12-06 11:02:36:878 Setting up clients...
2016-12-06 11:02:37:631 calling getHostVM() on jappclient...
2016-12-06 11:04:52:138 Remote exception in setup() from client1:1091
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
    java.rmi.RemoteException: Connection refused (Connection refused); nested exception is:
    java.lang.Exception: Connection refused (Connection refused)
2016-12-06 11:04:52:138 Aborting...
2016-12-06 11:04:52:142 abortTest() signal sent...
2016-12-06 11:04:52:143 clientsRunning = true
2016-12-06 11:04:52:143 calling client.exit()...

lroderic

  • Moderator
  • Full Member
  • *****
  • Posts: 167
  • Karma: +6/-0
Re: runspecvirt.sh not progressing
« Reply #8 on: December 06, 2016, 11:02:27 PM »
You only need to reboot the VMs after you set them up to make sure the changes applied during the workload VM tuning stick. So reboot all VMs as documented in Section 5.0.

Please post Control.config. You need to make sure the SPECpoll process is running on each VM (it doesn't run on the client). The helper script pollmecheck.sh checks that SPECpoll process is running on each workload VM. You can run that and/or on each VM check the contents of /tmp/pollme.out (for example, webserver):

[root@webserver ~]# cat /tmp/pollme.out
Creating RMI listener using RMI Registry port 8001
webserver/10.4.3.61:8001 ready...
2015-10-27 19:20:07:588 contacting host 'infraserver'...
webserver: 1445944807646
infraserver: 1445944807645

You can have Control.config automatically stop and restart the SPECpoll agents between tests by calling the helper script pollInit.sh in Control.config, but I don't usually stop/restart the processes. Once it's up, it tends to stay up unless you reboot the VMs.

tdeneau

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-1
Re: runspecvirt.sh not progressing
« Reply #9 on: December 07, 2016, 05:30:04 PM »
OK, I wanted to start with one workload, and the workload being the Webserver
I have attached the Control.config I am using (Not really sure the best way to run only webserver but I swapped [1] and
  • in all the arrays that looked like they needed it)

I am getting further than before but am getting the following errors in the log

2016-12-07 16:17:22:620 SslConnection:  IOException during SSL handshake: javax.net.ssl.SSLHandshakeException: No appropriate protocol\
 (protocol is disabled or cipher suites are inappropriate)
2016-12-07 16:17:22:620 Connection:  createSocket() failed.
2016-12-07 16:17:22:621 SslConnection:  IOException during SSL handshake: javax.net.ssl.SSLHandshakeException: No appropriate protocol\
 (protocol is disabled or cipher suites are inappropriate)
2016-12-07 16:17:22:621 Connection:  Write to socket failed! IOException was: javax.net.ssl.SSLException: Connection has been shutdown\
: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
2016-12-07 16:17:22:622 SslConnection:  IOException during SSL handshake: javax.net.ssl.SSLHandshakeException: No appropriate protocol\
 (protocol is disabled or cipher suites are inappropriate)
2016-12-07 16:17:22:622 SPECweb_Support:  STATE 0; makeHttpRequest() failed.

lroderic

  • Moderator
  • Full Member
  • *****
  • Posts: 167
  • Karma: +6/-0
Re: runspecvirt.sh not progressing
« Reply #10 on: December 07, 2016, 05:35:39 PM »
SSLv3 is disabled by default in your version of Java. See https://www.spec.org/virt_sc2013/docs/SPECvirt_TechnicalSupport.html#Webserver

If you want to use TLS (you don't have to), we're adding this to next revision of the Technical Support FAQ:

Q. If I want to use TLS, which cipher suites do you recommend?

A. Many Java 1.7 JRE versions do not support TLS_RSA_WITH_AES_128_GCM_SHA256. We found that the following two cipher suites perform similarly to SSLv3 and are available options for Java 1.7 JREs:

TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_CBC_SHA

Note that the CPU consumption on the SPECweb prime client driver will likely be noticeably higher. Please review the documentation for your version of Java 1.7 to verify which cipher suites are supported. Also, some cipher suites must be enabled explicitly in the JRE settings.

Alternatively, Java 1.8 offers a larger range of TLS cipher suites (namely, the TLS GCM varieties). If Java 1.7 cipher options are too limited, you may want to consider upgrading to Java 1.8 to enable and experiment with the additional cipher options.

Lisa
« Last Edit: December 07, 2016, 05:37:56 PM by lroderic »

tdeneau

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-1
Re: runspecvirt.sh not progressing
« Reply #11 on: December 07, 2016, 05:54:28 PM »
Lisa --

Following the directions in https://www.spec.org/virt_sc2013/docs/SPECvirt_TechnicalSupport.html#Webserver
have made those changes on just the webserver, do they need to be made anywhere else?

Also after making the changes, what do I have to restart if anything on the webserver or infraserver?

-- Tom


tdeneau

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-1
Re: runspecvirt.sh not progressing
« Reply #12 on: December 07, 2016, 06:17:12 PM »
The only java process I see running on the webserver is pollme.jar so I wasn't sure what would be reading the modified java.security file.

tdeneau

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-1
Re: runspecvirt.sh not progressing
« Reply #13 on: December 07, 2016, 06:23:36 PM »
Still getting same No Appropriate Protocol errors

Attaching java.security from the webserver.

tdeneau

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-1
Re: runspecvirt.sh not progressing
« Reply #14 on: December 08, 2016, 01:03:01 PM »
Just a note that when I run a little java program, attached, that calls GetSupportedCipherSuites or GetEnabledCipherSuites I do not see SSL_RSA_WITH_RC5_128_MD5 in either one of those lists (this is after following the instructions and having
jdk.tls.legacyAlgorithms= \
        K_NULL, C_NULL, M_NULL, \
        DHE_DSS_EXPORT, DHE_RSA_EXPORT, DH_anon_EXPORT, DH_DSS_EXPORT, \
        DH_RSA_EXPORT, RSA_EXPORT, \
        DH_anon, ECDH_anon, \
        RC4_128, RC4_40, DES_CBC, DES40_CBC, SSL_RSA_WITH_RC5_128_MD5

Should I be seeing SSL_RSA_WITH_RC5_128_MD5 in those lists?

-- Tom