[OPEN-ILS-DEV] Evergreen install: Very close!

[Dale Arntson]

Hmm. Well that's good news indeed. I assumed it was a real timeout 
problem because my output didn't match the example output of the 
installation doc. (Not very deep reasoning, I admit.)

We are also having a problem with the new client admin login, which 
seems to result from some cruft that is getting picked up from an old 
1.2.2 client install. When we try to log in with the 1.4.0.2 client, it 
sees the old 1.2.2 registered workstation. It then says that it is not 
registered with this server, and throws the attached network failure 
error. The error says "the ou is not defined". This is presumably the ou 
from our old 1.2.2 server installation that it thinks we are trying to 
access. The old ou does not exist because we did not save any of our 
data from the old install. Does anyone know of a workaround for this 
problem? (By the way, we first uninstalled the old client, and deleted 
the install directory before we did the new install.)

Thanks,

-dale



Dan Scott wrote:
> 2009/2/16 Dale Arntson <arnt at uchicago.edu>:
>> Hi all,
>>
>> My Redhat 5 install is nearly there. But I have one more problem I would
>> like to pose to the dev-list. When I login as admin using srfsh, the login
>> succeeds, but then immediately times out. Im not sure how to read the logs
>> on this one. It seems like there may be a timeout set to 0 somewhere that
>> shouldn't be there. But I can't find any such timeout. But maybe some on the
>> list could comment?
>>
>> Thanks,
>>
>> -dale
>>
>> srfsh# login admin open-ils
>>
>> Received Data: "772300b1de59f02903567d6aa7ae300e"
>>
>> ------------------------------------
>> Request Completed Successfully
>> Request Time in seconds: 0.002844
>> ------------------------------------
>>
>> Received Data: {
>>  "ilsevent":0,
>>  "textcode":"SUCCESS",
>>  "desc":" ",
>>  "pid":5440,
>>  "stacktrace":"oils_auth.c:312",
>>  "payload":{
>>    "authtoken":"19422d7157c7fee398eb9aa897a12624",
>>    "authtime":420.000000
>>  }
>> }
>>
>> ------------------------------------
>> Request Completed Successfully
>> Request Time in seconds: 0.121702
>> ------------------------------------
>> Login Session: 19422d7157c7fee398eb9aa897a12624.  Session timeout:
>> 420.000000
>>
> 
> Are you interpreting the "Session timeout: 420.000000" statement as an
> indication that your session has timed out? That's actually an
> indication that your session will timeout in 420 seconds. It sounds
> like you might be able to declare success...
> 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: client_error.log
Url: http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20090216/0aceb957/attachment.txt