On 18/10/2007, at 12: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
Nico, When you start the server manually and clients can connect to all venues, which directory are you starting from? With the line above there may be a problem with which VenueServer.dat file is used. What is the entry for 'persistenceFilename' in your /home/ag/venue_server3/ VenueServer.cfg file? chris > 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 >> >> >> >> >> Christoph Willing +61 7 3365 8350 QCIF Access Grid Manager University of Queensland
