On 10/29/2015 02:21 PM, Steve Singer wrote:
> On 10/29/2015 04:01 PM, CS DBA wrote:
>> Its an older version, I'll need to check with the client to be sure, if
>> we restart the slon daemons then everything works fine, until we add
>> another table
>>
>
> If you can reproduce this in a 2.2.x version I'll try to see why it 
> happens (looking at the code nothing jumps out at me)
>
> If you can only reproduce this in 1.2.x then there is a good chance 
> that it has already been fixed.

OK I'll let you know what we find, thanks


>
>
>>
>> On 10/29/2015 08:03 AM, Steve Singer wrote:
>>> On 10/28/2015 11:28 AM, CS DBA wrote:
>>>
>>> That error seems to be generated when it tries to write data to the
>>> archive file but when no the file pointer to the archive is null.
>>>
>>> It isn't obvious to me looking at the code how this can happen at
>>> least in the current version of slony.
>>>
>>> Which version of slony are you using?
>>>
>>> I assume if you restart the slon you get this right away?
>>>
>>> The log message 'does not require Slony-I serial key' also looks 
>>> suspect.
>>>
>>>
>>>
>>>
>>>> We're seeing this in the slon logs (we are doing slon archiving as 
>>>> well,
>>>> the slon -a flag):
>>>>
>>>> 2015-10-28 07:54:56 PDTDEBUG1 remoteWorkerThread_1: connected to
>>>> provider DB
>>>> 2015-10-28 07:54:56 PDTDEBUG2 remoteWorkerThread_1: prepare to copy
>>>> table "abc"."data_set_720"
>>>> 2015-10-28 07:54:56 PDTDEBUG3 remoteWorkerThread_1: table
>>>> "sch1"."data_set_720" does not require Slony-I serial key
>>>> 2015-10-28 07:54:56 PDTDEBUG2 remoteWorkerThread_1: all tables for set
>>>> 14 found on subscriber
>>>> 2015-10-28 07:54:56 PDTDEBUG2 remoteWorkerThread_1: copy table
>>>> "sch1"."data_set_720"
>>>> 2015-10-28 07:54:56 PDTDEBUG3 remoteWorkerThread_1: table
>>>> "sch1"."data_set_720" does not require Slony-I serial key
>>>> 2015-10-28 07:54:56 PDTDEBUG2 remoteWorkerThread_1: Begin COPY of 
>>>> table
>>>> "sch1"."data_set_720"
>>>> 2015-10-28 07:54:56 PDTDEBUG2 remoteWorkerThread_1: nodeon73 is 0
>>>> NOTICE:  truncate of "sch1"."data_set_720" succeeded
>>>> 2015-10-28 07:54:56 PDTERROR  remoteWorkerThread_1: Cannot write to
>>>> archive file
>>>> /usr/local/pgsql/slon_logs/slony1_log_2_00000000000001552202.sql.tmp -
>>>> not open
>>>> 2015-10-28 07:54:56 PDTWARN   remoteWorkerThread_1: data copy for 
>>>> set 14
>>>> failed 1103 times - sleep 60 seconds
>>>> 2015-10-28 07:55:04 PDTDEBUG2 remoteListenThread_1: queue event
>>>> 1,1587129 SYNC
>>>>
>>>>
>>>> The archive dir is writable by postgres and the file perms are:
>>>> ls -l
>>>> /usr/local/pgsql/slon_logs/slony1_log_2_00000000000001552202.sql.tmp
>>>> -rw-r--r-- 1 postgres postgres 504 2015-10-27 13:18
>>>> /usr/local/pgsql/slon_logs/slony1_log_2_00000000000001552202.sql.tmp
>>>>
>>>>
>>>> Thoughts?
>>>>
>>>> Thanks in advance
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Slony1-general mailing list
>>>> Slony1-general at lists.slony.info
>>>> http://lists.slony.info/mailman/listinfo/slony1-general
>>>>
>>>
>>
>