[AG-DEV] AG3 VenueServer error

[Christoph Willing]

On 19/01/2006, at 4:31 AM, Thomas D. Uram wrote:

> Hi Chris:
>
> We've been focusing on secure mode, so I'm not surprised to see a  
> problem
> in insecure mode.  I am, however, still interested in this problem,  
> especially
> since I can't reproduce it here.  Do you have a cert installed?   
> What type?
> Can you send along the VenueServer.log file?

Tom,

I think I solved this last thing last night - for some reason, there  
was no /etc/AccessGrid/Config directory (& contents) in the  
particular package build I was using. I copied the Config directory  
across from a previous build's dist-* directory and the error  
disappeared. That means there is a packaging gliche to sort out.

Anyway, now the server seems to be running without errors. However,  
its not responding to access attempts from VenueManagement or  
VenueClient. I'm out of the lab this morning, but this afternoon I'll  
confirm that behaviour and advise if it persists.


chris


>
> On 1/17/06 8:52 PM, Christoph Willing wrote:
>> Working from a packaged AG3 (Linux), I see the following error:
>> ag at v2:~$ VenueServer.py --secure=0
>> Traceback (most recent call last):
>>   File "/usr/bin/VenueServer.py", line 154, in ?
>>     main()
>>   File "/usr/bin/VenueServer.py", line 110, in main
>>     venueServer = VenueServer(server, app.GetOption 
>> ('configfilename'))
>>   File "/usr/bin/VenueServer.py", line 262, in __init__
>>   File "/usr/lib/python2.4/site-packages/AccessGrid/AccessGrid/  
>> Toolkit.py", line 210, in GetContext
>>     defaultId = self.GetCertificateManager().GetDefaultIdentity()
>>   File "/usr/lib/python2.4/site-packages/AccessGrid/AccessGrid/  
>> Toolkit.py", line 416, in GetCertificateManager
>>     raise Exception("No user config dir, Toolkit may not be   
>> initialized.")
>> Exception: No user config dir, Toolkit may not be initialized.
>> Any ideas?
>> This is on a machine which is able to run the VenueClient OK  
>> (well,  the UI appears), so I'm assuming that it can see the user  
>> config  directory. In fact:
>> ag at v2:~$ ls -l .AccessGrid3
>> total 4
>> drwxr-xr-x  7 ag ag 4096 2006-01-18 08:31 Config/
>> drwxr-xr-x  2 ag ag  150 2006-01-18 11:38 Logs/
>> drwxr-xr-x  2 ag ag    6 2006-01-16 18:56 Services/
>> drwxr-xr-x  2 ag ag    6 2006-01-16 18:56 SharedApplications/
>> drwxr-xr-x  3 ag ag   25 2006-01-18 10:33 local_services/
>> and:
>> ag at v2:~$ ls -l .AccessGrid3/Config/
>> total 16
>> -rw-r--r--  1 ag ag    0 2006-01-16 18:56 ApplicationDatabase
>> -rw-r--r--  1 ag ag 2531 2006-01-18 08:32 VenueManagement.log
>> -rw-r--r--  1 ag ag   11 2006-01-17 17:00 bridges
>> drwxr-xr-x  6 ag ag   93 2006-01-17 17:03 certRepo/
>> drwxr-xr-x  2 ag ag    6 2006-01-16 18:56 nodeConfig/
>> -rw-r--r--  1 ag ag   11 2006-01-17 17:00 preferences
>> -rw-r--r--  1 ag ag  295 2006-01-17 17:00 profile
>> drwxr-xr-x  2 ag ag    6 2006-01-16 18:56 profileCache/
>> drwxr-xr-x  2 ag ag    6 2006-01-17 17:08 serverProfileCache/
>> drwxr-xr-x  2 ag ag    6 2006-01-17 17:03 trustedCACerts/
>> chris
>> Christoph Willing                           +61 7 3365 8350
>> QPSF Access Grid Manager
>> University of Queensland

Christoph Willing                           +61 7 3365 8350
QPSF Access Grid Manager
University of Queensland