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 <[email protected]>:
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...

Network or server failure.  Please check your Internet connection to libopen 
and choose Retry Network.  If you need to enter Offline Mode, choose Ignore 
Errors in this and subsequent dialogs.  If you believe this error is due to a 
bug in Evergreen and not network problems, please contact your help desk or 
friendly Evergreen administrators, and give them this information:
method=open-ils.auth.session.retrieve
params=["69346ac61d8f8967882936221b3d2ab2"]
THROWN:
{"message":"au is not 
defined","fileName":"http://libopen/opac/common/js/JSON_v1.js","lineNumber":46,"stack":"decodeJS([object
 Object])@http://libopen/opac/common/js/JSON_v1.js:46\ndecodeJS([object 
Object])@http://libopen/opac/common/js/JSON_v1.js:46\n([object 
Array],0)@http://libopen/opac/common/js/JSON_v1.js:58\njsIterate([object 
Array],(function (o, i) {o[i] = 
decodeJS(o[i]);}))@http://libopen/opac/common/js/JSON_v1.js:24\ndecodeJS([object
 Array])@http://libopen/opac/common/js/JSON_v1.js:57\n([object 
Object],\"payload\")@http://libopen/opac/common/js/JSON_v1.js:58\njsIterate([object
 Object],(function (o, i) {o[i] = 
decodeJS(o[i]);}))@http://libopen/opac/common/js/JSON_v1.js:28\ndecodeJS([object
 
Object])@http://libopen/opac/common/js/JSON_v1.js:57\nJSON2js(\"{\\\"payload\\\":[{\\\"__c\\\":\\\"au\\\",\\\"__p\\\":[null,null,null,null,null,null,null,null,null,null,null,null,\\\"1\\\",null,\\\"t\\\",null,\\\"f\\\",null,1,0,\\\"2009-02-12T11:35:26-0600\\\",\\\"0.00\\\",null,\\\"1979-01-22T00:00:00-0600\\\",null,null,\\\"2012-02-12T11:35:26-0600\\\",\\\"System
 
Account\\\",\\\"Administrator\\\",1,1,1,null,\\\"identification\\\",null,\\\"none\\\",null,\\\"t\\\",1,null,\\\"\\\",null,null,1,null,1,null,\\\"t\\\",1,\\\"admin\\\",null,\\\"f\\\"]}],\\\"status\\\":200}\")@http://libopen/opac/common/js/JSON_v1.js:9\n()@http://libopen/opac/common/js/RemoteRequest.js:319\n([object
 
Object])@http://libopen/xul/rel_1_4_0_2/server/main/JSAN.js:250\n(\"open-ils.auth\",\"open-ils.auth.session.retrieve\",[object
 Array],[object Object],undefined,[object 
Object])@http://libopen/xul/rel_1_4_0_2/server/main/JSAN.js:379\n(\"open-ils.auth\",\"open-ils.auth.session.retrieve\",[object
 Array],undefined,undefined,[object 
Object])@http://libopen/xul/rel_1_4_0_2/server/main/JSAN.js:362\n(\"open-ils.auth\",\"open-ils.auth.session.retrieve\",[object
 Array],undefined,undefined,[object 
Object])@http://libopen/xul/rel_1_4_0_2/server/main/JSAN.js:277\n(\"FM_AU_RETRIEVE_VIA_SESSION\",[object
 
Array])@http://libopen/xul/rel_1_4_0_2/server/main/JSAN.js:239\nwsinfo_init()@http://libopen/xul/rel_1_4_0_2/server/main/ws_info.xul:44\nonload([object
 
Event])@http://libopen/xul/rel_1_4_0_2/server/main/ws_info.xul:1\n@:0\n","name":"ReferenceError"}
STATUS:

Reply via email to