BR 4.20o Client Server under 32bit CentOS Linux

[Gabriel]

I'm trying to set up BR 4.20o Client Server under 32bit CentOS Linux.

We had issues with PAM but we got those resolved. We're getting past the PAM part of the authentication, then its failing with an error.

ACC CS Error.gif (3.65 KiB) Viewed 29611 times

The BR CS Logfile contains the following information:

ACC CS Log.gif (9.62 KiB) Viewed 29611 times

I am able to start BR just fine if I login through putty with the same user and enter the following commands:
cd /u/wb
/u/wb/wb -/u/wb/wbconfig.acc

Does anyone have any suggestions? Does anyone have BR CS working successfully with a Linux server under BR 4.2?

Gabriel

[mluchterhand]

That particular log file looks normal to me. Do you have any other log files you can share? I'm curious what your STDERR log is showing, if anything. Perhaps that will have more information that may help narrow down the problem. In my experience, the client-server error receiving data errors are almost always tied to some networking issue.

[Gabriel]

The problem is the final line in the log file says its about to start brserver. But it doesn't ever start it. And nothing else is added to the logfile.

We created a BR log file too, but nothing is placed in it when CS attempts to start up.

It may well be a networking issue. We have lots of strange things going on with this network. Unfortunately the test network we're working on has completely different issues then the ones we'll run into on the live network .. but i guess that just makes it interesting.

[bluesfannoz]

I would make sure the user your logging in with has full rights to the folder where the wbserver/brserver.dat file is getting created. That often time leads to strange errors like this when logging in.

[bluesfannoz]

Another thing to check is to make sure there are no flags set on the user like Change password at login BR does not know how to handle those situations so often it will kick you out with a strange error.

[Gabriel]

Those are both good suggestions, and I've run into them before with Windows servers where i'm in more familiar territory.

The user accounts we're testing with are able to log in just fine through Putty, and we're able to start BR from putty without problems..

gabriel

[bluesfannoz]

Can you post your brconfig including your drive statements?

[Gabriel]

Code: Select all

logging 10,/u/wb/startlog.txt
WBSERVER :/wbserver/
DRIVE C, /u/wb/cdsk,x,\
COLLATE ALTERNATE
rem SHMSIZE 64000
BREAK 8
WORKSTACK 917000 
RPNSTACK 10000
FLOWSTACK 1000
FORSTACK 2000
SCREEN B 84,H 0F,I 00,N 03,R 40,S 40,U 1D
SPOOLCMD /u/wb/shcc/qmisa [SPOOLFILE] r
DATAHILITE OFF
SEARCH_CHAR OFF
OPTION 29
OPTION 56 ON
OPTION 33 64

I'm a little unsure of what the wbserver line is doing, so I just tried playing around with it but I couldn't get anything to work.

Whats weird is there is a file on the server called "\wbserver.dat" with the beginning "\":

acc wbserver dat.gif (5.5 KiB) Viewed 29602 times

That seems strange to me. But I changed the wbserver specification in the wbconfig.acc file, but I still get the same errors.

Gabriel

[bluesfannoz]

I got to thinking.. Is it possible you have non matching versions between your client and your server? I experienced a similar error when I was doing that. It would also explain why it works with putty but not with the brclient.

[mluchterhand]

Steve may be on to something. What are the contents of your brlistener.conf?

Ours looks something like this:

Code: Select all

logfile=/usr/br/brlistener.log
loglevel=10
[
LABEL=BR431fb
EXECUTABLE=/usr/br/br431fb_executable.sh
STARTDIR=/usr/br/
STDERR=/usr/br/br431fb_stderr.log
CONFIG=/usr/br/br431fb_config.sys
]

Then the contents of the EXECUTABLE file referenced in the listener file is:

Code: Select all

TERM=ansi
PATH=$PATH:/usr/br
export PATH TERM
umask 000
/usr/br/brserver431fb run mainmenu.wb -10+ $*

[Gabriel]

I'm using the brlistener, and brclient from ftp://ftp.brulescorp.com/Dll_Distr/CURRENT/420o/, and their br version is 4.20o.

[bluesfannoz]

Do you have the correct brserver instaled for 4.20o The server was a separate application in 4.20 from the regular and you would need your brlistener.conf set to run that version when they connect.

[Gabriel]

Oh my goodness, Steve, I can't believe I forgot that. This is embarrassing. What an obvious step. I'd gotten so used to working with 4.3 that I forgot it was a separate executable in 4.2!

Thats all it was! I put the proper brserver in place, set the appropriate permissions, and voila!

[bluesfannoz]

Fully understand. It came to my mind because I had obviously been there and done that! Glad you got it resolved!