Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Wednesday, January 19th, 2011

< Tuesday, January 18th, 2011Raw Log FileThursday, January 20th, 2011 >
#TimeNickMessage
#00:01:43dbsaha, methinks authority.by_heading_and_thesaurus index is missing from upgrades
#00:01:46dbs goes to check
#00:04:25dbsnope, failed during the upgrade due to dupes - as the comments explain. right-o
#01:22:43jamesrf has joined #evergreen
#01:25:40AaronZ-PLS has quit IRC
#01:25:40Ghidorah has quit IRC
#01:25:41mrpeters-isl has quit IRC
#01:25:42berick has quit IRC
#01:25:43mtate has quit IRC
#01:25:43brendan2 has quit IRC
#01:25:44phasefx_ has quit IRC
#01:25:45senator has quit IRC
#01:25:45dbwells has quit IRC
#01:27:21senator has joined #evergreen
#01:36:43dbs has quit IRC
#01:40:05bshum has joined #evergreen
#01:40:51bshum has left #evergreen
#01:47:26lisppastedbs pasted "public.naco_normalize() in 2.0 still needs some love?" at http://paste.lisp.org/display/118783
#02:14:28jamesrf has quit IRC
#03:28:45phasefx_ has joined #evergreen
#03:28:46brendan2 has joined #evergreen
#03:28:46mtate has joined #evergreen
#03:28:46Ghidorah has joined #evergreen
#03:28:46AaronZ-PLS has joined #evergreen
#03:28:46mrpeters-isl has joined #evergreen
#03:28:46dbwells has joined #evergreen
#03:28:46berick has joined #evergreen
#07:27:16alxp has joined #evergreen
#07:30:47rickd_ has joined #evergreen
#07:32:02sfortin has joined #evergreen
#08:00:02collum has joined #evergreen
#08:37:05gmcharlt@later tell dbs interesting; I'll see how this does in trunk; probably should backport the trunk naco_normalize() work to rel_2_0
#08:37:05pinesolgmcharlt: The operation succeeded.
#08:39:46dbs has joined #evergreen
#08:42:06kmlussier has joined #evergreen
#08:55:14Dyrcona has joined #evergreen
#09:08:51Lowery has joined #evergreen
#09:09:38Meliss has joined #evergreen
#09:11:30lowery_ has joined #evergreen
#09:13:14Lowery has quit IRC
#09:16:08lowery_ has quit IRC
#09:16:46Dyrcona has quit IRC
#09:20:22Dyrcona has joined #evergreen
#09:26:51sfortin has quit IRC
#09:27:07dbseeevil: I think I've got one more fix for RC3 - a more robustified authority.normalize_heading() (it broke on some ugly authority MARCXML corner cases; switched to spi_prepare/spi_exec_query rather than going down the foolish path of trying to escape input myself)
#09:28:05dbsgmcharlt: I think I'm going to blame authority.normalize_heading() first, but I wouldn't be averse to backporting the robustified/authoritative public.naco_normalize() from trunk
#09:28:15sfortin has joined #evergreen
#09:29:03dbsJust running our ~2 million authority record test set through the robustified authority.normalize_heading() to ensure that it survives our many flawed records, first :)
#09:31:09eeevildbs++
#09:34:28dbsthe one that broke its back was the 956,943 record with <subfield code="a">Foo, Bar\</subfield> - the trailing slash of death! could have just stripped that out, but... invoking the robustified authority.normalize_heading() on that record worked nicely, so confidence is high
#09:34:39dbsI'll commit it to trunk for now
#09:35:31jenny has joined #evergreen
#09:35:43eeevilahh, yes ... was it eascaping/interpolation? (there were issues with trailing \s re call numbers before ... pain, indeed)
#09:35:52dbseeevil: yessir
#09:35:52eeevilbefore as in back in 1.2, IIRC
#09:42:14dbscalling 0476
#09:42:21dbsring, ring
#09:49:39gmcharltis the hard_due_date_name_check constraint on chdd necessary? or in particular, its dislike of spaces in the name?
#09:50:15tsbereI just copied the code from the duration/fine rules. Is it needed there?
#09:50:55tsbereI wasn't sure if there was a scripts reason for no spaces, and I believe the hard due dates are available via scripts as well as DB
#09:52:43eby has quit IRC
#09:54:09tsbere would offer gmcharlt more information, but his entire logic set on that piece has been dealt with at this point
#09:54:41tsbereOh, I think someone else did question that constraint when I submitted it, but kept it when I pointed out I had just copied from the other circ rules. Forget who
#09:55:02eby has joined #evergreen
#09:57:04dbsgmcharlt: you and your questioning of existing practices! It's so.... healthy
#09:57:20gmcharlttsbere: looking at the script code, I don't see any particular reason why allowing spaces in the rule names would break anything
#09:58:57tsberegmcharlt: I was just going for "things named in circ rules/scripts/whatever are consistent in their naming rules" when I copied the constraint from the duration rules. I figured it would be more likely to be accepted that way, question naming rules later.
#09:59:01gmcharltI could see somebody possibly coming to grief if they used diacritics in the rule names and using leagcy scripts
#09:59:25gmcharlttsbere: sure - I understanding wanting to keep it consistent
#10:00:15tsbereOne benefit of no spaces in general is "you don't get leading/trailing spaces", though.
#10:00:43tsbereTwo rules that differ in number of trailing spaces might be a problem
#10:01:23gmcharltand I don't care about the details of the constraint, per se - more that (a) AutoGrid currently doesn't pass check constraint exceptions back in any way visible to the user and (b) even if it did, it would be nicer if the validatingtextbox widget knew the appropriate regex to apply if a constraint of that form was in force
#10:01:58gmcharlttsbere: agreed re leading/trailing whitespace
#10:02:25tsbereFor the most part? I thought the constraint was silly, and mentally questioned "why is this here?" on the duration/fine rule names to begin with. I just thought of the leading/trailing whitespace now, and that is fixable with trimming.
#10:03:54tspindler has joined #evergreen
#10:05:53sfortin has quit IRC
#10:06:19sfortin has joined #evergreen
#10:06:47tsberegmcharlt: Could there be scripts out there that turn the various duration/fine rules into actual perl objects of some kind? The constraint rules seem very similar to naming rules in that regard.
#10:07:10dbsCREATE INDEX with the new authority.normalize_heading() succeeded on our 1.2 M authority records; if you guys want to take a look at r19201 before I backport it, I'll be happy to give you some time
#10:07:22gmcharlttsbere: none that I've seen, but I suppose anything is possible
#10:07:34eeevildbs: was just looking
#10:08:48lowery has joined #evergreen
#10:09:04eeevildbs: looks great to me!
#10:09:24gmcharltdbs: agreed
#10:09:25jenny has left #evergreen
#10:10:16dbsthanks, I appreciate the extra/skilled extra-skilled eyes at this stage of the 2.0 game
#10:10:29loweryhello all, i am trying to install opensrf on ubuntu and i keep getting /bin/bash: ./build: no such file or directory when i do the ./configure part. can anyone give me a hand please?
#10:10:54mrpeters-isllowery: any chance you forgot to run the prerequisites makefile?
#10:10:58gmcharltdbs: heh - and you get to pass some of blame on to us if it breaks things horribly ;)
#10:11:14mrpeters-islmake -f Open-ILS/src/extras/Makefile.install <distribution>
#10:11:22loweryremember to run the make file. had no problems with that step
#10:11:36mrpeters-islso, either ubuntu-lucid or something like that
#10:11:46mrpeters-islhmm, kind of seems like build-essentials may be missing?
#10:11:54loweryubuntu-lucid
#10:11:55tsberegmcharlt: That is another (retroactive) reason to not mess with naming constraints in my patch. Not breaking things horribly ;)
#10:12:35dbslowery: what directory are you in when you're running ./configure ?
#10:13:24dbsgmcharlt: we all hang together, right?
#10:13:27loweryi an in the opensrf directory
#10:13:49dbslowery: can you type the results of "pwd" ?
#10:14:12gmcharltdbs: beats hanging separately
#10:14:28lowerypwd = /evergreen/opensrf
#10:14:32eeevilre the no-spaces constraint, the original constraint was there because .-notation (foo.bar.baz) is easier to teach than associative array notation (foo["bar"]["baz"]) in the scripts (which were all that existed) and so it was used as a guide rail
#10:14:45gmcharlteeevil++
#10:14:54dbslowery: you have to cd into the OpenSRF source directory
#10:15:01eeeviljust to give some context
#10:15:09dbs"cd opensrf-1.6.2" or whatever
#10:15:40loweryso i would be in /evergreen/opensrf/src?
#10:15:42dbseeevil: oh right - you were teaching librarians how to write javascript!
#10:16:15eeevildbs: silly me, yes :)
#10:17:03dbslowery: your directory structure confuses me, most people would have downloaded the OpenSRF source tarball to /home/<username>/opensrf-1.6.2.tar.gz
#10:17:11tsbereeeevil: heh. At least now we know. Can we give up on that silly idea in 2.1? ;)
#10:17:29dbslowery: but you've created a new root /evergreen directory and unpacked the tarballs into that?
#10:17:30gmcharltsince the library I'm working with wanted to be able to enter things like 'Branch Foo End of Winter Term' as the hdd name, unless there's any serious objection, I'm inclined to go ahead and drop the constraint in trunk
#10:17:41mrpeters-isllowery: wherever you find the NEWS, README, etc. for OpenSRF
#10:17:55loweryi created a directory top level called /evergreen downloaded opensrf-1.6.2 and renamed it to opensrf
#10:18:03tsberegmcharlt: I would say drop the constraint from all the rules, personally.
#10:18:05eeeviltsbere: how about when we remove script support? FWIW, autogrid (well, autofieldwidget) can apply regex's if they are defined in the IDL
#10:18:10mrpeters-islso then /evergreen/opensrf
#10:18:19loweryyes
#10:18:24tsbereeeevil: When will that be removed? 3.0?
#10:18:27mrpeters-islbut usually, as dbs says, keeping the tarballs with their original names is good practice
#10:18:51eeeviltsbere: it hasn't been decided, but certainly after 2.1
#10:18:55mrpeters-islI'd highly reccomend using the /home/opensrf/OpenSRF-1-x-x-x structure
#10:19:08dbslowery: okay. maybe mrpeters-isl is right then: sudo aptitude install build-essentials
#10:19:32gmcharlt is going to punt for now and just write up a lp bug
#10:19:33mrpeters-isljust do a wget of the tarball, and tar xzf OpenSRF-1.x.x.tar.gz
#10:20:04mrpeters-isldbs: build-essentials is in the Makefile IIRC, right?
#10:20:45mrpeters-islkinda makes me worried for what other deps may be missing
#10:20:48dbslowery: the location and names shouldn't matter, really, as long as we're sure he's in the right directory
#10:20:55tsberegmcharlt: can autoblah things be shown how to convert "_" to " " and back?
#10:21:37dbsmrpeters-isl: build-essential is in the Makefile.install "DEBS" list
#10:21:51mrpeters-islyep, thought so...so we may see more problems
#10:21:58mrpeters-isl**IF** that's what's missing
#10:22:09dbslowery: can you link to the documentation you're following?
#10:22:25dbsit will help us help you along
#10:22:34loweryhttp://evergreen-ils.org/dokuwiki/doku.php?id=opensrf:1.6:install
#10:23:02mrpeters-islso you're crashing out at step 4?
#10:23:05dbslowery: okay - and what operating system are you running on?
#10:23:11mrpeters-isldbs: lucid
#10:23:42loweryyes, however just redid it in the home/user/opensrf directory and it worked. so my idea of going to a top level directory must have messed it up
#10:23:56mrpeters-isllowery: so you ran - cd /evergreen/opensrf && make -f src/extras/Makefile.install ubuntu-lucid ?
#10:24:50dbslowery: hmm - that's pretty interesting & frighteningly fragile if that problem can be reproduced
#10:24:57mrpeters-isl tries
#10:25:47mrpeters-isl10.4 = lucid right?
#10:25:54tsberedbs lowery mrpeters-isl etc: Could it be a permissions issue on his /evergreen folder?
#10:26:24mrpeters-isltsbere: that's an idea - i guess it would need to be chown'd as opensrf if he downloaded as a different user?
#10:26:25dbstsbere: anything's possible
#10:27:07tsbereWas thinking "root extracts tarball, what user(s) did it just give all the files to?"
#10:27:17mrpeters-isltrue
#10:28:08mrpeters-isllowery: if you still have the /evergreen/opensrf structure, could you do a ls -ltrh /evergreen/opensrf
#10:28:16mrpeters-islto check the ownership?
#10:28:30dbsdid anyone else see my response to Anthony Ortega?
#10:28:45dbs(on the mailing list)
#10:28:46eeevilgmcharlt: that constraint is the only thing holding back the use of spaces, and since we're looking to remove it at some point it would seem ok to me to drop it for that instance
#10:29:11mrpeters-isldbs: i did, i responded to him last week too
#10:29:13gmcharlteeevil: true - installed base for chdd users is tiny
#10:29:16mrpeters-islhe never replied
#10:29:17loweryevergreen is root:root
#10:29:28mrpeters-isllowery: i kind of bet thats the problem...it should be owned by opensrf
#10:29:44mrpeters-islif you grab the tarball as opensrf, and extract as opensrf...you don't run into the permissions issue
#10:30:24r123 has joined #evergreen
#10:30:40loweryaww, well ill tell you what the guy that made that folder and didnt changes the permission must feel like an ass for such a simple overlook.
#10:30:45dbsmrpeters-isl: I thought he did reply to you, in that he included the memcached / ejabberd info you requested, in his subsequent post
#10:30:56mrpeters-isldbs: crap, maybe i missed it then
#10:31:03dbsmrpeters-isl: thanks for letting me know I'm not crazy though :)
#10:31:08mrpeters-isli tuned out over the weekend
#10:31:31gmcharlt grabs 0477
#10:31:34dbslowery: happens to everybody sometime
#10:33:13mrpeters-isldbs: FWIW it looks like he replied to your email from last night
#10:33:44mrpeters-isloh, actually maybe not...i thought i saw that earlier but i was dreaming
#10:33:54mrpeters-islhe just reposted his initial message
#10:34:24dbsmrpeters-isl: yeah, that's why I was questioning my sanity
#10:34:39mrpeters-islill shoot him an email directly and tell him to come join us here
#10:35:37mrpeters-isli know i've had this issue before...i'm just forgetting what caused it
#10:36:24dbsSuggestion: one day, we have a "break OpenSRF / Evergreen" party, where we find creative ways to break configs, document the broken config and the resulting log messages / evidence
#10:36:48mrpeters-islonly if we keep score! i bet I'll have the most broken configs
#10:37:29dbsand then that documentation can help people find their way back to unbrokenness. For bonus points, revise the code to trap the known broken configs and throw more prescriptive error messages.
#10:37:30mrpeters-isli kind of bet OpenSRF C isn't started on Anthony's server
#10:37:41tsberemrpeters-isl: Don't forget, you have to document how they are broken, and how to fix them.
#10:37:48jeffonly if the end result of that day is a series of patches and commits that bulk up the error handling!
#10:37:54mrpeters-isltsbere: no fair! i just want to break things!
#10:38:07jeffdbs: ah, you already said that.
#10:39:30mrpeters-islwould a settings-tester.pl for OpenSRF be a possibility?
#10:39:46mrpeters-islto check things like jabber, memcache, etc?
#10:40:11mrpeters-islit's helped me catch a jabber config issue or a postgres permission issue many of times
#10:40:17dbsmrpeters-isl: yes, but better errors would be even better
#10:40:56mrpeters-isltrue
#10:41:07mrpeters-islAnthony just emailed back, he will be in here in a bit
#10:41:17mrpeters-isl thinks he gets a daily digest
#10:41:32mrpeters-islin one of his replies, it's a digest
#10:43:07jamesrf has joined #evergreen
#10:48:55dbsmrpeters-isl: that makes sense
#10:50:23gmcharlt grabs 0478
#10:53:58jamesrf has quit IRC
#10:54:24eeevillooks like we've found a potential blocker :( ... we need to get a work-ou filtered, ordered tree into some dojo data stores, and there's code that trys to do it, but falls down when work-ous are ordered in particular ways
#10:55:21eeevilso, I'm going to attack that. and berick is poking at https://bugs.launchpad.net/evergreen/+bug/699914
#10:58:30lowery has quit IRC
#11:09:30gmcharlt has finished backporting the naco_normalize() changes to rel_2_0
#11:09:42gmcharltI'd appreciate extra eyes and testing
#11:13:28berick submitted a patch that could use some independent testing for https://bugs.launchpad.net/evergreen/+bug/699914
#11:22:49Dyrconamessing with hard due dates requires permission at the consortium level?
#11:31:55dbsDyrcona: according to fm_IDL.xml, requires CREATE/UPDATE/DELETE_CIRC_DURATION + work_ou; maybe the UI or middle layer code introduces some other complications?
#11:34:57finnapz has quit IRC
#11:36:27tsberedbs: <update permission="UPDATE_CIRC_DURATION" global_required="true"/> That looks like "we don't have a table field specified for where to get a permission value from, need it everywhere" to me. Even though there is an "owner" id (that would need linking to aou, I think)
#11:37:31tsbere wonders how the permissions would have to work for chddv though
#11:38:07youdonotexist has joined #evergreen
#11:38:42eeeviltsbere: you can link through to another related table to use the aou field "over there"
#11:39:03tsbereeeevil: Good to know. No clue how yet, may look at that later.
#11:40:45tsbere found an example in the IDL
#11:41:04eeevil:)
#11:41:35tsbereccmcmt uses ccmm for permissions.
#11:42:35finnapz has joined #evergreen
#11:44:45gdunbar has joined #evergreen
#12:11:20jenny has joined #evergreen
#12:30:54tspindler has quit IRC
#12:46:24sfortin has quit IRC
#12:46:39mrpeters-islhey all, looking to submit a new triggered event to Evergreen Contrib, but seeking some help with the proper way to seed the action_trigger.event_params and action_trigger.environment rows - currently, I just have a file at.event_params that contains - http://pastie.org/1477933 - with the comment to update with the proper id matching the new event_def
#12:46:44mrpeters-islis there a better way to do this?
#12:48:35mrpeters-islif i remember correctly, i can't do both a SELECT and VALUES within the INSERT INTO, right?
#12:51:03phasefxthere's a way to use the normal sequence (which would put it out of the reserved range of id's), and then reference that same id value elsewhere. I can dig up an example once there's no food on my fingers
#12:51:14mrpeters-islhaha
#12:51:16eeevilmrpeters-isl: you can use functions, like currval to get the last value pulled from a specific sequence (the ev_def seq, in this case)
#12:51:18mrpeters-islthanks phasefx
#12:51:21tsberemrpeters-isl: "You can do SELECT 'SOMEID', 'sender_email', email FROM table" as your source
#12:51:40tsbereer, extra_quotes-- :(
#12:51:48tsbereBut you should get the idea
#12:52:06eeevilmrpeters-isl: http://www.postgresql.org/docs/current/static/functions-sequence.html
#12:52:23eeevil(what phasefx and I are talking about)
#12:52:33mrpeters-isleeevil: so that'd be accepted? i guess it makese sense since one would hope this is the only event being added at the particular time
#12:53:08eeevilmrpeters-isl: it's per-session ... it's safe
#12:53:14mrpeters-islok
#12:53:40mrpeters-islonly thing i guess i don't follow is how i can do both an INSERT VALUES and SELECT together...it's not possible right?
#12:54:00mrpeters-islmaybe someone has a simple foo/bar type example?
#12:54:31eeevilwhy would you need to?
#12:54:48tsberemrpeters-isl: Use literals in your select (see above)
#12:55:06eeevilINSERT INTO blah (a,b,c) VALUES ('literal',CURRVAL('sequence_name'),42);
#12:55:15tsbereOr that
#12:55:43mrpeters-islah ok i was thinking i need to do a direct SELECT on the id_seq
#13:01:57mrpeters-islawesome. works like a charm
#13:01:58mrpeters-islthank you guys
#13:12:43phasefxmrpeters-isl: your separate .sql files, that may cause problems with currval if you're using it one file but depending on a sequence that got incremented in another file. \i file1.sql \i file2.sql \i etc. in a single psql shell may fix that, but I'm not sure
#13:14:16mrpeters-islphasefx: you know, you kind of make a good point...it might be safer to have this all in one transaction too
#13:14:37phasefxyeah
#13:14:56phasefxlike an upgrade/ script in trunk
#13:16:14phasefxsee 0355.data.missing_pieces_format.sql, though it's not using currval
#13:17:19mrpeters-islcool. i'll submit this as a single SQL within a transaction
#13:17:46dbstsbere: going way back - duh, on my part, for failing to read alllll the way over to the "global_required" attribute
#13:20:37dbseeevil: as it's been a full 24 hours (hah), any progress on the security mailing list?
#13:22:33dbstsbere had a suggested follow-on to my early morning commits and it would be good to be able to start talking about those a little more broadly
#13:25:29lowery has joined #evergreen
#13:26:46loweryhello again, so having another problem with the install. for shits and giggles jus to make sure i had not done anything wrong i have done a reformat and gotten to this step and get the same proble. when doing the install of opensrf i get STEP 5
#13:26:46loweryepmd -kill
#13:26:46lowerykillall beam; killall beam.smp
#13:26:46loweryrm /var/lib/ejabberd/*
#13:26:46loweryecho 'ERLANG_NODE=ejabberd@localhost' >> /etc/default/ejabberd
#13:26:46loweryuser@Evergreen:/$ sudo etc/init.d/ejabberd start
#13:26:46loweryStarting Jabber Server: ejabberd
#13:26:47loweryCrash dump was written to: /var/log/ejabberd/erl_crash.dump
#13:26:47lowerykernel pid terminated (application_controller) ({application_start_failure,kerne;,{kernel,start,[normal.[]]}}})
#13:26:48lowerycrash dump was written to: /var/log/ejabberd/erl_crash.dump
#13:26:48lowerykernel pid terminated (application_controller) ({applcation_start_failure,kernel,{shutdown,kernel,start,[normal,[]]}}})
#13:26:49lowery.
#13:27:06lowerysorry for spam size of post
#13:27:59csharp notes that the pastebin link is not visible in the topic on his irssi screen...
#13:28:46csharplowery: http://paste.lisp.org/new/evergreen
#13:29:19csharplowery: what OS are you building on?
#13:29:29mrpeters-isllucid
#13:30:02csharplowery: had you modified anything ejabberd-related before receiving this?
#13:30:04mrpeters-islecho 'ERLANG_NODE=ejabberd@localhost' >> /etc/default/ejabberd is that right?
#13:30:14loweryubuntu
#13:30:23mrpeters-isli think there is a good bit more to modify in ejabberd.cfg
#13:30:27csharpnm - I see now
#13:30:28lowerydid standard install
#13:30:31lowerypostgresql install
#13:30:39loweryand then followed the walkthrough
#13:30:53mrpeters-isllowery: just to be clear, you didn't install ejabberd manually...you got it through the makefile?
#13:30:58loweryyes
#13:31:11mrpeters-islso, ps aux | grep ejabberd
#13:31:14mrpeters-islis it stopped still?
#13:31:27csharplowery: can you pastebin your /etc/ejabberd/ejabberd.cfg file (srubbed of passwords, please)?
#13:32:01csharps/srubbed/scrubbed/
#13:32:06mrpeters-islignore my comment about the "echo..." i see what you did now
#13:32:11mrpeters-islno passwords in ejabberd.cfg :)
#13:32:27loweryejabberd 31582 0.0 0.0 10760 348 ? S 11:38 0.00 /usr/lib/erlang/erts-5.7.4/bin/epmd -daemon
#13:32:37mrpeters-islhmm so it seems still to be running
#13:32:45mrpeters-isljust plain /etc/init.d/ejabberd stop doesn't work?
#13:33:03lowerycorrect
#13:33:18mrpeters-islhmm
#13:33:37mrpeters-island you tried epmd -kill, etc.
#13:34:35loweryyes
#13:34:51mrpeters-island you get the crash when you try to kill jabber?
#13:35:26loweryjust crash when i try to stop or start. no messages when i do a kill
#13:35:34mrpeters-island you're starting/stoping/killing as root, not opensrF?
#13:35:58dbslowery: were you able to start ejabberd without that ERLANG_NODE=ejabberd@localhost line?
#13:36:06loweryi do a sudo to do the stop / start
#13:36:12mrpeters-islok
#13:36:26loweryno i was not able to start ejabberd either way
#13:36:45mrpeters-islyou can ping private.localhost / public.localhost ok?
#13:37:01dbsI haven't installed on ubuntu in a long time, and haven't seen that particular ejabberd issue for a long time either. Coincidence?
#13:37:28mrpeters-isli have a lucid server here...let me give a crack at this
#13:37:41mrpeters-islwhich OpenSRF version again?
#13:37:47lowerycan ping both just fine
#13:37:56lowery1.6.2
#13:38:05mrpeters-islk let me catch up to you here
#13:38:06dbsmrpeters-isl: the problem is ejabberd at the moment, let's solve that first
#13:38:28mrpeters-isldbs: right, i have Lucid here so i was going to see if i ran into the same crash with jabber
#13:39:40dbslowery: to be clear, did you make any modifications to ejabberd's configuration, other than the ERLANG_NODE bit, before trying to start it or stop it?
#13:41:00loweryjust the addition fo the public and private localhost bit from the walkthrough
#13:41:23dbsto /etc/ejabberd/ejabberd.cfg ?
#13:41:26lowery{hosts, ["localhost"]}. to {hosts, ["localhost", "private.localhost", "public.localhost"]}.
#13:41:52mrpeters-islneed to stop jabber before changing the config perhaps?
#13:41:56dbsejabberd will crash like crazy if that file has bad syntax
#13:42:23dbslowery: you might need to do a "dpkg -purge ejabberd" to clean up the ejabberd database and remove the package, then "aptitude install ejabberd" for a clean start. I think in the past ubuntu had problems with some versions of ejabberd that were cleared up by subsequent updates; if you haven't run "sudo aptitude update; sudo aptitude safe-upgrade" now might be a good time
#13:43:13mrpeters-islhmmm starting ejabberd................failed
#13:43:30mrpeters-islduring the run of the makefile
#13:43:43lowerycan i get a cookie for making your's fail too?
#13:43:52mrpeters-isldid yours do the same?
#13:43:54mrpeters-islduring the install process?
#13:44:10mrpeters-isljust sits on "Starting jabber server" for a good minute, and then fails
#13:44:17lowerynot problems with ejabberd till this point
#13:44:27dbsalternately, perhaps the current version of the ejabberd package for Ubuntu is busted
#13:44:28csharp suspects two separate issues
#13:44:35mrpeters-islperhaps
#13:44:44dbsquite possible
#13:45:19dbsfor lowery, please purge the ejabberd package, update aptitude, and reinstall it to get to a known point
#13:45:37loweryok trying that now
#13:46:10csharp 's ejabberd on lucid is running fine
#13:46:18csharpand no updates to it
#13:46:42mrpeters-isllooks like i have 2.1.2-2
#13:47:10mrpeters-islsame failure after aptitude update/upgrade
#13:47:24csharpmrpeters-isl: that's the version I'm on
#13:47:26dbsmust be the other jabber servers that mrpeters-isl is running that's blocking his port
#13:47:36loweryafter reinstall i have 2.1.5-2
#13:47:47dbsmrpeters-isl: time to check the /var/log/ejabberd.log (or whatever)
#13:47:57mrpeters-islyeah don't worry about me
#13:48:10dbslowery: can you start ejabberd right now?
#13:49:02loweryworks now.
#13:49:08dbsyay
#13:49:39dbsso stop it, and then make the config changes to /etc/ejabberd/ejabberd.cfg - very carefully :)
#13:49:59dbsbtw - debian squeeze release is scheduled for February 5/6 - huzzah
#14:03:26rsoulliere has joined #evergreen
#14:04:08finnapz has quit IRC
#14:06:25finnapz has joined #evergreen
#14:09:15loweryable to start and stop without problems after the uninstall reinstall
#14:12:00jenny has quit IRC
#14:13:41alxp has quit IRC
#14:13:41mtate has quit IRC
#14:13:41brendan2 has quit IRC
#14:13:42phasefx_ has quit IRC
#14:13:42Ghidorah has quit IRC
#14:13:43AaronZ-PLS has quit IRC
#14:13:44youdonotexist has quit IRC
#14:13:45kmlussier has quit IRC
#14:13:46mrpeters-isl has quit IRC
#14:13:47berick has quit IRC
#14:13:48dbwells has quit IRC
#14:13:49leed has quit IRC
#14:13:49Callender has quit IRC
#14:13:50kbeswick has quit IRC
#14:13:51finnapz has quit IRC
#14:13:51Dmagick has quit IRC
#14:13:52eeevil has quit IRC
#14:13:52_bott_ has quit IRC
#14:13:52denials has quit IRC
#14:13:53csharp has quit IRC
#14:16:45pmplett has joined #evergreen
#14:16:45rsoulliereHi, I see it was said at yesterday's DEV meeting that I "requested a SIP backport"
#14:16:48rsoulliereActually, that was more of a question/enquiry.
#14:17:33collum has left #evergreen
#14:22:28rsoulliereI used launchpad to report just in case someone using 1.6 and SIP checkin might be able to see that it can be done.
#14:22:37finnapz has joined #evergreen
#14:22:37youdonotexist has joined #evergreen
#14:22:37kmlussier has joined #evergreen
#14:22:37alxp has joined #evergreen
#14:22:37berick has joined #evergreen
#14:22:37dbwells has joined #evergreen
#14:22:37mrpeters-isl has joined #evergreen
#14:22:37AaronZ-PLS has joined #evergreen
#14:22:37Ghidorah has joined #evergreen
#14:22:37tater has joined #evergreen
#14:22:37brendan2 has joined #evergreen
#14:22:37phasefx_ has joined #evergreen
#14:22:37Dmagick has joined #evergreen
#14:22:37leed has joined #evergreen
#14:22:37Callender has joined #evergreen
#14:22:37eeevil has joined #evergreen
#14:22:37kbeswick has joined #evergreen
#14:22:37_bott_ has joined #evergreen
#14:22:37csharp has joined #evergreen
#14:22:37denials has joined #evergreen
#14:22:49rsoulliereAlso, if I can be of any assistance in testing or sharing my logs let me know.
#14:33:23rsoulliere has quit IRC
#14:34:27rsoulliere has joined #evergreen
#14:34:39pmplett has quit IRC
#14:39:24lowery has quit IRC
#14:41:40pmplett has joined #evergreen
#14:42:31bshum has joined #evergreen
#14:50:56kmlussier has quit IRC
#14:57:39sfortin has joined #evergreen
#15:00:10ChanServ changes topic to "Welcome to the #Evergreen library system channel! | We are publicly logged. | Large pastes at http://paste.lisp.org/new/evergreen"
#15:12:05bshumberick: Hmm, about the patch to add back permission checking for patron registration in 2.0... I've been trying to apply it and have found that I can't seem to find the positioning for the new code pieces. Was it built against something other than RC1/2?
#15:13:24bshumSome of the surrounding code doesn't appear in those versions, so I guess I was wondering if maybe I'm doing it wrong :)
#15:15:38rsoulliere has quit IRC
#15:16:51berickbshum: built against trunk, lemme make sure it will apply cleanly. in the meantime, make sure you apply with patch -p1, since git adds an extra bit to the path
#15:17:25bshumberick: Ah, alright. Thanks :)
#15:17:33bshumI didn't know about the -p1 part
#15:17:42bshumI started out by trying to copy/paste pieces by hand
#15:17:48bshumAnd realized that things didn't quite look the same
#15:17:52berickmy bad for not posting a patch that will cleanly apply..
#15:19:43berickhmm, trunk register.js is a little different..
#15:19:55berickah, the save-on-exit stuff
#15:23:04csharpI'm still trying to make the biblios and loc z39.50 servers not appear in the MARC import interface...
#15:23:29csharpI have removed biblios and loc as sources from the GUI (verified this in the database)
#15:23:52csharpand I have commented out their config in /openils/conf/opensrf.xml
#15:24:40csharpI've also cleared my local staff client cache, but they are still showing up (along with an entry "#text" - perhaps that's a typo?)
#15:25:01csharpwhat other steps are there to this?
#15:26:15csharpI can see that the z3950.js file loops over a list of active_servers... where does that list get its values?
#15:26:21bshumcsharp: You restarted opensrf right? I think dbs mentioned a specific service
#15:26:49csharpbshum: pretty sure I did, but I'll do it again
#15:27:13moodaepocsharp: autogen (?)
#15:27:31csharpmoodaepo: hmm - does that require autogen?
#15:27:37csharpI can try that too
#15:27:54moodaepoJust throwing it out there
#15:28:04jenny has joined #evergreen
#15:28:11csharp starts by restarting opensrf
#15:31:01berickbshum: this should apply cleanly to rel_2_0 http://dev198.esilibrary.com/~berick/patches/reg_perm_2_0.patch (no -p1 needed)
#15:31:38csharpopensrf restarted, cache cleared, still visible
#15:31:43csharp tries autogen
#15:32:08berickcsharp: you removed them from the DB and opensrf.xml?
#15:32:29csharpberick: yes - removed from DB and commented them out in opensrf.xml
#15:32:46berickand restart opensrf.setting and open-ils.search (at minimum)
#15:32:56berickor just all perl services
#15:34:22csharpberick: yes and still there
#15:34:34csharp sticks fist through monitor
#15:36:27bshumcsharp: For fun thoughts, what if you deleted them entirely from opensrf.xml. Not just commenting it out.
#15:36:39csharpbshum: good thought
#15:38:47tsbere celebrates security list welcome message
#15:39:18csharpyay!
#15:39:29csharpapparently commenting out is not enough ;-)
#15:39:36bshumEvil.
#15:39:43bshumIt should have worked, oh well
#15:39:44csharp seeks tools to repair his monitor
#15:39:44tsberedbs: Which of us should start that discussion?
#15:39:53tsberecsharp: how did you comment out?
#15:40:15csharptsbere: single #'s at the beginning of each line
#15:40:40bshumcsharp: I think you need to use those silly <-- --> arrows?
#15:40:41eeevilcsharp: <!-- ... --> is XML commmenting
#15:40:42tsberecsharp: Aren't the config files XML? And thus needing XML style comments? Like <!-- commented out -->
#15:40:46bshumErm, !
#15:40:47bshumYeah
#15:41:05csharp forehead slap
#15:41:13csharpthanks all ;-)
#15:41:43alxp has quit IRC
#15:41:52csharp needs more sleep, apparently
#15:41:54DyrconaC-a C-[Space] C-e C-w is how I comment things out. :)
#15:42:07Dyrconaor C-k C-k is faster.
#15:43:11csharpDyrcona: which editor?
#15:44:05bshumberick++ # the patch applied nicely and testing so far appears quite functional. Awesome!
#15:44:27berickbshum: great, thanks for testing
#15:46:01Dyrcona*Which* editor? Why the One, True editor, Emacs.... :)
#15:46:34DyrconaOr, if you're old-fashioned, you can hit [Esc] dd
#15:46:37csharpDyrcona: I'm a vim guy ;-)
#15:46:52csharp prepares for fisticuffs
#15:48:36berickcsharp: syntax:on
#15:48:44csharpberick: ha!
#15:49:05bericker, :syntax on
#15:49:29bshumHmm, how are statistical categories ordered in 2.0? By ID rather than name?
#15:49:37bshumErm, patron statistical categories
#15:49:42bshumFrom the dropdown selection
#15:50:04Dyrconabsum: could be.
#16:00:19Meliss has quit IRC
#16:02:47brendan2 has quit IRC
#16:04:11sfortin has quit IRC
#16:06:24dbsapologies, folks, I was just out snowshoeing in the -18C weather
#16:07:30dbstsbere: if you have time to open it up, please do!
#16:07:41tsberedbs: Will do. Was already writing an email.
#16:07:46dbstsbere++
#16:18:09tsbere has sent his email, thus starting the first security list discussion
#16:31:44tsbere grumbles about greylisting
#16:32:31dbsweird, I got phasefx's reply (on one of my accounts, only), haven't seen tsbere's post yet. greylisting, heh
#16:33:27tsbereMy own fault for implementing it, although phasefx's reply was apparently "to all" not "to list" so I am getting a copy via google. Which hasn't made it through the greylister yet.
#16:35:15tsbereHuh. I haven't gotten anything from a google-based account sent to me in over a month.
#16:37:00phasefxdbs: the Finding stories one? weird, I thought I _just_ sent that less than a minute ago, but IRC says 3 minutes. spooky time travel :)
#16:37:10phasefxgmail says 1 minute ago
#16:37:42dbsphasefx: no, security
#16:37:49phasefxah, okay *8)
#16:53:34Dyrconadbs: I see that time travel phenomena quite a bit on some lists. I get replies sometimes before getting the original message.
#16:56:11bshumDo money.billing entries with a timestamp of '2011-01-19 23:59:59-05' (i.e. tonight before midnight) show up in the patron records? Or is this just a placeholder event till it actually passes?
#16:56:45bshumAlso, when should the fine_generator.pl script run at night usually?
#16:57:29jeffbshum: they show, the event is not a "placeholder", just a quirk. i'd like for it not to be a quirk, but that will be... complex.
#16:57:51jeffbshum: some people run the fines generator more frequently, if they have things like hourly fines.
#16:57:58bshumjeff: Right, that makes sense.
#16:58:15bshumjeff: I guess I'm wondering if this is where the communication is breaking down between us and front-line staff.
#16:58:49jeffif you run it after close and it completes before midnight, i think it might stop generating those "future" billings.
#16:59:18jeffthat might be the simplest fix for the "quirk" that annoys me so. :)
#16:59:34jeffi don't know the internals well enough at this point.
#16:59:54jeffi know it changed from 1.4 to 1.6 to accomodate hourly fines, etc.
#17:00:14jeffthat's when the due time of 23:59 came into existance also.
#17:00:18dbwellsjeff: but wouldn't that effectively change the amount being fined?
#17:00:24bshumjeff: I'm trying to figure out exactly what's happening, because now I'm not sure whether we're seeing "extra" fines that shouldn't be there. Vs. fines that haven't happened yet. Vs. fines that aren't being reported right.
#17:01:14jeffdbwells: it could, and that may or may not be "fixed" at checkin... see my disclaimer about not knowing the internals well enough yet :)
#17:02:32dbwellsjeff: fair enough. Then I guess I will also chime in to say that fines for 11:59 of the current day are 'normal' for us, too.
#17:02:47jeffbshum: been there, it was Really Fun for circs that had fines that spanned 1.4 and 1.6 ;-)
#17:03:08jeffthose I can guarantee got at least one day's worth of "extra" fines.
#17:03:14jeff(for our system, at least)
#17:03:21bshumjeff: Well I'm just trying to make sure that it's not our perception of fines or if there really are extra days.
#17:03:30bshumThis all relates to the bug I filed about backdating and voiding of fines.
#17:03:42bshumBecause if that extra day really exists, then maybe it's not a real bug
#17:03:47bshumBut our mistaken perception of it.
#17:04:08bshumAnd if it does exist, then we need to try getting rid of it, because it's really wigging people out
#17:04:15bshumThe extra day I mean
#17:04:27bshumThat's an interesting though about running fines before midnight though
#17:04:28jeffthis assumes that none of the circulations in question are "leap circs". due to gravitational forces related to large library collections, every 1048576th circulation is a "leap circ"...
#17:04:32jeff stops
#17:04:43dbwells:D
#17:04:54bshumGahh.........
#17:05:55bshumIf the fine generator only runs once a day, and finishes its run before midnight, then these current day entries would probably not generate till it runs later in the evening.
#17:06:21Dyrconatime and written language: two things that computers (and people) have a hard time with.
#17:06:28bshumSigh
#17:06:34bshumJust can't win.
#17:07:04Dyrconabshum: add a few minutes to the dates and see what happens. You can play with this in a test server, right?
#17:07:35bshumDyrcona: Sort of, yeah
#17:07:40AaronZ-PLS has quit IRC
#17:13:14mjg_ has joined #evergreen
#17:17:55tsbere wonders if this email from denials caught in the greylister was supposed to go to the security list too
#17:20:58dbwellsbshum: not sure if this is still true concerning newer releases, but in 1.6, you can think of the the overdue timestamp as "this overdue charge covers until x"
#17:21:51dbwellsthat is, if the bill is dated 1/19/2011 at midnight, the fine generator won't generate another fine until that time has passed.
#17:22:01dbstsbere: I replied all to yours, and failed on Dyrcona's
#17:22:13berickbshum: think it's safe for me to push that user registration perm patch?
#17:22:26dbwellsbshum: by overdue timestamp, I mean the timestamp on the overdue billing.
#17:22:50bshumberick: I think so. Seemed to work well on our test server with several different custom group permissions.
#17:23:17bshumdbwells: Right, I think I get that. That's what the money.billing_ts is for an "Overdue Materials" entry.
#17:23:23berickbshum++ great, thanks again
#17:23:43bshumdbwells: But that seems to me that we have an extra entry when there really shouldn't be one.
#17:24:20bshumdbwells: Because that entry that's there, means we won't generate a new fine, sure. But that still counts towards the total billed/owed by the patron
#17:24:34bshumEven if they were to return the item today before closing time
#17:24:40bshumThe entry seems to stick
#17:25:45tsberedbs: I don't see anything from you on the list yet? Not according to archives, anyway.
#17:25:58phasefxhrmm, I'm on trunk, and I see this log line from open-ils.actor, editor[!|1] checking perms user=1, org=4, perm=VIEW_CIRCULATIONS, but then immediately after get an error from open-ils.storage.permission.user_has_perm, where it's trying to pass an empty string instead of an integer, SELECT permission.user_has_perm('1','VIEW_CIRCULATIONS','');
#17:26:08dbstsbere: "awaiting moderator approval" is what I got back
#17:26:52tsbere wonders why
#17:27:40dbwellsbshum: In my experience, if an item is due on 1/18 (at 11:59pm), when the generator runs anytime after that it will create a billing dated 1/19 at 11:59pm. That essentially means bill for today (1/19) and don't bill again until after this billing date (1/19 at 11:59pm)
#17:28:06dbwellsis this different that what you are seeing?
#17:28:42dbwellsSo the bill is not for the future, but it 'covers' the future.
#17:28:51bshumdbwells: No, you're right. I just need to count from the initial date forwards properly.
#17:29:32dbwellsbshum: but I think you are then correct that the backdate is one day too generous.
#17:30:21finnapz has quit IRC
#17:30:21Dmagick has quit IRC
#17:30:22eeevil has quit IRC
#17:30:22_bott_ has quit IRC
#17:30:22denials has quit IRC
#17:30:23csharp has quit IRC
#17:30:53bshumdbwells: Tell me if this makes any sense
#17:30:54bshumdbwells: An item that was due on 1/12 isn't returned till today
#17:30:55bshumThere's entries showing for 1/13, 1/14, 1/15, 1/18, and 1/19
#17:31:05bshumSo that's 5 days of fines
#17:31:11bshumEven though the patron returned the item today
#17:31:15Dyrcona has quit IRC
#17:31:17bshumThey still get charged for the 1/19 entry
#17:32:12dbwellsYes, that is what I would expect, unless you have a grace period. The simplest example is one day overdue.
#17:32:25bshumHmm
#17:32:33dbwellsif its due on the 12th, they bring it back the 13th, they are charged for the 13th.
#17:32:45bshumYeah, you're right.
#17:34:00finnapz has joined #evergreen
#17:34:00Dmagick has joined #evergreen
#17:34:00eeevil has joined #evergreen
#17:34:00_bott_ has joined #evergreen
#17:34:00denials has joined #evergreen
#17:34:00csharp has joined #evergreen
#17:34:04bshumThat makes sense.
#17:34:04bshumOkay, I think I'm back on the ball now. Kind of.
#17:34:17bshumYep, I think I finally get it. Thanks dbwells.
#17:34:38bshumThat really helps to put things back into perspective. Been running myself in circles trying to think it through.
#17:35:24dbwellsThe quirkiest part really is the use of future dates on the billings (for me at least), but it allows really simple code like 'next if ($last_fine > $now);'
#17:35:56bshumIndeed, I think that's where some folks have gotten so confused.
#17:36:09bshumMyself included, apparently
#17:36:15dbstsbere: maybe it's filtering my denials@gmail.com mail
#17:36:17dbwellsnot much more work to adjust by fine_interval, but I'm not sure how many places would need adjusting.
#17:40:53eeevilsec mailing list needs some adjustment (private archive, etc) ... then members won't be moderated. sorry for the delay
#17:42:19eeevilso, tonight or tomorrow morning for completion
#17:45:57mjg_ has left #evergreen
#17:51:51jenny has left #evergreen
#17:54:47pmplett has quit IRC
#17:57:42tsbereeeevil: The archive defaults to private. I checked that they were before starting stuff on it. And I wasn't moderated, so I dunno.
#18:39:24dbs has quit IRC
#19:20:40youdonotexist has quit IRC
#19:48:31eeeviltsbere: I'm not personally addressing the mailing list config, thus "tonight or tomorrow", but it looks like "tonight" was it in any case :)
#19:49:23dave-esi is now known as dave-esi-away
#21:08:26jeff grins
#22:21:37bshum has quit IRC
#23:57:46moodaepo has quit IRC
< Tuesday, January 18th, 2011Raw Log FileThursday, January 20th, 2011 >