Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Wednesday, November 23rd, 2011

< Tuesday, November 22nd, 2011Raw Log FileThursday, November 24th, 2011 >
#TimeNickMessage
#00:19:35phasefx has quit IRC
#00:19:37dbs has quit IRC
#01:16:06darshan has joined #evergreen
#01:17:54darshanWhen I am taking reference of any record and importing that record ,I am receiving error mention in 1error.log file, After that when I am placing hold for my patron I am receiving error mention in 2error.log file, Then at time of capturing hold ,I am receiving error mention in 3error.log file. Atlast ,I want to set action trigger and for that I have set hook for hold.available and hold.capture but after doing set up also ,mail i
#01:18:08darshanthe links are-- 1error file-http://www.woofiles.com/dl-272575-iTt6ZCIw-1error.log 2error file-http://www.woofiles.com/dl-272576-q4Ru51P6-2error.log 3error file-http://www.woofiles.com/dl-272577-OxGOv9ye-3error.log
#01:18:31darshanplz ans me if ne1 can..plzz :(
#07:20:01dbs has joined #evergreen
#07:21:27Dyrcona has joined #evergreen
#07:42:28collum has joined #evergreen
#08:01:22tspindler has joined #evergreen
#08:05:48dbs has quit IRC
#08:55:17akilsdonk has joined #evergreen
#09:19:45darshan has quit IRC
#09:31:05jenny1 has joined #evergreen
#10:05:18kivilahtio has joined #evergreen
#10:15:52dbs has joined #evergreen
#10:18:43dbstspindler: http://evergreen-ils.org/dokuwiki/doku.php?id=versioning has a summary of alpha / beta / release candidate requirements
#10:19:11phasefx has joined #evergreen
#10:20:33kivilahtioHello #Evergreen! What does a boy need to do to get the "Copy Summary" visible in the OPAC. I checked and I have 3 items bound to the call_number and the call_number is bound to the record I am searching. I get the copies in the main search listing, but not in the "Record Summary".
#10:21:06kivilahtioRecord Summary -> Copy Summary
#10:21:21tsbereClick "Show all Copies" or whatever it is?
#10:21:27tsbere guesses at random without actually looking
#10:21:52tsbere"View Copy information for all...."
#10:22:49tsbereOh, and maybe make sure you checked the copies in. :P
#10:22:58kivilahtiohmm havent done that
#10:23:26kivilahtioi think I have to modify hte import script I did to set all the items as present
#10:24:57phasefxkivilahtio: oh, if you're importing these items in some way, make sure the opac_visible flag on them is set to true
#10:26:43kivilahtiophasefx: yup it is set true on default
#10:26:59kivilahtiogoogled on some leads
#10:27:04phasefxother things that have opac_visible flags include copy locations and copy statuses
#10:27:17kivilahtiochecking on the status column possibilities
#10:27:54phasefxbut if your search is finding the record outside of the staff client, it's probably not visibility
#10:28:13kivilahtiostatus is 0
#10:28:37dbskivilathio: publicly visible URL?
#10:29:18kivilahtiodbs: where can i set that?
#10:29:34dbskivilahtio: I mean, can you point us at a URL so we can poke directly?
#10:29:42kivilahtioah sorry not quite yet
#10:29:47kivilahtiohmm
#10:30:16kivilahtiohttp://193.65.112.189/opac/en-US/skin/default/xml/rdetail.xml?l=1&d=0&t=big%20knockover&tp=keyword&hc=1&r=400016&rt=keyword
#10:30:31kivilahtiodbs: got it
#10:30:54kivilahtiodbs: I am having some issues with the local it department and firewalls, but for the time being that port should be visible
#10:33:01phasefxthe page is dying with a javascript error
#10:35:21dbsis there a mix of opac JS (maybe from master?) and middle layer Perl (maybe from 2.1?)
#10:35:52dbs grasping at straws as to why open-ils.search.peer_bibs.test 404s
#10:36:07kivilahtiohmm
#10:37:05kivilahtioI wil lmake a new install on our production test server on a clean ubuntu server, maybe that will solve such issues. Now I have few diferent versions of eg and perl and psql on my platform
#10:37:55dbsheh, process gets easier every time you reinstall :)
#10:38:16kivilahtiodbs: so true. First time I tried I failed, now I did it, and maybe next time with flying colours
#10:38:31kivilahtiobut now I can push some stress tests on the db
#10:38:50kivilahtiowe will see how your search algorithm compares to Kohas ;D
#10:39:21phasefxthe stock algorithm. It's configurable :)
#10:39:47kivilahtioyeah, so is Koha. But I think we get a nice overview with factory settings
#10:40:12kivilahtioback to python::mechanize
#10:41:10dbshmm. it looks like 2.1.0-2.1.1.sql is only in the tarball, not in rel_2_1 branch
#10:42:51rsoulliere has joined #evergreen
#10:42:53dbsIt only lives in the the tags/rel_2_1_1 branch, okay - so if we need to fix it, so that a person jumping from 2.0.11 to 2.1.2 doesn't hit a bug in the existing 2.1.0-2.1.1.sql script, that doesn't really work
#10:46:56tsbereI may have overlooked a "put upgrade scripts generated during make release elsewhere" step.
#10:47:18dbstsbere: no, we've always been inconsistent in our practices with upgrade scripts
#10:47:39tsbereI also badly named it. Future copies will be better named. ;)
#10:48:14tsbereBut yea, having no docs on what to do with it I just went with "stick it in the tags/ branch" as that was the easiest solution at the time.
#10:49:10dbs thinks it makes sense to treat version-upgrade scripts like a base part of the schema, so if you are sitting at 2.0.4, you could check out master and apply the upgrade scripts until you're current
#10:49:38dbsotherwise, right now you have to download every frickin' tarball to get the right version of the script for that particular version
#10:50:16dbsmaybe to avoid polluting the Pg directory we could create a version-upgrade subdirectory to hold all of the point-to-point upgrades?
#10:51:04tsbereI would have no complaints there
#10:51:07Dyrconagoogle++ :)
#10:51:46kivilahtionow to integrate python to Eclipse
#10:54:36dbskivilahtio: pydev ?
#10:54:41kivilahtioyup
#11:03:30berick+1 for version-upgrade dir
#11:04:12dbs will open a bug and begin the attempt to populate said dir with the canonical versions of all existing version-upgrade scripts
#11:11:39phasefxdbs++
#11:24:47rsoulliereHi all, we are getting these errors when running the MarkItemLost action trigger:
#11:26:17rsoullierehttp://paste.lisp.org/display/126038
#11:28:10berickrsoulliere: does your event_definition have a group field set?
#11:29:34rsoulliereI tried a few options there: usr, owner...
#11:29:44berickrsoulliere: you'll want to clear the group field
#11:29:54rsoulliereI then tried to leave it blank.
#11:30:28bshumDoes your trigger have the editor param?
#11:33:47rsoullierebshum: that might be the answer. editor should be the para? Is there a good value to use, or do I enter a user ID of anyone with the proper permissions?
#11:36:38tsbereI think we set ours to run as the admin user.
#11:44:24bshumSame
#11:44:29bshumWe set ours to 1 for the admin user
#11:44:40bshumTook us awhile to solve that quirk too.
#11:44:50bshumIt's "documented" in the perl mod that runs the triggers.
#11:44:56bshumBut not really well explained elsewhere.
#11:45:10bshumI think as long as the user has the permission to mark an item lost, it can do so.
#11:46:20pmpcat has joined #evergreen
#12:00:30rsoulliereThanks guys, I have made the suggested changes and it looks very promising.
#12:02:29rsoulliereIt worked! Items have been updated to status lost. Thanks!
#12:02:56tspindler has quit IRC
#12:04:51tsbere grumbles about his previous putting too many things on the same server as he prepares to move all those things....to a single server
#12:09:33tsbereHuh
#12:09:50tsbereI would love to know how this FTP server is working without a config file. <_<
#12:10:03bshumYay! Glad it worked rsoulliere!
#12:15:38dbs wonders if tsbere is running exploitmeFTPd
#12:16:16tsbere would rather not run ftpd at all, but routers have limited "upload my config file to..." options
#12:38:58bshumFor the reshelving script, it seems that we should lower the value in the .srfsh from '24h' to maybe '1h' or less if we're supposed to be reshelving faster?
#12:39:22bshumDoesn't seem to be following the entry set for reshelving interval in the library settings alone.
#12:39:36tsbereI thought that was supposed to be a default if there was no setting
#12:39:38tsbereI could be wrong
#12:40:08bshumWell, I lowered it from '24h' to '1h' and over 14k items changed statuses.
#12:40:40tsbereok
#12:44:57tsbere waits on multiple "first time" backups to finish on the new backup server....so that he can start other "first time" backups
#12:44:58dbsbshum: O:A:Storage:Publisher:action.pm says http://pastebin.com/NmFcfDid so it looks like it's getting a NULL value for the ac.circ_lib setting
#12:45:30bshumdbs: Oh... well that's weird.
#12:45:45dbserr, for the setting of that name for the circ_lib for those copies
#12:46:22tsbereAlternatively, do you have it set for every circ lib? Looks like it doesn't fall through.
#12:46:32bshumAh, it's set at CONS level
#12:46:33dbstsbere: that's where I was heading
#12:46:49tsberedbs: Apparently we both were going the same route ;)
#12:46:52bshum1 - circ.reshelving_complete.interval - "1 hours"
#12:46:53dbsdamn you and your cut to the chase :)
#12:47:12bshumSo they have to be distinct at the library levels to work? Yuck... :(
#12:47:34tsberebshum: You could always submit a patch to change that. <_<
#12:47:59dbszactly!
#12:48:32dbsAnyone from SC Lends on channel?
#12:51:37tspindler has joined #evergreen
#12:54:45DyrconaThat would be an easy patch.
#12:54:48dbs watches the IRC-to-Twitter bridge (aka bshum) in action
#12:54:53dbsbshum++
#12:54:58bshum:)
#12:55:09dbsDyrcona: yes. thought of opening it and marking it as "bitesize"
#12:55:21bshumRogan might be on vacation already but figured I'd pester him on your behalf anyways ;)
#13:10:24tsbere keeps getting tempted to do someone else's work for them
#13:10:37tsbereSo far I have resisted the temptation.........
#13:11:42bshumdbs: tsbere: I'll poke at that setting thing, good thing for me to learn more about how all that works. I'll write up an LP and attach once I get something going.
#13:12:28bshumHave to update that file on our servers anyways, it seems we're still using the old code from before the recent change.
#13:15:00Dyrconatsbere: my work?
#13:15:17tsbereScott's.
#13:15:19tsbere<_<
#13:16:07tsbereDyrcona: 90% of your work I don't *want* to touch. ;)
#13:27:00tecoripa has joined #evergreen
#13:28:50rsoulliere has quit IRC
#14:07:47phasefxDyrcona: the 008 fixer script, what are the pre-reqs for that? Would/should it work on a 2.1 system? I'm getting a funny error from OpenILS::Utils::Cronscript, "GetOptionsFromArray" is not exported by the Getopt::Long module
#14:10:55Dyrconaphasefx: It should work on a master, 2.1 or 2.0 system, since it uses nothing added to Cronscript.pm that I'm aware of, but I'll look at my code again to be sure.
#14:11:27tecoripa has left #evergreen
#14:12:01dbsCould be the version of Getopt::Long at work (ergo the version of Perl, as it's a core module)
#14:12:23dbshttp://cpan.uwinnipeg.ca/htdocs/Getopt-Long/Changes.html - don't know what 2.36 lines up to in terms of Perl versions
#14:12:42phasefxthis is perl 5.8.8
#14:13:05phasefx2.35 for Getopt
#14:13:21phasefx2.38 is what I see on cpan
#14:14:10dbsperl 5.8.8?
#14:14:12dbsjeez
#14:14:16DyrconaI have 2.38.
#14:14:20Dyrconaand perl 5.10.1
#14:14:39phasefxthis is a redhat system I think; not real familiar with it
#14:14:53dbsmust be - debian lenny comes with 5.10.0
#14:15:58DyrconaI'm pretty sure that you can update just Getopt::Long.
#14:16:21dbsanother nail in the community-support coffin for RHEL (5, at least)
#14:16:46dbswhat's the point of an enterprise stable distribution if you're manually updating half of the packages
#14:17:09DyrconaWe only support Debian, Ubuntu, Fedora, and FreeBSD. :p
#14:17:52phasefx goes and EOL's himself
#14:18:14phasefxoh, smileys :)
#14:18:38Dyrcona=-O
#14:22:01bshumDyrcona++
#14:22:44bshumWith his guidance I think I've got something to fix our reshelving wackiness. Tested and it looks good so far in test server and production side too. I'll add an LP and mock up all the changes into a working branch to pull in.
#14:23:01Dyrconabshum++
#14:23:21DyrconaWelcome to the Evergreen mutual admiration society. :)
#14:23:23moodaepobshum++
#14:24:38moodaepophasefx: Only after you've released two stable release series!
#14:25:17Dyrconamoodaepo: define "stable" :p
#14:25:42tsberemoodaepo: I think you are allowed to EOL unstable release series without releasing stable ones ;)
#14:25:53moodaepoIt's all relative man : )
#14:25:57moodaepotsbere++
#14:26:25moodaepo goes back to listening to hippy music
#14:29:17Dyrcona has released 1 stable series and may EOL before another is released. ;)
#14:33:51DyrconaThink I'll get myself some FreeBSD 9.0 installation media so I can try out berick's steps this weekend.
#14:34:10Dyrcona has a 8.0 or 8.1 disc kicking around somewhere.
#14:36:02Dyrcona"Creating an installation tape"!? Seriously....
#14:54:29tsberebshum: You may still need the btrim to remove any " from around the setting
#14:55:00bshumtsbere: Easy enough to add back I think.
#14:55:02DyrconaI thought btrim only removes spaces....
#14:55:11Dyrconaso, I told him he didn't need it.
#14:55:17Dyrconahmmm....
#14:55:55tsberebtrim takes two args. The string, and the bytes to remove from the start/end
#14:56:34tsberealthough replacing btrim with just trim may not be a bad idea either
#14:58:11bshumSo, uh
#14:58:18bshumWhich way do you suggest I go with that?
#14:59:32bshumI mean, it works without it. But I suppose we'd need them in case someone put extra quotes in the setting?
#15:00:21tsbereIs your setting valid json right now?
#15:00:31Dyrconabshum: you could add extra quotes in the setting and see what happens on your test server. that would be one way to test it.
#15:01:13Dyrconaoh that's right. these are supposed to be valid JSON.
#15:03:06tsbere stands by his "you need a trim or btrim in there" as a result ;)
#15:03:12dbs notes that bare integers are valid JSON, but if he recalls correctly the settings UI treats everything as strings, so double-quoting is assumed
#15:03:22dbs stands by tsbere
#15:05:08bshumI'll make the change then and add back the btrim that was there before.
#15:05:31bshumShould I make it a different commit or find some way of changing the one I made already and force pushing it?
#15:06:33dbsbshum: you could commit it separately, then rebase -i to squash the two commits together and then force push it
#15:06:46bshumAh, didn't realize that.
#15:07:03bshumI'll try that.
#15:07:09dbsbshum++
#15:09:24Dyrconagrrr.
#15:09:29Dyrconachromium--
#15:09:47DyrconaIt won't download the FreeBSD 9.0-RC2 ISO.
#15:10:09DyrconaIt gets to 502 of 502 MB and then says, Interrupted and erases the file.
#15:10:31Dyrcona tries wget.
#15:11:21dbswget -c ++
#15:18:59collum has quit IRC
#15:28:21Dyrconawget++
#15:28:25DyrconaDyrcona--
#15:28:29Dyrconasshfs++
#15:28:35DyrconaStupid me.
#15:28:54DyrconaPasted the wget line into a terminal where I was logged into my workstation at the office.
#15:29:04akilsdonk has quit IRC
#15:41:23gdunbar has quit IRC
#15:44:46bshumQuestion
#15:44:54bshumThere's a 2.0.12 branch for milestone in LP
#15:45:01bshumBut 2.0.11 hasn't been cut yet, right?
#15:45:08bshumOr have I missed a release somewhere
#15:46:07dbsmmm, that series milestone is my fault
#15:46:37bshumAh okay.
#15:46:53bshumNo problem, just was starting to panic that I had forgotten to build a 2.0.11 staff client...
#15:46:58dbsI had assumed that 2.0.11 would be cut when 2.1.1 was, or thereabouts
#15:47:26bshumCan you mark the 2.1.1 release as released for us actually?
#15:49:09dbsbshum: done
#15:50:04bshumdbs++ thanks!
#15:50:46bshumI've adjusted the one bug targeted at 2.0.12 back to 2.0.11 for now.
#15:54:44tsberedbs: I think eeevil wanted me to cut 2.0.11, but I don't have anything set up for the 2.0 series
#15:55:10tspindler has quit IRC
#15:56:15dbs can't wait for 2.2 to be released + 1 month to pass so all release-cutting will be automated :)
#15:56:26bshum+1
#16:00:19finnx has joined #evergreen
#16:16:19dbsbshum: mmm - what happens when multiple rows are returned for an OU setting in your branch?
#16:16:32bshumdbs: I... didn't test that.
#16:16:37bshumI suppose I could try finding out.
#16:17:01dbs thinks a quick fix, if there is a problem, which there probably will be, would be to append "LIMIT 1" to the new SELECT clause
#16:17:10bshumThere was a patch awhile back that fixed something in the function I used
#16:17:41bshumhttp://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=b1be1ab9d3f6032e76cf3b519abe21d9cc476dae
#16:17:51bshumReturn only one applicable OU setting value
#16:17:54Dyrconadbs: does that function return more than 1 row ever?
#16:17:57bshumAt least that's what the function says
#16:18:03bshum*commit
#16:19:39DyrconaWhat's the command to check if a branch has a commit? git contains?
#16:19:59tsberegit branch --contains
#16:20:12tsbereBut that doesn't always work. Especially on pre-git branch splits.
#16:20:22dbsoh yeah - now I remember discussing that behaviour with gmcharlt :)
#16:21:32dbs doesn't have that fix on his production system
#16:22:25DyrconaLooks like 2.1 has the commit, but not 2.0 or master.
#16:23:00dbs applies fix
#16:23:06DyrconaAll of my rel_2_1 branches come back when I run git branch --contains b1be1ab9d3f6032e76cf3b519abe21d9cc476dae
#16:23:29dbsno, "git show dfaa0791cbffbe4d625ace9812aa4a5d33366460" is in rel_2_0
#16:23:39tsberedbs: git show ignores branches.
#16:23:54tsbereDyrcona: I bet 2.1, 2.0, and master have different hashes
#16:24:03Dyrconayeah, most likely.
#16:24:05dbstsbere: yes, but git log Open-ILS/src/sql/Pg/020.schema.functions.sql shows that commit hash in rel_2_0
#16:24:15tsbereok
#16:24:29Dyrconaok. so panic is over.
#16:24:32Dyrcona:)
#16:24:41dbs apologizes for skipping "git checkout origin/rel_2_0; git log Open-ILS/src/sql/Pg/020.schema.functions.sql;"
#16:24:59DyrconaI should have run the log myself.
#16:25:04tsbere just goes "git log origin/rel_2_0 <file>"
#16:25:56dbstsbere is awesome
#16:26:21dbs always forgets where to put the branch
#16:26:48tsberedbs: Putting a -- before the file name (as an argument) tells git (whenever files and branches are allowed) to stop looking for possible branches and start looking for files. Thus, files always go on the end.
#16:26:51DyrconaAh, but I don't see it in master.
#16:26:54dbsbut even with my two-step approach I confirmed it faster :)
#16:27:08tsbere isn't actually looking ;)
#16:27:17dbstsbere: simple, all that I have to do is remember all of that and it's simple
#16:27:18tsbereI am fighting with a backup server :/
#16:27:33dbs will never remember that
#16:27:36tsberedbs: "branch" comes before "file" when sorting, thus branches come first ;)
#16:27:52dbs might have a chance of remembering that!
#16:29:02Dyrconaok. I find it when I look at the correct file.
#16:30:21Dyrcona needs to copy and paste more and type/command line complete less often.
#16:31:29Dyrconatsbere: mrbackup giving you problems?
#16:32:09tsbereIt appears to have stopped the aptitude update. But I started that when I had it backing up the mail server in another window, so it might just be unhappy about having both happening.
#16:34:54Dyrcona imagines the sound of disks grinding away in the background.
#16:35:24_bott_ has quit IRC
#16:36:28_bott_ has joined #evergreen
#16:51:03tsbere has just noticed that there is 49 GIG of email to back up
#16:53:10Dyrconawow. that built up in a hurry. everybody must have switched to IMAP.
#16:53:42tsbereWe only have 46 gig of file server to keep backed up. :/
#16:55:14tsbere may need to re-think the whole "turn the mail server into a VM" if only for storage space reasons
#16:56:33matt_carlson has joined #evergreen
#17:02:46dbstsbere: time to impose radical mailbox size limits so that everyone just goes and uses gmail :)
#17:03:29dbs splits
#17:03:30dbs has quit IRC
#17:05:39moodaepoSo if I create a new facet in config.metabib_field and map it in config.metabib_field_index_norm_map I presume the records need to be reingested?
#17:06:13bshumProbably
#17:06:32bshumAny time we've created a new field, we've had to reingest all our bibs to have them populate out.
#17:06:54bshumReingest + vacuum analyze, whatnot.
#17:11:05moodaepobshum: So use the magic spell to update/reingest right?
#17:11:27bshummoodaepo: http://paste.lisp.org/display/125221
#17:11:31bshumThat's what I ran last time
#17:11:37bshumYou may choose to break it up into smaller chunks though
#17:11:54bshumIf you find you have lots of records
#17:12:08bshumIt's very similar to the reingest script we ran after upgrading to 2.0
#17:12:19bshumYou could probably tailor something out of that.
#17:12:26moodaepoRight the 1.6-2.0 one
#17:15:19DyrconaIf you run it in the middle of the night, it should be no big deal.
#17:15:59bshumEspecially over Thanksgiving holiday, right? :)
#17:16:15bshumStart it in screen, leave it, go have some turkey, check it next working day.
#17:17:01bshumSpeaking of turkey, now I'm really leaving.
#17:17:05bshumHave a good one all!
#17:18:00moodaepobshum++
#17:23:07tsbereOnly a couple gig to go on the mail backup. :/
#17:29:41jenny1 has left #evergreen
#17:31:52moodaepoNotices that to run the reingest in 2.0.10a the schema needs to be added as noted during 2.1 upgrade testing - https://bugs.launchpad.net/evergreen/+bug/825881
#17:48:04Dyrcona thinks he'll disable his IRC account for the next couple of days, but leave his other chat accounts open.
#17:48:13Dyrcona has quit IRC
#18:34:37finnx has quit IRC
#18:51:12matt_carlson has quit IRC
#20:08:14fredericd has quit IRC
#20:08:19fredericd has joined #evergreen
#20:10:26bwicksall has quit IRC
#20:41:09jeff yawns
#20:46:21pmpcat has quit IRC
< Tuesday, November 22nd, 2011Raw Log FileThursday, November 24th, 2011 >