| Time |
Nick |
Message |
| 02:46 |
|
remingtron joined #evergreen |
| 04:02 |
|
umarzuki joined #evergreen |
| 04:02 |
umarzuki |
hi, evergreen docker image unable to be pulled |
| 04:02 |
umarzuki |
https://hub.docker.com/r/mobiusoffice/evergreen-ils/ |
| 04:02 |
umarzuki |
Error response from daemon: manifest for mobiusoffice/evergreen-ils:latest not found |
| 05:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 05:29 |
|
umarzuki joined #evergreen |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:11 |
|
agoben joined #evergreen |
| 07:12 |
|
rjackson_isl joined #evergreen |
| 07:39 |
umarzuki |
what t means by "Change the value of the STAFF_CLIENT_STAMP_ID variable to match the version of the staff client that you will use to connect to the Evergreen server."? |
| 07:39 |
umarzuki |
I don't have any client yet and this is my first time installing ILS |
| 07:50 |
|
Dyrcona joined #evergreen |
| 08:04 |
|
collum joined #evergreen |
| 08:08 |
|
rlefaive joined #evergreen |
| 08:38 |
JBoyer |
umarzuki, If you plan to use the web client (a good idea, especially for testing) you don't need to worry about it. Also, if you don't set it to anything you can still use the XUL client, you just have to download it directly from your server instead of evergreen-ils.org. |
| 08:39 |
JBoyer |
it would be at (your-server)/updates/manualupdate.html |
| 08:48 |
|
tsbere joined #evergreen |
| 08:48 |
|
bos20k joined #evergreen |
| 08:58 |
umarzuki |
JBoyer: thanks |
| 09:24 |
|
yboston joined #evergreen |
| 09:31 |
|
jvwoolf joined #evergreen |
| 09:36 |
|
kmlussier joined #evergreen |
| 09:38 |
|
maryj joined #evergreen |
| 10:01 |
|
rlefaive joined #evergreen |
| 10:10 |
|
Christineb joined #evergreen |
| 10:31 |
|
gsams joined #evergreen |
| 10:58 |
|
Jillianne joined #evergreen |
| 11:02 |
|
jwoodard joined #evergreen |
| 11:04 |
pinesol_green |
[evergreen|Jason Boyer] LP1690434: Date Comparisons in the Reporter - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=2a36365> |
| 11:05 |
|
rlefaive joined #evergreen |
| 11:41 |
|
sandbergja joined #evergreen |
| 11:58 |
|
rlefaive_ joined #evergreen |
| 12:02 |
|
_adb joined #evergreen |
| 12:07 |
|
jihpringle joined #evergreen |
| 12:16 |
|
jvwoolf joined #evergreen |
| 12:40 |
|
bos20k joined #evergreen |
| 12:57 |
|
krvmga joined #evergreen |
| 13:08 |
|
kmlussier joined #evergreen |
| 13:30 |
|
collum joined #evergreen |
| 13:50 |
kmlussier |
@quote random |
| 13:50 |
pinesol_green |
kmlussier: Quote #103: "* mrpeters is now known as whatismyname" (added by gmcharlt at 03:08 PM, December 23, 2014) |
| 14:04 |
dbs |
bshum et al: another translation platform candidate which apparently retains good translator credit info: https://weblate.org/en/ |
| 14:16 |
Dyrcona |
dbs++ Definitely worth looking into. |
| 14:20 |
berick |
huh, first time noticing the database application_name settings in opensrf.xml. nice! |
| 14:21 |
berick |
dbs++ |
| 14:21 |
Dyrcona |
:) |
| 14:22 |
Dyrcona |
After seeing it in pg_stat_activity, I've been considering doing the same for my Perl DBI scripts. |
| 14:22 |
|
jeff_ joined #evergreen |
| 14:43 |
|
bpmcneilly joined #evergreen |
| 15:03 |
gsams |
I'm currently trying to troubleshoot a widespread issue with my consortium that I can't seem to nail down. I'm getting 504 errors, along with other errors that are all over the board. |
| 15:03 |
gsams |
I'm not seeing any signs of the system having any major errors that would point out a possible problem. |
| 15:04 |
|
Jillianne joined #evergreen |
| 15:09 |
jeff |
gsams: logs are generally your friend. |
| 15:10 |
jeff |
gsams: looking for ERR level log entries starting just before the earliest reports can be useful. |
| 15:10 |
jeff |
gsams: there are of course many approaches and techniques. what have you looked into so far? |
| 15:12 |
|
rlefaive joined #evergreen |
| 15:12 |
gsams |
jeff: I've looked over just about all of our logs around the times that we've had major hiccups, I've restarted both services and all through osrf_control, I've even restarted all of the servers and brought everything back up as a sort of last ditch effort. Nothing has seemed to help so far. I originally wrote it off as a network issue between a single library and the server, but now I'm not so sure. |
| 15:14 |
gsams |
I can connect to our servers without any issues, it seems to be just the staff client side of things that's running into contstant problems. |
| 15:17 |
gsams |
I think I may be looking for the wrong thing, going to try re-examining the logs and see what turns up. |
| 15:18 |
jeff |
an HTTP 504 implies that there's a proxy server in front of your web server(s). do you know if that's pound proxy or nginx or something else? |
| 15:18 |
|
Dyrcona joined #evergreen |
| 15:18 |
gsams |
jeff: nginx |
| 15:23 |
|
kmlussier joined #evergreen |
| 15:24 |
dbs |
gsams: what sort of timeout values have you set for nginx's proxying? |
| 15:25 |
dbs |
default is 60s I believe, maybe some requests are simply timing out (sigh) |
| 15:27 |
gsams |
dbs: keepalive timeout is set to 65 |
| 15:27 |
jeff |
does a request for https://example.com/osrf-gateway-v1?service=open-ils.circ&method=opensrf.open-ils.system.ils_version return quickly and reliably, or does it sometimes 504 also? |
| 15:28 |
jeffdavis |
We added "proxy_read_timeout 180s;" to the "location /" block of our nginx config to avoid some timeout issues |
| 15:28 |
jeff |
if you run that query as a curl request several times, does the result differ? curl 'https://example.com/osrf-gateway-v1?service=open-ils.circ&method=opensrf.open-ils.system.ils_version' |
| 15:28 |
gsams |
jeff: I'll set that up and see, I think it's fairly intermittent though |
| 15:28 |
jeffdavis |
we had been seeing 504's on some requests like very broad searches |
| 15:28 |
jeff |
and, if nginx is throwing the 504, how often are you seeing those errors in nginx logs? |
| 15:32 |
berick |
jeffdavis: good to know. didn't realize the default was 60s. |
| 15:33 |
jeff |
jeffdavis: how often were you seeing them, and on anything other than search? |
| 15:34 |
|
JBoyer joined #evergreen |
| 15:35 |
gsams |
jeff: I just found the appropriate logs, and I'm met with incorrect times. I'm seeing them anywhere from once every few minutes, to once every 5 seconds. |
| 15:37 |
gsams |
apologies folks, this current setup is relatively new to us, so I'm still figuring a few things out |
| 15:39 |
berick |
har, looking at unofficial http status codes: 420 Enhance Your Calm (Twitter / rate limiting) |
| 15:44 |
Dyrcona |
Kernel update that supposedly fixes my laptop hanging under load issues. BBIAB. |
| 15:46 |
gsams |
most recent errors show once per minute at super consistent intervals |
| 15:47 |
gsams |
I'm giving some of the changes a chance and I'll report back if things clear up, I do appreciate the amazing help |
| 15:50 |
|
kmlussier joined #evergreen |
| 15:51 |
|
Dyrcona joined #evergreen |
| 15:51 |
jeffdavis |
jeff: the only timeout-related reports I recall seeing were related to search. Not super common (how often do you need to do a cross-consortium keyword search for "dogs" grouping by formats and editions?), but enough so that a few libraries ran into it. |
| 15:55 |
|
jwoodard joined #evergreen |
| 15:55 |
gsams |
I'm wondering if 5 minutes error free at this point is a good thing or not. |
| 15:55 |
|
mmorgan joined #evergreen |
| 16:01 |
gsams |
jeff++ |
| 16:01 |
gsams |
dbs++ |
| 16:01 |
gsams |
jeffdavis++ |
| 16:02 |
gsams |
I believe the issue may have been resolved. I'm going to remain vigilant in any case. |
| 16:24 |
|
maryj joined #evergreen |
| 16:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 16:53 |
|
mmorgan left #evergreen |
| 17:00 |
|
bpmcneilly left #evergreen |
| 17:04 |
|
jvwoolf joined #evergreen |
| 17:24 |
|
yboston joined #evergreen |
| 18:38 |
|
JBoyer_alt joined #evergreen |
| 18:38 |
|
Dyrcona joined #evergreen |
| 20:37 |
|
jvwoolf joined #evergreen |
| 20:48 |
|
Jillianne joined #evergreen |
| 22:20 |
|
genpaku joined #evergreen |
