#sysadmining — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #sysadmining, aggregated by home.social.
-
Sysadmining Like It's 2009
https://lambdacreate.com/posts/sysadmining-like-its-2009
#HackerNews #Sysadmining #2009 #Tech #Nostalgia #IT #Community #Sysadmin #Life
-
Sysadmining Like It's 2009
https://lambdacreate.com/posts/sysadmining-like-its-2009
#HackerNews #Sysadmining #2009 #Tech #Nostalgia #IT #Community #Sysadmin #Life
-
Sysadmining Like It's 2009
https://lambdacreate.com/posts/sysadmining-like-its-2009
#HackerNews #Sysadmining #2009 #Tech #Nostalgia #IT #Community #Sysadmin #Life
-
Sysadmining Like It's 2009
https://lambdacreate.com/posts/sysadmining-like-its-2009
#HackerNews #Sysadmining #2009 #Tech #Nostalgia #IT #Community #Sysadmin #Life
-
Sysadmining Like It's 2009
https://lambdacreate.com/posts/sysadmining-like-its-2009
#HackerNews #Sysadmining #2009 #Tech #Nostalgia #IT #Community #Sysadmin #Life
-
Once again my personal web server is on its knees, this time thanks to Amazon who's probing a non-existent Health Check endpoint with a rare intensity. In the Apache access log, it looks like this:
<domain>:80 15.177.10.187 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)" <domain>:80 15.177.26.71 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)" <domain>:80 15.177.42.155 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)" <domain>:80 15.177.30.95 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)" <domain>:80 15.177.50.106 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)"I followed the link provided and submitted a report, but I'm guessing they are only handled during US business hours. To be able to access my other web sites, I took offline the target vhost, and Amazon immediately switched to another one. I filed a report, took it offline, etc... Four vhosts down the line, the web form prevented me from submitting yet another report because of a rate limiting feature.
I am seething with rage and I want AWS IPs off my web server, but I'm off my depth in system administration. I see I could do it with iptables (by compiling a list of IP blocks from the JSON provided by Amazon) and I was hoping fail2ban would have a ready-made jail, but it seems to be meant for repeated authentication errors, not for crawler errors.
Neither of these solutions feel workable, would anyone have an easier method to cut AWS off my box?
Thanks a bunch!
-
Once again my personal web server is on its knees, this time thanks to Amazon who's probing a non-existent Health Check endpoint with a rare intensity. In the Apache access log, it looks like this:
<domain>:80 15.177.10.187 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)" <domain>:80 15.177.26.71 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)" <domain>:80 15.177.42.155 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)" <domain>:80 15.177.30.95 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)" <domain>:80 15.177.50.106 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)"I followed the link provided and submitted a report, but I'm guessing they are only handled during US business hours. To be able to access my other web sites, I took offline the target vhost, and Amazon immediately switched to another one. I filed a report, took it offline, etc... Four vhosts down the line, the web form prevented me from submitting yet another report because of a rate limiting feature.
I am seething with rage and I want AWS IPs off my web server, but I'm off my depth in system administration. I see I could do it with iptables (by compiling a list of IP blocks from the JSON provided by Amazon) and I was hoping fail2ban would have a ready-made jail, but it seems to be meant for repeated authentication errors, not for crawler errors.
Neither of these solutions feel workable, would anyone have an easier method to cut AWS off my box?
Thanks a bunch!
-
Once again my personal web server is on its knees, this time thanks to Amazon who's probing a non-existent Health Check endpoint with a rare intensity. In the Apache access log, it looks like this:
<domain>:80 15.177.10.187 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)" <domain>:80 15.177.26.71 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)" <domain>:80 15.177.42.155 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)" <domain>:80 15.177.30.95 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)" <domain>:80 15.177.50.106 - - [25/Sep/2025:22:04:50 +0000] "GET /ok HTTP/1.1" 404 457 "-" "Amazon-Route53-Health-Check-Service (ref 0c1421fb-b0fe-4dbd-af57-dc05457a9d2e; report http://amzn.to/1vsZADi)"I followed the link provided and submitted a report, but I'm guessing they are only handled during US business hours. To be able to access my other web sites, I took offline the target vhost, and Amazon immediately switched to another one. I filed a report, took it offline, etc... Four vhosts down the line, the web form prevented me from submitting yet another report because of a rate limiting feature.
I am seething with rage and I want AWS IPs off my web server, but I'm off my depth in system administration. I see I could do it with iptables (by compiling a list of IP blocks from the JSON provided by Amazon) and I was hoping fail2ban would have a ready-made jail, but it seems to be meant for repeated authentication errors, not for crawler errors.
Neither of these solutions feel workable, would anyone have an easier method to cut AWS off my box?
Thanks a bunch!
-
Since I moved server, I left behind my #Devuan install to restart from a #Debian 11 offered by my hosting provider which I immediately upgraded to Debian 12. This means I am back to #systemd land, and I'm already annoyed with it.
See,
service mariadb [action]callsmariadb-adminthat requires password-less root access (??) to localhost to do anything, which I don't allow for obvious security reasons.On the other hand,
systemctl [action] mariadb.servicedoesn't rely onmariadb-admin, but there's no graceful reload available either. 🤷♂️I already miss
/etc/init.d/mysqld [action]. -
Since I moved server, I left behind my #Devuan install to restart from a #Debian 11 offered by my hosting provider which I immediately upgraded to Debian 12. This means I am back to #systemd land, and I'm already annoyed with it.
See,
service mariadb [action]callsmariadb-adminthat requires password-less root access (??) to localhost to do anything, which I don't allow for obvious security reasons.On the other hand,
systemctl [action] mariadb.servicedoesn't rely onmariadb-admin, but there's no graceful reload available either. 🤷♂️I already miss
/etc/init.d/mysqld [action]. -
Since I moved server, I left behind my #Devuan install to restart from a #Debian 11 offered by my hosting provider which I immediately upgraded to Debian 12. This means I am back to #systemd land, and I'm already annoyed with it.
See,
service mariadb [action]callsmariadb-adminthat requires password-less root access (??) to localhost to do anything, which I don't allow for obvious security reasons.On the other hand,
systemctl [action] mariadb.servicedoesn't rely onmariadb-admin, but there's no graceful reload available either. 🤷♂️I already miss
/etc/init.d/mysqld [action]. -
24 hours later, I'm back!
Summary of the previous episodes:
- 3 days ago, my old dedicated server started spewing error messages about the CPU.
- On a hunch, I ran
backup-managerwith my existing configuration that's supposed to send the compressed database dump + files to an FTP backup server. - I contacted my hosting provider to figure out the error.
- Answer was quick: "we can't physically intervene on the server, and the same offer isn't available anymore, you have to pick a new offer".
- I pick an upgrade, no answer for a day.
- A day ago, they made the new server available to me, and immediately removed access to the old server from my account, including the attached FTP backup storage.
- Asked the support to restore access either to the old server or at least the FTP storage. At this point I've lost all my Internet history from 2009 onwards.
- The "Customer Excellence Specialist Level 2" throws his hands in the air, saying that the CPU errors are making either SSH or KVM impossible.
- 12 hours ago, they restored my access to the server and the FTP storage. No luck, last backup on that server dates back to 2019. Server's IP is "very pingable" according to support, but no remote connection is possible.
- Through the hosting provider console, I rebooted in rescue mode. No luck, still no remote connection. I switch back to regular mode with a new reboot.
- I start to receive emails from my third-party monitoring system that my web sites are available again!
- I jump on my terminal, the remote connection works! I don't know how much time I have, I stop the web server to save CPU cycles. I found the fresh local backup files. I start to download them locally. 25 GB at 500 kB/s, it's not looking good. I try to access my old server from my new server directly, transfer rate is 50 MB/s, we're getting somewhere.
- The archive is compressed with LZMA, but I'm unable to expand the archive, lzma reports an succint error.
- Pushing my luck, I start a full MariaDB database backup on the old server. Meanwhile, I start copying the old server's files onto the new using
scp. Wrong choice, permissions and symbolic links aren't preserved. Started again withrsyncwith better success. - Importing the database backup was straightforward, works right out of the box with the already existing user credentials.
- I finish importing the files, fire the web server after fixing several unmet dependency issues, and here I am again!
Phew. Did you miss me?
-
24 hours later, I'm back!
Summary of the previous episodes:
- 3 days ago, my old dedicated server started spewing error messages about the CPU.
- On a hunch, I ran
backup-managerwith my existing configuration that's supposed to send the compressed database dump + files to an FTP backup server. - I contacted my hosting provider to figure out the error.
- Answer was quick: "we can't physically intervene on the server, and the same offer isn't available anymore, you have to pick a new offer".
- I pick an upgrade, no answer for a day.
- A day ago, they made the new server available to me, and immediately removed access to the old server from my account, including the attached FTP backup storage.
- Asked the support to restore access either to the old server or at least the FTP storage. At this point I've lost all my Internet history from 2009 onwards.
- The "Customer Excellence Specialist Level 2" throws his hands in the air, saying that the CPU errors are making either SSH or KVM impossible.
- 12 hours ago, they restored my access to the server and the FTP storage. No luck, last backup on that server dates back to 2019. Server's IP is "very pingable" according to support, but no remote connection is possible.
- Through the hosting provider console, I rebooted in rescue mode. No luck, still no remote connection. I switch back to regular mode with a new reboot.
- I start to receive emails from my third-party monitoring system that my web sites are available again!
- I jump on my terminal, the remote connection works! I don't know how much time I have, I stop the web server to save CPU cycles. I found the fresh local backup files. I start to download them locally. 25 GB at 500 kB/s, it's not looking good. I try to access my old server from my new server directly, transfer rate is 50 MB/s, we're getting somewhere.
- The archive is compressed with LZMA, but I'm unable to expand the archive, lzma reports an succint error.
- Pushing my luck, I start a full MariaDB database backup on the old server. Meanwhile, I start copying the old server's files onto the new using
scp. Wrong choice, permissions and symbolic links aren't preserved. Started again withrsyncwith better success. - Importing the database backup was straightforward, works right out of the box with the already existing user credentials.
- I finish importing the files, fire the web server after fixing several unmet dependency issues, and here I am again!
Phew. Did you miss me?
-
24 hours later, I'm back!
Summary of the previous episodes:
- 3 days ago, my old dedicated server started spewing error messages about the CPU.
- On a hunch, I ran
backup-managerwith my existing configuration that's supposed to send the compressed database dump + files to an FTP backup server. - I contacted my hosting provider to figure out the error.
- Answer was quick: "we can't physically intervene on the server, and the same offer isn't available anymore, you have to pick a new offer".
- I pick an upgrade, no answer for a day.
- A day ago, they made the new server available to me, and immediately removed access to the old server from my account, including the attached FTP backup storage.
- Asked the support to restore access either to the old server or at least the FTP storage. At this point I've lost all my Internet history from 2009 onwards.
- The "Customer Excellence Specialist Level 2" throws his hands in the air, saying that the CPU errors are making either SSH or KVM impossible.
- 12 hours ago, they restored my access to the server and the FTP storage. No luck, last backup on that server dates back to 2019. Server's IP is "very pingable" according to support, but no remote connection is possible.
- Through the hosting provider console, I rebooted in rescue mode. No luck, still no remote connection. I switch back to regular mode with a new reboot.
- I start to receive emails from my third-party monitoring system that my web sites are available again!
- I jump on my terminal, the remote connection works! I don't know how much time I have, I stop the web server to save CPU cycles. I found the fresh local backup files. I start to download them locally. 25 GB at 500 kB/s, it's not looking good. I try to access my old server from my new server directly, transfer rate is 50 MB/s, we're getting somewhere.
- The archive is compressed with LZMA, but I'm unable to expand the archive, lzma reports an succint error.
- Pushing my luck, I start a full MariaDB database backup on the old server. Meanwhile, I start copying the old server's files onto the new using
scp. Wrong choice, permissions and symbolic links aren't preserved. Started again withrsyncwith better success. - Importing the database backup was straightforward, works right out of the box with the already existing user credentials.
- I finish importing the files, fire the web server after fixing several unmet dependency issues, and here I am again!
Phew. Did you miss me?
-
24 hours later, I'm back!
Summary of the previous episodes:
- 3 days ago, my old dedicated server started spewing error messages about the CPU.
- On a hunch, I ran
backup-managerwith my existing configuration that's supposed to send the compressed database dump + files to an FTP backup server. - I contacted my hosting provider to figure out the error.
- Answer was quick: "we can't physically intervene on the server, and the same offer isn't available anymore, you have to pick a new offer".
- I pick an upgrade, no answer for a day.
- A day ago, they made the new server available to me, and immediately removed access to the old server from my account, including the attached FTP backup storage.
- Asked the support to restore access either to the old server or at least the FTP storage. At this point I've lost all my Internet history from 2009 onwards.
- The "Customer Excellence Specialist Level 2" throws his hands in the air, saying that the CPU errors are making either SSH or KVM impossible.
- 12 hours ago, they restored my access to the server and the FTP storage. No luck, last backup on that server dates back to 2019. Server's IP is "very pingable" according to support, but no remote connection is possible.
- Through the hosting provider console, I rebooted in rescue mode. No luck, still no remote connection. I switch back to regular mode with a new reboot.
- I start to receive emails from my third-party monitoring system that my web sites are available again!
- I jump on my terminal, the remote connection works! I don't know how much time I have, I stop the web server to save CPU cycles. I found the fresh local backup files. I start to download them locally. 25 GB at 500 kB/s, it's not looking good. I try to access my old server from my new server directly, transfer rate is 50 MB/s, we're getting somewhere.
- The archive is compressed with LZMA, but I'm unable to expand the archive, lzma reports an succint error.
- Pushing my luck, I start a full MariaDB database backup on the old server. Meanwhile, I start copying the old server's files onto the new using
scp. Wrong choice, permissions and symbolic links aren't preserved. Started again withrsyncwith better success. - Importing the database backup was straightforward, works right out of the box with the already existing user credentials.
- I finish importing the files, fire the web server after fixing several unmet dependency issues, and here I am again!
Phew. Did you miss me?
-
It looks like I'm going to have to move server, and the offer I got isn't available anymore at my current hosting provider, which means I'm going to have to pay more or get less.
I currently have: for 20 euros/month:
- CPU: Intel® C2750 (Avoton)
- Memory: 8 GB
- Disk: 1 TB
- Price: 20€/month
The currently available offers that are close to this are:
Start-1-L- CPU: Intel® Xeon E3 1220v2
- Memory: 16 GB
- Disk: 2 x 1 TB
- Price: 21€/month
or
Pro-4-S- CPU: Intel® Xeon E3 1245v5
- Memory: 32 GB
- Disk: 3 x 250 GB SSD
- Price: 23€/month
My main question is: is the C2750 so much better thanks to its 8 threads than the Xeon E3? I only use my server as a web server, so isn't the thread count more important?
Would the unavailability of the C2750 be a good enough reason to move provider?
-
It looks like I'm going to have to move server, and the offer I got isn't available anymore at my current hosting provider, which means I'm going to have to pay more or get less.
I currently have: for 20 euros/month:
- CPU: Intel® C2750 (Avoton)
- Memory: 8 GB
- Disk: 1 TB
- Price: 20€/month
The currently available offers that are close to this are:
Start-1-L- CPU: Intel® Xeon E3 1220v2
- Memory: 16 GB
- Disk: 2 x 1 TB
- Price: 21€/month
or
Pro-4-S- CPU: Intel® Xeon E3 1245v5
- Memory: 32 GB
- Disk: 3 x 250 GB SSD
- Price: 23€/month
My main question is: is the C2750 so much better thanks to its 8 threads than the Xeon E3? I only use my server as a web server, so isn't the thread count more important?
Would the unavailability of the C2750 be a good enough reason to move provider?
-
It looks like I'm going to have to move server, and the offer I got isn't available anymore at my current hosting provider, which means I'm going to have to pay more or get less.
I currently have: for 20 euros/month:
- CPU: Intel® C2750 (Avoton)
- Memory: 8 GB
- Disk: 1 TB
- Price: 20€/month
The currently available offers that are close to this are:
Start-1-L- CPU: Intel® Xeon E3 1220v2
- Memory: 16 GB
- Disk: 2 x 1 TB
- Price: 21€/month
or
Pro-4-S- CPU: Intel® Xeon E3 1245v5
- Memory: 32 GB
- Disk: 3 x 250 GB SSD
- Price: 23€/month
My main question is: is the C2750 so much better thanks to its 8 threads than the Xeon E3? I only use my server as a web server, so isn't the thread count more important?
Would the unavailability of the C2750 be a good enough reason to move provider?
-
It looks like I'm going to have to move server, and the offer I got isn't available anymore at my current hosting provider, which means I'm going to have to pay more or get less.
I currently have: for 20 euros/month:
- CPU: Intel® C2750 (Avoton)
- Memory: 8 GB
- Disk: 1 TB
- Price: 20€/month
The currently available offers that are close to this are:
Start-1-L- CPU: Intel® Xeon E3 1220v2
- Memory: 16 GB
- Disk: 2 x 1 TB
- Price: 21€/month
or
Pro-4-S- CPU: Intel® Xeon E3 1245v5
- Memory: 32 GB
- Disk: 3 x 250 GB SSD
- Price: 23€/month
My main question is: is the C2750 so much better thanks to its 8 threads than the Xeon E3? I only use my server as a web server, so isn't the thread count more important?
Would the unavailability of the C2750 be a good enough reason to move provider?
-
kernel:[61609207.604309] NMI: IOCK error (debug interrupt?) for reason 71 on CPU 0.
Uh-oh... -
kernel:[61609207.604309] NMI: IOCK error (debug interrupt?) for reason 71 on CPU 0.
Uh-oh... -
kernel:[61609207.604309] NMI: IOCK error (debug interrupt?) for reason 71 on CPU 0.
Uh-oh... -
kernel:[61609207.604309] NMI: IOCK error (debug interrupt?) for reason 71 on CPU 0.
Uh-oh... -
The regularity with which I work out my difficult tech problems while hanging out the washing is uncanny. #WorkingFromHome #Sysadmining
-
The regularity with which I work out my difficult tech problems while hanging out the washing is uncanny. #WorkingFromHome #Sysadmining
-
The regularity with which I work out my difficult tech problems while hanging out the washing is uncanny. #WorkingFromHome #Sysadmining
-
The regularity with which I work out my difficult tech problems while hanging out the washing is uncanny. #WorkingFromHome #Sysadmining
-
The regularity with which I work out my difficult tech problems while hanging out the washing is uncanny. #WorkingFromHome #Sysadmining
-
I'm okay, right? #SysAdmin #SysAdmining# ls -al friendica/log total 641075504 drwxr-xr-x 2 friendica friendica 4096 Jan 26 04:47 . drwxr-xr-x 22 friendica friendica 4096 Feb 20 13:47 .. -rw-r--r-- 1 friendica friendica 307536 Mar 8 14:35 db_log.sql -rw-r--r-- 1 friendica friendica 939041091 Feb 19 08:17 debug.log -rw-r--r-- 1 friendica friendica 521392713728 Mar 8 13:17 error.log -rw-r--r-- 1 friendica friendica 134123690097 Mar 8 15:01 friendica.log -rw-r--r-- 1 friendica friendica 1 Mar 25 2019 php.out -rw-r--r-- 1 friendica friendica 3489792 Mar 7 20:33 slow_queries.log -rw-r--r-- 1 friendica friendica 1 Sep 17 2020 slow_queries_sorted.log -
I'm okay, right? #SysAdmin #SysAdmining# ls -al friendica/log total 641075504 drwxr-xr-x 2 friendica friendica 4096 Jan 26 04:47 . drwxr-xr-x 22 friendica friendica 4096 Feb 20 13:47 .. -rw-r--r-- 1 friendica friendica 307536 Mar 8 14:35 db_log.sql -rw-r--r-- 1 friendica friendica 939041091 Feb 19 08:17 debug.log -rw-r--r-- 1 friendica friendica 521392713728 Mar 8 13:17 error.log -rw-r--r-- 1 friendica friendica 134123690097 Mar 8 15:01 friendica.log -rw-r--r-- 1 friendica friendica 1 Mar 25 2019 php.out -rw-r--r-- 1 friendica friendica 3489792 Mar 7 20:33 slow_queries.log -rw-r--r-- 1 friendica friendica 1 Sep 17 2020 slow_queries_sorted.log -
I'm okay, right? #SysAdmin #SysAdmining# ls -al friendica/log total 641075504 drwxr-xr-x 2 friendica friendica 4096 Jan 26 04:47 . drwxr-xr-x 22 friendica friendica 4096 Feb 20 13:47 .. -rw-r--r-- 1 friendica friendica 307536 Mar 8 14:35 db_log.sql -rw-r--r-- 1 friendica friendica 939041091 Feb 19 08:17 debug.log -rw-r--r-- 1 friendica friendica 521392713728 Mar 8 13:17 error.log -rw-r--r-- 1 friendica friendica 134123690097 Mar 8 15:01 friendica.log -rw-r--r-- 1 friendica friendica 1 Mar 25 2019 php.out -rw-r--r-- 1 friendica friendica 3489792 Mar 7 20:33 slow_queries.log -rw-r--r-- 1 friendica friendica 1 Sep 17 2020 slow_queries_sorted.log