On 19/10/2007, at 7:23 AM, Jeremy Mann wrote:
> On 10/18/07, Christoph Willing <will...@vislab.uq.edu.au> wrote:
>>
>> On 19/10/2007, at 5:50 AM, Jeremy Mann wrote:
>>
>>> I could never solve the problems of 3.1, so we decided to revert
>>> back
>>> to the latest build of 3.0.2. And I've got major problems now. I had
>>> to recreate our virtual venues by hand which was ok, but I can't
>>> even
>>> connect to the Venue server, the client just hangs forever.
>>
>> Jeremy,
>>
>>
>> If you recreated your venues, I assume you were able to connect to
>> the server with the VenueManagement tool and I'm guessing that you
>> ran the VenueManagement tool on the same machine that the server was
>> running on. Are you able to run VenueClient on that same machine and
>> connect to the server? (I know the media tools won't work properly in
>> this case - just want to know if the VenueClient connection works).
>
> I ran VenueClient and VenueManagement tools on the same computer as
> the VenueServer. Neither would connect, just sit there hanging. I
> eventually started trying things and something happened when I first
> started to recreate the Venues. I deleted the cfg and dat files and
> restarted the Venue Server. I could then connect to the default Lobby.
> I then started VenueManagement and began readding my venues. Once I
> was finished, I clicked 'Go' in my client and the same thing happened,
> the client just hangs.
>
> I started over this time, but after each venue I added, I clicked Go
> on the VenueClient. Now I'm about halfway through adding our Venues
> and the client is not hanging either on the server itself or an
> external client in my office.
OK, even though its a pain to recreate all the venues by hand its
good that its actually working again.
I think the cause is related of corruption of the VenueServer.dat
file due to different servers accessing it. I recall there was some
confusion over the (wrong) inclusion of a '-f' option in 3.1beta2
which overrode the previous '-c' option you'd been using. All that
would have contributed to the wrong VenueServer.dat file being used
(see the previous email on this list with the subject "Problems with
Access Grid 3 .0.2" - similar principle).
BTW there's a more common cause of VenueServer.dat corruption which
may be relevant if you were starting and stopping the server a lot
while working on this problem. That is the problem of the VenueServer
being closed down just as the VenueServer.dat file is being written
to by the server. This may be due to some KILL signals not being
processed correctly and when finally you run 'kill -9 ...', the
VenueServer.dat file is left in an incomplete state. When you next
start the server it reads in the incomplete VenueServer.dat file and
just sits there, confused ... For this reason, I periodically make a
dated backup of the file i.e.
cp -p VenueServer.dat VenueServer.dat.20071019
After that, if I find that the VenueServer.dat file is corrupted, I
stop the server and overwrite the VenueServer.dat file with the last
dated version and then restart the server.
> The only other thing I'm having difficulty with is restoring the
> contents of each venues Data directory. I can't simply copy the old
> directory to the new one, it doesn't show in the client window. I
> guess I can lose this, because its not that important.
Well you _could_ copy the data across but the difficulty (not an
impossibilty, its just tedious) is to corelate the directories in the
old 'Data' directory (each of which represents a particular venue's
data store) with the entries in the new 'Data' directory.
chris
Christoph Willing +61 7 3365 8350
QCIF Access Grid Manager
University of Queensland
