Skip to main content

Thierry Meyssan: The idea that it is possible to “democratise” from the exterior, not only the institutions of a state, but the political practises of a People, is quite simply contradictory and grotesque. For the Trotskyists who run the NED, it is the old fantasy of “world revolution”. The peoples, countries and histories do not matter, the revolution is for all, and the power is for the revolutionary elite. During the Bolshevik revolution, Leon Trotsky and his secretary were encouraged by the British to massacre their compatriots on a massive scale, thus weakening Russia. In the Greater Middle East, his US disciples followed in his footsteps – spouting extreme-left wing gibberish, they organised massive crimes in the service of imperialism. https://wordsmith.social/protestation/quotes#quote9156

Thierry Meyssan: During the whole of the “Arab Spring”, MI6 specialised in war propaganda. A sensible division of labour, since the use of modern psychology to hoodwink your own population and obtain their support was an English invention, developed well before the USSR and the Third Reich. In 1914, London created the War Propaganda Bureau at Wellington House. One of its methods was to use artists, since images are direct and untrammelled by logic. In 1914, they also recruited the great writers of the day – Arthur Conan Doyle, H.G. Wells, Rudyard Kipling – to publish screeds ascribing imaginary crimes to the German enemy. Then they recruited the editors of their major newspapers to publish the imaginary tales served up by the writers. https://wordsmith.social/protestation/quotes#quote9157

Thierry Meyssan: Brzeziński set up “Operation Cyclone” in Afghanistan. Between 17,000 and 35,000 Muslim Brothers from about 40 countries came to fight the USSR, which had come to the defence of the Democratic Republic of Afghanistan, at its request. There had never been a “Soviet invasion”, as US propaganda pretended. The men of the Brotherhood came to reinforce a local coalition of conservative combatants and the local Muslim Brotherhood, including the Pashtun Gulbuddin Hekmatyar and the Tajik Ahmad Shah Massoud. They received the major part of their armament from Israel – officially their sworn enemy, but now their partner. All these forces were commanded from Pakistan by General Muhammad Zia-ul- Haq, and financed by the United States and Saudi Arabia. This was the first time that the Brotherhood had been used by the Anglo-Saxons to wage war. Among the combatants present were the future commanders of the wars in the Caucasus, of the Indonesian Jemaah Islamiyah, the Abu Sayyaf group in the Philippines, and of course al-Qaeda and Daesh. In the United States, the anti-Soviet operation was supported by the Republican Party and a small group from the extreme left, the Trotskyists of Social Democrats USA. https://wordsmith.social/protestation/quotes#quote9158

Short Planned Maintenance Tonight

My apologies if this is inconvenient, I opted to do it on shorter notice without a set hour because (a) there's not a lot of activity on the server and (b) I'm really impatient.

I'm doing a hardware upgrade that requires rebooting the network storage backend which will bring down everything for a short time. It should take well under 30 minutes to do the hardware swap and most of the downtime is just going to be the database starting back up (which often takes in the range of another 30 minutes).

As part of this I'll also be deploying some software updates that require a reboot to take effect.

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)

⇧