15:47 |
* Dyrcona |
hasn't actually used MariaDB. I've stuck mainly with MySQL despite it being acquired by the Evil Empire. |
15:48 |
jeff |
Dyrcona: can you share steps to reproduce the issue you're seeing, and the symptoms? I'm curious. |
15:48 |
Dyrcona |
OK. Thought I'd ask, because a lot of people don't like table inheritance. |
15:48 |
Dyrcona |
jeff: Just --load-all-sample on Pg11+ and watch the tests fail, particularly, live_t/20-hold-targeter.t |
15:49 |
Dyrcona |
I'm comparing between Pg10 and Pg11 side by side and they get different numbers of copies in different copy locations. |
15:50 |
Dyrcona |
I'm assuming parallel execution is the problem, but it could be something else. Unfortunately, there are no errors or other useful messages logged. |
15:50 |
rhamby |
just a straight up count(*) from asset.copy where location = foo; ? |
15:53 |
Dyrcona |
Since Evergreen paste is busted, I'll paste a one-liner here: |
15:53 |
Dyrcona |
select copy_location.id, copy_location.name, copy_location.holdable from asset.copy_location join asset.copy on copy.location = copy_location.id join asset.call_number on copy.call_number = call_number.id and call_number.record = 42 order by id; |
15:54 |
Dyrcona |
On Pg 11 you get 10 copies in non-holdable locations. On Pg 10, I get 7 copies in non-holdable copy locations. Also the location names are different. |
15:55 |
Dyrcona |
Also, if you do 'request open-ils.hold-targeter open-ils.hold-targeter.target {"hold":263}' in srfsh, you get different results. This is from the failing hold-targeter test and record 42 is the record in question. |
15:55 |
Dyrcona |
I should also mention that the copies and call numbers tend to get different ids in either Pg version. |
15:57 |
Dyrcona |
I'm going to bug the good people of #postgresql about disabling parallel workers while running a script. |
16:01 |
Dyrcona |
I'm also starting to think that the problem isn't parallel execution per se. |
16:17 |
jeff |
I suspect it's "test data load relies on assumptions about sequences that are no longer valid", but I haven't gotten hands-on with it yet. Might carve out time tonight. |
16:18 |
Dyrcona |
jeff: It's more than that. |
16:23 |
jeff |
ah, I see. |
16:29 |
Dyrcona |
That query I pasted gives very different results, so I think it is more than just assumptions about ids. Setting max_parallel_workers_per_gather to 0 doesn't help, so I'm starting to think the problem is something else. |
16:46 |
Dyrcona |
There is such a thing as being too clever. |
17:27 |
|
mmorgan left #evergreen |
17:28 |
abneiman |
belatedly mmorgan++ for also release-notes-ing for those two monster releases! & pursuant to what sandbergja said above, I'm always willing to help but don'tspend a lot of time in IRC (and windows doesn't like to give me Quassel notificaitons), so, alternate methods of flagging me down are always OK :) |
18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
19:43 |
|
Christineb joined #evergreen |
19:43 |
|
troy joined #evergreen |
19:51 |
|
troy joined #evergreen |
06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
06:57 |
|
bgillap_ joined #evergreen |
06:58 |
|
bgillap__ joined #evergreen |
07:15 |
|
rjackson_isl_hom joined #evergreen |
15:03 |
sandbergja |
#info sandbergja = Jane Sandberg, LBCC |
15:04 |
JBoyer |
Feel free to #info up if you're joining us later. |
15:04 |
JBoyer |
#topic Action Items from Last Meeting |
15:04 |
JBoyer |
#info shulabear will test out the staff client in Microsoft Edge |
15:04 |
JBoyer |
Any luck in this testing pursuit shulabear? |
15:04 |
JBoyer |
Who I just noticed didn't say anything above, so may not be available... |
15:05 |
Dyrcona |
#info Dyrcona = Jason Stephenson, CW MARS |
15:05 |
JBoyer |
We can come back to this if shulabear is available later. |
15:11 |
Dyrcona |
JBoyer: Pidgin |
15:12 |
JBoyer |
Dyrcona, I'll check it out. |
15:12 |
JBoyer |
shulabear, any word on staff client functionality in MS Edge? |
15:13 |
shulabear |
Everything I tested - which was, admittedly, mainly circ and OPAC functions - worked fine in Edge |
15:13 |
JBoyer |
shulabear++ |
15:13 |
terranm |
shulabear++ |
15:13 |
JBoyer |
Those are things that see a lot of use |
15:16 |
JBoyer |
Hey, the agenda has been updated. :D |
15:16 |
Dyrcona |
:) |
15:17 |
JBoyer |
(and I sure did miss those 2 point release announcements. :-/ ) |
15:17 |
Dyrcona |
Yeah, so I know that JBoyer had mentioned wanting to have a look at some of the tests. I just wanted to see if anyone else is interested in having a look. If not, I will. |
15:18 |
Dyrcona |
It's important that we get moving on more recent PostgreSQL support in Evergreen because 9.6 is EOL on Thursday, and 10 is EOL in about a year. |
15:18 |
JBoyer |
I think the one I was kind of poking at during my last few hours at the hackaway may have been updated already. I'd like to have a look at more of them, but that's probably a couple weeks off. |
15:19 |
csharp_ |
upgrading to 10 over the next month or so |
15:19 |
Dyrcona |
JBoyer: OK. I can revisit the tests with more recent master and update the bug. |
15:19 |
Dyrcona |
We're running 10 in production, FWIW. |
15:19 |
csharp_ |
Dyrcona++ |
15:20 |
JBoyer |
Dyrcona++ |
15:20 |
Dyrcona |
In testing newer Pg releases, I've noticed performance gains in some areas and performance degradation in some others. |
15:21 |
Dyrcona |
I'm inclined at the moment to add support for newer releases in 3.9 regardless of whether or not all of the performance issues have been addressed. We can sort that out later. |
15:21 |
JBoyer |
+1 |
15:22 |
Dyrcona |
Maybe we can get a more comprehensive test suite along the way? |
15:22 |
JBoyer |
What did you have in mind, pgtap, live db, something else? |
15:23 |
JBoyer |
(Aside from "some of everything" because that would be great, but... ;) ) |
15:24 |
Dyrcona |
I'd like to figure out a way to combine pgtap with plprofiler. However, I got no output with plprofiler on Pg 14, but haven't had time to investigate. |
15:25 |
Dyrcona |
Testing performance can be tricky because some issues don't crop up until you have thousands or millions of records. |
15:26 |
alynn26 |
There is work on a large dataset for testing for Evergreen. |
15:26 |
Dyrcona |
I'm going to info the link to the Google drive folder where I've been making notes about what I've done so far. |
15:26 |
JBoyer |
Yeah, a performance testing suite might be something that has to be put together and expected to run on live-ish data, not so much for concerto. That would still be a useful thing. (and wouldn't necessarily need to be tied to any particular verison) |
15:26 |
Dyrcona |
#info Dyrcona's notes on PostgreSQL testing: https://drive.google.com/drive/folders/1sRZ8P1RHCOcZx42DxUehvOpoNkJJnfqn |
15:28 |
|
bgillap joined #evergreen |
15:28 |
Dyrcona |
So, in the meantime, I'll look at fixing the tests on newer Pg versions. It looks like the breakage is identical for Pg 12 through Pg 14. |
15:30 |
|
bgillap_ joined #evergreen |
15:30 |
JBoyer |
I know the version numbering change is somewhat symbolic, but it does feel like they're a lot more comfortable breaking things lately. We've hit issues with 10 in the past and now 12+ in just the last couple of years. |
15:31 |
|
bgillap_ left #evergreen |
15:32 |
JBoyer |
#info array_accum Aggregate and PostgreSQL 14 ( lp 1947595 ) |
15:32 |
pinesol |
Launchpad bug 1947595 in Evergreen "array_accum Aggregate and PostgreSQL 14" [Undecided,New] https://launchpad.net/bugs/1947595 |
15:33 |
Dyrcona |
This one is more concrete. There's a branch on that bug that replaces our custom array_accum function with array_agg from Pg. If someone would like to look at it, that would be great! |
15:35 |
JBoyer |
It does seem pretty straightforward, does anyone want to volunteer to put a test system together to make sure that 2-3 calls of array_accum work the way we think they do? (which they almost certainly do) |
15:35 |
JBoyer |
I can get to it in a week or two if not. |
15:37 |
JBoyer |
I'd like to add that *anywhere* we have a func that largely duplicates (or because of age, exactly duplicates) an internal function we do whatever we can to remove it. I keep giving evergreen.upper and .lower sideeye but I know it's something to do with consistency in the face of multiple potential Unicode implementations, etc. |
15:38 |
JBoyer |
#action JBoyer will test out the branch in lp 1947595 |
15:38 |
pinesol |
Launchpad bug 1947595 in Evergreen "array_accum Aggregate and PostgreSQL 14" [Undecided,New] https://launchpad.net/bugs/1947595 |
15:38 |
JBoyer |
Moving on with less than 20 before I vanish, |
15:38 |
JBoyer |
#info Hackaway followup: Automating point release notes (abneiman) |
17:02 |
|
mmorgan left #evergreen |
17:21 |
JBoyer |
bgillap_, check out https://github.com/HitScan/systemd-evergreen |
17:22 |
JBoyer |
shouldn't be version-specific, though you'll want to make sure that they cover your needs (may need to remove some things from Requires or things along those lines) |
17:23 |
JBoyer |
they've been developed and well-tested against single server setups, but will likely need tweaking for production use. |
18:02 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
07:19 |
|
rjackson_isl_hom joined #evergreen |
08:17 |
rhamby |
Keith-isl fyi, downloading the recorded sessions from the hack-a-way and will have them online later today |
08:35 |
|
mantis joined #evergreen |
10:43 |
|
terranm joined #evergreen |
11:00 |
mmorgan |
terranm: Are you trying to clone yourself? If you figure it out, let me know! |
11:00 |
|
mantis joined #evergreen |
11:14 |
mantis |
I'm running through the Docker version of the Evergreen test server install: https://wiki.evergreen-ils.org/doku.php?id=newdevs:testserver |
11:15 |
mantis |
When trying to mount via cifs, I get a host is down error (mount error 112) |
11:15 |
terranm |
I wish! My internet keeps blipping and causing irc to kick me out |
11:15 |
mantis |
From what I'm reading based on other isos, it seems to be an issue with something from cifs that isn't supported anymore |
11:19 |
Keith-isl |
Something I was hoping to ask some GA Pines folk during the Hack-A-Way but couldn't due to putting out other fires: I am very interested in how you handle student cards from a policy perspective (which isn't as much fun as talking about the technical perspective, I know). |
16:25 |
|
jvwoolf left #evergreen |
17:10 |
|
mmorgan left #evergreen |
17:25 |
jeff |
> Be cautious about sharing sensitive information. MARClistserv.loc.gov is outside your organization and isn't in your contacts. |
18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
02:59 |
|
phasefx_ joined #evergreen |
02:59 |
|
gmcharlt_ joined #evergreen |
03:42 |
|
jvwoolf joined #evergreen |
06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
07:00 |
JBoyer |
Keith-isl++ |
07:22 |
|
rjackson_isl_hom joined #evergreen |
08:39 |
|
mantis joined #evergreen |
11:40 |
|
jihpringle joined #evergreen |
11:56 |
Dyrcona |
miker: It looks like array_accum is only used in booking when I grep the code. |
13:34 |
|
jihpringle joined #evergreen |
13:46 |
Dyrcona |
jeffdavis: I was running live tests and live_t/29-lp1817645-remoteauth-patron-api.t failed. It got 502 instead of the expected 403. Do you think I missed something in my setup? |
13:48 |
Dyrcona |
@blame nginx |
13:48 |
pinesol |
Dyrcona: nginx 's bugfix broke Dyrcona's feature! |
13:50 |
jeffdavis |
yeah, 502 implies a problem with proxy setup to me, but the live test ought to work with stock Apache + concerto data |
13:50 |
jeffdavis |
(or at least stock user data if we consider that "concerto") |
13:51 |
Dyrcona |
yeah. I usually setup nginx on my test vms just because. |
13:52 |
Dyrcona |
Ok. nginx and apache2 disagree on the ports that apache2 is using. |
14:02 |
Dyrcona |
That was it. Now that nginx and apache2 are talking to each other, all tests pass. |
14:06 |
Dyrcona |
I ran the db tests, too. |
14:08 |
Dyrcona |
3.9-beta, really? Maybe we should make like #postgresql and drop the first digit? |
14:14 |
Dyrcona |
Well, I guess they actually dropped the second digit, didn't they? |
14:17 |
jeff |
third? |
16:28 |
abneiman |
csharp_: indeed; the only way I know to do it is painstakingly by hand (for point releases, that is) |
16:56 |
|
jvwoolf left #evergreen |
17:06 |
|
mmorgan left #evergreen |
18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
21:26 |
|
alynn26 joined #evergreen |
00:30 |
|
rhamby joined #evergreen |
00:32 |
|
book` joined #evergreen |
06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
07:29 |
|
rjackson_isl_hom joined #evergreen |
08:39 |
|
mmorgan joined #evergreen |
08:46 |
|
rfrasur joined #evergreen |
09:39 |
Bmagic |
collum++ |
09:41 |
Dyrcona |
Never go in against a movie when Wallace Shawn is in the cast. :) |
09:42 |
mmorgan |
:) |
09:43 |
Dyrcona |
So, I've managed to get the array_accum aggregate recreated in my Pg 14 database. I'm going to go ahead with my testing and see what happens. Also, Lp 1947595. |
09:43 |
Bmagic |
hahahaha. Side note: I signed up to listen to the cast perform a reading of the script live on zoom last year. That was really fun. Of course Andre the giant wasn't there but Josh Gadd did awesome as the giant |
09:43 |
pinesol |
Launchpad bug 1947595 in Evergreen "array_accum Aggregate and PostgreSQL 14" [Undecided,New] https://launchpad.net/bugs/1947595 |
09:43 |
Bmagic |
Dyrcona++ |
09:54 |
Dyrcona |
Hah. |
09:54 |
Dyrcona |
I wasn't talking to you, pinesol. |
09:55 |
Bmagic |
I didn't know you would actually* try it on production |
09:59 |
Dyrcona |
Bmagic: That's not on production. It's a test db server. |
10:00 |
Dyrcona |
It is a copy of production data, though. |
10:00 |
|
alynn26 joined #evergreen |
10:01 |
Bmagic |
yeah, I was kidding ya |
13:58 |
|
mmorgan left #evergreen |
15:51 |
|
jihpringle joined #evergreen |
16:57 |
|
jvwoolf left #evergreen |
18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
07:27 |
|
rjackson_isl_hom joined #evergreen |
07:55 |
|
collum joined #evergreen |
08:08 |
|
Dyrcona joined #evergreen |
09:36 |
|
jvwoolf joined #evergreen |
11:18 |
|
alynn26 joined #evergreen |
11:20 |
|
alynn26 joined #evergreen |
12:09 |
mantis |
I am installing via ansible to a new test environment. After running sudo ansible-playbook playbook.yml, I get this error when downloading websocketd |
12:10 |
mantis |
changed, true "cmd": "cd/tmp/ && wget --quiet https://github.com/joewalnes/websocketd/releases/download/v0.3.1/websocketd-0.3.1-linux_amd64.zip", "delta".... |
12:10 |
|
jihpringle joined #evergreen |
12:11 |
berick |
mantis: which branch? |
12:11 |
mantis |
20.04 |
13:03 |
* Dyrcona |
is trying to get Net::SFTP::Foreign to work from a cron job. I suspect the issue is that it can't fine the known hosts file. |
13:10 |
Dyrcona |
Also, you just have to love it when your remote connections hang. |
13:13 |
Dyrcona |
mantis: I'm not sure what's going on, but I suspect either your VB networking is not quite right or github are temporarily blocking wget from your IP for some reason. |
13:16 |
Dyrcona |
Also, it helps not to make typos in the configuration file of the program that you're testing. RE: my issue with Net::SFTP::Foreign. |
13:24 |
Dyrcona |
Looks like the typo was my problem all along. :( |
13:24 |
mmorgan |
typos-- |
13:29 |
mantis |
Dyrcona++ |
13:29 |
mantis |
typos-- |
13:37 |
|
jvwoolf joined #evergreen |
14:15 |
* Dyrcona |
removes Pg 9.6 from the test db server and configures Pg 14 to use the port that Pg 9.6 was listening on. |
14:38 |
|
mantis joined #evergreen |
14:48 |
Dyrcona |
So, the 1288 upgrade script blows up on my data: psql:Open-ILS/src/sql/Pg/upgrade/1288.schema.note_and_message_consolidation.sql:297: ERROR: null value in column "create_date" violates not-null constraint |
14:50 |
Dyrcona |
Yeah, we have 94,011 actor.usr_note entries with a null create date. |
15:54 |
Dyrcona |
After updating the notes, the rest of the upgrade script succeeds. |
15:54 |
Dyrcona |
We may end up deleting a lot of these old notes at some point. |
17:40 |
|
mmorgan left #evergreen |
18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
18:29 |
jeffdavis |
tag_updaters++ |
22:08 |
|
troy joined #evergreen |
22:08 |
|
Christineb_ joined #evergreen |
02:56 |
|
jweston joined #evergreen |
02:56 |
|
miker joined #evergreen |
02:56 |
|
akilsdonk joined #evergreen |
06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
06:38 |
|
abneiman joined #evergreen |
07:22 |
|
rjackson_isl_hom joined #evergreen |
08:02 |
|
Dyrcona joined #evergreen |
09:00 |
|
rfrasur joined #evergreen |
09:14 |
|
collum joined #evergreen |
10:34 |
|
jvwoolf joined #evergreen |
12:13 |
Dyrcona |
So, from what it looks like (i.e. all of my tests say that the replication is caught up with zero lag), and from what RhodiumToad implied over in #postgresql, that starting replication query I mentioned yesterday is apparently normal in Pg 10. |
12:15 |
jeff |
not sure I saw you mention that yesterday. |
12:15 |
jeff |
(in here, anyway) |
12:22 |
|
jihpringle joined #evergreen |
15:05 |
|
sandbergja joined #evergreen |
15:05 |
JBoyer |
#info JBoyer will look at adding Edge on Windows support to the Hatch installer |
15:05 |
JBoyer |
To be honest with myself as much as the rest of you, this just isn't happening until November at the earliest, and I don't have the highest hopes for that either. |
15:05 |
JBoyer |
I can promise you that it will be an uneventful thing to test if anyone else would like to volunteer to experiment with the staff client in Edge. |
15:06 |
|
sandbergja joined #evergreen |
15:06 |
JBoyer |
Are there any volunteers interested in downloading Microsoft Chrome and making sure it Does The Thing? |
15:06 |
sandbergja |
#info sandbergja = Jane Sandberg, Linn-Benton Community College, coming in late |
15:07 |
JBoyer |
shulabear++ |
15:09 |
JBoyer |
I don't expect any surprises since I do use it at home to work with Evergreen, but I use a pretty limited subset of the client. If you could go through and poke at most interfaces side by side with Chrome and note any differences that would go a long way towards answering the question of how hard it would be to support. |
15:10 |
shulabear |
Got it. |
15:10 |
JBoyer |
#action shulabear will test out the staff client in Microsoft Edge |
15:10 |
terranm |
Speaking of which, has anybody done any extensive testing with ChromeOS? I know there are lots of printing headaches with ChromeOS, but not sure about any other potential problems |
15:10 |
|
terranm89 joined #evergreen |
15:11 |
JBoyer |
I mean, it literally is Chrome, even moreso than Edge, so I would hope it works, printing (and Hatch) aside. |
15:11 |
terranm89 |
Love it when I ask a question and IRC immediately kicks me off |
15:17 |
rfrasur |
gmcharlt++ |
15:18 |
gmcharlt |
some comments: |
15:18 |
abneiman |
gmcharlt++ |
15:18 |
gmcharlt |
1. we should also do an OpenSRF release, but that would mostly be about noting the Debian support changes |
15:19 |
gmcharlt |
2. For the release notes, I used 'asciidoctor' rather than 'asciidoc' to generate the HTML version. Main reason: asciidoctor supports the number of headings levels we're currently using, asciidoc does not |
15:19 |
gmcharlt |
3. testers welcome and needed |
15:19 |
gmcharlt |
so I'm wondering if anybody can make commitments to test this week or early next week |
15:20 |
gmcharlt |
assuming successful testing, I think the RC period could be truncated or potentially even dropped |
15:21 |
JBoyer |
Note if anyone is on the fence that some of the bugsquash servers could be updated to have the 3.8 beta if you're concerned about not being able to install it locally. |
15:22 |
rfrasur |
Are we just testing what's in the release notes? |
15:22 |
rfrasur |
(sorry, I know this is a dumb question) |
15:22 |
abneiman |
I can test against an updated bugsquash (need to finalize some docs things anyway) |
15:22 |
JBoyer |
Making sure that nothing existing was broken would also be good. |
15:22 |
gmcharlt |
rfrasur: that would be a started point, but the broader testing that we collectively do, the more regressions that get identified |
15:22 |
rfrasur |
So, release notes and generalized "everything" testing? |
15:23 |
gmcharlt |
yeah |
15:23 |
JBoyer |
I'll just plan to load up pattypan and festivus with 3.8b. pattypan will be a fresh db, festivus an upgrade from 3.7.1 |
15:23 |
rfrasur |
If there's a server, I can commit some time. |
15:25 |
JBoyer |
later today basically means plan to look at them whenever you have time tomorrow or later; I'm not working on them this particular moment. ;) |
15:25 |
rfrasur |
lol, slacker |
15:26 |
JBoyer |
Only one keyboard on this machine. |
15:26 |
JBoyer |
So, if no one has anything else to add re: testing 3.8b we have our LP updates coming up. |
15:27 |
terranm89 |
Do these LP tag changes sound okay to everyone? Any red flags or other tag suggestions? https://docs.google.com/document/d/1rB11V4Lla_c5Sw_CuytvQRbDBaa6RsIgGA6ZswaaUhs/edit# |
15:27 |
terranm89 |
Sorry, did I jump ahead? |
15:27 |
JBoyer |
Technically, but that's LP too. :) |
15:31 |
Dyrcona |
I don't necessarily think so, unless by needsrepatch we mean it doesn't work as advertised. |
15:31 |
terranm89 |
That's how I was interpreting needsrepatch |
15:32 |
JBoyer |
And I think there are a couple instances where that's the case. |
15:32 |
terranm89 |
This is the description in the official tags list: testing revealed that the submitted code needs more work |
15:32 |
terranm89 |
Of course, we could just change that description, too |
15:33 |
Dyrcona |
I'm not sure that I like the two tags being so similar, but guess I'll have to live with it. |
15:33 |
Dyrcona |
Also, I agree with gmcharlt regarding the deprecation tag. |
15:34 |
terranm89 |
Whatabout "needsrebase" and "needswork" ? |
15:56 |
Dyrcona |
JBoyer: I had some scripts for updating Lp bugs by series for releases, setting Fix Committed to Fix Released, but they stopped working a few years ago. I have meant to revisit them. |
16:03 |
JBoyer |
Dyrcona++ hopefully that newer python module will make that easier |
16:04 |
|
jvwoolf joined #evergreen |
18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
03:30 |
|
jweston joined #evergreen |
03:30 |
|
miker joined #evergreen |
03:30 |
|
akilsdonk joined #evergreen |
06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
09:18 |
|
collum joined #evergreen |
09:27 |
|
mantis joined #evergreen |
10:35 |
|
Dyrcona joined #evergreen |
10:43 |
Bmagic |
not yet, but maybe your my canary |
10:48 |
Dyrcona |
It all worked before doing apt upgrade and a reboot. |
10:49 |
Dyrcona |
What makes me suspect iptables on the load balancer is it works on machines with external IPs as well as non-routable IPs. |
10:49 |
Dyrcona |
I have tested on all of my vms, yet. |
10:50 |
Dyrcona |
That should be I have NOT tested on all of the vms. |
10:50 |
Dyrcona |
It's always something... |
10:52 |
Dyrcona |
OK. It is not iptables. DNS works on a physical server that was upgraded previously from Ubuntu 16 to Ubuntu 18, had updates applied today, and still has /etc/network/interfaces. So, maybe its with netplan and systemd? |
10:52 |
Dyrcona |
The DNS nameservers are the same. |
11:26 |
Dyrcona |
s/you're/your/ |
12:37 |
|
collum joined #evergreen |
12:43 |
|
collum joined #evergreen |
13:15 |
mantis |
This was something I asked once already in IRC. I tried to set up an autorenewal notice in a test environment to display the item barcode but received failures. The latest I had were [%- SET idx = loop.count - 1; SET udata = user_data.$idx -%] |
13:15 |
mantis |
[%- SET cid = circ.target_copy.id || udata.copy -%] |
13:15 |
mantis |
[%- SET copy_details = helpers.get_copy_bib_basics(cid) -%] |
13:15 |
mantis |
Barcode: [% circ.target_copy.barcode %] |
13:17 |
Dyrcona |
mantis: You added circ.target_copy to the environment: action_trigger.environment table? |
13:19 |
mantis |
ah I didn't I'll try that now |
14:03 |
Dyrcona |
iptables-- |
14:03 |
Dyrcona |
pf++ |
14:18 |
Dyrcona |
So, my DNS problem ended up being iptables on the load balancer/router. I had to switch from a SNAT rule to a MASQUERADE. I'm not sure why the SNAT stopped working for DNS, but still seemed to work for connections via IP address. Oh well, it's all working, now. |
14:25 |
Dyrcona |
On the plus side, we're running Pg 10 in production. The pg_upgrade with a copy, not --link, took about 1 hour, then another hour or so to restart replication with pg_basebackup. |
18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
21:35 |
|
degraafk joined #evergreen |