montag,

Hello ,

after I had problems with some relay servers (relay.fedi.buzz and relay.21314.de) two weeks ago, I deactivated them and my system calmed down again. However, my log is still full of these entries:

2024-02-27T16:40:18Z app [NOTICE]: Relay is no sharer {"actor":"https://relay.21314.de/actor"} - {"file":"Receiver.php","line":230,"function":"processRelayPost","request-id":"65de1072ed93a","stack":"Receiver::processRelayPost (112), Receiver::processInbox (101), Inbox::post (233), BaseModule::run (109), BaseApi::run (43), Inbox::run (711), App::runFrontend (46)","uid":"1d2560","process_id":24297}
2024-02-27T16:40:19Z app [NOTICE]: Unable to retrieve AP contact for actor - message is discarded {"actor":"https://relay.fedi.buzz/instance/relay.fedi.buzz"} - {"file":"Receiver.php","line":109,"function":"processInbox","request-id":"65de107304b46","stack":"Receiver::processInbox (101), Inbox::post (233), BaseModule::run (109), BaseApi::run (43), Inbox::run (711), App::runFrontend (46)","uid":"07b1c2","process_id":32516}

So there are probably still some entries for these relays somewhere in the database. Does anyone have any idea where I can look for them?

musenhain,

@montag Did you manage to completely disconnect from relay.21314.de in the meantime? I got the same problem here, too - removed the relay from my server's list, but it keeps POSTing to /inbox more than once a second. relay.21314.de/ still names your server (and mine) …

montag,

@musenhain no, my logs are still full of these entries. I just haven't found the time to deal with them yet. As I have the feeling that my system is being put under quite a lot of strain from time to time, I need to find a solution to this.

@helpers

musenhain,

@montag Maybe @hankarus can shed some light on why his relay keeps sending messages.

hankarus,

@musenhain @montag I have updated the relay now, the error should be gone. unfortunately the database convert did not work and I added all servers I had in the database manually. I hope that worked. If not please deactivate/activate the relay in your instance.

musenhain,

@hankarus Ok, thanks for caring and the update. Unblocked the IP of your relay and added/removed the relay once - now my server is gone from your list on relay.21314.de/. Maybe I give it another try as soon as all lights are flashing green again. 😉

Your relay had contacted my server more than once a second, causing almost half of the traffic my server gets. My server is subscribed to 6 other relays, none of them showing the same behaviour. Is there anything special your relay is configured for?

@montag

hankarus,

@musenhain @montag Nothing special, just a buggy version I think. Maybe remove and readd? My Mastodon did not need that, maybe friendica behaves different?

hankarus,

@musenhain @montag Now I have done the same again, my site is shown but mastodon says it’s waiting for approval. Just leave it that way, I‘ll look into it. Maybe another bug.

musenhain,

@hankarus Tomorrow I will have access to the logs of today. Then I am going to see if what my hosting provider calls a DoS 🤷 is gone.

@montag

musenhain,

@hankarus Indeed, the access numbers went down big. Still some POSTs now and then, but that's ok.

@montag

hankarus,

@musenhain @montag Nice, sorry for the "DOS" and thanks for the info. None of my logs indicated that.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • helpers@forum.friendi.ca
  • Durango
  • DreamBathrooms
  • InstantRegret
  • tacticalgear
  • magazineikmin
  • Youngstown
  • thenastyranch
  • mdbf
  • slotface
  • rosin
  • Leos
  • kavyap
  • modclub
  • ethstaker
  • JUstTest
  • everett
  • GTA5RPClips
  • cubers
  • khanakhh
  • ngwrru68w68
  • anitta
  • provamag3
  • cisconetworking
  • tester
  • osvaldo12
  • megavids
  • normalnudes
  • lostlight
  • All magazines