Evergreen ILS Website

IRC log for #evergreen, 2019-01-03

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
01:45 beanjammin joined #evergreen
07:11 rjackson_isl joined #evergreen
07:15 bdljohn joined #evergreen
07:22 bos20k joined #evergreen
07:37 sandbergja joined #evergreen
08:00 csharp 7c3cdbbd
08:00 pinesol csharp: [evergreen|Mike Rylander] LP#1706107: Offline mode - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=7c3cdbb>
08:44 mmorgan joined #evergreen
09:12 aabbee joined #evergreen
09:12 agoben joined #evergreen
09:51 Dyrcona joined #evergreen
10:16 bos20k_ joined #evergreen
10:40 khuckins joined #evergreen
10:57 sandbergja joined #evergreen
11:06 Christineb joined #evergreen
11:30 khuckins joined #evergreen
13:24 jamesrf joined #evergreen
13:33 hbrennan joined #evergreen
14:24 mcgriff joined #evergreen
14:30 phasefx just noting that on stretch I need to do systemctl start apache2@websockets.service and not /etc/init.d/apache2-websockets start
14:34 jihpringle joined #evergreen
14:48 mmorgan I'm not able to search demo.evergreencatalog.com, getting no hits for every search.
15:01 * phasefx is poking at it
15:01 mmorgan phasefx++
15:02 phasefx mmorgan: should be working now
15:05 mmorgan Thanks!
15:06 blongwel joined #evergreen
15:10 phasefx welcome
15:13 phasefx hrmm, so some instances of stretch seem to require use of /etc/init.d/ in places instead of systemctl :-/
15:14 berick phasefx: apache2ctl-websockets should work universally
15:15 phasefx berick++   in this most recent case, it was ejabberd surprising me
15:15 phasefx what do you guys think of this look/layout for the live tester?  http://testing.evergreen-ils.org/~live/
15:16 bshum phasefx++ # neat :)
15:16 phasefx will put a shortuct at the top to indicate/jump to the first failure
15:17 bshum berick: phasefx: that step's in the OpenSRF readme right?  It probably hasn't been touched since we introduced apache2-websocket
15:18 phasefx yeah, I'm reworking eg_stretch_installer to actually follow the instructions as closely as possible, and will do the same for Evergreen after this part is solid
15:18 phasefx will probably hyperlink to sections in the install instructions as well
15:20 bshum Makes sense to update the instruction to be distro specific, if necessary.  Or just use the one berick suggests.
15:20 bshum That's assuming we keep it as option #1 over the new websocketd :D
15:25 pinesol News from qatests: Failed configuring ejabberd <http://testing.evergreen-ils.org/~li​ve/test.15.html#2019-01-03T15:08:51,961120528-0500 -0>
15:25 pinesol News from qatests: Failed creating jabber users <http://testing.evergreen-ils.org/~li​ve/test.16.html#2019-01-03T15:08:51,970774027-0500 -2>
15:25 pinesol News from qatests: Failed start opensrf <http://testing.evergreen-ils.org/~li​ve/test.18.html#2019-01-03T15:08:51,980501558-0500 -4>
15:25 pinesol News from qatests: Failed start opensrf <http://testing.evergreen-ils.org/~li​ve/test.20.html#2019-01-03T15:08:51,990116639-0500 -6>
15:25 pinesol News from qatests: Failed test opensrf <http://testing.evergreen-ils.org/~li​ve/test.21.html#2019-01-03T15:08:51,999747537-0500 -8>
15:25 pinesol News from qatests: Failed configuring websockets <http://testing.evergreen-ils.org/~li​ve/test.22.html#2019-01-03T15:08:52,009366939-0500 -10>
15:38 blongwel In 3.1.7 with duplicate tcn (from 035) on import we are seeing long tcns generated with all isbns in the record. Is this expected behavior or a bug?
15:55 pinesol News from qatests: Failed configuring websockets <http://testing.evergreen-ils.org/~li​ve/test.22.html#2019-01-03T15:48:20,626585144-0500 -0>
16:04 gsams_ joined #evergreen
16:06 gsams_ joined #evergreen
16:25 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
16:45 mmorgan Anybody getting reports from patrons using Comcast as an email provider that they are not getting their Evergreen notifications?
16:45 csharp not here that I've heard
16:46 mmorgan We're getting lots of reports, but see no problems in our email logs, and we've successfully seen messages delivered to staff members who have Comcast email.
16:47 csharp do your libraries use the sending email address feature? (where they enter their email so it looks like the message comes from them and not a central server)
16:48 csharp actually, in the stock A/T templates, it pulls from the email on the Org Unit, then falls back to the library setting, then to the default address
16:49 mmorgan Emails come from a central server, but reply-to is the library's email address.
16:49 csharp mmorgan: the reason I ask is that we have to get our libraries to set up SPF records: http://pines.georgialibraries.org/spf
16:49 csharp basically they have to set that up that gives the central server permission to send email on their behalf
16:49 csharp er.. I think you get my gist :-/
16:50 mmorgan Yes, got it. Interesting - but we're not using the "Sending email address for patron notices" setting.
16:50 csharp email providers are getting stricter about enforcing that - but I would expect problems with Gmail and Yahoo too
16:51 mmorgan We send through gmail and those logs indicate those messages are all being delivered to Comcast servers. We're only seeing the usual occasional bounce when a user doesn't exist.
16:52 csharp yeah - the logs on your end will look fine - the receiving server accepts the mail in most cases, then trashes it on their end
16:54 mmorgan Tests we've done work fine. Hold notifications, etc. appear in the Comcast inboxes of the patrons, who just happen to be staff members who tested with their Comcast email addresses.
16:54 csharp oh - hmm
16:55 mmorgan But we've had a large number of reports from patrons that they're not getting messages in the past two weeks.
16:55 csharp we have a standard line of "all looks correct on our end - please contact your email provider" (sometimes including the log message on our end showing successful receipt
16:55 csharp I never hear back though
16:56 mmorgan Yes, that's where we are right now, but I was just wondering if anyone else had had similar reports recently.
16:56 csharp I'll let you know if we start hearing from people about it
16:57 mmorgan csharp++
16:57 mmorgan Thanks!
17:17 mmorgan left #evergreen
21:08 dbwells_ joined #evergreen
21:08 JBoyer_alt joined #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat