mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2024-11-22 06:35:03 +01:00
Add notes for 2018-08-01
This commit is contained in:
parent
e6eefc2b0f
commit
7a73c183b0
GPG Key ID:
0FB860CC9C45B1B9
27
content/posts/2018-08.md
Normal file
27
content/posts/2018-08.md
Normal file
@ -0,0 +1,27 @@
|
||||
---
|
||||
title: "August, 2018"
|
||||
date: 2018-08-01T11:52:54+03:00
|
||||
author: "Alan Orth"
|
||||
tags: ["Notes"]
|
||||
---
|
||||
|
||||
## 2018-08-01
|
||||
|
||||
- DSpace Test had crashed at some point yesterday morning and I see the following in `dmesg`:
|
||||
|
||||
```
|
||||
[Tue Jul 31 00:00:41 2018] Out of memory: Kill process 1394 (java) score 668 or sacrifice child
|
||||
[Tue Jul 31 00:00:41 2018] Killed process 1394 (java) total-vm:15601860kB, anon-rss:5355528kB, file-rss:0kB, shmem-rss:0kB
|
||||
[Tue Jul 31 00:00:41 2018] oom_reaper: reaped process 1394 (java), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
|
||||
```
|
||||
|
||||
- Judging from the time of the crash it was probably related to the Discovery indexing that starts at midnight
|
||||
- From the DSpace log I see that eventually Solr stopped responding, so I guess the `java` process that was OOM killed above was Tomcat's
|
||||
- I'm not sure why Tomcat didn't crash with an OutOfMemoryError...
|
||||
- Anyways, perhaps I should increase the JVM heap from 5120m to 6144m like we did a few months ago when we tried to run the whole CGSpace Solr core
|
||||
- The server only has 8GB of RAM so we'll eventually need to upgrade to a larger one because we'll start starving the OS, PostgreSQL, and command line batch processes
|
||||
- I ran all system updates on DSpace Test and rebooted it
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!-- vim: set sw=2 ts=2: -->
|
||||
244
docs/2018-08/index.html
Normal file
244
docs/2018-08/index.html
Normal file
@ -0,0 +1,244 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
|
||||
|
||||
<meta property="og:title" content="August, 2018" />
|
||||
<meta property="og:description" content="2018-08-01
|
||||
|
||||
|
||||
DSpace Test had crashed at some point yesterday morning and I see the following in dmesg:
|
||||
|
||||
|
||||
[Tue Jul 31 00:00:41 2018] Out of memory: Kill process 1394 (java) score 668 or sacrifice child
|
||||
[Tue Jul 31 00:00:41 2018] Killed process 1394 (java) total-vm:15601860kB, anon-rss:5355528kB, file-rss:0kB, shmem-rss:0kB
|
||||
[Tue Jul 31 00:00:41 2018] oom_reaper: reaped process 1394 (java), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
|
||||
|
||||
|
||||
|
||||
Judging from the time of the crash it was probably related to the Discovery indexing that starts at midnight
|
||||
From the DSpace log I see that eventually Solr stopped responding, so I guess the java process that was OOM killed above was Tomcat’s
|
||||
I’m not sure why Tomcat didn’t crash with an OutOfMemoryError…
|
||||
Anyways, perhaps I should increase the JVM heap from 5120m to 6144m like we did a few months ago when we tried to run the whole CGSpace Solr core
|
||||
The server only has 8GB of RAM so we’ll eventually need to upgrade to a larger one because we’ll start starving the OS, PostgreSQL, and command line batch processes
|
||||
I ran all system updates on DSpace Test and rebooted it
|
||||
|
||||
|
||||
" />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2018-08/" />
|
||||
|
||||
|
||||
|
||||
<meta property="article:published_time" content="2018-08-01T11:52:54+03:00"/>
|
||||
|
||||
<meta property="article:modified_time" content="2018-08-01T11:52:54+03:00"/>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="August, 2018"/>
|
||||
<meta name="twitter:description" content="2018-08-01
|
||||
|
||||
|
||||
DSpace Test had crashed at some point yesterday morning and I see the following in dmesg:
|
||||
|
||||
|
||||
[Tue Jul 31 00:00:41 2018] Out of memory: Kill process 1394 (java) score 668 or sacrifice child
|
||||
[Tue Jul 31 00:00:41 2018] Killed process 1394 (java) total-vm:15601860kB, anon-rss:5355528kB, file-rss:0kB, shmem-rss:0kB
|
||||
[Tue Jul 31 00:00:41 2018] oom_reaper: reaped process 1394 (java), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
|
||||
|
||||
|
||||
|
||||
Judging from the time of the crash it was probably related to the Discovery indexing that starts at midnight
|
||||
From the DSpace log I see that eventually Solr stopped responding, so I guess the java process that was OOM killed above was Tomcat’s
|
||||
I’m not sure why Tomcat didn’t crash with an OutOfMemoryError…
|
||||
Anyways, perhaps I should increase the JVM heap from 5120m to 6144m like we did a few months ago when we tried to run the whole CGSpace Solr core
|
||||
The server only has 8GB of RAM so we’ll eventually need to upgrade to a larger one because we’ll start starving the OS, PostgreSQL, and command line batch processes
|
||||
I ran all system updates on DSpace Test and rebooted it
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.45.1" />
|
||||
|
||||
|
||||
|
||||
<script type="application/ld+json">
|
||||
{
|
||||
"@context": "http://schema.org",
|
||||
"@type": "BlogPosting",
|
||||
"headline": "August, 2018",
|
||||
"url": "https://alanorth.github.io/cgspace-notes/2018-08/",
|
||||
"wordCount": "183",
|
||||
"datePublished": "2018-08-01T11:52:54+03:00",
|
||||
"dateModified": "2018-08-01T11:52:54+03:00",
|
||||
"author": {
|
||||
"@type": "Person",
|
||||
"name": "Alan Orth"
|
||||
},
|
||||
"keywords": "Notes"
|
||||
}
|
||||
</script>
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://alanorth.github.io/cgspace-notes/2018-08/">
|
||||
|
||||
<title>August, 2018 | CGSpace Notes</title>
|
||||
|
||||
<!-- combined, minified CSS -->
|
||||
<link href="https://alanorth.github.io/cgspace-notes/css/style.css" rel="stylesheet" integrity="sha384-Upm5uY/SXdvbjuIGH6fBjF5vOYUr9DguqBskM+EQpLBzO9U+9fMVmWEt+TTlGrWQ" crossorigin="anonymous">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
|
||||
<div class="blog-masthead">
|
||||
<div class="container">
|
||||
<nav class="nav blog-nav">
|
||||
<a class="nav-link " href="https://alanorth.github.io/cgspace-notes/">Home</a>
|
||||
</nav>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<header class="blog-header">
|
||||
<div class="container">
|
||||
<h1 class="blog-title"><a href="https://alanorth.github.io/cgspace-notes/" rel="home">CGSpace Notes</a></h1>
|
||||
<p class="lead blog-description">Documenting day-to-day work on the <a href="https://cgspace.cgiar.org">CGSpace</a> repository.</p>
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-sm-8 blog-main">
|
||||
|
||||
|
||||
|
||||
|
||||
<article class="blog-post">
|
||||
<header>
|
||||
<h2 class="blog-post-title"><a href="https://alanorth.github.io/cgspace-notes/2018-08/">August, 2018</a></h2>
|
||||
<p class="blog-post-meta"><time datetime="2018-08-01T11:52:54+03:00">Wed Aug 01, 2018</time> by Alan Orth in
|
||||
|
||||
<i class="fa fa-tag" aria-hidden="true"></i> <a href="/cgspace-notes/tags/notes" rel="tag">Notes</a>
|
||||
|
||||
</p>
|
||||
</header>
|
||||
<h2 id="2018-08-01">2018-08-01</h2>
|
||||
|
||||
<ul>
|
||||
<li>DSpace Test had crashed at some point yesterday morning and I see the following in <code>dmesg</code>:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code>[Tue Jul 31 00:00:41 2018] Out of memory: Kill process 1394 (java) score 668 or sacrifice child
|
||||
[Tue Jul 31 00:00:41 2018] Killed process 1394 (java) total-vm:15601860kB, anon-rss:5355528kB, file-rss:0kB, shmem-rss:0kB
|
||||
[Tue Jul 31 00:00:41 2018] oom_reaper: reaped process 1394 (java), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>Judging from the time of the crash it was probably related to the Discovery indexing that starts at midnight</li>
|
||||
<li>From the DSpace log I see that eventually Solr stopped responding, so I guess the <code>java</code> process that was OOM killed above was Tomcat’s</li>
|
||||
<li>I’m not sure why Tomcat didn’t crash with an OutOfMemoryError…</li>
|
||||
<li>Anyways, perhaps I should increase the JVM heap from 5120m to 6144m like we did a few months ago when we tried to run the whole CGSpace Solr core</li>
|
||||
<li>The server only has 8GB of RAM so we’ll eventually need to upgrade to a larger one because we’ll start starving the OS, PostgreSQL, and command line batch processes</li>
|
||||
<li>I ran all system updates on DSpace Test and rebooted it</li>
|
||||
</ul>
|
||||
|
||||
<p></p>
|
||||
|
||||
<!-- vim: set sw=2 ts=2: -->
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</article>
|
||||
|
||||
|
||||
|
||||
</div> <!-- /.blog-main -->
|
||||
|
||||
<aside class="col-sm-3 ml-auto blog-sidebar">
|
||||
|
||||
|
||||
|
||||
<section class="sidebar-module">
|
||||
<h4>Recent Posts</h4>
|
||||
<ol class="list-unstyled">
|
||||
|
||||
|
||||
<li><a href="/cgspace-notes/2018-08/">August, 2018</a></li>
|
||||
|
||||
<li><a href="/cgspace-notes/2018-07/">July, 2018</a></li>
|
||||
|
||||
<li><a href="/cgspace-notes/2018-06/">June, 2018</a></li>
|
||||
|
||||
<li><a href="/cgspace-notes/2018-05/">May, 2018</a></li>
|
||||
|
||||
<li><a href="/cgspace-notes/2018-04/">April, 2018</a></li>
|
||||
|
||||
</ol>
|
||||
</section>
|
||||
|
||||
|
||||
|
||||
|
||||
<section class="sidebar-module">
|
||||
<h4>Links</h4>
|
||||
<ol class="list-unstyled">
|
||||
|
||||
<li><a href="https://cgspace.cgiar.org">CGSpace</a></li>
|
||||
|
||||
<li><a href="https://dspacetest.cgiar.org">DSpace Test</a></li>
|
||||
|
||||
<li><a href="https://github.com/ilri/DSpace">CGSpace @ GitHub</a></li>
|
||||
|
||||
</ol>
|
||||
</section>
|
||||
|
||||
</aside>
|
||||
|
||||
|
||||
</div> <!-- /.row -->
|
||||
</div> <!-- /.container -->
|
||||
|
||||
|
||||
|
||||
<footer class="blog-footer">
|
||||
<p>
|
||||
|
||||
Blog template created by <a href="https://twitter.com/mdo">@mdo</a>, ported to Hugo by <a href='https://twitter.com/mralanorth'>@mralanorth</a>.
|
||||
|
||||
</p>
|
||||
<p>
|
||||
<a href="#">Back to top</a>
|
||||
</p>
|
||||
</footer>
|
||||
|
||||
|
||||
</body>
|
||||
|
||||
</html>
|
||||
Loading…
Reference in New Issue
Block a user