yukimochi / Activity-Relay

Yet another powerful customizable ActivityPub relay server written in Go.
https://relay.toot.yukimochi.jp/
GNU Affero General Public License v3.0
279 stars 39 forks source link

Questions related to logs output #33

Closed shleeable closed 4 years ago

shleeable commented 4 years ago

1) Lots of duplicate users in the Accept relay status? is that normal?

server_1  | Accept Relay Status :  https://aus.social/users/martintheg
server_1  | Accept Relay Status :  https://aus.social/users/martintheg
server_1  | Accept Relay Status :  https://aus.social/users/martintheg
server_1  | Accept Relay Status :  https://aus.social/users/BOMwarnings_bot
server_1  | Accept Relay Status :  https://aus.social/users/martintheg
server_1  | Accept Relay Status :  https://aus.social/users/BOMwarnings_bot
server_1  | Accept Relay Status :  https://aus.social/users/martintheg
server_1  | Accept Relay Status :  https://aus.social/users/martintheg
server_1  | Accept Relay Status :  https://aus.social/users/martintheg
server_1  | Accept Relay Status :  https://aus.social/users/martintheg
server_1  | Accept Relay Status :  https://aus.social/users/martintheg
server_1  | Accept Relay Status :  https://aus.social/users/shlee
server_1  | Accept Relay Status :  https://mstdn.social/users/SilkyNsa
server_1  | Accept Relay Status :  https://aus.social/users/martintheg
server_1  | Accept Relay Status :  https://aus.social/users/peemee
server_1  | Accept Relay Status :  https://aus.social/users/martintheg
server_1  | Accept Relay Status :  https://aus.social/users/martintheg

2) Lots of failed hosts. How can I remove dead instances easily?

worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_6f8490cb-741b-4777-8ab6-12e102b98176. Error = Post https://social.strueker.net/inbox: dial tcp: lookup social.strueker.net on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_9ee78135-f7fa-455b-a10a-433492a392bf. Error = Post https://lost-angles.im/inbox: dial tcp: lookup lost-angles.im on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_6463e5ad-ae2e-49b5-9306-e97fb83e076d. Error = Post https://social.zwei.net/inbox: dial tcp: lookup social.zwei.net on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_4637ba43-3d49-44a3-ad1f-5142509c061c. Error = Post https://mastodon.zwei.net/inbox: dial tcp: lookup mastodon.zwei.net on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_4b50febf-00aa-4e7e-9f2f-ce71e0137888. Error = Post https://project.social/inbox: dial tcp: lookup project.social on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_036897f8-a1fc-4fb9-aced-29ac23f2d57c. Error = Post https://snel.social/inbox: dial tcp: lookup snel.social on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_90ac8701-15f2-4c02-b28c-40843e55153b. Error = Post https://mastodon.circlelinego.com/inbox: dial tcp: lookup mastodon.circlelinego.com on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_6519968f-76c0-4509-adf7-f3086cf2da1d. Error = Post https://social.joshuacasey.net/inbox: dial tcp: lookup social.joshuacasey.net on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_ee204150-80d4-48a9-a3e4-ed5f492fcda4. Error = Post https://m.zuidbook.com/inbox: dial tcp: lookup m.zuidbook.com on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_fa3f8d5d-0ce7-4e81-95d6-dc4ac1dc2c57. Error = Post https://mypolis.zapto.org/inbox: dial tcp: lookup mypolis.zapto.org on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_14f12ac8-8bee-4d28-98c5-da642e37badd. Error = Post https://lost-angles.im/inbox: dial tcp: lookup lost-angles.im on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_bfe45956-9f16-42c2-8f24-e9afb51c9f6a. Error = Post https://lost-angles.im/inbox: dial tcp: lookup lost-angles.im on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_7cfada8d-4cd1-42b8-82f6-596ff3f823b3. Error = Post https://social.zwei.net/inbox: dial tcp: lookup social.zwei.net on 127.0.0.11:53: no such host
worker_1  | ERROR: 2020/04/11 14:58:07 worker.go:352 Failed processing task task_7eb01510-df3d-440c-a3f8-6e8c3b2ecf65. Error = Post https://project.social/inbox: dial tcp: lookup project.social on 127.0.0.11:53: no such host
yukimochi commented 4 years ago

Answers

  1. It's maybe abnormal things. But true abnormality may be user's actions? (note: Boost is one of status) In my environment, duplicate reports are not recognized.

  2. Now unfollow command try sending unfollow request to server many time (up to 25 times). I decided to schedule implement Unilaterally unfollowing option