BR Client-Server 4.2 Installation
Posted: Fri Nov 30, 2012 4:47 pm
Hi, we recently purchased BR 4.2 and a new Red Hat Enterprise Linux 6.3 Santiago 64-bit server. One of the first packages I installed was redhat-lsb.i686 to allow 32-bit applications to be run. I am under the impressions that you need BR 4.3 to run true 64-bit. Is that correct?
Anyhow, I am currently having a problem with the listener that I downloaded from ftp://ftp.brulescorp.com/Dll_Distr/BETA ... ux_lsb_32/. The brlist script runs fine and the listener automatically starts on bootup as expected. When I try to connect from a client, I am receiving "Socket Error: Connection Failed" on the client side. I am not prompted for a user name or password. When I look at the listener log on the server I see the following:
(6) - Fri Nov 30 11:08:59 2012
Log level set to 10.
(8) - Fri Nov 30 11:08:59 2012
Made new application entry for br420o
(6) - Fri Nov 30 11:08:59 2012
The configuration file /etc/brlistener.conf has been read.
(6) - Fri Nov 30 11:08:59 2012
Starting brlistener version 2.3 on port 8555. brlistener was made from br source base 4.30beta+u on 2011-11-01
(6) - Fri Nov 30 11:08:59 2012
BrListener has daemonized
(8) - Fri Nov 30 15:46:17 2012
accepting connection
(0) - Fri Nov 30 15:46:22 2012
Accepting SSL connection failed SSL_accept an EOF was observed that violates the protocol.
(8) - Fri Nov 30 15:46:27 2012
accepting connection
(0) - Fri Nov 30 15:46:32 2012
Accepting SSL connection failed SSL_accept an EOF was observed that violates the protocol.
I can not find any documentation on SSL and the brlistener. Here is what I have confirmed/tried:
Port 8555 is open on the server
brserial.dat is present in /usr/brfolder
brlistener.conf is present in /usr/brfolder and /etc
brlistener is present and executable in /usr/brfolder and /usr/sbin
A file named brserver has been placed in /etc/pam.d/. The contents of that file follow:
#%PAM-1.0
auth include system-auth
account include system-auth
For the heck of it, I did try the 64-bit listener as well. I received the same log results so I do not think the issue is isolated to the 32-bit version.
I'd appreciate any info to steer me in the right direction. Thanks in advance.
Anyhow, I am currently having a problem with the listener that I downloaded from ftp://ftp.brulescorp.com/Dll_Distr/BETA ... ux_lsb_32/. The brlist script runs fine and the listener automatically starts on bootup as expected. When I try to connect from a client, I am receiving "Socket Error: Connection Failed" on the client side. I am not prompted for a user name or password. When I look at the listener log on the server I see the following:
(6) - Fri Nov 30 11:08:59 2012
Log level set to 10.
(8) - Fri Nov 30 11:08:59 2012
Made new application entry for br420o
(6) - Fri Nov 30 11:08:59 2012
The configuration file /etc/brlistener.conf has been read.
(6) - Fri Nov 30 11:08:59 2012
Starting brlistener version 2.3 on port 8555. brlistener was made from br source base 4.30beta+u on 2011-11-01
(6) - Fri Nov 30 11:08:59 2012
BrListener has daemonized
(8) - Fri Nov 30 15:46:17 2012
accepting connection
(0) - Fri Nov 30 15:46:22 2012
Accepting SSL connection failed SSL_accept an EOF was observed that violates the protocol.
(8) - Fri Nov 30 15:46:27 2012
accepting connection
(0) - Fri Nov 30 15:46:32 2012
Accepting SSL connection failed SSL_accept an EOF was observed that violates the protocol.
I can not find any documentation on SSL and the brlistener. Here is what I have confirmed/tried:
Port 8555 is open on the server
brserial.dat is present in /usr/brfolder
brlistener.conf is present in /usr/brfolder and /etc
brlistener is present and executable in /usr/brfolder and /usr/sbin
A file named brserver has been placed in /etc/pam.d/. The contents of that file follow:
#%PAM-1.0
auth include system-auth
account include system-auth
For the heck of it, I did try the 64-bit listener as well. I received the same log results so I do not think the issue is isolated to the 32-bit version.
I'd appreciate any info to steer me in the right direction. Thanks in advance.