Time |
Nick |
Message |
07:26 |
|
collum joined #evergreen |
07:30 |
|
kworstell-isl joined #evergreen |
08:05 |
|
BDorsey joined #evergreen |
08:07 |
|
rfrasur joined #evergreen |
08:35 |
|
mmorgan joined #evergreen |
09:08 |
|
dguarrac joined #evergreen |
09:21 |
|
kworstell_isl joined #evergreen |
09:28 |
|
kworstell-isl joined #evergreen |
09:31 |
|
Dyrcona joined #evergreen |
09:36 |
Dyrcona |
I find it amusing when a library staff links to the marc_export documentation on one of our tickets. |
09:48 |
|
kworstell-isl joined #evergreen |
10:00 |
|
ahazaril joined #evergreen |
10:05 |
ahazaril |
Hi all! Can someone guide me on how to enable email notification in Evergreen ILS? I can't find the manual regarding the email configuration. Thanks. |
10:16 |
Dyrcona |
ahazaril: Email configuration on the server is a bit beyond the scope of Evergreen documentation. You need to pick a mail transfer agent software (MTA) and configure that according to the directions for your LInux distribution and local circumstances. |
10:19 |
ahazaril |
i see, tq so much! I try to learned more deeper regarding the email configuration on server |
10:19 |
Dyrcona |
I can make a few recommendations. 1. If you have more than one server, pick one to run the utility scripts. 2. Configure email on that server. 3. Configure the notification cron jobs to run on that server. |
10:21 |
|
sandbergja joined #evergreen |
10:21 |
ahazaril |
noted on that! lots of things need to learn from you guys! |
10:22 |
Dyrcona |
ahazaril: Postfix is a popular MTA, and I think it is relatively simple to set up. I prefer on that is a bit more complicated called Exim. If you search for how to set those up with your distribution, then you should find some good howtos. Assuming you are using Debian or Ubuntu, the Debian instructions for either software should work. |
10:23 |
Dyrcona |
If you have any questions about terminology or get stuck on something, I can probably help. I've been working with email servers for over 20 years. |
10:24 |
ahazaril |
the postfix i learn before this, but forgot already. need to learn back |
10:24 |
ahazaril |
sure Dyrcona! tq so much!! |
10:30 |
mmorgan |
Dyrcona++ |
10:33 |
Dyrcona |
Y'know. I just had a hunch about what may be breaking searching on my two virtual machines, and if it turns out to be trued, then that's not good. |
10:41 |
|
BrianK joined #evergreen |
10:49 |
Dyrcona |
Before I test it, I'm going to try a clean installation of what I've got. |
10:51 |
|
sleary joined #evergreen |
10:59 |
|
Christineb joined #evergreen |
11:21 |
Dyrcona |
Nope. My hunch appears to be wrong, so that's actually good. It means a mainline patch is not causing the problem. |
12:06 |
|
jihpringle joined #evergreen |
12:09 |
Dyrcona |
So, I don't think the problem is my templates because when I look at the source, the structure is there but the content is missing. |
12:11 |
Dyrcona |
Display field, innit? |
12:12 |
Dyrcona |
A pingest run should have fixed that, no? |
12:24 |
|
Dyrcona joined #evergreen |
12:24 |
Dyrcona |
Guess I can forget about that for a while. Der VPN ist kaput. |
12:31 |
Dyrcona |
I did this comparison before, and there are no differences in these templates and those that work in another place, so the database must be the problem. |
12:53 |
|
Dyrcona joined #evergreen |
13:00 |
|
sleary joined #evergreen |
13:01 |
jeffdavis |
Is there a way to see the generated SQL for a report? I feel like there's something and I'm just not recalling it |
13:19 |
mmorgan |
jeffdavis: The generated SQL can be viewed in the client. Looks like it's stored in a file. Here's what a url in the client looks like: <host>/reporter/3669/38417/109191/report-data.html.debug.html |
13:20 |
jeffdavis |
aha! thank you! |
13:20 |
jeffdavis |
mmorgan++ |
13:22 |
Dyrcona |
Yeah, it's definitely something with the database. The search result rows are "blank" with a set of stock templates, too. Oddly enough, I have a DB upgrade to a recent main branch and that one works. I think I'll try the ingest SQL from that db upgrade. |
13:26 |
jeffdavis |
Dyrcona: are you using a fresh database with concerto data, or is this a snapshot of an existing one? sometimes I have to vaccum a restored db before it gives search results |
13:32 |
Dyrcona |
jeffdavis: It's a restored database. |
13:32 |
Dyrcona |
Also, the ingest I was thinking of happens in the 3.10 upgrade and not master. I'll give it a vaccuum full analyze. |
13:54 |
|
jihpringle joined #evergreen |
13:59 |
Dyrcona |
thumbs-- # Inadvertent trackpad clicks can be frustrating. |
13:59 |
Dyrcona |
thumbs++ # Without them, we wouldn't be what we are. :) |
14:13 |
jeffdavis |
it's ok to be anti-thumb, they're opposable |
14:24 |
Dyrcona |
jeffdavis++ |
14:25 |
Dyrcona |
jeffdavis: Do you a full vaccuum or just an analyze, or something else? |
14:25 |
Dyrcona |
There's a "do" missing there. |
14:27 |
jeffdavis |
just a vacuum analyze on a few dozen tables - metabib, asset, circ/hold, and money stuff |
14:28 |
Dyrcona |
Thanks! I have a vacuum full analyze going on one database, now, but I'll try just an analyze on the other. |
14:28 |
Dyrcona |
I think I'll add to my monthly reload process right after the pg_restore. |
14:30 |
Dyrcona |
Time to play some Eurytmics: Here comes the rain again. |
14:31 |
Dyrcona |
I also have a little SQL script to "copy" a database with 'create database' using the source as a template. I think I'll add an analyze on the end of that one, too. |
14:35 |
|
jihpringle joined #evergreen |
15:16 |
* Dyrcona |
cringes at typos in his own commit messages. In a private repo, but still.... I should spell check more often. |
15:16 |
Dyrcona |
That vacuum full is still going. |
15:33 |
* Dyrcona |
switches networks yet again. |
15:41 |
|
jonadab joined #evergreen |
15:41 |
|
Dyrcona joined #evergreen |
16:13 |
|
jihpringle joined #evergreen |
17:08 |
|
mmorgan left #evergreen |
17:35 |
|
jihpringle joined #evergreen |
18:19 |
|
jihpringle joined #evergreen |
20:10 |
|
jonadab joined #evergreen |