| Time |
Nick |
Message |
| 00:14 |
atlas__ |
nope, just only showing increments of 10,000 now so doesn't change often |
| 00:14 |
atlas__ |
had to check on it running top.. |
| 00:15 |
atlas__ |
two postgres processes taking up 60% of the limited CPU i gave that VM |
| 00:15 |
atlas__ |
damn |
| 00:16 |
atlas__ |
i should provision a total overkill VM for this. too bad I've got more iron at home than at work for this... |
| 00:16 |
atlas__ |
hmm |
| 00:52 |
|
ankita joined #evergreen |
| 00:56 |
|
atlas__ joined #evergreen |
| 02:00 |
|
mnsri joined #evergreen |
| 02:58 |
|
mnsri joined #evergreen |
| 03:03 |
|
mnsri joined #evergreen |
| 03:07 |
|
mnsri joined #evergreen |
| 04:27 |
|
mnsri joined #evergreen |
| 05:40 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 06:38 |
|
mtate joined #evergreen |
| 06:38 |
|
eeevil joined #evergreen |
| 06:39 |
|
Callender joined #evergreen |
| 06:39 |
|
phasefx joined #evergreen |
| 06:40 |
|
graced joined #evergreen |
| 07:59 |
|
Stompro joined #evergreen |
| 09:07 |
|
gsams joined #evergreen |
| 10:16 |
|
ankita joined #evergreen |
| 10:25 |
|
sarabee joined #evergreen |
| 10:59 |
|
Dyrcona joined #evergreen |
| 11:02 |
|
ankita left #evergreen |
| 13:05 |
|
atlas__ joined #evergreen |
| 13:06 |
atlas__ |
any ideas on building a 2.7.0 staff client for mac |
| 13:07 |
Dyrcona |
atlas__: My recommendation is don't. |
| 13:07 |
Dyrcona |
There have been issues. |
| 13:09 |
atlas__ |
alright, i've got it in a windows VM, guess if I wanted to be cooler I could the 64 bit linux client for 2.7.0 works well I presume? |
| 13:09 |
atlas__ |
*use the |
| 13:10 |
Dyrcona |
There are suggestions on this page: http://evergreen-ils.org/dokuwiki/doku.php?id=mozilla-devel:building_the_staff_client |
| 13:10 |
Dyrcona |
Yep. I use the Linux staff client all the time. |
| 13:10 |
atlas__ |
kind of wanted an excuse for a small linux dev laptop anyways |
| 13:12 |
atlas__ |
what OS are most of the devs working off of? |
| 13:12 |
Dyrcona |
Windows, probably. I use Linux. |
| 13:13 |
Dyrcona |
I thought there were more bugs on Launchpad about using the staff client on Mac OS X, but I'm not finding them. |
| 13:13 |
Dyrcona |
Launchpad search is pretty bad. |
| 13:14 |
atlas__ |
sounds like a lot of dev is going into the web client anyways |
| 13:14 |
Dyrcona |
Anyway, IIRC, bshum had trouble with it on "Mavericks," is that OS X 10.9. |
| 13:14 |
Dyrcona |
Well, yeah, that is the focus. |
| 13:14 |
atlas__ |
looking good so far |
| 13:14 |
atlas__ |
I managed to get it running...sans documentation |
| 13:15 |
bshum |
Dyrcona: atlas__: for mac client building, there are "steps" on general approaches to building it. |
| 13:16 |
bshum |
I think off the downloads page to wiki pages. |
| 13:16 |
Dyrcona |
Yep. I shared the link to one. |
| 13:16 |
bshum |
There's some GUI glitches |
| 13:16 |
bshum |
For some row rendering |
| 13:16 |
Dyrcona |
Yep, that, too, and some worse than others depending on how you run it. |
| 13:16 |
bshum |
I never filed them cause mac isn't really a supported client os |
| 13:17 |
bshum |
And I didn't have tuits for xul debugging. |
| 13:17 |
Dyrcona |
IIRC, when running via xulrunner on the command line, you can't type into any text boxes. It all shows up in the terminal. |
| 13:17 |
atlas__ |
ahaha |
| 13:17 |
Dyrcona |
You can also use --install-app and that mostly seemed to work on 10.5, but I haven't tried it since. |
| 13:17 |
* bshum |
keeps walking down Chinatown. |
| 13:18 |
atlas__ |
I don't have a real good reason for wanting to build the mac client, our office we're all on macbook airs/pros so it would be fun but totally not necessary since all staff would be on windows anyway and we should run it in a windows VM |
| 13:18 |
atlas__ |
I've just got this underpowered macbook air and hate having to keep a windows VM running if at all possible |
| 13:19 |
atlas__ |
should probably just hassle my boss to get me a pro |
| 13:32 |
|
atlas__ joined #evergreen |
| 13:57 |
atlas__ |
any docs for this for 2.7? http://docs.evergreen-ils.org/2.1/html/emptydatabase.html |
| 13:57 |
atlas__ |
or is it the same?? |
| 14:00 |
atlas__ |
rerun the schema creation script here maybe ? http://docs.evergreen-ils.org/2.7/_creating_the_evergreen_database.html |
| 14:01 |
bshum |
Yeah rerunning that script will blow away and start over a system. |
| 14:01 |
bshum |
But don't do it unless you mean it. :P |
| 14:01 |
atlas__ |
I half ass loaded some gutenberg records for funsies |
| 14:01 |
atlas__ |
but I've got a very recent full marc export of our entire db |
| 14:02 |
atlas__ |
just sitting at work so I'm going to blow it away and try to load that on monday |
| 14:02 |
atlas__ |
I don't have a lot of resources to provision to this machine though...so...it might take a while to do the 1.3m records |
| 14:03 |
Dyrcona |
Yeah, it might. |
| 14:03 |
atlas__ |
what does a large evergreen deployment look like |
| 14:03 |
Dyrcona |
If you can search the IRC logs, you find some discussions from the past few years of things you can do speed up a large load of MARC records. |
| 14:03 |
atlas__ |
will do |
| 14:04 |
Dyrcona |
large? Dunno. C/W MARS has about 3 million bibliographic records. |
| 14:04 |
atlas__ |
looking for info on load balancing/multiple app servers/hardware spec |
| 14:04 |
atlas__ |
say 320 libraries |
| 14:05 |
Dyrcona |
Ah. |
| 14:05 |
atlas__ |
yeah that's twice the size of our collection |
| 14:05 |
Dyrcona |
Not sure what you'd want for that. You'll be want to hear from csharp at PINES. |
| 14:06 |
Dyrcona |
I was going to say at MVLC, where I am, we have just under 1 million bibs. |
| 14:06 |
Dyrcona |
With 36 members at about 40 sites. |
| 14:06 |
atlas__ |
we've got..1.3m bibs, 320 sites, 11 members |
| 14:07 |
atlas__ |
it's an interesting system |
| 14:07 |
Dyrcona |
You'll definitely want multiple bricks, but I can't begin to say how many. |
| 14:07 |
atlas__ |
when you say bricks you're talking app server |
| 14:07 |
atlas__ |
i read bricks before |
| 14:07 |
atlas__ |
the term |
| 14:08 |
Dyrcona |
It's a collection of servers. |
| 14:08 |
Dyrcona |
It's kind of an Evergreenism. |
| 14:08 |
atlas__ |
okay |
| 14:08 |
atlas__ |
referring to the application and database server together? |
| 14:09 |
Dyrcona |
No, you usually run the database server on its own. |
| 14:09 |
Dyrcona |
A brick is a collection of Evergreen app servers, all communicating via XMPP. |
| 14:10 |
Dyrcona |
One usually serves as the "brick head" and communicates with the other bricks, if I understand it correctly. |
| 14:10 |
atlas__ |
that makes more sense -- was wondering what 'collection of servers' make up a 'brick' |
| 14:10 |
atlas__ |
so it's a bunch of evergreen app servers |
| 14:10 |
Dyrcona |
We just run the apps on one server at my location, though we've considered playing around with multiple jabber instances and a soft-of brick environment. |
| 14:10 |
atlas__ |
and the 'brick head' is a load balancer/proxy |
| 14:11 |
atlas__ |
great |
| 14:11 |
Dyrcona |
Well, the brick heads usually communicate with a separate load balancer, but basically, yes. |
| 14:12 |
atlas__ |
here we go...http://wiki.evergreen-ils.org/doku.php?id=system_requirements |
| 14:12 |
Dyrcona |
OpenSRF, the protocol that Evergren uses to communicate, is somewhat decentralized, as is XMPP, the typical medium of communications. |
| 14:14 |
atlas__ |
wish there was more info here |
| 14:15 |
atlas__ |
http://docs.evergreen-ils.org/2.1/html/hardwareconfigurations.html |
| 14:15 |
atlas__ |
probably applies to 2.7 too ? |
| 14:18 |
Dyrcona |
Probably, but I think it overstates the case. |
| 14:18 |
Dyrcona |
We run with one app server/brick, web and Evergreen apps on one box. |
| 14:18 |
Dyrcona |
Database on another. |
| 14:19 |
Dyrcona |
We come pretty close to the description of the academic library requiring a load balancer. |
| 14:33 |
bshum |
Heh, pretty much. |
| 14:34 |
bshum |
we just switched to our new server architecture today. 2 load balancers (one at a time, heartbeat between them), 2 Evergreen app servers, 2 app servers (with SIP server on them) and one app server acting as utility server |
| 14:34 |
bshum |
To run cron scripts, etc. |
| 14:34 |
bshum |
And of course, the primary DB server. |
| 14:35 |
bshum |
I think there's something else out there. I'm starting to lose track of all the parts :( |
| 14:35 |
bshum |
(again) |
| 14:35 |
bshum |
atlas__: System provisioning isn't an exact science per say, there are estimates and generalizations. |
| 14:36 |
Dyrcona |
tsbere has been thinking about setting up a multi-brick environment via VMs and using multiple jabber servers. |
| 14:36 |
bshum |
All I can say is that your database is the single most important thing to provide for. |
| 14:36 |
bshum |
Lots of memory is good. Good speedy cores is better. |
| 14:37 |
Dyrcona |
Enough memor to load the whole thing into RAM is bliss, especially if your data is stored on spinning rust. |
| 14:37 |
bshum |
So true :) |
| 14:37 |
bshum |
There's lots of good suggestions for PostgreSQL servers that apply to us. |
| 15:09 |
atlas__ |
anyone have a working websockets config out there? having some trouble... |
| 15:09 |
atlas__ |
WebSocket connection to 'wss://192.168.5.123:7682/osrf-websocket-translator' failed: WebSocket opening handshake was canceled |
| 15:10 |
atlas__ |
had this working...redid the apache configs...and now can't seem to get it working again |
| 15:10 |
atlas__ |
Uncaught Error: WebSocket Error [object Event] : undefined opensrf_ws.js:89socket.onerror |
| 15:14 |
atlas__ |
okay so this totally has to do with ssl and certs |
| 15:14 |
atlas__ |
it works when I'm hitting it on http://shrubbery.sasklibraries.ca |
| 15:14 |
atlas__ |
but getting the error opening handshake when hitting it at 192.168.5.123 |
| 15:14 |
atlas__ |
interesting |
| 15:16 |
Dyrcona |
Dunno. I haven't messed with websockets, yet. |
| 15:18 |
bshum |
Yeah the websockets are only happiest with valid SSL certs. |
| 15:21 |
bshum |
I think there's a way to set an exception in certain browsers. I haven't tested that far yet. |
| 15:21 |
* bshum |
is back in the car headed home. Good time for a nap. |
| 16:08 |
|
atlas__ joined #evergreen |
| 17:21 |
|
tpham joined #evergreen |
| 17:22 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 18:01 |
atlas__ |
how to blow away the database on 2.7? tried running the eg_db_config script again but got a bunch of error |
| 18:29 |
|
sbrylander joined #evergreen |
| 19:14 |
|
atlas__ joined #evergreen |
| 19:31 |
|
tpham joined #evergreen |
| 19:54 |
|
tpham joined #evergreen |
| 19:54 |
|
atlas__ joined #evergreen |
| 20:41 |
|
atlas__ joined #evergreen |
| 21:53 |
|
buzzy joined #evergreen |
| 22:03 |
|
tpham joined #evergreen |
| 22:32 |
|
mlilenium_ joined #evergreen |
| 22:32 |
|
mlilenium_ left #evergreen |
