attachment is not synced

baddate commented 6 months ago

Have you read a contributing guide?

[X] I have read CONTRIBUTING.md
[X] I have searched the existing issues and didn't find any that were similar
[X] I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

upload a pdf files on client A, then go client B to check the pdf object, it always at Syncing status and file is broken

Expected Behavior

attachment file sync is working

Steps To Reproduce

upload a file
check it on another device

Environment

- OS:Win11
- Version:v0.39.0

Anything else?

No response

fb929 commented 6 months ago

@baddate all you clients it's win11 ?

baddate commented 6 months ago

@baddate all you clients it's win11 ?

Win11 and iOS 17

fb929 commented 6 months ago

did you setup external listen address ? https://github.com/anyproto/any-sync-dockercompose?tab=readme-ov-file#configuration

by default, we have only 127.0.0.1 in listen address on server

baddate commented 6 months ago

did you setup external listen address ? https://github.com/anyproto/any-sync-dockercompose?tab=readme-ov-file#configuration

by default, we have only 127.0.0.1 in listen address on server

yeah, I changed it to my server IP, and it appeared in the client.yml, like this:

David-Melik commented 6 months ago

I confirm this problem I have the same with pictures, PDF and all kind of files ... (for win 10 and 11 and android -> all are updated)

Remark I don't know why but media to windows 11 and android work (same in the reverse way)

What I did

did a make update
try older version of anytype client on win 10 and 11 it do not solve the issue
I changed the listen address to a other than ip 127.0.0.1 in order that client device can access in the network here the .env I used

If you need more info ask me

fb929 commented 6 months ago

I found the problem and fixed it. Please update to release v3.0.0. Also you need make migration - https://github.com/anyproto/any-sync-dockercompose/blob/main/UPGRADE.md#upgrading-from-v2xx-to-v3xx

David-Melik commented 5 months ago

Thank you it solved the problem for me !

Yunp3 commented 5 months ago

Can I set multiple listening addresses? For example: Nodes: -Addresses: -Any sync node-1:1001 -192.168.1.15:1001 -10.199.199.5:1001

fb929 commented 5 months ago

Can I set multiple listening addresses? For example: Nodes: -Addresses: -Any sync node-1:1001 -192.168.1.15:1001 -10.199.199.5:1001

yes. now we don't have support for configure it, but you can do it manual

fb929 commented 5 months ago

@Yunp3 I'm added support for multiple listening addresses, please use this release: https://github.com/anyproto/any-sync-dockercompose/releases/tag/v4.0.0

TaoRone commented 4 months ago

@Yunp3 I'm added support for multiple listening addresses, please use this release: https://github.com/anyproto/any-sync-dockercompose/releases/tag/v4.0.0

Dear fb929: This problem has occurred again. When I create a service on server A (which also has IPV4+IPV6) on the Internet, I log in with the generated client file on my home computer (Windows) and mobile phone (Android). If the computer and mobile phone are connected to the LAN at the same time, all attachments (pictures and videos) can be synchronized successfully. But if I disconnect my phone from the local area network and use a 4G service provider signal, although I can synchronize text messages, the attachments on both sides cannot be synchronized, even if the synchronization status shows successful synchronization. It shows:"Image is broken" My environment configuration file is as follows:

AWS_ACCESS_KEY_ID=minio_access_key
AWS_SECRET_ACCESS_KEY=minio_secret_key
MINIO_BUCKET=minio-bucket
MINIO_PORT=12500
EXTERNAL_MINIO_PORT=${MINIO_PORT}
MINIO_WEB_PORT=12501
EXTERNAL_MINIO_WEB_PORT=${MINIO_WEB_PORT}

ANY_SYNC_NODE_VERSION=prod
ANY_SYNC_FILENODE_VERSION=prod
ANY_SYNC_COORDINATOR_VERSION=prod
ANY_SYNC_CONSENSUSNODE_VERSION=prod
ANY_SYNC_ADMIN_VERSION=latest

MONGO_VERSION=7.0.2
REDIS_VERSION=7.2.0-v6
MINIO_VERSION=RELEASE.2024-01-16T16-07-38Z

EXTERNAL_LISTEN_HOSTS="144.24.xxx.xxx"

