mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2025-01-27 05:49:12 +01:00
Add notes for 2018-12-29
This commit is contained in:
@ -21,7 +21,7 @@ I noticed that there is another issue with PDF thumbnails on CGSpace, and I see
|
||||
" />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2018-12/" /><meta property="article:published_time" content="2018-12-02T02:09:30+02:00"/>
|
||||
<meta property="article:modified_time" content="2018-12-20T12:56:16+02:00"/>
|
||||
<meta property="article:modified_time" content="2018-12-20T17:41:09+02:00"/>
|
||||
|
||||
<meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="December, 2018"/>
|
||||
@ -38,7 +38,7 @@ Then I ran all system updates and restarted the server
|
||||
|
||||
I noticed that there is another issue with PDF thumbnails on CGSpace, and I see there was another Ghostscript vulnerability last week
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.52" />
|
||||
<meta name="generator" content="Hugo 0.53" />
|
||||
|
||||
|
||||
|
||||
@ -48,9 +48,9 @@ I noticed that there is another issue with PDF thumbnails on CGSpace, and I see
|
||||
"@type": "BlogPosting",
|
||||
"headline": "December, 2018",
|
||||
"url": "https://alanorth.github.io/cgspace-notes/2018-12/",
|
||||
"wordCount": "2940",
|
||||
"wordCount": "3086",
|
||||
"datePublished": "2018-12-02T02:09:30+02:00",
|
||||
"dateModified": "2018-12-20T12:56:16+02:00",
|
||||
"dateModified": "2018-12-20T17:41:09+02:00",
|
||||
"author": {
|
||||
"@type": "Person",
|
||||
"name": "Alan Orth"
|
||||
@ -670,6 +670,47 @@ UPDATE 1
|
||||
<li>After all that I started a full Discovery reindex to get the index name changes and rights updates</li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2018-12-29">2018-12-29</h2>
|
||||
|
||||
<ul>
|
||||
<li>CGSpace went down today for a few minutes while I was at dinner and I quickly restarted Tomcat</li>
|
||||
<li>The top IP addresses as of this evening are:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code># zcat --force /var/log/nginx/*.log /var/log/nginx/*.log.1 | grep -E "29/Dec/2018" | awk '{print $1}' | sort | uniq -c | sort -n | tail -n 10
|
||||
963 40.77.167.152
|
||||
987 35.237.175.180
|
||||
1062 40.77.167.55
|
||||
1464 66.249.66.223
|
||||
1660 34.218.226.147
|
||||
1801 70.32.83.92
|
||||
2005 50.116.102.77
|
||||
3218 66.249.66.219
|
||||
4608 205.186.128.185
|
||||
5585 54.70.40.11
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>And just around the time of the alert:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code># zcat --force /var/log/nginx/*.log.1 /var/log/nginx/*.log.2.gz | grep -E "29/Dec/2018:1(6|7|8)" | awk '{print $1}' | sort | uniq -c | sort -n | tail -n 10
|
||||
115 66.249.66.223
|
||||
118 207.46.13.14
|
||||
123 34.218.226.147
|
||||
133 95.108.181.88
|
||||
137 35.237.175.180
|
||||
164 66.249.66.219
|
||||
260 157.55.39.59
|
||||
291 40.77.167.55
|
||||
312 207.46.13.129
|
||||
1253 54.70.40.11
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>All these look ok (<code>54.70.40.11</code> is known to us from earlier this month and should be reusing its Tomcat sessions)</li>
|
||||
</ul>
|
||||
|
||||
<!-- vim: set sw=2 ts=2: -->
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user