[Csync2] Csync2 Digest, Vol 122, Issue 5

[Vadim Abdulayev]

Hello.

All command executed on node1.

After resync i receive wrong owner on node1. On node2, i always have correct owner and permission.

node2 is backup node. No one working there.

I will add new logs from node's later.

Best regards,
Vadim

> On 8 Aug 2017, at 04:06, csync2-request at lists.linbit.com wrote:
> 
> Date: Tue, 8 Aug 2017 02:06:16 +0200
> From: Lars Ellenberg <lars.ellenberg at linbit.com <mailto:lars.ellenberg at linbit.com>>
> Subject: Re: [Csync2] 2-node masters and root-owned files
> To: csync2 at lists.linbit.com <mailto:csync2 at lists.linbit.com>
> Message-ID: <20170808000616.GL25125 at soda.linbit <mailto:20170808000616.GL25125 at soda.linbit>>
> Content-Type: text/plain; charset=utf-8
> 
> On Mon, Aug 07, 2017 at 11:26:38PM +0400, Vadim Abdulayev wrote:
>> Hello.
>> 
>> Thank you for help.
>> Sometimes = one time per day or more often
>> 
>> example:
>> 
> 
> would have been useful if you also included the node name in the command
> line...
> 
>> #ll /home/myuser/.git/index
>> -rw------- 1 root root 9955696 ???  7 18:03 /home/myuser/.git/index
>> 
>> #chown myuser:myuser /home/myuser/.git/index
>> 
>> ?RESYNC...
> 
>> From where to where?
> 
>> # ll /home/myuser/.git/index
>> -rw------- 1 root root 9955696 ???  7 22:05 /home/myuser/.git/index
> 
> and still the "wrong" uid, even immediately after a "successful" update?
> 
>> LOG:
> 
> "check" log is boring.
> 
> "update" log may be interesting, 
> especially on the *receiving* ("server") side
> (the side where the "wrong" uid/gid is observed)
> 
> This seems to be the log of the "client" side.
> which exact command produced this?
> Still,
> 
>> File /home/myuser/.git/index is different on peer (cktxt char #18).
>>>>> PEER:  v1:mtime=0:mode=33204:uid=1000:gid=1000:type=reg:size=9955696
>>>>> LOCAL: v1:mtime=0:mode=33152:uid=1000:gid=1000:type=reg:size=9955696
> 
> differing permissions trigger the sync,
> 
>> SQL: DELETE FROM dirty WHERE filename = '/home/myuser/.git/index' AND peername = 'node2.domain.local'
>> SQL: SELECT command, logfile FROM action GROUP BY command, logfile
>> SQL Query finished.
>> Connection closed.
>> Finished with 0 errors.
> 
> and to csync2 the sync looks as if it was ok.
> 
> debug level logs and maybe even strace from the "receiving" side would be interesting.
> 
> but in this case, until proven otherwise,
> I suspect you have some git command on the other node
> running as root, and updating the index file there.
> 
> 
> -- 
> : Lars Ellenberg
> : LINBIT | Keeping the Digital World Running
> : DRBD -- Heartbeat -- Corosync -- Pacemaker
> : R&D, Integration, Ops, Consulting, Support
> 
> DRBD? and LINBIT? are registered trademarks of LINBIT

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/csync2/attachments/20170814/5a6f3f4f/attachment-0001.htm>