Conversation
Notices
-
@lakwnikos Regarding the "not-responding database server every few minutes" phenomenon I really wonder what the cause of it could be.
1) I think only quitter.se and quitter.no are affected. I did some research and asked on IRC but couldn't find any other instance with this problem yet
At https://fediverse.network/quitter.no we can see a visualisation of the outages: https://quitter.no/attachment/1778104 . I checked a couple of other instances and there was none with a pattern like this.
2) so why only quitter.se and quitter.no? They are independant instances. Or is there some config setting that quitter.no got from quitter.se back when .no was created? Maybe @knuthollund has an idea?
@knuthollund @hannes-
@lakwnikos @knuthollund Another thought:
3) Could this be a denial-of-service attack against quitter.se and quitter.no?? Or some misconfigured other instance flooding q.no and q.se??
Because: Some 3 weeks ago I told @knuthollund on #IRC about the issue and he said he would have a look. Soon after that the problem was completely gone and quitter.no worked flawlessly for at least the rest of the day! And moreover: quitter.se also worked flawlessly! But later it turned out @knuthollund didn't actually do anything at that point, not even restart anything.)
So I think that something on the fediverse network must have changed within those couple of hours. I think the cause of the problem is somewhere in the internet and that cause did stop its weird behaviour against quitter.se and quitter.no just for a while. Too bad the problem came back the next day.
I think one could check the logs of the webserver or use wireshark to look out for weird/excessive traffic.-
@knuthollund @lakwnikos Besides: as a user I can still live with issues like this. GNUsocial is a grassroot network for me and I like instances run by common people I like, even if there are some issues occasionally. It doesn't need to be "professional"! @hannes
-
-
