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

> #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?

> 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 

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
Csync2 mailing list

Reply via email to