Skip to main content

Mao Zedong: Communists the world over are wiser than the bourgeoisie, they understand the laws governing the existence and development of things, they understand dialectics and they can see farther. The bourgeoisie does not welcome this truth because it does not want to be overthrown. To be overthrown is painful and is unbearable to contemplate for those overthrown, for example, for the Kuomintang reactionaries whom we are now overthrowing and for Japanese imperialism which we together with other peoples overthrew some time ago. But for the working class, the labouring people and the Communist Party the question is not one of being overthrown, but of working hard to create the conditions in which classes, state power and political parties will die out very naturally and mankind will enter the realm of Great Harmony. https://wordsmith.social/protestation/quotes#quote1562

Mao Zedong: Who are the people? At the present stage in China, they are the working class, the peasantry, the urban petty bourgeoisie and the national bourgeoisie. These classes, led by the working class and the Communist Party, unite to form their own state and elect their own government; they enforce their dictatorship over the running dogs of imperialism -- the landlord class and bureaucrat-bourgeoisie, as well as the representatives of those classes, the Kuomintang reactionaries and their accomplices -- suppress them, allow them only to behave themselves and not to be unruly in word or deed. If they speak or act in an unruly way, they will be promptly stopped and punished. Democracy is practiced within the ranks of the people, who enjoy the rights of freedom of speech, assembly, association and so on. The right to vote belongs only to the people, not to the reactionaries. The combination of these two aspects, democracy for the people and dictatorship over the reactionaries, is the people's democratic dictatorship. https://wordsmith.social/protestation/quotes#quote1584

Lenin: The bourgeois court, which claimed to maintain order, but which, as a matter of fact, was a blind, subtle instrument for the ruthless suppression of the exploited, and an instrument for protecting the interests of the moneybags. https://wordsmith.social/protestation/quotes#quote1675

WTF?

I honestly haven't the foggiest idea how this happened, but apparently the DNS settings got changed a few days ago on the servers with absolutely no explanation (and to junk nonsense settings for some reason). I'm going to keep an eye on them to make sure they don't change again.

Additionally I think that created a cascade that caused the other problems.

Any posts you've made over the past 2-3 days haven't been sent to other servers, but will start sending now.

As far as the other problems, I think when that happened it caused so many processes to lag and take way longer and more resources than usual as any time it tried to contact another server it timed out on the dns request.

DOS Overload

There's been some recent outages of the server, the root cause I've tracked down to the server getting overloaded with requests (mostly updates from other servers). Those updates have been coming in faster than the server can process them and preventing other requests from coming through.

I've made some tweaks that I believe have resolved it, fingers crossed.

Technical explanation:

The servers ran out of php-fpm threads to handle requests. It was configured with static count of 30 each (60 total). They were definitely impacted significantly by memory leaks which kept the count low.

I've changed it from static to ondemand and increased the count to 100 each, I'll probably go in and increase it again since it's still pegged at that limit almost constantly. But thankfully running on-demand seems to be keeping the memory usage per thread drastically lower.

Where the static assignment of 30 was eating up 8GB of ram, 100 on-demand threads is only taking up 1.3GB.

I'm going to increase it until it's either hitting memory constraints or it's no longer constantly at full capacity.

in reply to Server News

Server News
Server News
•

There's definitely some sort of time and code problem involved as it hit again this morning even with the previous changes, though this time it only impacted updates (making posts/comments/likes, getting new posts). I think reading was unaffected because those operations are faster and require significantly less memory.

For whatever reason, sometime around midnight the server gets hit with a bunch of requests that all seem to lock up, eating up large quantities of memory and then won't exit. (With on-demand the threads exit after 10s of being idle, there was over 100 threads running continuously from midnight until I killed them around 9am). Likewise there was a very massive flood of updates from other servers corresponding to that, so I think it might just be a bunch of large servers sending bulk updates or some such.

New tuning to handle that: I put firmer time limits into PHP to prevent threads from running forever, there's two options for setting max times and the first was getting ignored (I think friendica overrode it? the second should override that and kill any threads going too long)

In addition to that, I set up a rate limiter to the inbox endpoint (where other servers send updates to), this should help keep that from overloading the server (majority of the time it'll just be slowing them down by a second or two unless the server is overloaded, at which point the rate limit should help get it accessible for users)

⇧