Re: [AG-TECH] Problems with Access Grid 3.0.2

["Thomas D. Uram" <turam@xxxxxxxxxxx>]

Hi Nico:

It would be helpful to see the VenueClient.log file from the client that 
fails to enter the venue, if you could put it somewhere we could look at it.

Also, when you say you 'connect a client and can see all Venues', which 
client are you connecting?  VenueManagement?  I ask because you say you 
can't enter any of the venues.

Tom


On 10/17/07 9:33 AM, Nico wrote:
> Hi Chris!
>
> Thanks for answering! When I start from the script in init.d and I 
> connect a client and I can see all Venues, but I can't enter in any of 
> them because I obtain the error messages I mentioned in the first mail.
>
> In the script I have a line different than you to execute VenueServer, 
> but I've specified the "ag" user:
>
> daemonAG --user ag VenueServer -c 
> /home/ag/venue_server3/VenueServer.cfg -p 9000
>
> Maybe our scripts are different. I used the syntax from this forum:  
> http://www-unix.mcs.anl.gov/web-mail-archive/lists/ag-tech/2006/02/msg00023.html 
>
>
> VenueServer for version 2.4 runs ok with the same syntax.
>
> Thanks again for your help! See you soon!
>
>                      Nico.
>
> Christoph Willing escribió:
> > On 17/10/2007, at 9:53 PM, Nico wrote:
> >
> > > Hi!
> > >
> > > In our company we have an AG Server on a Linux Fedora Core 4 machine 
> > > with Access Grid 3.0.2 installed. We have several Venues configured. 
> > > During these days I've been configuring start scripts on the 
> > > /etc/init.d folder to automatically run Venue Server at the start of 
> > > the system. So the proccess VenueServer is ok when I reboot the 
> > > machine, but when I connect a client I can connect to 
> > > https://server:9000/Venues/default but I can't enter in any 
> > > configured Venue on the server, I try it, but I receive the 
> > > following error message: "Error entering venue".
> > >
> > > So the quick solution is start Venue Server again manually, then I 
> > > can enter in any Venue.
> > >
> > > Could somebody tell me what can happen?
> >
> >
> > Nico,
> >
> > Are the additional venues you've created actually visible to the 
> > client when the server is started from the init.d script?
> >
> > If not, then my guess is that whenever the server is started from the 
> > script in init.d directory, it is being run by the root user instead 
> > of the ordinary user who created the additional venue structure. In 
> > that case the server starts in the wrong directory and doesn't find 
> > the VenueServer.dat file that contains your venue structure (which 
> > was created when you ran the server as an ordinary user).
> >
> > Your init.d script should explicitly cd to the directory containing 
> > the correct VenueServer.dat file. It should also su to an ordinary 
> > user account to actually run the venue server.
> >
> > Here is the crucial line in our startup script which starts the 
> > server. You can see the cd to the directory which contains the 
> > VenueServer.dat file and if that succeeds it runs VenueServer3.py as 
> > the user 'ag' (not root).
> >
> >     cd /var/lib/ag/server_HALL && su ag -c /usr/bin/VenueServer3.py &
> >
> > Since you run Fedora, I think your executable will be just 
> > 'VenueServer' (rather than 'VenueServer3.py')
> >
> >
> >
> > chris
> >
> >
> > Christoph Willing                       +61 7 3365 8350
> > QCIF Access Grid Manager
> > University of Queensland