Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Monday, February 13th, 2012

< Sunday, February 12th, 2012Raw Log FileTuesday, February 14th, 2012 >
#TimeNickMessage
#01:19:30elene has joined #evergreen
#03:46:36_bott_ has quit IRC
#03:47:32_bott_ has joined #evergreen
#04:56:05_bott_ has quit IRC
#04:56:05Callender has quit IRC
#04:56:05AaronZ-PLS has quit IRC
#04:56:05sylvar has quit IRC
#04:56:05eeevil has quit IRC
#04:56:05shadowspar has quit IRC
#04:56:06mrpeters-isl has quit IRC
#04:56:06asmodai has quit IRC
#04:56:06kbeswick has quit IRC
#04:56:06bwicksall has quit IRC
#04:59:36_bott_ has joined #evergreen
#04:59:36Callender has joined #evergreen
#04:59:36AaronZ-PLS has joined #evergreen
#04:59:36sylvar has joined #evergreen
#04:59:36eeevil has joined #evergreen
#04:59:36shadowspar has joined #evergreen
#05:00:14mrpeters-isl has joined #evergreen
#05:00:14asmodai has joined #evergreen
#05:00:14kbeswick has joined #evergreen
#05:37:48mrpeters-isl has quit IRC
#05:37:48asmodai has quit IRC
#05:37:48kbeswick has quit IRC
#05:39:20mrpeters-isl has joined #evergreen
#05:39:20asmodai has joined #evergreen
#05:39:20kbeswick has joined #evergreen
#06:33:10csharp___ is now known as csharp_GPLS
#07:10:55csharp_GPLS is now known as csharp__
#07:49:42collum has joined #evergreen
#08:06:22akilsdonk has joined #evergreen
#08:07:09tspindler has joined #evergreen
#08:12:49mrpeters-isl has quit IRC
#08:19:41csharp__good morning all, I'm chasing the trail of some "lost" functionality between 1.6.1 and 2.1 regarding the ability to "Retrieve Hold Patron" from the F5 item status screen (and possibly from the checkin screen)...
#08:19:58csharp__any clues on what got changed and why?
#08:21:52tspindlergm, i have a different question, wasn't there a file to run to link authorities to the bibs? I am certain I saw that somewhere but can't find it now
#08:33:12tsberecsharp__: Not sure what you are going after there. Unless the item is on the hold shelf that patron may be wrong, for the record.
#08:41:27csharp__tsbere: use case: http://paste.lisp.org/display/127739 - from the Helpdesk ticket submitted to us
#08:42:47csharp__if I knew the controlling file, I could look up the commit history and infer what/why from the comments, probably
#08:44:32kmlussier has joined #evergreen
#08:44:54mrpeters-isl has joined #evergreen
#08:45:32mrpeters-islmorning, I'm still looking for a home for the new Evergreen Master Development VM. Anyone who can upload it to evergreen-ils.org for me?
#08:45:47mrpeters-isl(and maybe a tester or 2)
#08:46:22senatormrpeters-isl++ for making it
#08:46:46senatori can't upload for it, but will test (eventually; in a low-bandwidth situation here right now)
#08:47:10mrpeters-islcool. i probably need moodapoo or bshum.
#08:47:45tsberecsharp__: Would need to know where the "retrieve the hold patron" button was. >_>
#08:48:04tsbere can upload to evergreen-ils.org
#08:48:24tsbereForgot I could, was given that power when I was building stuff previously.
#08:48:26tsbere>_>
#08:48:31mrpeters-isltsbere: i'll upload it to someoen where you can grab it from then
#08:48:36mrpeters-isl*somewhere
#08:48:49tsbereOh, even better, I won't even have to download it then! ;)
#08:48:57mrpeters-islright!
#08:49:07tsbereJust tell the server to grab it
#08:53:06Dyrcona has joined #evergreen
#08:55:28mrpeters-islDev VM (Master as of 2/10): http://apple.evergreen.lib.in.us/downloads/EvergreenMasterSqueeze.ova
#08:56:28collum has quit IRC
#08:56:37bwicksall has joined #evergreen
#08:59:01mrpeters-isltsbere: just let me know where it ends up so I can update the dev:summer_of_coding_ideas page.
#08:59:04csharp__tsbere: I'm trying to resurrect our legacy cluster to be sure, but if memory serves, it was in the Actions for this Record menu/context menu
#08:59:35collum has joined #evergreen
#09:01:00bwicksall has quit IRC
#09:03:02tsbere has a corrupt entry in his SSH config.....and it happens to be the one that contains the port for SSH on evergreen-ils.org >_>
#09:04:20mrpeters-islDo these upgrade instructions for the VM look appropriate to everyone? http://pastie.org/3373792
#09:05:21Meliss has joined #evergreen
#09:06:05tsberethere we go, found a backup
#09:07:01tsberemrpeters-isl: Why not just automate all of that in a bash script? :P
#09:07:46mrpeters-isli always like to go through it one by one in case something goes wrong
#09:12:37mrpeters-islthough, if you have something like that share it up :)
#09:16:03tsberemrpeters-isl: http://pastie.org/3373863
#09:16:37mrpeters-islsweeeeet!
#09:18:49mrpeters-islhow does the <Filename> differ from <stamp>?
#09:19:02tsberemrpeters-isl: Well, the script has to have a filename, doesn't it? Otherwise how will you run it?
#09:19:18mrpeters-isloh, lol i was reading it like a variable. i'm sorry
#09:20:08tsbereI am sure you can see some patterns for "how to make this do more but fail when something goes wrong" ;)
#09:21:21jenny1 has joined #evergreen
#09:21:35tsberemrpeters-isl: That a vmware file you handed me?
#09:21:59mrpeters-islits an OVA, i used virtualbox but i think you can import it to vmware
#09:22:22tsbere is trying to decide where to put it
#09:23:30mrpeters-islold one was in ~denials
#09:23:39tsbereyea, would rather not have them in user folders ;)
#09:24:15mrpeters-islhttp://evergreen-ils.org/downloads.php could probably use an update after a couple people test
#09:26:00tsberemrpeters-isl: Decided on http://evergreen-ils.org/downloads/vm/EvergreenMasterSqueeze.ova
#09:26:44mrpeters-islcool
#09:28:51alynn26 has joined #evergreen
#09:30:43alynn26 has quit IRC
#09:32:22tsberecsharp__: I think your staff are seeing things. Or not seeing things. Hard to say, really. Can't find significant *removals* from those menus at all.
#09:33:41mtcarlson has joined #evergreen
#09:33:51jeffit's in the (old/legacy?) copy_details.xul.
#09:33:55jeffOpen-ILS/xul/staff_client/server/circ/copy_details.xul
#09:34:03jeff223: <button id="r_hold" label="&staff.circ.copy_details.r_hold.label;" accesskey="&staff.circ.copy_details.r_hold.accesskey;" oncommand="retrieve_hold_patron();"/>
#09:34:37tsberejeff: Well, that isn't in the menus, which is where I was told to look :P
#09:34:43mrpeters-isldbwells: i'm noticing my changes to remove the facet header images still haven't made it in. Am I still doing something wrong with my commits?
#09:34:49bwicksall has joined #evergreen
#09:35:20tsberemrpeters-isl: I can point you at a number of pullrequest bugs that have been sitting around for months. >_>
#09:35:34mrpeters-islwell, this is something dbwells and i were working on last week
#09:35:51dbwellsmrpeters-isl: that should be in there, one second
#09:35:53mrpeters-isli thought it got pulled into master, but maybe i was wrong
#09:36:33dbwellsmrpeters-isl: isn't it this? http://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=c01869eb3999223b41e792e913f8f43e1213178a
#09:36:34mrpeters-isli might know the problem...i think i installed from senator's search hint branch
#09:36:45mrpeters-islyes...im sorry
#09:37:03dbwellsmrpeters-isl: that might do it :) no problem
#09:37:05mrpeters-isltsbere's script worked good, i just wasn't on "master"
#09:38:14mrpeters-islhas the search hint stuff been pulled into master yet?
#09:38:44csharp__jeff: thanks for that tip
#09:38:52csharp__tsbere: thanks for looking too ;-)
#09:39:38tsberemrpeters-isl: You may want to add some more stuff to the script. For example, building clients might be a nice touch.
#09:39:53mrpeters-islyep, agreed. ill see what i can figure otu.
#09:40:43tsberemrpeters-isl: Change to the staff_client directory, "make updates-client". Then probably rm -rf /openils/var/updates/archives/* because automatic updates won't actually be enabled.
#09:40:52tsberemake sure nsis, zip, unzip are installed though ;)
#09:41:09mrpeters-islright
#09:41:32mrpeters-islcd /home/opensrf/Evergreen/Open-ILS/xul/staff_client && make STAFF_CLIENT_VERSION=master02132012 rigbeta devbuild AUTOUPDATE_HOST=master.evergreen.lib.in.us updates-client rebuild
#09:41:36mrpeters-islwas what i usually do
#09:42:08tsbereI would avoid the "cd blah && do something" model in favor of "cd blah <newline> do something" model in a script ;)
#09:42:34mrpeters-islsure, agreed
#09:42:43tsberemrpeters-isl: Also, the rebuild seems incorrectly placed there.....
#09:43:04mrpeters-isloh, maybe thats why my partial updates never work?
#09:43:09tsbereyou want rebuild *before* things like devbuild, but *after* things like rigbeta
#09:43:25mrpeters-islaha ok
#09:44:00tsbererebuild and devbuild both rely on "build". If devbuild runs first then rebuild won't re-run build, which is needed for how it functions.
#09:44:14mrpeters-islgreat info. thanks
#09:44:20tsbereOf course, rebuild also throws out some of the options like the version, in favor of the previously built version
#09:44:57csharp__huh - function retrieve_hold_patron() is still there in copy_details.xul...
#09:46:51j_scott has joined #evergreen
#09:47:51bshum waves at j_scott
#09:48:40mtcarlson_ has joined #evergreen
#09:49:23j_scott waves to everyone
#09:50:28pinesol_green has joined #evergreen
#09:53:47csharp__okay - a general question... have sites that have upgraded from 1.6 to 2.0/2.1 seen a rise in problems related to client bandwidth (screen freezes, network failures, etc.)?
#09:54:07csharp__we have libraries who were (purportedly) fine on 1.6 really struggling with 2.1
#09:54:14mrpeters-islcsharp__: i dont think we have. just the issue we're having where Cat service will die off randomly
#09:54:33Dyrconacsharp__: we have both from some libraries. :)
#09:54:43csharp__huh
#09:54:50Dyrconamrpeters-isl: It isn't random. We've traced it to large deletes.
#09:54:59mtcarlson_ has quit IRC
#09:55:23tsberemrpeters-isl: Specifically item status "load this CSV file then try and delete them all" and "take this really full bucket and delete them all"
#09:55:32Dyrconacsharp__: We've always been on 2.1+ and our some of our members complain of chronic Evergreen slowness and "network errors."
#09:55:33mrpeters-islhmm i havent heard back from gmcharlt and berick about our side of it yet
#09:55:55mrpeters-isli dont think anyone uses csv to feed deletes here. maybe full buckets, but i dont know.
#09:56:21tsberemrpeters-isl: I think the csv to feed deletes was because we told them to stop doing the mass bucket deletes. So they worked around that.......
#09:56:29Dyrconawhere "full" means somewhere upwards of 100 copies. We don't have a solid threshold.
#09:56:30mrpeters-islcrafty catalogers ;)
#09:57:03mrpeters-islwell im glad to hear some progress is being made on that issue then
#09:57:27Dyrconamrpeters-isl: You'll have to share some of your support $$ with us. :)
#09:58:30Dyrconalp921812
#09:58:41DyrconaLaunchpad bug 921812
#09:58:41pinesol_greenLaunchpad bug 921812 in Evergreen "Network Error when deleting all copies in bucket" (affected: 1, heat: 6) [Undecided,In progress] https://launchpad.net/bugs/921812 - Assigned to Jason Stephenson (jstephenson)
#09:59:58csharp__ is now known as csharp
#10:01:34csharpDyrcona: thanks for the information - that is exactly what we're hearing from *some* but not all of our libraries
#10:02:10bshumcsharp: fwiw, we also get periodic network difficulties from our libs, but I don't feel it's more or less than when we were on 1.6 vs. 2.0
#10:02:30bshumUsually tends to be a network issue. Or our statewide network going down.... but... yeah.
#10:04:32berickDyrcona: 921812 is the cause of the systemic open-ils.cat failures? Or is it just a failure within that particular action?
#10:05:19Dyrconaberick: We always check the logs when the open-ils.cat failures occur, and so far there has been a large delete going on every thime.
#10:05:40Dyrconaberick: Since we've told our staff not to batch delete, the crashes have not happened.
#10:05:56csharpbshum: good to know
#10:06:05Dyrcona is working on a more efficient batch delete that the client can use.
#10:06:23berick tries to finally recreate the problem
#10:06:24csharpwe are now seeking to establish a threshold for a "recommended" bandwidth requirement
#10:06:33mrpeters-islDyrcona++
#10:07:14Dyrconacsharp: We have comcast business cable at almost all of our sites. Some complain, and others don't.
#10:07:19mrpeters-islcsharp: we have a very helpful ISP who most of our libraries use. they were nice enough to configure traffic shaping so that all traffic to our Evergreen network had priority over other traffic on those lines.
#10:07:30Dyrcona blames shoddy infrastructure in some localities vs. others.
#10:09:57csharpmost of our libraries are on the aging state-managed network that connects the state colleges and universities
#10:12:21mrpeters-islcsharp: maybe they can do something similar then?
#10:13:15mrpeters-islit helped our libraries who had just a single T1 with a big group of users who'd sit on YouTube, etc.
#10:13:25DyrconaWe used to have packet shapers when we had a private WAN. Now everything comes over the Internet to us, so shapers are next to useless.
#10:14:02DyrconaAnyone have an example of using a request callback in the staff client? Looking at Vandelay was useless since it uses tpac.
#10:16:43berickDyrcona: to be clear, "delete all copies from a bucket", do you mean the "Remove Selected From Bucket" action or the "Delete All From Catalog" action?
#10:16:53tsbereberick: The latter
#10:16:58berickthanks
#10:16:58Dyrconaberick: Delete all from catalog
#10:17:14tsbereberick: Similar issue with item status and large lists in there, too.
#10:17:28DyrconaI think the issue is that if fleshes all the copies and sends all of that fleshed data back to the server.
#10:18:14tsbere is fairly confident that is the issue, the cat listener on the backend falls over and dies while trying to process the giant request <_<
#10:18:47Dyrconacopy_bucket_batch_copy_delete in copy_buckets.js for the client side of things.
#10:19:22berickinteresting. you'd think ejabberd would cut the apache client off if the request was too big
#10:19:29Dyrcona was working on make a smaller request for the delete.
#10:19:51tsbereberick: The problem is that we set *really* large message sizes.
#10:19:55Dyrconaberick: We think it might be having issues even if the message is under the max_stanza_size.
#10:20:14bericki see..
#10:20:24berickhow big is your max_stanza_size?
#10:20:27DyrconaYeah, delete these 2,600 fleshed copies for me, please......
#10:20:35Dyrconawe've tried infinity....
#10:20:38tsbereberick: Near as I can tell, large message sizes for *drone responses* are a good thing, and prevent issues with a lot of calls. Large message sizes for *listener requests* are a bad thing.....
#10:20:45wlayton has joined #evergreen
#10:22:09senatorDyrcona: http://pastesite.com/31595
#10:22:52Dyrconasenator++
#10:24:03berickmaybe i'm crazy, but wouldn't it be better to let excessively large requests like that fail than to have them gumming up the works for everyone? from a sysadmin perspective, that is. from a code perspective, yeah, let's fix it..
#10:24:30Dyrconaberick: trouble is, the large request gum everything up when the fail.
#10:24:51Dyrconaberick: I also think, it's 2012, if they want to delete 2,600 copies, then they should be able to do it.
#10:25:07bericki'm not saying they shouldn't
#10:25:20bericki'm saying, when it fails, we fix it
#10:25:23tsbereberick: I would rather they fail then crash out the system, and I would rather they work than fail. The only way I can think of to fail them early is to put a limit at the translator/gateway for max size....or at the router level for "reject any message bigger than X passing through you"
#10:25:54Dyrconaanyway, senator's paste point me in a good direction. I'm going to start a new branch and see if I can fix both batch deletes in one go.
#10:26:42DyrconaThe deletes don't actually cause a problem when done properly on the back end. I've written a couple of scripts as workarounds for now.
#10:27:04DyrconaStaff send me the bucket id or a csv of barcodes.
#10:28:13bericktsbere: hmm, if max_stanza_size catches it, it won't even get to the router. it should die on the way from the apache client to the ejabberd server (en route to the router). the only thing that should happen is the apache process is kicked off of jabber (and the request fails, of course).
#10:28:20bericki'm curious what kind of problems that causes
#10:28:56tsbereberick: Low max stanza size means some *responses* don't work. Large max stanza size means big requests kill things. We need an incoming max compared to an outgoing max, and ejabberd only has one.
#10:30:01Dyrconasounds like a problem at the OpenSRF layer. Perhaps listeners need to be threaded?
#10:30:08berickor we fix the code to stream responses
#10:30:38Dyrconahow about streaming requests? 'cause we see the problem before the request is processed.
#10:30:59tsbereyea. The problem is the message from the router to the perl listener being far too large. :/
#10:32:56bericksure, for those the API calls need to change. there's no sense in clients having to send MB's of data for an API call to, for example, delete copies. (IOW, what Dyrcona is doing in the ticket)
#10:34:27berick jacks up his max_stanza_size and sees what kind of damage he can do
#10:35:33tsbereberick: The keyword infinite is valid for max_stanza_size (not quoted) and is ejabberd's default. Just so you know.
#10:35:58berickthanks, was wondering about that
#10:37:07eeevilDyrcona: there was support for streaming requests, actually, in the perl implementation. but that got killed with opensrf 2.0
#10:37:16mrpeters-isltsbere: When you have some time -- what would cause "Update XML file malformed (200)" when i try to use auto updates?
#10:38:01tsberemrpeters-isl: *lots* of things. Bad version data and/or bad stamp data might be a good start.
#10:42:29mrpeters-islthanks
#10:57:49tsbereberick / Dyrcona / whoever else: Just thought of why the listener may be falling apart.....could the max rate settings in ejabberd be slowing things down to the point of timeouts? Perhaps setting those to the same as the max stanza size (when not using infinity) might help.
#11:03:38berickaha, was able to kill it.
#11:03:47berickconfirmed the listener is not reading the entire message
#11:04:05berickI wonder if the open-ils.cat network buffer just filled up and started dropping packets
#11:04:30tsberecould be
#11:06:43berickfor me, the listener didn't die. it read what it could and passed it off to the child process. the child proc. died and logged an error about premature end of data in the xml
#11:06:46berickthe listener is fine though
#11:07:06berickafter a brief period of not responding, while it read the data
#11:07:11tsbereberick: Well, sometimes.
#11:07:23berickk
#11:07:25tsbereberick: Do what you just did 9 times in rapid succession, see what the router does about it.
#11:07:58tsbere finds the "request router opensrf.router.info.class.list" srfsh command useful in that case, for the record
#11:09:09tsbereor at least I think that was it <_<
#11:09:30elene has quit IRC
#11:09:33tsbereyea, that is the one
#11:17:15tsberereporting template creator--
#11:17:22tsbereIn fact....
#11:17:23tsberereporting template creator--
#11:17:24tsberereporting template creator--
#11:17:25tsberereporting template creator--
#11:17:26tsbere<_<
#11:20:07bshumHeh
#11:21:50tsbere may have to add "re-write that POS" to this list of things to work on
#11:25:05eeeviltsbere: I'll send the librarians with 50k templates that they need to rewrite to /your/ house
#11:25:47tsbereeeevil: And if the new one is 100% data compatible with the existing one?
#11:25:58eeevilgood luck with all that
#11:26:00tsbereAt least for the existing one's templates
#11:26:16eeevilsrsly, good luck
#11:38:16mrpeters-islany idea of a "safe" number of items in a bucket for now to prevent this?
#11:39:55berickmrpeters-isl: i'm sure it varies, but on my last run, mine died around the 800th copy.
#11:40:14mrpeters-isli was thinking we'd say no more than 20 or 30 in a bucket until this is fixed
#11:40:46mrpeters-islthink it's only deleting from buckets, or maybe other actions with buckets too?
#11:42:36berickmrpeters-isl: i imagine any kind of mass update/delete on copies from the staff client would have the same effect
#11:42:45plux has joined #evergreen
#11:44:09bshumcsharp: I added the revised link info to git and will figure out how to deal with the local change you made to the file on Lupin
#11:47:30bshumAll settled, I think.
#11:47:35bshumcsharp++
#11:47:57stompro__ has quit IRC
#11:48:16Stompro has joined #evergreen
#11:48:22csharpbshum: ah
#11:48:33csharpwasn't thinking about git :-)
#11:49:46tsbereeeevil: For the record, my goal with re-writing the front end of the reporter interface would be "don't even touch clark kent" - That should make it a lot easier to stay backwards comptaible ;)
#11:50:00tsbereer, compatible.
#11:50:06tsbere is having spelling issues today, apparently
#11:50:20elene has joined #evergreen
#11:53:11denials_tsbere: I'm sure eeevil can take it, but I'm not comfortable with community members publicly calling someone else's work a "POS". For whatever my opinion is worth.
#11:55:05mrpeters-isltsbere: its lightyears better than the first reports interface!
#11:55:30mrpeters-islwe still have a few reports written in that one...its much less flexible
#11:56:48mrpeters-islanyone from the dig team kicking around? I was wondering why http://docs.evergreen-ils.org/1.6/draft/html/UsingtheBookingModule.html isn't included in the 2.x versions of the documentation?
#11:57:00eeeviltsbere: the version there is the 4th UI that's existed ... there's plenty of room for improvement, but IMO the lesson is "building a template is hard, and the UI can only help so much if the user isn't familiar with the required concepts" ... if, of course, the goal is a general system.
#11:57:43mrpeters-islthe 1.6 version did the trick for us, fwiw, so i think it would be 2.x doc worthy
#11:58:18tsberedenials_: I am several templates into my day today....and only have one to show, due to a number of issues. I am making a list of things to look at fixing and/or adding. But most of my list is what I consider to be bugs today.
#11:59:03kmlussiermrpeters-isl: Probably because nobody has reviewed it and confirmed that there are no changes for 2.x.
#11:59:14mrpeters-islaha good reason :)
#11:59:27denials_tsbere: I understand that you're probably neck-deep in annoyances, but I wouldn't be interested in joining a community that slings mud at one another. And if we're trying to grow our community, we need to support one another.
#11:59:42mrpeters-islas far as we've found, that documentation was helpful
#12:00:14kmlussiermrpeters-isl: If it looks good to you and you send a message to the DIG list, rsoulliere will probably just move what's there to the 2.x docs.
#12:00:39mrpeters-isl10-4
#12:00:43tsbereeeevil: Running into a pile of things that should work but don't doesn't help those of us who are familiar with those concepts.
#12:00:58mrpeters-isltsbere: i can proabbly help with building some templates
#12:01:05mrpeters-isli think im pretty good at it
#12:01:45berickdenials_++
#12:02:14mrpeters-islif anyone has a second to confirm my subscription to the dig list i'd <3 you
#12:02:41tsberemrpeters-isl: My issues stem from things like "oh, hey, a date picker....for a value that shouldn't be a date"
#12:05:14mrpeters-islok
#12:05:50mrpeters-islthats interesting, haven't seen a case like that. will be glad to see it fixed though if it is happening.
#12:13:02luisb has joined #evergreen
#12:20:19jenny2 has joined #evergreen
#12:23:10jenny1 has quit IRC
#12:23:11jamesrf has quit IRC
#12:23:15jamesrf_ has joined #evergreen
#12:35:09elene has quit IRC
#12:54:21DyrconaWhee! My client has drifted off to La-La Land.
#12:58:45DyrconaWow! Twelve kinds of crazy.....
#12:58:51DyrconaDon't try this at home, kids!
#12:59:19DyrconaRetrieve a bucket with 14,888 copies in it. Try to quit the client while it is loading.....
#12:59:48DyrconaOh, then delete 14,000 of the copy_bucket_item entries behind the client's back....
#12:59:49bshumYikes.
#13:01:10tsbere doesn't think the client can be blamed for going off into la-la land
#13:02:23jamesrf_ is now known as jamesrf
#13:18:30bshumSigh, it occurs to me that we never actually decided anything about when to hold the next dev meeting.
#13:18:42bshumDay/time, etc.
#13:31:32berickbshum: iir, the plan was to set up a survey. do you know if there is a particular survey app/site people like to use?
#13:32:38tsbere dislikes survey apps and sites in general, but is probably in the minority there
#13:32:46bshumberick: Oh that's right. I think doodle is usually pretty good.
#13:32:58bshumI'll go poke around I guess, thanks for the reminder.
#13:33:06berickbshum++
#13:43:54Dyrcona doesn't trust his development machine.
#13:44:14DyrconaOf course, someone is playing with acq on there at the moment.....
#13:44:25kmlussier:-)
#13:44:36kmlussierDyrcona: Do you want me to get off?
#13:44:50Dyrconano, that's all right.
#13:45:03elene has joined #evergreen
#14:04:06elene has quit IRC
#14:04:45DyrconaMonster bucket has 13,999 items left. Here we go!
#14:16:48csharpI need a hold policy that will universally set anything that is reference = true to be non-holdable - can anyone point me in the right direction?
#14:17:22csharpseems like most of these are "allow the hold" type rules and I don't know how to exclude reference items :-/
#14:24:49tsberecsharp: indb?
#14:25:19tsberecsharp: if so, update everything in the hold table to "reference = false" except for one rule that says "reference=true and holdable = false"
#14:26:10bshumcsharp: What I would try in that situation, if you only wanted say... one rule to rule them all might be to write a single rule that says all reference = true is not holdable.
#14:26:15bshumThen adjust the hold weight
#14:26:21bshumSo that it matches on that the most.
#14:26:33bshumAnd then assign all your other hold rules with reference = false
#14:26:38bshumSo that it knows the difference.
#14:27:15tsberebshum: If you alter every rule to include the reference flag then weight adjusting isn't needed. The ones that don't match the reference flag get thrown out anyway. ;)
#14:27:25bshumtsbere: Oh true.
#14:27:30bshumYes, then do that csharp :P
#14:29:29natschil has joined #evergreen
#14:30:42kmlussier_ has joined #evergreen
#14:30:48Dyrconagreat....
#14:30:58Dyrconaflesh a copy bucket with 13,999 entries.
#14:31:13Dyrconagather up the target_copy ids from the bucket items.
#14:31:14vxbush has joined #evergreen
#14:31:40Dyrconamake a call to my experimental open-ils.cat.asset.copy.batch.delete.override and get no output and no copies deleted.
#14:31:56Dyrconano events thrown or returned anywhere, either. :(
#14:32:30kmlussier has quit IRC
#14:32:58Dyrconaworks fine with 53 and 84 item count buckets.
#14:38:38csharptsbere: bshum: thanks - will try
#14:41:45csharparg - you can't edit hold policies!
#14:41:51tsbere?
#14:41:58tsberedouble-click on them?
#14:43:15csharpokay - that works - I've gotten unique constraint errors (and just did when trying to batch change them)
#14:43:21bshum*cough* just use SQL :P
#14:43:42bshumOh, weird.
#14:44:01tsberecsharp: You probably already had some with the flag set
#14:47:10csharphttp://paste.lisp.org/display/127754
#14:48:25tsberecsharp: Yea, you probably already have a rule that differs from a second rule *only* in the value of the reference flag (null compared to true/false)
#14:53:09bshumtsbere: Do you guys use hold soft stalling?
#14:53:47tsberebshum: Not currently, unless someone tweaked settings when I wasn't looking.
#14:53:51bshumtsbere: Trying to figure out if hold stalling period applies differently with suspended holds, or if it'll ignore the suspended state and go based on the request date only.
#14:54:08bshumSo wait 3 days or whatnot, but that still counts even if the hold is suspended
#14:54:23bshumSo far as I can tell, it doesn't seem to distinguish
#14:54:25bshumThat might be "bad"
#14:54:27tsberebshum: If I know the code, the suspended time is included in the stalling period.
#14:54:44tsbereIt has to be, really. There is no record kept of when the hold was "thawed"
#14:54:49bshumRight.
#14:54:55bshumNo activation date per say
#14:55:01bshumPeachy.
#14:55:25tsberebshum: The activation date may not apply (not provided, manually thawed before it, etc)
#14:56:05tsbereWould be relatively trivial to add in a new date on holds to say "this hold was active on...."
#14:57:17vxbushMay I post a new question about my upgrading data from 1.6 to 2.1.1? I'm making progress, but I've his a snag running to 2.0 -> 2.1 upgrade script, and not the one I ran into last week (I fixed that.)
#14:58:07wlayton has quit IRC
#14:58:18vxbushThe following code generates an error: In the script 2.0-2.1-upgrade-db.sql, on line 1474, the code is:
#14:58:35vxbush 1472 CREATE TABLE metabib.record_attr (
#14:58:35vxbush 1473 id BIGINT PRIMARY KEY REFERENCES biblio.record_entry (id) ON DELETE CASCADE,
#14:58:35vxbush 1474 attrs HSTORE NOT NULL DEFAULT ''::HSTORE
#14:58:35vxbush 1475 );
#14:58:53vxbushThe error is: 2.0-2.1-upgrade-db.sql:1475: ERROR: type "hstore" does not exist
#14:59:13vxbushWell, yeah, that makes sense. The question is: Is there something it should be? Is this a typo problem?
#14:59:25gmcharltvxbush: you need to make sure that the hstore contrib (if you're running Pg 9.0) or extension (if 9.1.x) is installed
#15:00:06vxbushHmm, I'm guessing that's not part of the 9.0_server package. I'll have to research that. Thanks, gmcharlt. I didn't see this come up as a pre-requisite anywhere.
#15:00:49Dyrcona upped the recv timeout to 300 in his client/test script and is now happily deleting 13,999 copies via a copy bucket.
#15:02:35vxbushHmmm. postgres-contrib is installed already…….
#15:02:36bshumfwiw, it definitely mentions the hstore contrib in the upgrading wiki page from 2.0 to 2.1.
#15:03:38gmcharltvxbush: right, but the existence of the contrib package doesn't mean that it automatically installs any specific contribs into the database
#15:03:40vxbush(Thanks, bshum. My problem is having to use CentOS and running into all sorts of weirdness.)
#15:05:26gmcharltvxbush: so, psql evergreen -f /path/to/pgcontribs/contrib/hstore.sql
#15:09:02vxbushgmcharlt: Cool. I never ran into this problem before, so this was a new one on me. Sigh. I'll need to adapt the startup script for postgres to make sure it loads this module, then.
#15:09:31gmcharltvxbush: ah, no, it's a once-and-done per database
#15:10:47kmlussier__ has joined #evergreen
#15:11:29vxbushgmcharlt: ah. Going to play now.....
#15:11:38gmcharltenjoy!
#15:13:04kmlussier_ has quit IRC
#15:13:58vxbushStupid question: I'm playing with test data now, so I'm blowing away and recreating databases left, right, and center as I perfect my scripts to do this update on the production server. I am assuming said items in the hstore contrib file will need to be applied again if I blow away the evergreen database.
#15:15:13gmcharltvxbush: correct
#15:17:23vxbushgmcharlt: shiny. Okay, off to play some mroe
#15:20:41vxbushHmmm. Okay, loaded the contrib file per gmcharlt's psql command, loaded the data fresh, ran 2.0-2.1-upgrade-db.sql, and I'm getting the same error.
#15:21:11vxbushPerhaps there is another contrib I must add. Let me check bshum's upgrade page again.
#15:22:32vxbushNope, but it looks like gmcharlt's psql command wasn't quite complete. Needed to specify the database.
#15:22:35vxbushTrying again....
#15:25:51tsbereeeevil: Now bshum is poking me about if I have heard about holds go home type stuff. You ever get the code that covers that use case out into a visible location?
#15:26:34kmlussier__tsbere: Huh, I just got off a conference call where we were discussing that.
#15:27:42eeeviltsbere: serendipitous timing ... working on making that happen right now
#15:28:39tsbereOh good. I can hopefully take that into account for my circ and holds major rewrite project then. :D
#15:28:54eeevilbshum: I'll alert you, sir, as well
#15:29:02bshumeeevil: Thank you :P
#15:29:40eeeviltsbere: trying to remember if you sent plans for that
#15:29:59vxbushgmcharlt, bshum: much, much better running 2.0-2.1-upgrade-db.sql this time. Besides getting notices that seem informational, I did get one error that might be of concern:
#15:30:04tsbereeeevil: Still *working* on the plans. >_> Lots of interconnected pieces. Figure I will hit them all at once.
#15:30:22vxbushAt line 8858, the error is: insert or update on table "org_unit_setting_type" violates foreign key constraint "org_unit_setting_type_grp_fkey"
#15:30:22vxbushDETAIL: Key (grp)=(circ) is not present in table "settings_group".
#15:30:37vxbushat comment 0633.
#15:30:48bshumvxbush: Interesting, I think I saw that in my upgrade testing as well (I'm also testing 2.0-2.1)
#15:31:10vxbushbshum: I'm moving up from 1.6.0.4, so I'm slowly having to build up my process. Should I worry about this?
#15:31:13bshumBut I'm working on other issues along the way.
#15:31:57tsbereeeevil: I should probably make a page somewhere to keep track of everything I want to hit with the circ/holds reworking. Most of it is in various note files right now.
#15:32:11vxbushEverything elder was just a notice-level error.
#15:32:29vxbushelder? ggggr. Everything else was just notices.
#15:32:44eeeviltsbere: that would be rad
#15:43:34enhancin has quit IRC
#15:43:59enhancin has joined #evergreen
#15:45:43enhancinI need some generic advice. I've got the 150,000 books in and I put them in in 30 separate chunks...now I'm doing the Holdings and since they're much faster I was wondering if it would be safe to do them all at once, or should I take the same method as before? If i DO do each one separately do I need to run the .sql script in src/support-scripts after each holdings insert or just after all of them?
#15:50:12jenny2 has quit IRC
#15:52:32denials_ wonders whether the 2.0-2.1-upgrade-db.sql that vxbush and bshum are running include the fixes he posted like https://bugs.launchpad.net/evergreen/+bug/893345
#15:52:32pinesol_greenLaunchpad bug 893345 in Evergreen "Upgrade from 2.0 to 2.1 fails due to conflicts with custom permission groups" (affected: 1, heat: 6) [High,Fix committed]
#15:52:49bshumdenials_: Maybe not, but I'm toying with the one in master.
#15:53:13plux has quit IRC
#15:55:00bshumdenials_: I'll let you know though. After I'm done crying my way through a list of requested "enhancements"
#15:55:23denials_you guys appear to be running into https://bugs.launchpad.net/evergreen/+bug/883036 fwiw
#15:55:23pinesol_greenLaunchpad bug 883036 in Evergreen "2.0-2.1-upgrade.sql script: insert or update on table "org_unit_setting_type" violates foreign key constraint "org_unit_setting_type_grp_fkey"" (affected: 1, heat: 6) [Undecided,New]
#15:56:17vxbushdenials_, et al: I'm willing to be a guinea pig.
#15:57:48tspindler has quit IRC
#15:59:54Meliss has quit IRC
#16:02:29natschil has quit IRC
#16:02:38denials_base schema for rel_2_0 creates config.org_unit_setting_type with a "grp" column
#16:03:16denials_as does the 1.6.1-2.0 upgrade script in rel_2_0. hmm
#16:04:06collum has quit IRC
#16:05:50denials_ is now known as denials
#16:05:55akilsdonk has quit IRC
#16:08:33elene has joined #evergreen
#16:10:40denials changes his job title to "Killer of long-lived 100% Apache processes"
#16:16:14shadowspars/Killer/Grandmaster Slayer/
#16:19:27vxbush**vxbush hands shadowspar dragon hide gloves**
#16:21:33denialsshould probably gin up a script that checks the process list, looks for any Apache processes with > 5 minutes of processing time, and just kills them
#16:22:49tsbereeeevil: My notes so far: http://egdev.mvlcstaff.org/Circ_and_Holds_Rewrite <_<
#16:46:48enhancinhm, so I've got a huge query that got stuck..it's sucking up all the memory, is it bad to shut down evergreen during this time?
#16:47:03denialsps -eo pid,pcpu,time,comm --sort=-pcpu | grep apache2 | perl -ane '($h,$m,$s) = split /:/, $F[2]; if (int($m) > 5 && $F[1] > 95) { kill $F[0] }'
#16:47:07enhancinit's running in postgresql, but evergreen is using a ton of processor
#16:47:10denialsI think I'm going to cron that.
#16:48:39denialsenhancin: why not just kill the query?
#16:49:14enhancini'm not experienced with psql, do i do that inside of it or just kill -9 the PID of the process that is using it all?
#16:49:26denialsenhancin: I use pg_top (from http://ptop.projects.postgresql.org/)
#16:49:55denialsI wouldn't knee-jerk "kill -9" anything, that's pretty harsh
#16:50:19enhancinah, ptop is in apt-get repo : )
#16:51:10denialsso "pg_top # lists postgresql processes; "k" from inside it lets you kill a given long-running process; "Q" shows you the query that's running for a given process)
#16:51:29denialsnothing you can't get via raw pg_statistics queries but handier
#16:52:40enhancindenials: sweet, looks pretty handy.
#16:53:30denialsbut if SELECT * FROM pg_stat_activity WHERE current_query != '<IDLE>'; floats your boat, have at it :)
#16:53:53enhancinnah I use screen so i always have one window with top on anyways, I'll have another with pg_top now
#16:53:53gmcharltjust as long as the end result is pg_cancel_backend(), not kill -9
#16:53:57enhancinright
#16:53:59csharpargh! in my attempt to block holds on reference copies I have apparently blocked items that *aren't* reference!
#16:54:04enhancini got it, it's clearing the memory now
#16:54:23enhancininteresting when a server can have 25+ load and using 12GB of it's memory and still be able to respond fairly quickly
#16:54:30tsberecsharp: You get something backwards in your queries?
#16:54:34csharp@hate dojo_hold_policies_interface
#16:54:34pinesol_greencsharp: The operation succeeded. csharp hates dojo_hold_policies_interface.
#16:54:47csharptsbere: yes apparently
#16:55:14tsberecsharp: Ahh, yes, see my previous link. The first item in the "overall circ/hold stuff" group is "new editing interfaces" <_<
#16:55:22tsbereNot sure *what* to use for new ones, but we need new ones.
#16:55:24csharptsbere: excellent
#16:56:42csharpall I did was set reference = false where it was unset, then I made a rule... (sec...)
#16:58:19denialsback to django
#16:58:28jeffdjango!
#16:59:36kmlussier__ has left #evergreen
#17:01:55csharpI don't know what I did!
#17:02:07csharp shakes fists at sky
#17:04:30bshumcsharp: :(
#17:05:43bshumSo all your regular rules are ref = false
#17:05:53bshumAnd you have deny rules setup for ref = true
#17:06:07csharpI don't understand enough to know
#17:09:25bericktsbere: Dyrcona: opensrf patch to prevent services dying from too-large messages. http://git.evergreen-ils.org/?p=working/OpenSRF.git;a=shortlog;h=refs/heads/user/berick/perl-pipe-read-data-size
#17:10:29Dyrconaok. will give it a go tomorrow.
#17:10:49berickthe commit msg should spell it out pretty good. this change allowed me to delete 1k copies from the staff client. note! the request still times out in the client, because it's just too much data, but it doesn't die in the back end.
#17:11:11berick will open an lp ticket
#17:14:03jenny has joined #evergreen
#17:15:07berickbug 931747
#17:15:07pinesol_greenLaunchpad bug 931747 in OpenSRF "Perl parent/child pipe locking IO blocks on large messages" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/931747
#17:18:14Dyrcona went ahead and merged and recompiled OpenSRF so it will be ready tomorrow.
#17:23:28berickDyrcona++
#17:24:19jenny has quit IRC
#17:29:56Dyrcona has quit IRC
#17:45:54vxbush has quit IRC
#19:18:01elene has quit IRC
#21:00:08luisb_ has joined #evergreen
#21:02:42edoceo has joined #evergreen
#21:03:16luisb has quit IRC
#21:03:32edoceo has left #evergreen
#21:04:08luisb_ has quit IRC
#21:41:38finnx has joined #evergreen
#23:40:50luisb has joined #evergreen
#23:45:07luisb has quit IRC
< Sunday, February 12th, 2012Raw Log FileTuesday, February 14th, 2012 >