Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Thursday, October 7th, 2010

< Wednesday, October 6th, 2010Raw Log FileFriday, October 8th, 2010 >
#TimeNickMessage
#00:17:57StephenGWills has quit IRC
#00:30:08pmplett has quit IRC
#00:46:50StephenGWills has joined #evergreen
#01:11:49pmplett has joined #evergreen
#01:39:35pmplett has quit IRC
#02:02:40mrpeters-isl has quit IRC
#02:25:37pmplett has joined #evergreen
#02:59:22phasebb has quit IRC
#03:08:14pmplett has quit IRC
#03:35:55atz has joined #evergreen
#03:39:02atz_ has quit IRC
#04:16:46zigo-_- has quit IRC
#05:02:18pmplett has joined #evergreen
#08:07:08dbs has quit IRC
#08:32:57Melissa has joined #evergreen
#08:36:24mrpeters-isl has joined #evergreen
#08:38:50mck9 has left #evergreen
#08:38:58mck9 has joined #evergreen
#08:54:24dbs has joined #evergreen
#08:54:24dbs has joined #evergreen
#08:58:46Dyrcona has joined #evergreen
#09:09:29mrpeters-islmorning everyone. is anyone out there doing any sort of database replication for a seperate reports database? i had some high hopes that i could use the hot standby feature in postgres until i found out its not supported until version 9.0! :(
#09:10:16gmcharltseveral EG sites use slony for that purpose
#09:11:46mrpeters-islok. we're having a LOT of downtime lately due to reports that seem to turn into never ending SELECT's and really would like to get a seperate reports only server up to avoid this
#09:12:38mrpeters-isli was looking at pgpool II with master/slave replication but Slony looks interesting too
#09:14:28dbsgmcharlt: slony seems to be the standard evergreen option
#09:14:36dbss/gmcharlt/mrpeters-isl/
#09:14:40dbstoo tired, sorry
#09:14:47mrpeters-islok!
#09:14:48mrpeters-islthanks guys
#09:15:17gmcharltdbs: wow! news! ;)
#09:16:23dbsgmcharlt: yeah, I'm a total broken record. sorry (again)
#09:16:31dbscongrats on the 3.2.0 release candidate, btw
#09:16:34gmcharltthanks
#09:18:09dbs peeks at http://ask.debian.net/ - built on shapado - maybe something to put into the web/communication committee's hopper to chew on?
#09:22:44gmcharltheh - I see that a question from somebody trying to install Koha is on the top of the list
#09:23:49gmcharltdbs: the interface looks interesting; I think the trick is getting enough people actively answering questions
#09:24:59dbsgmcharlt: yes, actively + usefully
#09:25:37gmcharltdarn, I can't just write a script to supply '42' in response to every question?
#09:26:11dbsAlthough responses like "I have no clue, that interface is really confusing and I don't see any docs for it anywhere" could be interpreted as useful in a broader sense, I suppose
#09:28:07jeffmoof.
#09:30:03Melissa has left #evergreen
#09:30:17jeffwow that shapado site looks quite a bit like stackexchange.
#09:30:21jeffaha: http://blog.ricodigo.com/2009/9/27/shapado-a-foss-replacement-for-stackoverflow/shapado
#09:30:29eeevilmrpeters-isl: re replication, yes, don't use pgpool's replication, it's not smart enough, but you can use it all day long for load balancing
#09:31:03gmcharltand even during nights, too! *rimshot(*
#09:31:30eeevil:)
#09:31:47kmlussier has joined #evergreen
#09:31:51jeff(two drums and a cymbal fall off a cliff...)
#09:32:14dbsjeff: yes, I imagine that's the point. stackexchange-ish but with code and data under the control of the community
#09:32:57jeffdbs: one of the comments on that blog post was somewhat critical, calling it "free-as-in-autocracy". i was amused. :)
#09:33:23jeff(though i'm not sure it's accurate)
#09:34:10dbsjeff: I'm just throwing out another option, in the past we've been criticized as not being approachable because we don't have web forums, this seems like a possible option for a middle way
#09:34:38jeffthe stackexchange model does have a lot going for it over web forums.
#09:35:11dbsOr we could just put it all of Facebook.
#09:35:18jeff:P
#09:35:44jefffwiw, there's another library community using the stackexchange framework here: http://answers.unshelved.com/
#09:36:05jeffthat is stackexchange incubated through their area51 site, not shapado.
#09:37:02jefflike apache's incubator, there are stages... they're in "bootstrap" mode. shapado would probably be the better option for evergreen at this point.
#09:43:47dbsheh. never good to get high load alerts from servers you've almost completely forgotten about.
#09:43:59jeffstarved for attention.
#09:44:59tsberedbs: A few days ago I got a high load alert for a server I haven't logged into for years
#09:48:23tsbere wants to know why his email address is still in that server, given that he hasn't had login access to it for years
#09:49:37collum has joined #evergreen
#09:51:29dbstsbere: you're its last hope, obi-wan tsbere
#09:51:58tsberedbs: I don't have login access due to a desire to shut it off. For good. :P
#10:11:57tsbere starts work on circ matchpoint docs
#10:12:33dbstsbere++
#10:20:00dbs@later tell bshum thanks for your questions about the draft rules of governance; I was beginning to wonder if anyone had even read them
#10:20:00pinesoldbs: The operation succeeded.
#10:28:09jeffdocs++
#10:28:12jefftsbere++
#10:50:28mrpeters-isl has quit IRC
#11:01:46atzMEMEBERSHIP => Meme-bership? or Me Me bership? # All about me.
#11:02:44dbsatz++
#11:07:54Melissa has joined #evergreen
#11:07:57eeevilwho do I petition for a membership nomination? ;)
#11:13:02Dyrconaeeevil: I asked this question yesterday and on Friday, but I don't think you noticed, so I'll ask again.
#11:13:27Dyrconaeeevil: Is r18151 going to be backported from trunk to rel_2_0?
#11:13:41DyrconaIt was, apparently, backported to rel_1_6.
#11:14:38eeevilDyrcona: no, it will not
#11:14:58eeevilbecause it's a significant new feature and schema change it will be 2.1 and 1.6.2
#11:15:13Dyrconaok. thanks.
#11:15:48DyrconaIt looks like something I'd want to use. :)
#11:18:44eeevilDyrcona: and you'll be able to ;)
#11:21:21moodaepo has quit IRC
#11:21:21youdonotexist has joined #evergreen
#11:33:56youdonotexist_ has joined #evergreen
#11:35:07youdonotexist has quit IRC
#11:38:38youdonotexist_ has quit IRC
#12:03:07brendan2 has joined #evergreen
#12:10:47parsr has joined #evergreen
#12:10:56r123 has joined #evergreen
#12:14:46b_bonner has joined #evergreen
#12:16:25mrpeters-isl has joined #evergreen
#12:17:16parsrupgraded a test system from Ubu 8.04 to 10.04; but it knocked out my pgl install; now have PG 8.4 installed, started, then stopped to update *.conf files to match our system including custom db data directory; now restart of Mr Postgres gives me two errors: mydirectory/xx is "not a valid data directory" and mydirectory/PG_VERSION is missing. Tips for the newbie errors?
#12:19:47jeffparsr: could be a mess. here's a few thigns to check...
#12:19:59jeffparsr: do you now have two installs of postgres?
#12:20:32jeffparsr: you can't just copy an 8.3 data directory and use it with 8.4 without upgrading it -- but since postgres can't even find your data dir, we're not there yet.
#12:21:02jeffparsr: sounds like you've pointed postgres at a directory that either doesn't exist or doesn't contain PG_VERSION, which it expects to find. double-check your config changes?
#12:21:51jamesrf has joined #evergreen
#12:22:23jeffparsr: the value for data_directory should point to a directory (mine does not have a trailing slash) such as the default /var/lib/postgresql/8.3/main (for 8.3 on ubuntu hardy)
#12:22:59parsrjeff: correct -- just 8.4 install; not copying any EG data from previous versions; working to start EG database from scratch
#12:23:05jeffparsr: that dir needs to have proper permissions also, in my case owner:group postgres:postgres and perms 0700
#12:23:17pmplett has quit IRC
#12:23:39jeffparsr: aha. then in that case you'll need to create the data directory -- you can either move the contents of the system-installed directory, or...
#12:24:20pmplett has joined #evergreen
#12:24:31jeffparsr: see here for directions on creating a new cluster in your preferred location on disk: http://www.postgresql.org/docs/8.4/interactive/creating-cluster.html
#12:26:05jeffparsr: there may be gotchas on charset/locale with calling initdb in this way -- you may want to copy/move the system installed default, or consult your previous install's charset/locale -- it may or may not have any impact when you create/restore your eg db.
#12:27:55parsrjeff: thanks -- will try both your suggestions ; data directory previous created with good perms for postgres user so copy or initdb should work. will try after munch time..Thx!
#12:35:57b_bonner_phone has joined #evergreen
#12:40:34b_bonner has left #evergreen
#12:58:49parsr has quit IRC
#13:17:04moodaepo has joined #evergreen
#13:18:42bshum has joined #evergreen
#13:23:19eby has quit IRC
#13:23:25brian_f has joined #evergreen
#13:35:09b_bonner_phone has quit IRC
#13:39:27b_bonner_phone has joined #evergreen
#13:42:39brian_f has quit IRC
#13:49:33brian_f has joined #evergreen
#13:53:20b_bonner_phone has quit IRC
#13:56:04Dyrcona has quit IRC
#14:00:04parsr has joined #evergreen
#14:06:13parsrjeff: your initdb suggestion worked, then I ran into "server.crt: No such file or directory" error which in turn could be solved by either running these openssl steps: http://tinyurl.com/3464h4b ; or in my case creating links for server.crt and server.key to /etc/ssl/certs/ssl-cert-snakeoil.pem and /etc/ssl/private/ssl-cert-snakeoil.key respectively. Back up now. Thanks for the tips!
#14:08:00dbsparsr: your domain looks a little fishy
#14:08:13dbs"haddock.kyleandjessica.com" eh?
#14:11:08parsrdbs: yes, the things we have to do to access IRC from my employer's network! Note to employer: please open port for me and it's ok to log/review my posts (yes, I'm trying to work here!)
#14:11:29dbsparsr++
#14:11:42mrpeters-islto those using slony: i've got the two servers talking to each other, but need some information on what tables need to be replicated
#14:14:49eeevilmrpeters-isl: all of them? there's a script in support-scripts IIRC that will give you a list of tables and sequences that need to be added to the replication set
#14:16:11mrpeters-isleeevil: ok. I had assumed it would be all of them, but just checking. thanks for the clue I'll look there
#14:17:45eeeviljust not the tables in the replication setup schema ... that would be bad
#14:18:00mrpeters-isli'm not eeing anything obvious in there....do you have any idea which script it might be?
#14:18:08mrpeters-isllooking in the 1.6.0.0 source tree
#14:19:13eeevilOpen-ILS/examples/build-eg-replication.sh in the trunk tree I'm looking at
#14:19:45bshumatz++ user group wishlist, ha :)
#14:20:06mrpeters-isleeevil: ok ill have a look
#14:29:45mrpeters-isleeevil: "NUMNODES" = server + # hosts or just # of hosts
#14:30:21eeevilI don't recall
#14:30:40mrpeters-islok
#14:31:07moodaepodbs++ atz++ gmcharlt++ bshum++ # governance discussion
#14:43:15bshumgmcharlt: Hmm, have you had a chance to poke at pushing that fix you alluded to for the 1.6.0.x upgrades?
#14:43:32gmcharltbshum: not yet, should have a moment later today
#14:43:58bshumgmcharlt: Cool deal. Will keep my eyes open and test it out. Thanks!
#14:44:45mrpeters-isleeevil: do you happen to know what verison of Postgres this was written for? I'm getting some "No function matches" errors
#14:45:28mrpeters-islERROR: function array_accum(text) does not exist as well
#14:47:21dbsmrpeters-isl: did you just use a blank database?
#14:47:32eeevilmrpeters-isl: that's created by 002.functions.aggregate.sql ... perhaps you need to point it at your evergreen db
#14:48:00mrpeters-isldbs: no, i'm using the evergreen db, though, i don't ever recall applying 002.functions... after restoring it from a snapshot
#14:48:20dbssounds like the restore might have gone poorly
#14:48:24eeevilmrpeters-isl: you don't have to after restoring from a snapshot
#14:48:35mrpeters-islok then something else is wrong
#14:48:37eeevilif, by snapshot, you mean a backup
#14:48:43mrpeters-islyeah, a backup
#14:49:24mrpeters-islok...i see my problem here
#14:49:36mrpeters-islpostgres user is looking at the wrong cluster
#14:54:42dbseeevil++ # pinpointing the problem immediately
#14:58:47mrpeters-islFWIW: passing "-d evergreen" into the embedded query you have in the script helped...not sure if thats just my setup or that's how it should read
#14:59:28eeevilmrpeters-isl: PGDATABASE=evergreen on the command line should be enough
#14:59:50mrpeters-islok, i had set that in my .bashrc so perhaps i had a typo
#15:03:06eeevilif it's su'ing with a - or something, that won't work, obviously
#15:03:30mrpeters-isleeevil: thanks for taking the time to create this script...its quite helpful
#15:08:18eeevilnp ... no promises that it delivers 100% coverage. it's meant to be a starting point and an example
#15:08:51mrpeters-isljust experimenting righ tnwo
#15:11:48LBA1 sneaking away
#15:18:24mrpeters-isl has quit IRC
#15:18:32mrpeters-isl has joined #evergreen
#15:28:50Melissa1 has joined #evergreen
#15:29:18Melissa has quit IRC
#15:34:35Melissa has joined #evergreen
#15:36:23Melissa1 has quit IRC
#15:42:01finnapz has quit IRC
#15:42:10parsr has quit IRC
#15:42:32finnapz has joined #evergreen
#15:43:19finnapz has quit IRC
#15:43:42finnapz has joined #evergreen
#15:47:40collum has left #evergreen
#15:47:55JMCraig has joined #evergreen
#15:54:16artunit_ has joined #evergreen
#15:58:08agJohn has quit IRC
#16:00:55jhaig has joined #evergreen
#16:01:19kmlussier_ has joined #evergreen
#16:01:39_bott_1 has joined #evergreen
#16:02:51kmlussier_ has quit IRC
#16:03:43jhaigI'm just listening to the podcast on Floss Weekly from a few weeks ago. I had a look at koha some time ago and found it way, way too complicated. Is evergreen simpler? (Ie, usable by someone who is not already an expert librarian)
#16:06:04csharp_GPLS has joined #evergreen
#16:06:40kmlussier has quit IRC
#16:06:41lisppaste has quit IRC
#16:06:41csharp has quit IRC
#16:07:10r123 has quit IRC
#16:08:08jhaigHmmm, koha has just been mentioned. :-)
#16:08:14artunit has quit IRC
#16:08:14_bott_ has quit IRC
#16:13:47dbsjhaig: there are some people on IRC like atz and gmcharlt who can do a much better comparison of koha vs. evergreen than I can. It's probably safe to say, though, that evergreen is as complicated, if not more complicated, than koha.
#16:14:13dbsIt's the nature of libraries to demand that their systems be complicated, I think.
#16:14:27atzEG is certainly more complicated that koha. but the main difference besides architecture is UNIMARC support.
#16:14:55gmcharltjhaig: dbs has it; both Koha and EG are systems used by professional librarians, however you wish to define the term
#16:15:00jhaigOK, thanks. Since starting to look at library software I've come to realise that it is all a whole lot more complicated than I realised.
#16:15:30jhaigI think I'm just going to have to learn it properly. :-)
#16:15:48gmcharltdepending on your needs, there are other open source options that might be more suitable for managing a personal collection or one one with a small active patron population
#16:16:10dbsHeh. It all seems deceptively simple on the surface - then five years later you're realizing that your system doesn't index the 247 field as a title entry. ZOMG! :)
#16:16:52atzalso commercial software like delicious monster that more about ease of use for the individual
#16:17:00atz*that is more about...*
#16:17:16jamesrf has quit IRC
#16:17:53bshum has quit IRC
#16:18:33phasefx wants to make EG easier for personal libraries. it's a side project (I keep getting more and more books:)
#16:19:12gmcharltdog_fooding++
#16:19:32phasefxgmcharlt: have you seen the "self-check" in my office? :)
#16:19:52gmcharltheh
#16:20:02gmcharltactually, I don't think I have
#16:20:12phasefx(it's a clipboard)
#16:20:17dbsUntil dbwells cuts the gordian knot between call numbers and bib records, I don't know how to catalogue the various ebooks on my phone.
#16:25:50granitize has quit IRC
#16:26:28granitize has joined #evergreen
#16:28:26dbs has quit IRC
#16:31:20brian_f has quit IRC
#16:33:35brian_f has joined #evergreen
#16:43:39tildeequals has quit IRC
#16:45:15tildeequals has joined #evergreen
#16:48:03Melissa has quit IRC
#17:22:51pmplett has quit IRC
#17:23:47jhaig has quit IRC
#17:31:02brian_f has left #evergreen
#17:34:57jamesrf has joined #evergreen
#17:35:14jamesrf_ has joined #evergreen
#17:36:00jamesrf_ has left #evergreen
#19:06:26LBA has joined #evergreen
#19:07:18LBA1 has quit IRC
#19:12:26pmplett has joined #evergreen
#20:56:09chrissharp123 has joined #evergreen
#21:36:02jamesrf has quit IRC
#21:54:08pmplett has quit IRC
#21:58:30jamesrf has joined #evergreen
#22:36:27atz_ has joined #evergreen
#22:40:23atz has quit IRC
#23:15:51chrissharp123 has quit IRC
#23:18:26StephenGWills has quit IRC
#23:33:37jamesrf has quit IRC
#23:34:58jeffdbs++ # fixing internal dummy warnings
< Wednesday, October 6th, 2010Raw Log FileFriday, October 8th, 2010 >