[AG-TECH] AG3 and AG2.4 server on same machine

[Thomas D. Uram]

It has occurred to me before to fix this problem, so I agree that this 
should be fixed.
If one of you would file an enhancement request for
it, we can make sure it gets done.

Thanks,
Tom


On 8/14/06 9:25 AM, Derek Piper wrote:
>
>     Having just run into the same problem myself, I agree that would 
> indeed be a smart idea. It would save editing of the config files just 
> to move the port range. Many people aren't going to want to have to 
> fiddle in order to get things to work.
>     I'm not even sure why the default was kept the same between AG2 
> and AG3 when it's obvious they'll have to be run side-by-side for 
> quite a while as people gradually change over.
>
>     Derek
>
> Michael Braitmaier wrote:
>> I am in the progress of setting up AG3 and AG2.4 servers on the same 
>> machine Fedora Core 5.
>> When I now run the AG2.4 server with option -P 9000 to move it to the 
>> appropriate port to avoid port
>> overlapping of the two servers, it gives me the following output:
>>
>> Server: https://agserver.hlrs.de:9000/VenueServer
>> Event Port: 8002 Text Port: 8004 Data Port: 8006
>> Default Venue Url: https://agserver.hlrs.de:9000/Venues/default
>>
>> This gives me the conclusion that the server listens on 9000 but 
>> events, text and data arrives at 8002,8004 and 8006 which would then
>> overlap with a second server running on the machine?
>>
>> In fact when running the AG3 server in parallel it doesnt start, 
>> leaving with the follwoing error message:
>>
>> Couldn't listen on any:8002: (98, 'Address already in use').
>> Error occurred running server: Couldn't listen on any:8002: (98, 
>> 'Address
>> already in use').
>> Traceback (most recent call last):
>>  File "/usr/lib/python2.4/logging/handlers.py", line 71, in emit
>>    if self.shouldRollover(record):
>>  File "/usr/lib/python2.4/logging/handlers.py", line 143, in 
>> shouldRollover
>>    self.stream.seek(0, 2)  #due to non-posix-compliant Windows feature
>> ValueError: I/O operation on closed file
>> Exception in thread ftps server:
>> Traceback (most recent call last):
>>  File "/usr/lib/python2.4/threading.py", line 442, in __bootstrap
>>    self.run()
>>  File "/usr/lib/python2.4/threading.py", line 422, in run
>>    self.__target(*self.__args, **self.__kwargs)
>>  File "/usr/lib/python2.4/site-packages/AccessGrid/FTPSServer.py", 
>> line 66,
>> in run
>>    log_obj=log)
>>  File 
>> "/usr/lib/python2.4/site-packages/AccessGrid/FTPS/ftps_server.py", line
>> 317, in __init__
>>    self.bind((self.ip, self.port))
>>  File "/usr/lib/python2.4/asyncore.py", line 304, in bind
>>    return self.socket.bind(addr)
>>  File "<string>", line 1, in bind
>> error: (98, 'Address already in use')
>>
>> Wouldn't it make sense to alter the VenueServer to have the whole 
>> port used
>> range moved based on the base port given with the switch -p ?
>>
>> for example
>>
>> VenueServer24 -p 8000
>> Event: 8002 Text: 8004 Data: 8006
>>
>> VenueServer - p 9000
>> Event: 9002 Text: 9004 Data: 9006
>>
>> I think this would at least make sense in AG3 for the future which 
>> also allows to run it in parallel with Ag2.4, when launching AG3 on 
>> ports different than 8000.
>>
>> Michael
>>
>