| Time |
Nick |
Message |
| 07:04 |
|
collum joined #evergreen |
| 08:44 |
|
mmorgan joined #evergreen |
| 09:00 |
|
mmorgan1 joined #evergreen |
| 09:24 |
csharp_ |
@quote random |
| 09:24 |
pinesol |
csharp_: Quote #235: "<Dyrcona> The drug server is very aggressive. (as misquoted by Zoom auto-caption)" (added by Dyrcona at 11:21 AM, April 30, 2023) |
| 09:32 |
|
Dyrcona joined #evergreen |
| 09:47 |
Dyrcona |
Even with anubis, bots can still be a problem: Nov 30 00:18:17 cwmars-dev kernel: anubis invoked oom-killer |
| 09:59 |
Dyrcona |
And, the result of that was PostgreSQL being stopped, so I'm going to adjust some systemd unit files to tell it never to kill PostgreSQL and to prefer Apache. |
| 10:07 |
* gmcharlt |
claims 1505 |
| 10:08 |
Dyrcona |
hrm... postgresql@.service already sets OOMScoreAdjust to -900 for the postmaster, but postmaster is what I think went down, 'cause no PostgreSQL was running at all. |
| 10:09 |
Dyrcona |
I'll add to Apache's score. |
| 10:15 |
Dyrcona |
OK. Now it should stop apache before trying to stop postgres. |
| 10:16 |
* gmcharlt |
claims 1506 |
| 10:19 |
gmcharlt |
Dyrcona: in case you didn't notice it yet, I belive the fix for bug 2132031 that I just pushed is relevant to your (non-bot-related) interests |
| 10:19 |
pinesol |
Launchpad bug 2132031 in Evergreen "SQL Problems Applying Fix From 1847805" [Critical,Fix committed] https://launchpad.net/bugs/2132031 |
| 10:20 |
Dyrcona |
gmcharlt: Well, it is, but it's too late for me. We already did the dump and restore to apply the original patch. |
| 10:21 |
gmcharlt |
gotcha |
| 10:23 |
Dyrcona |
gmcharlt++ goood++ Bmagic++ |
| 10:27 |
|
Christineb joined #evergreen |
| 10:28 |
Bmagic |
gmcharlt++ goood++ Dyrcona++ |
| 10:31 |
pinesol |
News from commits: LP#2132031: stamp database updated <http://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=13db72ee4310e68e0cf8c9a865b3121e768290f5> |
| 10:31 |
pinesol |
News from commits: LP#2132031: update the 3.15.6-3.16.0 database update for 1501 <http://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=401dfd9b92c2ca16383232cd040ae18024505909> |
| 10:31 |
pinesol |
News from commits: LP#2132031: Fix issue that prevented installation of the bug 1847805 fixes in certain... <http://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=2002641af2d1dbbad3b138a2255e1629e076f0b4> |
| 10:31 |
pinesol |
News from commits: LP#2110638: stamp database update <http://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=9732b817f198a6eb5a586474e161020c33b127eb> |
| 10:31 |
pinesol |
News from commits: LP#2110638: OpenAPI improvements <http://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=76ff59105727e12a5d0ff7a70fb2ea3d07c11b70> |
| 10:48 |
Dyrcona |
csharp_: I think another benefit of using `git merge` over cherry-pick is that `git branch -d` will work more often, so that `git branch -D` is required less often. Not sure it's a benefit really, but I frequently end up doing them both with merged branches because I forget. |
| 10:49 |
csharp_ |
been using -D pretty much all the time |
| 10:49 |
csharp_ |
I don't have enough merge experience to know when -d would work :-) |
| 10:51 |
Dyrcona |
I believe -d works when commit hashes are the same, but I could be wrong. |
| 11:00 |
|
sandbergja joined #evergreen |
| 11:01 |
pinesol |
News from commits: LP2102739 Staff banner H1 & ID for link checker <http://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=39aba5e6e76078bdc758508c77ccafbf5bd5cd6f> |
| 11:20 |
goood |
Dyrcona: re no PG running after an OOM, any time a PG process of /any/ type is forcibly killed, /all/ of PG shuts itself down to avoid corruption. postmaster itself was probably not the process that got targeted |
| 11:23 |
Dyrcona |
goood: good to know. :) |
| 11:24 |
Dyrcona |
I'll search again to see if I can find the process that was killed. Didn't see it in the logs, and my journaltctl search used -k, which I probably wanted to remove. |
| 11:27 |
Dyrcona |
Yeah, I can't really tell, but judging by the high process id number, it was likely not the postmaster. |
| 11:28 |
Dyrcona |
It was probably the backend being used by a marc_export that kicks off every Sunday around midnight. |
| 11:30 |
|
jihpringle joined #evergreen |
| 11:45 |
Dyrcona |
Anyway, I've adjusted oom score for Apache and Anubis, so hopefully they go first and postgres will get spared. |
| 13:46 |
Dyrcona |
I found another case of "we're doing it wrong." |
| 13:48 |
Dyrcona |
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=blob;f=Open-ILS/src/perlmods/lib/OpenILS/Application/Circ/Circulate.pm;h=e20473162ac427698d6f0de691afa9c55b3adf97#l1762 |
| 13:49 |
Dyrcona |
from perldoc -f ref: It is a common mistake to use the result of "ref" directly as a truth value: this goes wrong because 0 (which is false) can be returned for a reference. |
| 13:50 |
Dyrcona |
However, we may not want to change the status in that case. Also, I'm not sure that's quite the proper use of ref. I'd have to write a test program. |
| 13:52 |
Dyrcona |
I've also spent only about 30 minutes looking at this today, so I could be off. |
| 13:56 |
Dyrcona |
OIC. |
| 14:39 |
|
kmlussier joined #evergreen |
| 15:01 |
|
kmlussier1 joined #evergreen |
| 15:07 |
|
hdarcy joined #evergreen |
| 15:13 |
hdarcy |
New dev volunteer here--I'm setting up the docker container provided by Blake. Is it correct to select public (host) as the network type versus private/default? |
| 15:22 |
sandbergja |
hdarcy: welcome! In what context are you seeing this network type question? |
| 15:31 |
pinesol |
News from commits: LP1835765 OPAC Settings Page Usability <http://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=9debb7d5143b8a9ab45d6151c9a36623aed468cb> |
| 15:41 |
|
kmlussier joined #evergreen |
| 15:45 |
|
hdarcy joined #evergreen |
| 15:48 |
hdarcy |
I selected 'run in docker desktop' to pull the container from the link provided (https://hub.docker.com/r/mobiusoffice/evergreen-ils) and when I go to start the brand new container docker desktop gives me this public/private network option. |
| 16:27 |
sandbergja |
hdarcy: I believe you would want the public (host) network option. My assumption is that this type would be able to communicate with your "host" machine (i.e. the computer that you have docker running within), which you do want, or else you wouldn't be able to see the running Evergreen. But if that doesn't work, definitely try the other one :-D |
| 16:36 |
|
hdarcy joined #evergreen |
| 16:36 |
hdarcy |
great, thanks! |
| 16:47 |
|
kmlussier1 joined #evergreen |
| 16:57 |
|
kmlussier1 left #evergreen |
| 17:00 |
|
mmorgan left #evergreen |
