Add notes for 2019-01-24

content/posts/2019-01.md

@@ -835,4 +835,62 @@ $ schedtool -D -e ionice -c2 -n7 nice -n19 /home/cgspace.cgiar.org/bin/dspace fi
 - I think this Launchpad discussion is relevant: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1806517
 - As well as the original Ghostscript bug report: https://bugs.ghostscript.com/show_bug.cgi?id=699815
 
+## 2019-01-24
+
+- I noticed Ubuntu's Ghostscript 9.26 works on some troublesome PDFs where Arch's Ghostscript 9.26 doesn't, so the fix for the first/last page crash is not the patch I found yesterday
+- Ubuntu's Ghostscript uses another [patch from Ghostscript git](http://git.ghostscript.com/?p=ghostpdl.git;h=fae21f1668d2b44b18b84cf0923a1d5f3008a696) ([upstream bug report](https://bugs.ghostscript.com/show_bug.cgi?id=700315))
+- I re-compiled Arch's ghostscript with the patch and then I was able to generate a thumbnail from one of the [troublesome PDFs](https://cgspace.cgiar.org/handle/10568/98390)
+- Before and after:
+
+```
+$ identify Food\ safety\ Kenya\ fruits.pdf\[0\]
+zsh: abort (core dumped)  identify Food\ safety\ Kenya\ fruits.pdf\[0\]
+$ identify Food\ safety\ Kenya\ fruits.pdf\[0\]
+Food safety Kenya fruits.pdf[0]=>Food safety Kenya fruits.pdf PDF 612x792 612x792+0+0 16-bit sRGB 64626B 0.000u 0:00.000
+identify: CorruptImageProfile `xmp' @ warning/profile.c/SetImageProfileInternal/1747.
+```
+
+- I reported it to the Arch Linux bug tracker ([61513](https://bugs.archlinux.org/task/61513))
+- I told Atmire to go ahead with the Metadata Quality Module addition based on our `5_x-dev` branch ([657](https://tracker.atmire.com/tickets-cgiar-ilri/view-ticket?id=657))
+- Linode sent alerts last night to say that CGSpace (linode18) was using high CPU last night, here are the top ten IPs from the nginx logs around that time:
+
+```
+# zcat --force /var/log/nginx/*.log /var/log/nginx/*.log.1 | grep -E "23/Jan/2019:(18|19|20)" | awk '{print $1}' | sort | uniq -c | sort -n | tail -n 10
+    305 3.81.136.184
+    306 3.83.14.11
+    306 52.54.252.47
+    325 54.221.57.180
+    378 66.249.64.157
+    424 54.70.40.11
+    497 47.29.247.74
+    783 35.237.175.180
+   1108 66.249.64.155
+   2378 45.5.186.2
+```
+
+- 45.5.186.2 is CIAT and 66.249.64.155 is Google... hmmm.
+- Linode sent another alert this morning, here are the top ten IPs active during that time:
+
+```
+# zcat --force /var/log/nginx/*.log /var/log/nginx/*.log.1 | grep -E "24/Jan/2019:0(4|5|6)" | awk '{print $1}' | sort | uniq -c | sort -n | tail -n 10
+    360 3.89.134.93
+    362 34.230.15.139
+    366 100.24.48.177
+    369 18.212.208.240
+    377 3.81.136.184
+    404 54.221.57.180
+    506 66.249.64.155
+   4642 70.32.83.92
+   4643 205.186.128.185
+   8593 45.5.186.2
+```
+
+- Just double checking what CIAT is doing, they are mainly hitting the REST API:
+
+```
+# zcat --force /var/log/nginx/*.log /var/log/nginx/*.log.1 | grep -E "24/Jan/2019:" | grep 45.5.186.2 | grep -Eo "GET /(handle|bitstream|rest|oai)/" | sort | uniq -c | sort -n
+```
+
+- CIAT's community currently has 12,000 items in it so this is normal
+
 <!-- vim: set sw=2 ts=2: -->