mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2025-01-11 22:43:20 +01:00
Add notes for 2016-04-30
This commit is contained in:
parent
25fc12c3fa
commit
c096b03b7d
@ -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
|
- 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...
|
- 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
|
||||||
|
@ -512,6 +512,22 @@ dspace.log.2016-04-27:7271
|
|||||||
<ul>
|
<ul>
|
||||||
<li>Problems with stability again. I’ve blocked access to <code>/rest</code> for now to see if the number of errors in the log files drop</li>
|
<li>Problems with stability again. I’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…</li>
|
<li>Later we could maybe start logging access to <code>/rest</code> and perhaps whitelist some IPs…</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’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>
|
</ul>
|
||||||
|
|
||||||
</section>
|
</section>
|
||||||
|
@ -451,6 +451,22 @@ dspace.log.2016-04-27:7271
|
|||||||
<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>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>
|
<li>Later we could maybe start logging access to <code>/rest</code> and perhaps whitelist some IPs&hellip;</li>
|
||||||
</ul>
|
</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>
|
||||||
</description>
|
</description>
|
||||||
</item>
|
</item>
|
||||||
|
|
||||||
|
@ -451,6 +451,22 @@ dspace.log.2016-04-27:7271
|
|||||||
<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>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>
|
<li>Later we could maybe start logging access to <code>/rest</code> and perhaps whitelist some IPs&hellip;</li>
|
||||||
</ul>
|
</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>
|
||||||
</description>
|
</description>
|
||||||
</item>
|
</item>
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user