Re: 1.4.0 released

Sorry, I meant registering the client made the server start working...no 
errors...

On 9/24/2002 12:42 PM, Hunter Matthews had said:
> After you reregistered, it works, or the error is still there?
> 
> 
> 
> On Tue, 2002-09-24 at 13:41, Anthony Mendoza wrote:
> 
>>re-Registering the client worked...
>>
>>On 9/24/2002 10:16 AM, Hunter Matthews had said:
>>
>>>On Tue, 2002-09-24 at 14:06, Alex Kramarov wrote:
>>>
>>>
>>>>Now i get 
>>>>
>>>>[Tue Sep 24 20:02:49 2002] [notice] Inside the PythonHandler
>>>>[Tue Sep 24 20:02:49 2002] [notice] Result = <Fault 1000 """Invalid client
>>>>certificate.""">
>>>
>>>
>>>GRRRRR.
>>>
>>>Ok, I just checked, and I narfled the Fault handling code in 1.4.0
>>>I'll try to get a 1.4.1 out tonight or tomorrow.
>>>@%$!@#$~$^#%^
>>>Narf.
>>>
>>>
>>>
>>>>[Tue Sep 24 20:02:49 2002] [error] PythonHandler current_apache: Traceback
>>>>(innermost last):
>>>>[Tue Sep 24 20:02:49 2002] [error] PythonHandler current_apache:   File 
>>>>/usr/lib/python1.5/site-packages/mod_python/apache.py", line 185, in
>>>>Dispatch
>>>>   result = object(req)
>>>>[Tue Sep 24 20:02:49 2002] [error] PythonHandler current_apache:   File 
>>>>/usr/share/current/current_apache.py", line 192, in handler
>>>>   return sendClientResult(req, result)
>>>>[Tue Sep 24 20:02:49 2002] [error] PythonHandler current_apache:   File 
>>>>/usr/share/current/current_apache.py", line 225, in sendClientResult
>>>>   if result['type'] == 'xml':
>>>>[Tue Sep 24 20:02:49 2002] [error] PythonHandler current_apache:
>>>>AttributeError: __getitem__
>>>>
>>>>
>>>>and i did copy the certificate i got to the client and to the server (i
>>>>mentioned prevously that i tried to setup it without ssl, so i setup https
>>>>after i got this error).
>>>
>>>
>>>Cease panicing. - that error message is generated by a failure to match
>>>sysid's, which THAT error message incorrectly calls it the
>>>'certificate'. (IE, Current is not talking about the SSL certificate.)
>>>
>>>So, I will fix the Fault handler soon, we still need to determine WHY your 
>>>sysid was judged bad. I guess I also need to audit the terminology
>>>around the sysid - that can be confusing.
>>>
>>>
>>>Could you reregister that client, and see if the error persists?
>>>
>>> 
>>
>>-- 
>>Anthony Mendoza
>>IT & Customer Support
>>[email protected]
>>t: 408-585-5612 / c: 408-314-5038
>>p: 888-886-7205 / f: 208-247-5501
> 

-- 
Anthony Mendoza
IT & Customer Support
[email protected]
t: 408-585-5612 / c: 408-314-5038
p: 888-886-7205 / f: 208-247-5501