alanorth/cgspace-notes
1
0
Fork 0
mirror of https://github.com/alanorth/cgspace-notes.git synced 2025-01-27 05:49:12 +01:00
Code Issues Projects Releases Wiki Activity

Add notes for 2023-01-01

Browse Source
This commit is contained in:
Alan Orth
2023-01-01 10:12:13 +02:00
parent 9768a0fe57
commit b781203a58
130 changed files with 1423 additions and 935 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
docs/2022-12/index.html
View File

@ -20,7 +20,7 @@ Replace “East Asia” with “Eastern Asia” region on CGSpac
<meta property="og:type" content="article" />
<meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2022-12/" />
<meta property="article:published_time" content="2022-12-01T08:52:36+03:00" />
<meta property="article:modified_time" content="2022-12-28T22:55:34+02:00" />
<meta property="article:modified_time" content="2022-12-29T08:32:08+02:00" />
@ -46,9 +46,9 @@ Replace &ldquo;East Asia&rdquo; with &ldquo;Eastern Asia&rdquo; region on CGSpac
"@type": "BlogPosting",
"headline": "December, 2022",
"url": "https://alanorth.github.io/cgspace-notes/2022-12/",
"wordCount": "2361",
"wordCount": "2671",
"datePublished": "2022-12-01T08:52:36+03:00",
"dateModified": "2022-12-28T22:55:34+02:00",
"dateModified": "2022-12-29T08:32:08+02:00",
"author": {
"@type": "Person",
"name": "Alan Orth"
@ -518,6 +518,43 @@ Replace &ldquo;East Asia&rdquo; with &ldquo;Eastern Asia&rdquo; region on CGSpac
<li>Then I added mappings for another handful of items</li>
</ul>
</li>
<li>I tagged ORCID identifiers for another thirty items or so</li>
<li>At 8PM I got a notice from UptimeRobot again that CGSpace was down
<ul>
<li>The load is still only around 2.x or 3.x, but there are a lot (and increasing) number of PostgreSQL connections and locks</li>
<li>They appear to be all from the frontend:</li>
</ul>
</li>
</ul>
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-console" data-lang="console"><span style="display:flex;"><span>$ psql -c <span style="color:#e6db74">&#39;SELECT * FROM pg_locks pl LEFT JOIN pg_stat_activity psa ON pl.pid = psa.pid;&#39;</span> | grep -o -E <span style="color:#e6db74">&#39;(dspaceWeb|dspaceApi|dspaceCli)&#39;</span> | sort | uniq -c
</span></span><span style="display:flex;"><span> 2892 dspaceWeb
</span></span><span style="display:flex;"><span>$ psql -c <span style="color:#e6db74">&#39;SELECT * FROM pg_locks pl LEFT JOIN pg_stat_activity psa ON pl.pid = psa.pid;&#39;</span> | grep -o -E <span style="color:#e6db74">&#39;(dspaceWeb|dspaceApi|dspaceCli)&#39;</span> | sort | uniq -c
</span></span><span style="display:flex;"><span> 2950 dspaceWeb
</span></span><span style="display:flex;"><span>$ psql -c <span style="color:#e6db74">&#39;SELECT * FROM pg_locks pl LEFT JOIN pg_stat_activity psa ON pl.pid = psa.pid;&#39;</span> | grep -o -E <span style="color:#e6db74">&#39;(dspaceWeb|dspaceApi|dspaceCli)&#39;</span> | sort | uniq -c
</span></span><span style="display:flex;"><span> 3792 dspaceWeb
</span></span><span style="display:flex;"><span>$ psql -c <span style="color:#e6db74">&#39;SELECT * FROM pg_locks pl LEFT JOIN pg_stat_activity psa ON pl.pid = psa.pid;&#39;</span> | grep -o -E <span style="color:#e6db74">&#39;(dspaceWeb|dspaceApi|dspaceCli)&#39;</span> | sort | uniq -c
</span></span><span style="display:flex;"><span> 4460 dspaceWeb
</span></span></code></pre></div><ul>
<li>I don&rsquo;t see any other system statistics that look out of order&hellip;
<ul>
<li>DSpace sessions, network throughput, CPU, etc all seem sane&hellip;</li>
<li>And then all of a sudden, I didn&rsquo;t do anything, but all the locks disappeared and I was able to access the website&hellip; WTF</li>
</ul>
</li>
</ul>
<h2 id="2022-12-30">2022-12-30</h2>
<ul>
<li>Start a harvest on AReS</li>
</ul>
<h2 id="2022-12-31">2022-12-31</h2>
<ul>
<li>I found a bunch of items on AReS that have issue dates in 2023 which made me curious
<ul>
<li>Looking closer, I think all of these have been tagged incorrectly because they were published online already in 2022</li>
<li>I sent a mail to Abenet and Bizu to ask, but for sure I know that PRMS will be considering first published date as first published date, no matter if that is online or in print</li>
<li>I also added some ORCID identifiers to our list and generated thumbnails for some journal articles that were Creative Commons</li>
</ul>
</li>
</ul>
<!-- raw HTML omitted -->
@ -540,6 +577,8 @@ Replace &ldquo;East Asia&rdquo; with &ldquo;Eastern Asia&rdquo; region on CGSpac
<ol class="list-unstyled">
<li><a href="/cgspace-notes/2023-01/">January, 2023</a></li>
<li><a href="/cgspace-notes/2022-12/">December, 2022</a></li>
<li><a href="/cgspace-notes/2022-11/">November, 2022</a></li>
@ -548,8 +587,6 @@ Replace &ldquo;East Asia&rdquo; with &ldquo;Eastern Asia&rdquo; region on CGSpac
<li><a href="/cgspace-notes/2022-09/">September, 2022</a></li>
<li><a href="/cgspace-notes/2022-08/">August, 2022</a></li>
</ol>
</section>