ANY_SYNC_NODE_1_HOST=any-sync-node-1
ANY_SYNC_NODE_1_PORT=12502
ANY_SYNC_NODE_1_ADDRESSES=${ANY_SYNC_NODE_1_HOST}:${ANY_SYNC_NODE_1_PORT}
ANY_SYNC_NODE_1_QUIC_PORT=12503
ANY_SYNC_NODE_1_QUIC_ADDRESSES=${ANY_SYNC_NODE_1_HOST}:${ANY_SYNC_NODE_1_QUIC_PORT}

ANY_SYNC_NODE_2_HOST=any-sync-node-2
ANY_SYNC_NODE_2_PORT=12504
ANY_SYNC_NODE_2_ADDRESSES=${ANY_SYNC_NODE_2_HOST}:${ANY_SYNC_NODE_2_PORT}
ANY_SYNC_NODE_2_QUIC_PORT=12505
ANY_SYNC_NODE_2_QUIC_ADDRESSES=${ANY_SYNC_NODE_2_HOST}:${ANY_SYNC_NODE_2_QUIC_PORT}

ANY_SYNC_NODE_3_HOST=any-sync-node-3
ANY_SYNC_NODE_3_PORT=12506
ANY_SYNC_NODE_3_ADDRESSES=${ANY_SYNC_NODE_3_HOST}:${ANY_SYNC_NODE_3_PORT}
ANY_SYNC_NODE_3_QUIC_PORT=12507
ANY_SYNC_NODE_3_QUIC_ADDRESSES=${ANY_SYNC_NODE_3_HOST}:${ANY_SYNC_NODE_3_QUIC_PORT}

ANY_SYNC_COORDINATOR_HOST=any-sync-coordinator
ANY_SYNC_COORDINATOR_PORT=12508
ANY_SYNC_COORDINATOR_ADDRESSES=${ANY_SYNC_COORDINATOR_HOST}:${ANY_SYNC_COORDINATOR_PORT}
ANY_SYNC_COORDINATOR_QUIC_PORT=12509
ANY_SYNC_COORDINATOR_QUIC_ADDRESSES=${ANY_SYNC_COORDINATOR_HOST}:${ANY_SYNC_COORDINATOR_QUIC_PORT}
ANY_SYNC_COORDINATOR_DEFAULT_LIMITS_SPACE_MEMBERS_READ=100000
ANY_SYNC_COORDINATOR_DEFAULT_LIMITS_SPACE_MEMBERS_WRITE=100000
ANY_SYNC_COORDINATOR_DEFAULT_LIMITS_SHARED_SPACES_LIMIT=100000

ANY_SYNC_FILENODE_HOST=any-sync-filenode
ANY_SYNC_FILENODE_PORT=12510
ANY_SYNC_FILENODE_ADDRESSES=${ANY_SYNC_FILENODE_HOST}:${ANY_SYNC_FILENODE_PORT}
ANY_SYNC_FILENODE_QUIC_PORT=12511
ANY_SYNC_FILENODE_QUIC_ADDRESSES=${ANY_SYNC_FILENODE_HOST}:${ANY_SYNC_FILENODE_QUIC_PORT}
ANY_SYNC_FILENODE_DEFAULT_LIMIT=1099511627776

ANY_SYNC_CONSENSUSNODE_HOST=any-sync-consensusnode
ANY_SYNC_CONSENSUSNODE_PORT=12512
ANY_SYNC_CONSENSUSNODE_ADDRESSES=${ANY_SYNC_CONSENSUSNODE_HOST}:${ANY_SYNC_CONSENSUSNODE_PORT}
ANY_SYNC_CONSENSUSNODE_QUIC_PORT=12513
ANY_SYNC_CONSENSUSNODE_QUIC_ADDRESSES=${ANY_SYNC_CONSENSUSNODE_HOST}:${ANY_SYNC_CONSENSUSNODE_QUIC_PORT}

MONGO_1_PORT=12514
MONGO_CONNECT=mongodb://mongo-1:${MONGO_1_PORT}
MONGO_REPLICA_SET=rs0
MONGO_URL=${MONGO_CONNECT}/?replicaSet=${MONGO_REPLICA_SET}

