avc: denied { bind } for scontext=u:r:untrusted_app

[packetfire]

Newbie user, using the Synchthing-fork on two Android phones, one a Pixel 3 running latest and greatest Andorid 11 updates from Google, and the other a Orginal Gangsta Pixel running Android 10.

The photos directories are to be synched, and it is one-way from the Pixel 3 → Pixel 1.

Progress stalled, with no additional files or GBs for several nights (synching only when on AC charge, via local WiFi).

Log says, over and over: “avc: denied for context untrusted_app”. I do not need encryption for any of this, nor do I need relays… what am I missing here, as I see no way to turn either off, and I seem to be running afowl of a “security” issue.

07:31:20W/libsyncthingnat type=[1400](tel:1400) audit([0.0](tel:0.0):[7494](tel:7494)): avc: denied { bind } for scontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tcontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tclass=netlink_route_socket permissive=0 b/[155595000](tel:155595000) app=[com.github.catfriend1.syncthingandroid](http://com.github.catfriend1.syncthingandroid)
07:31:24W/libsyncthingnat type=[1400](tel:1400) audit([0.0](tel:0.0):[7498](tel:7498)): avc: denied { bind } for scontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tcontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tclass=netlink_route_socket permissive=0 b/[155595000](tel:155595000) app=[com.github.catfriend1.syncthingandroid](http://com.github.catfriend1.syncthingandroid)
07:31:38W/libsyncthingnat type=[1400](tel:1400) audit([0.0](tel:0.0):[7501](tel:7501)): avc: denied { bind } for scontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tcontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tclass=netlink_route_socket permissive=0 b/[155595000](tel:155595000) app=[com.github.catfriend1.syncthingandroid](http://com.github.catfriend1.syncthingandroid)
07:31:38W/libsyncthingnat type=[1400](tel:1400) audit([0.0](tel:0.0):[7504](tel:7504)): avc: denied { bind } for scontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tcontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tclass=netlink_route_socket permissive=0 b/[155595000](tel:155595000) app=[com.github.catfriend1.syncthingandroid](http://com.github.catfriend1.syncthingandroid)
07:32:09W/libsyncthingnat type=[1400](tel:1400) audit([0.0](tel:0.0):[7511](tel:7511)): avc: denied { bind } for scontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tcontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tclass=netlink_route_socket permissive=0 b/[155595000](tel:155595000) app=[com.github.catfriend1.syncthingandroid](http://com.github.catfriend1.syncthingandroid)
07:32:23W/libsyncthingnat type=[1400](tel:1400) audit([0.0](tel:0.0):[7516](tel:7516)): avc: denied { bind } for scontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tcontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tclass=netlink_route_socket permissive=0 b/[155595000](tel:155595000) app=[com.github.catfriend1.syncthingandroid](http://com.github.catfriend1.syncthingandroid)
07:32:23W/libsyncthingnat type=[1400](tel:1400) audit([0.0](tel:0.0):[7519](tel:7519)): avc: denied { bind } for scontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tcontext=u:r:untrusted_app:s0:c[129](tel:129),c[257](tel:257),c[512](tel:512),c[768](tel:768) tclass=netlink_route_socket permissive=0 b/[155595000](tel:155595000) app=[com.github.catfriend1.syncthingandroid](http://com.github.catfriend1.syncthingandroid)

[bt90]

There are probably two different things happening here. Your logs stem from new restrictions in Android 11 which prevent syncthing from getting the IP addresses of the device itself. It’s not that problematic though as lookup of other device still works and you’ll end up with a useable connection.

The sync process stalls might be caused by an issue which is going to be fixed in 1.18.0:

lib/fs: Set expiry after DirNames in case-fs

[imsodin (Simon)]

@bt90

The sync process stalls might be caused by an issue which is going to be fixed in 1.18.0:

Nope, 99.9% certain that it has nothing to do with this here respectively will change nothing. That change has gotten some undue attention (I don’t really get why), but it really only is a simple change that might make scanning on a very slow system just “very slow”, instead of “very very slow”.

[packetfire]

So, how to jump-start the process? SOME files have been synched, but not even half the total. I have tried the usual tactics of rebooting phones, restarting apps, and manually invoking the synch by “start - ignore rules”.

But, no synch for me!

[imsodin (Simon)]

Are the devices connected, what’s the folder status, … Ideally check the web UI to get the “unfiltered” status info. Screenshots are always helpful.

Ah and I know windows has made that an almost undeniable reflex for all situations, but rebooting/restarting is not a panacea and not something to do over and over. Doing it frequently is likely to make things worse in this case.

[packetfire]

Here are screenshots, first from Pixel 1:

And from Pixel 3:

And the GUI status screens for each:

As you can see, there are 13.5 GB of photos on the pixel 3, but only 5.5 GB of those have made it over to the Pixel 1 via one-way synch. I am stumped.

[packetfire]

@imsodin I posted the screenshots requested, but forgot to “tag” you in the post. See above

[imsodin (Simon)]

Right. Both local and global state are missing the files - looks like missing indexes, with an unknown cause (that can’t be deduced now after it happened). There have been bugfixes since v1.16.0 relating to that, and upgrading will reset indexes, which should at least temporarily fix the issue (hopefully permanently). In other cases you need to start Syncthing with --reset-deltas command line option. I am not sure whether the app has an option to do that, but anyway in this case upgrading is the thing to do.