Add notes for 2016-04-30

This commit is contained in:
Alan Orth 2016-04-30 17:37:47 +02:00
parent 25fc12c3fa
commit c096b03b7d
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
4 changed files with 61 additions and 0 deletions

View File

@ -379,3 +379,16 @@ dspace.log.2016-04-27:7271
- Problems with stability again. I've blocked access to `/rest` for now to see if the number of errors in the log files drop
- Later we could maybe start logging access to `/rest` and perhaps whitelist some IPs...
## 2016-04-30
- Logs for today and yesterday have zero references to this REST error, so I'm going to open back up the REST API but log all requests
```
location /rest {
access_log /var/log/nginx/rest.log;
proxy_pass http://127.0.0.1:8443;
}
```
- I will check the logs again in a few days to look for patterns, see who is accessing it, etc

View File

@ -512,6 +512,22 @@ dspace.log.2016-04-27:7271
<ul>
<li>Problems with stability again. I&rsquo;ve blocked access to <code>/rest</code> for now to see if the number of errors in the log files drop</li>
<li>Later we could maybe start logging access to <code>/rest</code> and perhaps whitelist some IPs&hellip;</li>
</ul>
<h2 id="2016-04-30:c88be15f5b2f07c85f7742556a955e47">2016-04-30</h2>
<ul>
<li>Logs for today and yesterday have zero references to this REST error, so I&rsquo;m going to open back up the REST API but log all requests</li>
</ul>
<pre><code>location /rest {
access_log /var/log/nginx/rest.log;
proxy_pass http://127.0.0.1:8443;
}
</code></pre>
<ul>
<li>I will check the logs again in a few days to look for patterns, see who is accessing it, etc</li>
</ul>
</section>

View File

@ -451,6 +451,22 @@ dspace.log.2016-04-27:7271
&lt;li&gt;Problems with stability again. I&amp;rsquo;ve blocked access to &lt;code&gt;/rest&lt;/code&gt; for now to see if the number of errors in the log files drop&lt;/li&gt;
&lt;li&gt;Later we could maybe start logging access to &lt;code&gt;/rest&lt;/code&gt; and perhaps whitelist some IPs&amp;hellip;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;2016-04-30:c88be15f5b2f07c85f7742556a955e47&#34;&gt;2016-04-30&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Logs for today and yesterday have zero references to this REST error, so I&amp;rsquo;m going to open back up the REST API but log all requests&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;location /rest {
access_log /var/log/nginx/rest.log;
proxy_pass http://127.0.0.1:8443;
}
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;I will check the logs again in a few days to look for patterns, see who is accessing it, etc&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>

View File

@ -451,6 +451,22 @@ dspace.log.2016-04-27:7271
&lt;li&gt;Problems with stability again. I&amp;rsquo;ve blocked access to &lt;code&gt;/rest&lt;/code&gt; for now to see if the number of errors in the log files drop&lt;/li&gt;
&lt;li&gt;Later we could maybe start logging access to &lt;code&gt;/rest&lt;/code&gt; and perhaps whitelist some IPs&amp;hellip;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;2016-04-30:c88be15f5b2f07c85f7742556a955e47&#34;&gt;2016-04-30&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Logs for today and yesterday have zero references to this REST error, so I&amp;rsquo;m going to open back up the REST API but log all requests&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;location /rest {
access_log /var/log/nginx/rest.log;
proxy_pass http://127.0.0.1:8443;
}
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;I will check the logs again in a few days to look for patterns, see who is accessing it, etc&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>