hot standby problem

> Otto,
>
> Here's a response from engineering:
>>
>> I would delete the existing logsender.log
>>
>> Add
>> export GEMSTONE_SOCKET_DEBUG=1 to the environments before
>> startlogsender and startlogreceiver.
>>
>> and add
>> -d
>> to the command line of both startlogsender and startlogreceiver.
>>
>> Then we would like to see the log files again .
>
>
> Dale
>
>
> On 10/26/2015 01:48 AM, Otto Behrens via Glass wrote:
>>
>> Hi,
>>
>> We have a hot standby setup with a logsender and logreceiver.
>>
>> I not getting my standby to receive logs. I list details below. Can
>> anyone spot why? Any ideas how to debug this?
>>
>> I suspect my firewall setup may be incorrect. But I do not see
>> anything being blocked in the logs.
>>
>> Thanks
>> Otto
>>
>> I have 2 machines, one running prod_stone and one running standby_stone.
>> These machines are on different time zones.
>> I have a firewall rule on the prod_stone machine to allow connections
>> from the standby_stone machine, port 50379.
>> The prod_tranlog directory remains empty on the standby_stone machine.
>>
>> This is how I start the logsender:
>>
>> /opt/gemstone/GemStone64Bit3.2.6-x86_64.Linux/sys/gem logsender -s
>> prod_stone -l /var/log/gemstone/prod_stone/logsender.log -A 0.0.0.0 -P
>> 50379 -T /var/local/gemstone/prod_stone/tranlog
>>
>> and how I start the logreceiver
>>
>> /opt/gemstone/GemStone64Bit3.2.6-x86_64.Linux/sys/gem logreceiver -s
>> standby_stone -l /dev/stdout -A prod_stone -P 50379 -T
>> /var/local/gemstone/standby_stone/prod_tranlog
>>
>> Log snippet from logreceiver:
>>
>> --- 10/26/2015 12:36:25.390 SAST ---
>> [Info]: Connected to master on 27.131.76.19 using port 50379
>> [Error]: readCommandResponse error ok 0 timedOut 0, expected 9 bytes got
>> 0,
>> [Error]: STAT_VERSION getResponse failed
>> [Info]: Closing connection to master
>>
>>
>> Log snippet from logsender:
>>
>> --- 10/26/2015 19:36:14.790 AEDT ---
>> [Info]: Joining on dataTransmitThread
>> --- 10/26/2015 19:36:14.791 AEDT ---
>> [Info]: Joining on fileReadThread
>> [Info]: Closed network connection to slave
>> --- 10/26/2015 19:36:14.791 AEDT ---
>> [Info]: Exited clientCommandReadMain
>> [Info]: MasterAccept: acceptClient succeeded.
>> [Info]: StartClientServices for client 0 on localhost
>> [Info]: Created thread 139800824456960 for dataTransmitThread
>> [Info]: Started thread dataTransmitThread, threadId 139800824456960 ttid
>> 23168
>> [Info]: Created thread 139800816064256 for fileReadThread
>> [Info]: Started thread fileReadThread, threadId 139800816064256 ttid 23169
>> [Info]: Created thread 139800807671552 for commandReadThread
>> [Info]: Started thread commandReadThread, threadId 139800807671552 ttid
>> 23170
>> [Error]: ControlSocket read error,
>> --- 10/26/2015 19:36:15.810 AEDT ---
>> [Info]: Joining on dataTransmitThread
>> _______________________________________________
>> Glass mailing list
>> [hidden email]
>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
> _______________________________________________
> Glass mailing list
> [hidden email]
> http://lists.gemtalksystems.com/mailman/listinfo/glass