Time |
Nick |
Message |
04:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
06:40 |
|
rlefaive joined #evergreen |
07:15 |
|
rjackson_isl joined #evergreen |
07:30 |
|
agoben joined #evergreen |
07:47 |
|
rlefaive joined #evergreen |
08:41 |
|
bos20k joined #evergreen |
08:43 |
|
collum joined #evergreen |
08:53 |
|
jvwoolf joined #evergreen |
09:03 |
|
jvwoolf1 joined #evergreen |
09:08 |
|
yboston joined #evergreen |
09:34 |
|
Dyrcona joined #evergreen |
09:35 |
|
rlefaive_ joined #evergreen |
09:55 |
|
Freddy_Enrique joined #evergreen |
09:56 |
|
kmlussier joined #evergreen |
09:57 |
Freddy_Enrique |
Good morning everyone |
09:59 |
kmlussier |
Freddy_Enrique: Good morning!@ |
10:00 |
Freddy_Enrique |
coffee? |
10:02 |
Dyrcona |
@coffee Freddy_Enrique |
10:02 |
* pinesol_green |
brews and pours a cup of Kenya Peaberry Thika Gethumbwini, and sends it sliding down the bar to Freddy_Enrique |
10:02 |
Dyrcona |
@tea |
10:02 |
* pinesol_green |
brews and pours a pot of Laoshan Black, and sends it sliding down the bar to Dyrcona (http://ratetea.com/tea/verdant/laoshan-black/6664/) |
10:33 |
csharp |
hmm - interesting: https://metacpan.org/pod/Email::Send |
10:33 |
csharp |
"Email::Send is going away... well, not really going away, but it's being officially marked "out of favor." It has API design problems that make it hard to usefully extend and rather than try to deprecate features and slowly ease in a new interface, we've released Email::Sender which fixes these problems and others. As of today, 2008-12-19, Email::Sender is young, but it's fairly well-tested. Please cons |
10:33 |
csharp |
ider using it instead for any new work." |
10:36 |
Dyrcona |
Yeah, that rings a bell. Think I've known that for a while. |
10:36 |
bshum |
https://bugs.launchpad.net/evergreen/+bug/1466502 ? |
10:36 |
Dyrcona |
I believe our use of Email::Send predates that though. |
10:36 |
pinesol_green |
Launchpad bug 1466502 in Evergreen "Replace Email::Send with Email::Sender" [Wishlist,Confirmed] |
10:36 |
csharp |
gotcha |
10:36 |
csharp |
bshum: thanks |
10:37 |
Dyrcona |
And, yeah. :) |
10:37 |
csharp |
yep - same issue here as Dyrcona mentioned in comment 1 |
10:37 |
Dyrcona |
"Time permitting" kind of like the "Get out of jail free" card. :) |
10:40 |
Dyrcona |
Yeah, looks like we've "known" for 3 years. :) |
10:40 |
Dyrcona |
lp 1362260 |
10:40 |
pinesol_green |
Launchpad bug 1362260 in Evergreen 2.7 "Email::Send is deprecated" [Undecided,Fix released] https://launchpad.net/bugs/1362260 |
10:41 |
Dyrcona |
So bug squashing week corresponds with my vacation in the woods. |
10:41 |
Dyrcona |
Depending on what's going on, maybe I'll look at it (not likely). |
10:42 |
* Dyrcona |
has a db server to unbox and set up. |
10:52 |
kmlussier |
If I were vacationing in the woods, the only bugs I would worry about are the kind with 6 legs and antennae. |
10:54 |
Dyrcona |
:) |
10:56 |
* kmlussier |
just realized she scheduled her vacation during the August maintenance release. |
10:56 |
jvwoolf1 |
Is anybody using the ebook integration as-is in 2.12? Or are you waiting until circulation is in play? |
10:59 |
|
rlefaive joined #evergreen |
11:02 |
Freddy_Enrique |
*reading the manual while listening megalovania |
11:21 |
Dyrcona |
jvwoolf1: We're testing it on training, but I've only had reports that someone's circulations are not showing up and have not looked into it. |
11:22 |
gsams |
So it looks like we've had reports start duplicating for some reason, has anyone ever seen that happen? |
11:27 |
csharp |
gsams: outputs or scheduled reports? |
11:27 |
gsams |
csharp: schedule reports |
11:27 |
csharp |
I've seen clark-kent.pl hiccup before creating many multiples of outputs |
11:28 |
gsams |
yeah, I have some duplicates that have made it up to 600+ copies in the schedule |
11:28 |
gsams |
I'd like to fix that before turning things back on |
11:28 |
csharp |
gsams: are they recurring? or new reports |
11:28 |
csharp |
? |
11:28 |
gsams |
looks like it started on the first |
11:28 |
gsams |
recurring |
11:28 |
csharp |
gsams: yeah, that's probably clark freaking out |
11:29 |
csharp |
7/1 is first day after end of FY, so super crazy |
11:29 |
csharp |
probably a badly-formed report that swallowed up RAM or processors and clark spawned way too many processes |
11:30 |
csharp |
general advice is just to make sure your reports server is well-resourced and that not too many concurrent are running at a time |
11:31 |
gsams |
csharp: It's been fine for the most part, but I'll definitely double check things to make sure it's not running off the hook |
11:32 |
gsams |
csharp++ |
11:32 |
gsams |
now to figure out how best to dedup this thing. |
11:35 |
jvwoolf1 |
Drycona: Thanks. I was having the same issue with circs not showing up, but just figured out that we don't have an API key for patron authentication. So, that would do it. |
11:35 |
jvwoolf1 |
Dyrcona++ |
11:35 |
Dyrcona |
jvwoolf1: I think it might be we don't have all of the records loaded, but I've not really looked. |
11:36 |
miker |
gsams: you can get duplicates if you kill the clark process (or it gets killed by, say, OOM killer) rather than cancelling the postgres backend (if you're manually trying to stop a run-away report). |
11:36 |
Dyrcona |
Right this minute, I'm trying to figure something out about the drive configuration in my new db server. |
11:36 |
jvwoolf1 |
Dyrcona: I could see where that would take precedence. |
11:37 |
gsams |
miker: I'm just back from a full week of being sick, so I'm fuzzy on some details. I'll certainly entertain that that is a possibility all things considered. |
11:38 |
gsams |
I'd even wager that's exactly what may have happened. I'll have to see if I can remember if anything funky happened on the 30th or the 1st. |
11:45 |
gsams |
miker++ |
11:46 |
gsams |
I believe that was likely the cause of our problem, possibly trying to stop a run-away report. |
11:46 |
gsams |
now back to figuring out how best to fix the duplicates and get reports back up and running |
12:05 |
jeff |
good luck. i recall that when a scheduled report would fail to complete (say, due to a transient error like the reporting database being offline for maintenance), the error caused the reports to not be scheduled for their next run time. annoying when you had dozens or hundreds of recurring reports. |
12:16 |
|
jihpringle joined #evergreen |
12:54 |
* gsams |
breathes a sigh of relief as duplicates have been dealt with. |
13:06 |
csharp |
gsams: awesome |
13:13 |
csharp |
ugh - I'm going to have to go crawling back to comcast - we're moving into an area without AT&T fiber :-/ |
13:13 |
csharp |
monopolies-- |
13:18 |
kmlussier |
csharp: :( |
13:20 |
csharp |
https://frinkiac.com/video/S06E13/pAAuCDj_kpPInhg8BO0htp5S2fs=.gif |
13:22 |
* Dyrcona |
crosses his fingers. First boot of the new db server with Ubuntu installed. |
13:24 |
Dyrcona |
Yay! I have a login prompt. |
13:36 |
csharp |
heh |
13:43 |
Freddy_Enrique |
^_^ |
13:45 |
Freddy_Enrique |
One question guys, here I can ask question in real time about the EG system, but when it comes to library terms, marc, etc. What forum do you recommend me? |
13:47 |
Freddy_Enrique |
There are some terms im not familair with, and I don't really think I can ask them here. |
13:49 |
miker |
Freddy_Enrique: you could start here |
13:49 |
miker |
esp if they related to how Evergreen intersects with those terms |
13:51 |
Freddy_Enrique |
no problem, great :). Then I'm gonna finish first the this chapter of the manual |
13:57 |
Dyrcona |
zfs: Where have you been all my life? |
13:58 |
Dyrcona |
zfs++ |
14:00 |
Dyrcona |
So, what's the recommendation? Should I install PostgreSQL 9.5 from Ubuntu packages for Ubuntu 16.04, or should I use the PostgreSQL community packages? |
14:08 |
csharp |
Dyrcona: we use the PostgreSQL-provided packages |
14:09 |
Dyrcona |
csharp: That's how I'm leaning. We're using them for 9.2 in production. |
14:09 |
Dyrcona |
csharp++ # One opinion is enough for me. :) |
14:14 |
miker |
Dyrcona: IMO, always use the pgdg packages |
14:16 |
miker |
faster bug fix updates, eternal upgrades even on EOL'd distros (assuming basic deps are met) |
14:20 |
Dyrcona |
miker++ # Thanks, also. |
14:51 |
Dyrcona |
Now, to tune the beast. |
15:26 |
|
kmlussier joined #evergreen |
16:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
16:51 |
|
tsadok joined #evergreen |
20:37 |
|
jvwoolf joined #evergreen |
21:26 |
|
jvwoolf joined #evergreen |
22:20 |
|
genpaku joined #evergreen |