REDIS_HOST=redis
REDIS_PORT=12515
REDIS_URL="redis://${REDIS_HOST}:${REDIS_PORT}?dial_timeout=3&read_timeout=6s"

ANY_SYNC_ADMIN_HOST=0.0.0.0
ANY_SYNC_ADMIN_PORT=5000
EXTERNAL_ANY_SYNC_ADMIN_PORT=12516

Upon closer inspection, it seems that it was caused by any sync filenode not successfully connecting to Redis. about docker

root@arm-c-kr-5:~/anytype/any-sync-dockercompose# docker ps
CONTAINER ID   IMAGE                                            COMMAND                  CREATED          STATUS                          PORTS                                                                                                                                                                  NAMES
e8c1d1ca92d6   ghcr.io/anyproto/any-sync-filenode:v0.6.5        "/bin/sh -c '/bin/an…"   41 minutes ago   Restarting (1) 39 seconds ago                                                                                                                                                                          any-sync-dockercompose-any-sync-filenode-1
9648c7a3c437   ghcr.io/anyproto/any-sync-consensusnode:v0.1.7   "/bin/sh -c '/bin/an…"   41 minutes ago   Up 38 minutes                   443/tcp, 8080/tcp, 0.0.0.0:12512-12513->12512-12513/tcp, :::12512-12513->12512-12513/tcp, 0.0.0.0:8006->8000/tcp, :::8006->8000/tcp                                    any-sync-dockercompose-any-sync-consensusnode-1
c9d90c44d225   ghcr.io/anyproto/any-sync-node:v0.3.34           "/bin/sh -c '/bin/an…"   41 minutes ago   Up 38 minutes                   443/tcp, 0.0.0.0:12504-12505->12504-12505/tcp, :::12504-12505->12504-12505/tcp, 0.0.0.0:8002->8000/tcp, :::8002->8000/tcp, 0.0.0.0:8082->8080/tcp, :::8082->8080/tcp   any-sync-dockercompose-any-sync-node-2-1
ea5de8d26bda   ghcr.io/anyproto/any-sync-node:v0.3.34           "/bin/sh -c '/bin/an…"   41 minutes ago   Up 38 minutes                   443/tcp, 0.0.0.0:12506-12507->12506-12507/tcp, :::12506-12507->12506-12507/tcp, 0.0.0.0:8003->8000/tcp, :::8003->8000/tcp, 0.0.0.0:8083->8080/tcp, :::8083->8080/tcp   any-sync-dockercompose-any-sync-node-3-1
3cae816f66c1   ghcr.io/anyproto/any-sync-node:v0.3.34           "/bin/sh -c '/bin/an…"   41 minutes ago   Up 38 minutes                   443/tcp, 0.0.0.0:12502-12503->12502-12503/tcp, :::12502-12503->12502-12503/tcp, 0.0.0.0:8001->8000/tcp, :::8001->8000/tcp, 0.0.0.0:8081->8080/tcp, :::8081->8080/tcp   any-sync-dockercompose-any-sync-node-1-1
68bb090b8c4c   ghcr.io/anyproto/any-sync-coordinator:v0.3.25    "/bin/sh -c '/bin/an…"   41 minutes ago   Up 38 minutes                   443/tcp, 8080/tcp, 0.0.0.0:12508-12509->12508-12509/tcp, :::12508-12509->12508-12509/tcp, 0.0.0.0:8005->8000/tcp, :::8005->8000/tcp                                    any-sync-dockercompose-any-sync-coordinator-1
9a0e920adc2a   ghcr.io/anyproto/any-sync-admin:latest           "/bin/sh -c '/opt/ve…"   41 minutes ago   Up 39 minutes                   443/tcp, 8000/tcp, 8080/tcp, 0.0.0.0:12516->5000/tcp, :::12516->5000/tcp                                                                                               any-sync-dockercompose-any-sync-admin-1
a5716439a1b4   redis/redis-stack-server:7.2.0-v6                "redis-server --dir …"   41 minutes ago   Up 39 minutes (healthy)         6379/tcp, 0.0.0.0:12515->12515/tcp, :::12515->12515/tcp                                                                                                                any-sync-dockercompose-redis-1
70296cbc23a7   minio/minio:RELEASE.2024-01-16T16-07-38Z         "/usr/bin/docker-ent…"   41 minutes ago   Up 39 minutes (healthy)         9000/tcp, 0.0.0.0:12500-12501->12500-12501/tcp, :::12500-12501->12500-12501/tcp                                                                                        any-sync-dockercompose-minio-1
9d0b2e1518b5   mongo:7.0.2                                      "docker-entrypoint.s…"   41 minutes ago   Up 39 minutes (healthy)         0.0.0.0:12514->12514/tcp, :::12514->12514/tcp, 27017/tcp                                                                                                               any-sync-dockercompose-mongo-1-1
8ca4acda0b5e   generateconfig-processing                        "/bin/sh -c ./docker…"   22 hours ago     Up 39 minutes (healthy)                                                                                                                                                                                any-sync-dockercompose-generateconfig-processing-1
7da8157a651c   generateconfig-anyconf                           "/bin/sh -c ./docker…"   22 hours ago     Up 39 minutes (healthy)                                                                                                                                                                                any-sync-dockercompose-generateconfig-anyconf-1

