friendica (DFRN) - Link to source

Disappeared Thread from Dj33p


Someone seems to have disappeared a thread from Dj33p. I am not surprised that they could disappear it on the original server but I am somewhat surprised it can be disappearing from 3rd party sites it has propagated to. I didn't disappear it and I'm the only admin on my site. Perhaps an ADL or Mossad back door?

friendica (DFRN) - Link to source

I don't know if this is good or bad but another all-time traffic high friendica.eskimo.com


Apache Server Status for www.eskimo.com (via 204.122.16.7)

Server Version: Apache/2.4.63 (Unix) OpenSSL/3.0.13
Server MPM: event
Server Built: Mar 28 2025 19:59:23

Current Time: Wednesday, 25-Jun-2025 21:15:56 PDT
Restart Time: Wednesday, 25-Jun-2025 09:49:58 PDT
Parent Server Config. Generation: 1
Parent Server MPM Generation: 0
Server uptime: 11 hours 25 minutes 57 seconds
Server load: 32.13 47.69 38.95
Total accesses: 657386 - Total Traffic: 2.9 GB - Total Duration: 298990893
CPU Usage: u6.95 s6.36 cu157260 cs71095.2 - 555% CPU load
16 requests/sec - 74.2 kB/second - 4753 B/request - 454.818 ms/request
25 requests currently being processed, 0 workers gracefully restarting, 15 idle workers

Slot PID Stopping Connections Threads Async connections
total accepting busy graceful idle wait-io writing keep-alive closing
0 2850440 no 27 yes 14 0 6 0 0 3 9
1 2852625 no 1 yes 11 0 9 0 0 0 0
2 2848806 yes 12 no 0 0 0 0 0 0 5
6 2841164 yes 1 no 0 0 0 1 0 0 0
Sum 4 2 41 25 0 15 1 0 3 14

WWW_WWRWR___RR__WWRWWW_WR___WRRWW__R_R__......W...G....W........
................................................................
.........G......................................................
................................................................
................................................................
................................................................
................

Scoreboard Key:
"_" Waiting for Connection, "S" Starting up, "R" Reading Request,
"W" Sending Reply, "K" Keepalive (read), "D" DNS Lookup,
"C" Closing connection, "L" Logging, "G" Gracefully finishing,
"I" Idle cleanup of worker, "." Open slot with no current process
Srv PID Acc M CPU SS Req Dur Conn Child Slot Client Protocol VHost Request
0-0 2850440 1/15/7328 W 124.05 0 0 2612981 0.0 0.01 28.38 162.192.239.129 http/1.1 friendica.eskimo.com:443 GET /photo/profile/johnmuller.jpeg?ts=1643844469 HTTP/1.1
0-0 2850440 1/22/7263 W 144.44 0 0 2892369 0.0 0.01 39.35 89.58.27.129 http/1.1 friendica.eskimo.com:443 GET /.well-known/webfinger?resource=acct%3Asitusbandarqterperca
0-0 2850440 1/17/7166 W 130.45 0 0 2758829 0.0 0.00 15.57 89.58.27.129 http/1.1 friendica.eskimo.com:443 GET /profile/odin HTTP/1.1
0-0 2850440 0/18/7266 _ 147.55 0 611 2520951 0.0 0.01 19.16 195.91.209.59 http/1.1 friendica.eskimo.com:443 GET /.well-known/webfinger?resource=acct:markethan%40friendica.
0-0 2850440 1/22/7148 W 144.18 0 0 2603086 0.0 0.01 23.03 85.13.147.117 http/1.1 friendica.eskimo.com:443 GET /photo/profile/billyhank.jpeg?ts=1643844469 HTTP/1.1
0-0 2850440 1/22/7229 W 143.13 0 0 2609116 0.0 0.01 22.39 71.115.240.201 http/1.1 friendica.eskimo.com:443 GET /photo/profile/talkingpoint.png?ts=1664071425 HTTP/1.1
0-0 2850440 0/17/7180 R 146.49 0 440 2329600 0.0 0.04 29.39 83.146.143.222 http/1.1 friendica.eskimo.com:443
0-0 2850440 1/18/7209 W 142.80 0 0 3312026 0.0 0.11 16.66 89.58.27.129 http/1.1 friendica.eskimo.com:443 GET /profile/david HTTP/1.1

friendica (DFRN) - Link to source

14.3 hits/second mostly friendica.eskimo.com


Hit 14.3 hits/second tonight, the majority of it Friendica traffic. This is the busiest I've ever seen it. The 458% CPU load is a bit misleading, as the CPU usage is calculated on a single core but this is an 18 core 36 thread machine, so that really means 4.58 of those 36 threads is fully occupied.

Apache Server Status for www.eskimo.com (via 204.122.16.7)

Server Version: Apache/2.4.63 (Unix) OpenSSL/3.0.13
Server MPM: event
Server Built: Mar 28 2025 19:59:23

Current Time: Wednesday, 25-Jun-2025 20:24:23 PDT
Restart Time: Wednesday, 25-Jun-2025 09:49:58 PDT
Parent Server Config. Generation: 1
Parent Server MPM Generation: 0
Server uptime: 10 hours 34 minutes 24 seconds
Server load: 48.47 58.12 55.57
Total accesses: 542709 - Total Traffic: 2.7 GB - Total Duration: 229103454
CPU Usage: u4.63 s4.71 cu120338 cs54098 - 458% CPU load
14.3 requests/sec - 75.5 kB/second - 5.3 kB/request - 422.148 ms/request
36 requests currently being processed, 0 workers gracefully restarting, 24 idle workers

Slot PID Stopping Connections Threads Async connections
total accepting busy graceful idle wait-io writing keep-alive closing
0 2498072 yes 1 no 0 0 0 0 0 0 0
1 2505485 no 25 yes 18 0 2 0 0 0 4
2 2495570 yes 2 no 0 0 0 0 0 0 0
3 2507011 no 17 yes 5 0 15 0 0 2 0
4 2506349 no 23 yes 13 0 7 0 0 2 10
Sum 5 2 68 36 0 24 0 0 4 14

........G...........WWWWRWRWRWWWWW__WRWW...........G........_W_R
___RW________R__RW_W_RWW_WW____RWWWR............................
................................................................
................................................................
................................................................
................................................................
................

Scoreboard Key:
"_" Waiting for Connection, "S" Starting up, "R" Reading Request,
"W" Sending Reply, "K" Keepalive (read), "D" DNS Lookup,
"C" Closing connection, "L" Logging, "G" Gracefully finishing,
"I" Idle cleanup of worker, "." Open slot with no current process