| Time |
Nick |
Message |
| 00:30 |
|
eady joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 07:52 |
|
mantis joined #evergreen |
| 08:23 |
|
rfrasur joined #evergreen |
| 08:31 |
|
Dyrcona joined #evergreen |
| 08:34 |
|
mmorgan joined #evergreen |
| 09:22 |
|
jvwoolf joined #evergreen |
| 10:58 |
|
collum joined #evergreen |
| 11:44 |
Bmagic |
launchpad-- |
| 11:49 |
|
jihpringle joined #evergreen |
| 11:56 |
|
mantis joined #evergreen |
| 12:04 |
Bmagic |
bug 1943161 |
| 12:04 |
pinesol |
Launchpad bug 1943161 in Evergreen "Authority Browse "See" only works for "variant" headings" [Undecided,New] https://launchpad.net/bugs/1943161 |
| 12:31 |
mmorgan |
I understand that the actor.usr.passwd field is deprecated. Does anything in Evergreen update that field currently? (3.6) |
| 12:33 |
Dyrcona |
mmorgan: Lp 1730484 |
| 12:33 |
pinesol |
Launchpad bug 1730484 in Evergreen "Deprecated user password field should be removed" [Medium,Confirmed] https://launchpad.net/bugs/1730484 |
| 12:34 |
mmorgan |
Dyrcona: Saw that bug, but I guess I should have read it more closely :) |
| 12:36 |
Dyrcona |
As far as I know nothing other than authentication touches the field and passwords should be automatically migrated. |
| 12:36 |
mmorgan |
So if a patron who has had the same password since before 2.10, but has not logged in, a login now would update that field? Am I reading that right? |
| 12:37 |
Dyrcona |
The bug description says that it will migrate the password to the new table. Let me double check that, because I had thought it only happened when someone changed their password. |
| 12:39 |
|
collum joined #evergreen |
| 12:44 |
Dyrcona |
mmorgan: Yes, a password will be migrated when a user logs in. |
| 12:44 |
mmorgan |
Dyrcona++ |
| 12:44 |
mmorgan |
Thanks |
| 12:44 |
mmorgan |
That's helpful! |
| 12:47 |
* Dyrcona |
is lost in Vandelay, but that's OK. I was Lost in the Supermarket, yesterday morning: https://www.youtube.com/watch?v=hZw23sWlyG0 |
| 12:48 |
Dyrcona |
berick or anyone else: I'm trying to figure out if marc_stream_importer.pl will use the lwm_ratio on the merge profile or if we should add a match quality ratio option to the program. |
| 12:55 |
Dyrcona |
Going through the Vandelay code, I don't see how the two argument version of vandelay.auto_overlay_bib_record_with_best() gets called. |
| 13:27 |
Dyrcona |
marc_stream_importer.pl also seems like the kind of thing that would be useful to setup with inetd or the systemd equivalent. |
| 13:59 |
|
abowling joined #evergreen |
| 14:57 |
|
mixo joined #evergreen |
| 14:59 |
mixo |
Hello. I am trying to run "psql -U evergreen -h localhost -f version-upgrade/2.12.6-3.0.0-upgrade-db.sql evergreen" and geting an error |
| 14:59 |
mixo |
psql:version-upgrade/2.12.6-3.0.0-upgrade-db.sql:6803: ERROR: runtime error: file unknown-5584e26401d0 element variable |
| 14:59 |
mixo |
xsltApplySequenceConstructor: A potential infinite template recursion was detected. |
| 14:59 |
mixo |
You can adjust xsltMaxDepth (--maxdepth) in order to raise the maximum number of nested template calls and variables/params (currently set to 250). |
| 15:00 |
mixo |
what this mean? |
| 15:09 |
Dyrcona |
mixo: I've never seen that error before. Have you tried searching Google? |
| 15:09 |
Dyrcona |
Also, what version of the PostgreSQL server are you running? |
| 15:11 |
mixo |
Thank you for response. Postgresql 9.6 |
| 15:12 |
Bmagic |
mixo: that's a pretty old version of Evergreen. I wonder if it worked on an older OS (Ubuntu 14.04 maybe), perl modules are involved many times through EG.pg upgrades. |
| 15:13 |
Dyrcona |
That version of PostgreSQL should be OK, so I don't know what to tell you. |
| 15:14 |
Dyrcona |
mixo: Have you installed the prerequisites for Evergreen 3.0 on the database server? |
| 15:14 |
mixo |
yes |
| 15:14 |
Bmagic |
The last time I ran that upgrade, would have been more than 4 years ago. That error is pretty strange though. I think I would start by issuing each command from that upgrade script one at a time until you find the SQL that causes the error |
| 15:15 |
mixo |
I've installed postgreql 10 version but for some reason removed and then installed 9.6 |
| 15:16 |
mixo |
I mean with Evergreen prerequisities |
| 15:16 |
Bmagic |
woah, Did the database get upgraded to PG10 (with your data inside it), then back? |
| 15:16 |
mixo |
make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-buster |
| 15:17 |
mixo |
I've removed database and restore from backup |
| 15:17 |
Dyrcona |
Pg 10 should work but we didn't support it when 3.0 was released. I'm not saying it will resolve your issue. |
| 15:17 |
Bmagic |
mixo: ok, that's good. What version of PG created the back? |
| 15:18 |
Bmagic |
backup* |
| 15:18 |
mixo |
yes, I made mistake |
| 15:18 |
mixo |
9.4 from old server |
| 15:19 |
Bmagic |
Have you attempted to run the SQL upgrade script on PG 9.4? |
| 15:19 |
mixo |
no |
| 15:19 |
Dyrcona |
pg_restore should handle upgrading the data if you use the pg_restore for the release that you are going to: /usr/lib/postgresql/9.6/bin/pg_restore |
| 15:20 |
* Dyrcona |
dumps data from Pg 9.6 and restores to Pg 10 through 13 with no problems. |
| 15:20 |
Bmagic |
1. Break that script down into single PG commands. Run them by hand on psql CLI. Find the command that is causing the error. |
| 15:22 |
mixo |
Ok. Thank you for suggestions |
| 15:22 |
Bmagic |
2. Setup another server with PG 9.4 (and an older OS), restore the database and attempt the upgrade on that. |
| 15:22 |
Bmagic |
Couple of ideas for ya |
| 15:23 |
Dyrcona |
mixo: What are you ultimately trying to do? |
| 15:25 |
mixo |
I want new installation of evergreen after version 2.11.1 on new server debian 10 and migrate and upgrade database |
| 15:26 |
mixo |
I have 2.11.1 version on old server |
| 15:26 |
mixo |
and I want 3.7.1 |
| 15:27 |
Dyrcona |
OK. I thought so. Your backup is of Evergreen 2.11.1? |
| 15:27 |
mixo |
yes |
| 15:28 |
mixo |
with dump file has problem with unaccent function during restore |
| 15:29 |
mixo |
than I found solution and in sql backup file I change with public.unaccent |
| 15:31 |
Dyrcona |
OK. So, you're running all of the upgrades to 2.11.3, then upgrading to 2.12.0, then running all of the upgrades to 2.12.6 before doing the 2.12.6 to 3.0.0 upgrade? |
| 15:31 |
mixo |
yes |
| 15:32 |
Dyrcona |
2.12.6-3.0.0 is the first to have a problem? |
| 15:33 |
Dyrcona |
Ha! 2.12.6-3.0.0 would probably not work on Pg 10 because of the version check. |
| 15:34 |
mixo |
no, from 2.11.3-2.12.0, than 2.12.0-2.12.1, but I've ignored. than all was ok before that |
| 15:35 |
mixo |
yes, but I've removed postgresql 10 and installed postgresql 9.6 version then |
| 15:36 |
Dyrcona |
mixo: You have to run all of the intermediate upgrades. To go from 2.11.1 to 3.0 for example: 2.11.1-2.11.2, 2.11.2-2.11.3, 2.11.3-2.12.0, 2.12.0-2.12.1, 2.12.1-2.12.2, 2.12.2-2.12.3, 2.12.3-2.12.4, 2.12.4-2.12.5, 2.12.5-2.12.6, 2.12.6-3.0.0. |
| 15:36 |
mixo |
yes |
| 15:39 |
mixo |
may be installation with "make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-buster-10" and purge postgresql 10 and install postgresql 9.6 with "make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-buster" did this |
| 15:40 |
mixo |
? |
| 15:40 |
Dyrcona |
It could have. |
| 15:40 |
Dyrcona |
We didn't support buster when 3.0 came out, IIRC. |
| 15:41 |
mixo |
Ok. Thank you. I will try again from beginning. |
| 15:41 |
Dyrcona |
OK! Good luck! |
| 15:41 |
jihpringle |
mixo: if it's an option for you, when you reach 3.7 I'd recommend looking at applying the angular catalogue fixes that are coming in 3.7.2 |
| 15:42 |
jihpringle |
without them there's a significant difference in functionality between the old and new staff catalogues |
| 15:43 |
mixo |
Ok. thank you |
| 16:22 |
|
jvwoolf left #evergreen |
| 17:16 |
|
mmorgan left #evergreen |
| 18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 18:54 |
|
mantis joined #evergreen |
| 21:48 |
|
JBoyer joined #evergreen |
| 22:19 |
|
Stompro joined #evergreen |
