OE 11 Webspeed

[JamesBowen]

I'm in the process of upgrading to OE 11 on Linux server.

I've noticed that on performance is a lot slower on OE 11 compared to OE 10.2B also upon each web/AJAX request I've noticed this error message in the WebSpeed Broker.

I'm also getting other error messages in the Apache logs of "Timeout waiting for output from CGI script".

I can't find anything on the Progress online KB


Snippet from the WebSpeed broker file.

[12/03/23@12:38:46.906+1300] P-025597 T-C-0001 3 UB Basic      Client connected : . (8533)
[12/03/23@12:38:46.907+1300] P-025597 T-C-0001 3 UB Basic      Enqueued request UBRQ_CONNECT issued to S-0002 requestID= <none>
[12/03/23@12:38:46.908+1300] P-025597 T-C-0001 3 UB Basic      ubWSclientThread.processConnRsp(): ubRsp = 0, getNeedNewConnID() = false
[12/03/23@12:38:46.909+1300] P-025597 T-C-0001 3 UB Basic      IOException received on client connection C-0001 : Inbound closed before receiving peer''s close_notify: possible truncation attack?. (8085)
[12/03/23@12:38:46.929+1300] P-025597 T-C-0001 3 UB Basic      Client disconnected : . (8534)

 

[JamesBowen]

OE: Version 11

Apache: Version 2.2.3

Operating system: Redhat Enterprise Linux 5

Kernel and CPU: Linux 2.6.18-128.1.6.el5 on i686
Processor information:Intel(R) Xeon(TM) CPU 3.20GHz, 2 cores
Java: java version "1.6.0_20"

Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
​

 

[JamesBowen]

I starting to think this a perfectly normal response message in the broker log file. I had the log level set to verbose. I've now changed it to BASIC and the message has not gone.

 

[JamesBowen]

I've now tried installing OE 11 on another server and I still have have the problem. So far it only works on redhat se 5. Has any body else managed to get OE 11 working on centos6.2?

 

[JamesBowen]

SOLVED

The problem was that the passwords in the OS's /etc/shadow file was storing password as SHA-1. OE can't handle SHA-1encrytion method for passwords, only DES/MD5 encryption methods can be used (this does not apply to the ABL).

Quick fix was to run setup from the command line and change the 'Authentication Configuration', enabling the 'Use MD5 passwords' option. Then change the password for the progress user using the passwd command. Restart the WebSpeed brokers and it's up and running.

âââââââââââââââââ⤠Authentication Configuration ââââââââââââââââââ
â                                                                 â
â  User Information        Authentication                         â
â  [ ] Cache Information   [B]
[*] Use MD5 Passwords[/B]                  â
â  [ ] Use Hesiod          
[*] Use Shadow Passwords               â
â  [ ] Use LDAP            [ ] Use LDAP Authentication            â
â  [ ] Use NIS             [ ] Use Kerberos                       â
â  [ ] Use Winbind         
[*] Use Fingerprint reader             â
â                          [ ] Use Winbind Authentication         â
â                          
[*] Local authorization is sufficient  â
â                                                                 â
â            ââââââââââ                      ââââââââ             â
â            â Cancel â                      â Next â             â
â            ââââââââââ                      ââââââââ             â
â                                                                 â
â                                                                 â
âââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