relate log：

any-sync-filenode-1  | 2024-05-16T16:06:54.968Z FATAL   main    can't start app {"error": "can't run service 'filenode.redisprovider': dial tcp 172.21.0.6:12515: connect: connection refused"}
any-sync-filenode-1  | 2024-05-16T16:07:55.234Z INFO    common.nodeconf net configuration applied   {"netId": "N5Drbx56qxgJE4m2S9Fg6NNSYhoBsbS6cR3MWM5vgMv4HCWi", "id": "664626e1ef6fbaa78a51e334"}
any-sync-filenode-1  | 2024-05-16T16:07:55.238Z INFO    common.net.secure       secure service init {"peerId": "12D3KooWScngSpeQ8uxuQNWvrSAPiS9m8yfGFwBg2WdzbN1rHYN8"}
any-sync-filenode-1  | 2024-05-16T16:07:55.440Z DEBUG   net.peerservice dial    {"rootOp": "periodicCall", "peerId": "12D3KooWMxb55TMaGSwcxnxWzGyA4wNivJpQDxji2qK1CCmUTmi4", "addrs": ["any-sync-coordinator:12508", "quic://any-sync-coordinator:12509", "144.24.xxx.xxx:12508", "quic://144.24.xxx.xxx:12509"]}
any-sync-filenode-1  | 2024-05-16T16:07:55.440Z DEBUG   net.peerservice dial    {"peerId": "12D3KooWS1PLXCnLqV3EG7EBLodQeLMgeRCxHHh1W5a4nwcXL6HZ", "addrs": ["any-sync-consensusnode:12512", "quic://any-sync-consensusnode:12513", "144.24.xxx.xxx:12512", "quic://144.24.xxx.xxx:12513"]}
any-sync-filenode-1  | 2024-05-16T16:07:55.509Z ERROR   app     can't run service       {"service": "filenode.redisprovider", "error": "dial tcp 172.21.0.6:12515: connect: connection refused"}
any-sync-filenode-1  | 2024-05-16T16:07:55.510Z DEBUG   common.net.peer peer close      {"peerId": "12D3KooWS1PLXCnLqV3EG7EBLodQeLMgeRCxHHh1W5a4nwcXL6HZ"}
any-sync-filenode-1  | 2024-05-16T16:07:55.510Z DEBUG   common.net.peer peer close      {"peerId": "12D3KooWMxb55TMaGSwcxnxWzGyA4wNivJpQDxji2qK1CCmUTmi4"}
any-sync-filenode-1  | 2024-05-16T16:07:55.510Z FATAL   main    can't start app {"error": "can't run service 'filenode.redisprovider': dial tcp 172.21.0.6:12515: connect: connection refused"}

localhost redis redis-cli test

root@arm-c-kr-5:~/anytype/any-sync-dockercompose# redis-cli -h localhost -p 12515
localhost:12515> set fdaf 1231231
Error: Connection reset by peer
not connected>

fb929 commented 4 months ago

Yes, changing the redis port did not work. I made a fix: https://github.com/anyproto/any-sync-dockercompose/pull/58/commits/67e873932f3f4f4010f25c37c19b7a553ae4d5bc

anyproto / any-sync-dockercompose