Evergreen ILS Website

IRC log for #evergreen, 2014-11-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
05:08 mmorgan1 joined #evergreen
06:33 mtate joined #evergreen
06:34 phasefx joined #evergreen
06:34 TaraC joined #evergreen
06:34 Callender joined #evergreen
06:35 graced joined #evergreen
06:35 eeevil joined #evergreen
07:23 wsmoak joined #evergreen
07:23 wsmoak joined #evergreen
07:50 rjackson-isl joined #evergreen
07:54 sarabee joined #evergreen
07:58 akilsdonk joined #evergreen
08:15 collum joined #evergreen
08:38 mrpeters joined #evergreen
08:39 mmorgan1 left #evergreen
08:41 mmorgan joined #evergreen
09:10 kmlussier joined #evergreen
09:19 Dyrcona joined #evergreen
09:25 kmlussier berick: I added you to the eg dev calendar so that you can add the dev meetings now.
09:35 yboston joined #evergreen
09:47 mjingle joined #evergreen
09:53 berick thanks kmlussier
10:10 mllewellyn joined #evergreen
11:12 sciani joined #evergreen
11:16 csharp @dessert [someone]
11:16 * pinesol_green grabs some Lemon Chess Pie for artunit
11:46 sciani hi - I just upgrade by training server to postgresql 9.2 - we have EG 2.6 on this server and I no longer get any results in an opac search.  Is a reingest needed?
11:54 _bott_ joined #evergreen
12:01 eeevil sciani: to get the simple stuff out of the way, you restarted the opensrf services after any needed configuration updates, yes?
12:02 sciani yes - I even restarted the server and did a cold prime
12:07 nhilton joined #evergreen
12:17 ningalls joined #evergreen
12:30 Dyrcona @blame Time change
12:30 pinesol_green Dyrcona: Time change stole bradl's tux doll!
12:50 mrpeters joined #evergreen
12:53 ningalls joined #evergreen
13:04 nhilton_ joined #evergreen
13:06 csharp @insult time change
13:06 pinesol_green time change: You are nothing but a dankish plate of saucyspleened pond.
13:10 sandbergja joined #evergreen
13:25 kmlussier left #evergreen
13:26 mjingle left #evergreen
13:38 gmcharlt joined #evergreen
13:49 hbrennan joined #evergreen
13:49 Bmagic our old SIP server is running EG 2.3.3 and is functioning just fine. I setup a new SIP server running EG 2.7.0 to match our production environment. It is responding differently and throwing off some of our services. Am I looking for a config somewhere or did the response code change from 2.3.3 to 2.7.0 ?
13:51 Bmagic Example from our old server: "OUTPUT MSG: '64 Y 00120141103 123822000000000002000000000000A 28420000400000|AEShannon Last Name|BHUSD|BV0.00|BD2007 Road city, city USA zip|BEshannon@emailaddress.org|BFEMAIL|AQPBPL|BLY​|PA20150501|PB19770203|PCResident|P​IFiltered|XI16453|AFOK|AOmobius|'
13:52 Bmagic Example from our new server: "OUTPUT MSG: '64 Y 00020141103 123603000000000002000000000000A 28420000400000|AEShannon Last Name|BHUSD|BV0.00|BD2007 Road city, city USA zip|BEshannon@emailaddress.org|BFEMAIL|AQPBPL|BLY|PA2015050​1|PB19770203|PCResident|PIFiltered|XI16453|''
13:53 Bmagic oops, the new server example is wrong
13:53 Bmagic Example from our new server: "OUTPUT MSG: '64 Y 00020141103 123603000000000002000000000000AOm​obius|AA28420000400000|AEShannon Last Name|BHUSD|BV0.00|BD2007 Road city, city MO USA zip|BEshannon@emailaddress.org|BFEMAIL|AQPBPL|BLY|PA2015050​1|PB19770203|PCResident|PIFiltered|XI16453|'
13:54 Bmagic There is a slight difference around AOmobius and |AA284........
13:55 jeff Bmagic: i can dig out the change -- in the meantime, what services is it breaking?
13:57 Bmagic Our state electronic book service is tapping our SIP for patron auth
13:57 Bmagic it's breaking their verification routine
13:58 ningalls joined #evergreen
13:59 Dyrcona Bmagic: So tell them to fix it.
13:59 Dyrcona ;)
14:00 nhilton joined #evergreen
14:00 Bmagic Dyrcona: ha! That might be the solution though, it seems that they have customized their code to expect our old server responses
14:02 Dyrcona Bmagic: Did you upgrade both the SIPServer and Evergreen software at the same time?
14:02 jeff Bmagic: if you grabbed current SIPServer on your new install, I'm thinking at least part of what you're running into is bug 1180479
14:02 pinesol_green Launchpad bug 1180479 in SIPServer "adjust field order in patron information response" (affected: 1, heat: 6) [Medium,Fix committed] https://launchpad.net/bugs/1180479
14:03 jeff Bmagic: but I don't think that would explain the lack of screen message (AF) in your "new server" example above.
14:03 Bmagic Dyrcona: I used this http://wiki.evergreen-ils.org/d​oku.php?id=evergreen-admin:sip
14:03 Bmagic jeff: AF doesnt appear in either though
14:04 jeff Bmagic: can you confirm that there is no AF in the 64 response from your new server, even with an otherwise "valid" patron?
14:04 Bmagic jeff: nvm
14:04 jeff Bmagic: i see AFOK in the "Example from our old server" above
14:04 Bmagic jeff: yeah, that's right the AF is missing in our new server
14:06 Bmagic jeff: Dyrcona: That is correct, the new server does not include the AF
14:06 Bmagic (for a valid patron)
14:06 Dyrcona Well, that sounds wrong.
14:07 Bmagic the new server has a clone of the SIPserver code inside of /opt
14:07 Bmagic git branch tells me *master
14:09 jeff yeah, bug 1246745
14:09 pinesol_green Launchpad bug 1246745 in Evergreen "Remove "OK" screen message from SIP2 patron information response" (affected: 2, heat: 10) [Wishlist,Fix committed] https://launchpad.net/bugs/1246745
14:11 Dyrcona Yeah, I was about to say that I thought it was optional now.
14:11 jeff immediate fix, patch OpenILS::SIP::Patron to revert that change. longer term fix, get the vendor to treat lack of 'OK' and consider other common values as blocking (as appropriate) and/or pay attention to data in the fixed fields... and the longer term solution is to stop using SIP2 for third party patron authentication. ;-)
14:12 jeff that last comment there isn't helpful, but is more of a political statement. :-)
14:12 Dyrcona heh.
14:13 * csharp reiterates the need for bug 1083290
14:13 pinesol_green Launchpad bug 1083290 in SIPServer "SIPServer should be packaged into releases" (affected: 2, heat: 12) [Undecided,New] https://launchpad.net/bugs/1083290
14:13 jeff csharp: if we can agree that s/ into releases/ is just as good, if not better.
14:14 jeff csharp: SIPServer should be versioned and have releases and we should declare if and when a given SIPServer/Evergreen pairing isn't compatible, but I don't want to see the SIPServer codebase and Evergreen codebase get stuffed together. I don't think that's a good idea.
14:14 bshum Since that fix was against 2.7 not SIPServer, it wouldn't help I think.
14:14 csharp yeah, that's not what I want either
14:14 jeff csharp: though I suppose "packaged with" doesn't imply "shares source tree with"
14:15 Bmagic jeff: hmmm
14:15 bshum That said I am +1 to "versions"
14:15 Dyrcona jeff csharp We've done a pretty good job of keeping SIPServer compatible with supported versions of Evergreen.
14:15 jeff csharp: do you object to the idea of SIPServer remaining a distinct download, but having a version number and release notes and "works with Evergreen X, Y, and Z"?
14:15 Dyrcona Alos, AF should really only be sent when there is a message for the patron.
14:15 csharp "into releases" means into Evergreen-agnostic SIPServer releases, like we do OpenSRF (cf. https://bugs.launchpad.net/sips​erver/+bug/1083290/comments/2)
14:15 pinesol_green Launchpad bug 1083290 in SIPServer "SIPServer should be packaged into releases" (affected: 2, heat: 12) [Undecided,New]
14:16 csharp jeff: I never meant to imply "into Evergreen releases"
14:17 bshum Also, yay USA!
14:17 jeff Dyrcona: yeah, I think we've done good there, but there are cases where it is helpful to know "I am running Evergreen X and SIPServer Y". Also, we might want to give ourselves the option in the future to not maintain compatability.
14:17 jeff bshum: welcome back!
14:17 * csharp is good with SIPServer remaining a separate project available to EG, Koha, and others
14:17 csharp bshum: :-D
14:18 * Dyrcona thinks people get hung up on versions too much, just run the latest from git. If you have a problem, upgrade first. :)
14:18 jeff csharp: got it. now that you say that, i think some of this conversation was already hashed out in the bug. Regardless, I guess it's good to have explicit confirmation. :-)
14:18 csharp no prob ;-)
14:21 Bmagic jeff: Dyrcona: I guess what I would like to do is get the exact same "release" of master as our old SIP server. I need to abandon the older server for other reasons than SIP (OS and VM reasons). If I could just get the exact same version it's running on my other machine, I should be good in theory?
14:21 Bmagic git log on my old server shows: a96db89778f899fa9fcd8667f3b745ca7763bb57 as the last commit
14:21 jeff Bmagic: no.
14:22 jeff Bmagic: the missing screen message (AF) field value of OK is due to a change in Evergreen, not SIPServer
14:22 Dyrcona Bmagic: The change was in Evergreen and not SIPServer.
14:22 Bmagic oh dang
14:22 jeff Bmagic: if the different ordering of the SIP institution field is ALSO causing you problems, you'll want to backrev SIPServer as well, but that alone will not fix your issue with the AF field in the 64 response.
14:23 jeff Bmagic: if you undo the change in Evergreen and restart SIP you should be good, though.
14:23 Bmagic That IS* a problem isnt it. ok well, off to figure that conundrum out
14:23 csharp DST--
14:24 csharp @karma dst
14:24 pinesol_green csharp: Karma for "dst" has been increased 0 times and decreased 6 times for a total karma of -6.
14:24 jeff Bmagic: commit 916c0950 should be pretty painless for you to manually revert
14:24 pinesol_green [evergreen|Thomas Berezansky] LP#1246745: Remove OK message from SIP2 messages - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=916c095>
14:25 Bmagic jeff: I am weary of the ordering issue as well
14:27 jeff Bmagic: you could in that case install a matching revision of SIPServer as what you were previously running. You could also check out master and then attempt to revert the ordering change.
14:30 jeff Bmagic: There are performance-related bugfixes in SIPServer (which your new version of Evergreen can take advantage of) after the revision you stated your old server was running, so you might want to take advantage of that if you have any self checkout use of SIP.
14:32 Bmagic jeff: Thanks for the help jeff++ Dyrcona++
14:33 jeff Bmagic: also, I asked in privmsg but you may not have seen -- can you identify the vendor in question?
14:33 jeff Bmagic: (feel free to answer in privmsg if you don't care to here)
14:34 jeff (though answering in here would be great also)
14:36 Bmagic it's overdrive
14:37 jeff thanks! could have guessed just based on marketshare, but wondered.
14:38 Dyrcona Bmagic: Overdrive has no problem with us and we use the latest SIPServer and have the Evergreen changes.
14:39 jeff many variables.
14:39 jeff including simply a matter of what was best practice at the time you each were set up.
14:39 jeff or which rules you use, etc.
14:41 jeff i have a vague feeling that VoIP handset dialplans, SSL Cipher Suite specifications, and SIP validation rules are often subject to CWC -- Copied Without Comprehension. :P
14:41 Dyrcona jeff: I have a very strong hunch that 90+% of everything is CWC when it comes to configuration.
14:43 bmills joined #evergreen
14:57 Bmagic jeff: Dyrcona: That is encouraging. I bet Overdrive had setup their config to read that screen message. Anyway, I found the single line of code in Patron.pm and put 'OK' back in. It's back and working with the 2.7.0 code minus the commit
15:12 * berick wonders what's up with the 2015 EG conf
15:14 berick specifically, the dates.  just finding "May 2015"
15:15 csharp berick: http://evergreen-ils.org/meetings/evergreen/2​014/evergreen.2014-10-16-14.02.log.html#l-31 is the last I know about
15:15 berick oh, dates!
15:15 berick thanks csharp
15:15 berick may 13-16
15:17 kmlussier joined #evergreen
15:27 hbrennan csharp: Are those dates pretty well locked in? It's a graduation weekend, so I need all the time I can get to make it work
15:30 csharp hbrennan: I don't have enough information to answer that, but from Buzzy's report to the EOB, it sounds firm
15:31 hbrennan csharp: Thanks
16:10 jeff perl packages that include Simple in the name yet depend on:
16:10 jeff ==> Found dependencies: Capture::Tiny, Sub::Exporter, MooX::Types::MooseLike::Base, Email::Abstract, Email::Simple, List::MoreUtils, Try::Tiny, Test::More, MooX::Types::MooseLike, Moo::Role, Throwable::Error, Module::Runtime, Moo, Sub::Exporter::Util, Email::Address
16:12 wsmoak joined #evergreen
16:12 wsmoak joined #evergreen
16:15 jeff > 34 distributions installed
16:21 wsmoak well csharp this is no fun at all.  I talked to my local librarians and they say that all their issues with PINES are fixed promptly and they don’t really need anything. :)
16:21 kmlussier :D
16:22 kmlussier @praise PINES
16:22 * pinesol_green PINES is the very model of a modern major hacker
16:30 Dyrcona wsmoak: There's still Launchpad.
16:32 frank__ joined #evergreen
16:32 frank__ hi all, could someone telle what is the table name where I can review via data base the closed dates editor?
16:33 jeff frank__: the underlying database table for closed dates is actor.org_unit_closed
16:34 jeff frank__: there's also actor.hours_of_operation for normal "open on these days" information
16:35 wsmoak Dyrcona: yes, she said they had reported some things, so they are probably in the issue tracker
16:35 wsmoak and I think she probably also didn’t want to complain to random person walking in off the street.  :)
16:36 frank__ jeff: excellent, thanks, we are reviewing because I guess there is a bug that display their start and end dates as the current date
16:37 nhilton_ joined #evergreen
16:38 Dyrcona frank__: That sounds familiar. What version of Evergreen?
16:38 bshum https://bugs.launchpad.net/evergreen/+bug/1320048
16:38 pinesol_green Launchpad bug 1320048 in Evergreen "closed date editor shows all closed dates as today" (affected: 4, heat: 22) [High,Fix released]
16:39 bshum Looks like something that was fixed for 2.6.1
16:41 frank__ 2.6.0
16:41 bshum Yep, that's why.
16:42 Dyrcona Yep. I knew that sounded familiar.
16:42 bshum Dyrcona++
16:42 frank__ yes, the problem is that we planned to upgrade to 2.6.3 until december, Is there something I could do to solve this problem without upgrade?
16:43 Dyrcona frank__: Upgrading is the best bet, but you could apply the code from the above bug.
16:48 frank__ ok Dyrcona, thanks
17:00 pinesol_green Incoming from qatests: Test Failure - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:11 mmorgan left #evergreen
18:19 kmlussier joined #evergreen
18:25 nhilton joined #evergreen
18:59 bmills joined #evergreen
19:35 kmlussier joined #evergreen
21:08 bmills1 joined #evergreen
21:09 nhilton joined #evergreen
21:46 csharp wsmoak: well, I have mixed feelings about that :-) I hope you still find ways to plug into Evergreen though.
21:47 wsmoak :)

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