| Time |
Nick |
Message |
| 07:19 |
|
JBoyer joined #evergreen |
| 07:29 |
|
agoben joined #evergreen |
| 08:28 |
|
csharp joined #evergreen |
| 08:33 |
|
finnx joined #evergreen |
| 08:36 |
|
artunit_ joined #evergreen |
| 08:36 |
|
Callender_ joined #evergreen |
| 08:38 |
|
Bmagic_ joined #evergreen |
| 08:39 |
|
collum joined #evergreen |
| 08:39 |
|
mmorgan joined #evergreen |
| 08:40 |
|
jeff___ joined #evergreen |
| 08:40 |
|
berick_ joined #evergreen |
| 08:46 |
|
jeff___ joined #evergreen |
| 08:54 |
|
bos20k joined #evergreen |
| 09:17 |
|
jvwoolf joined #evergreen |
| 09:19 |
|
rjackson_isl joined #evergreen |
| 09:23 |
|
Dyrcona joined #evergreen |
| 09:27 |
|
yboston joined #evergreen |
| 09:32 |
|
kmlussier joined #evergreen |
| 09:45 |
|
dans-datalogics joined #evergreen |
| 10:03 |
|
mmorgan1 joined #evergreen |
| 10:03 |
|
Bmagic joined #evergreen |
| 10:39 |
|
jvwoolf joined #evergreen |
| 10:41 |
|
rlefaive joined #evergreen |
| 10:48 |
|
cgreen joined #evergreen |
| 11:39 |
|
mmorgan joined #evergreen |
| 11:46 |
|
kmlussier joined #evergreen |
| 11:53 |
dans-datalogics |
phasefx: i'm picking up where i left off on Friday. using the installation script (with lots of little tweaks to get it working) i'm able to connect and login via the staff client. |
| 11:54 |
dans-datalogics |
however, i'm now getting a new error after i log in -- document.getElementById("commonStrings") is null |
| 11:55 |
Dyrcona |
dans-datalogics: Sometimes, just quitting the client and starting it over again fixes that. |
| 11:55 |
|
Callender joined #evergreen |
| 11:55 |
dans-datalogics |
i'm also still a bit worried by the fact that almost all 2 GB of RAM on the server is taken. |
| 11:56 |
Dyrcona |
dans-datalogics: Yeah, 2GB is a bit slim, I prefer 4GB as a minimum or concerto data and 6-8 GB if I'm using production data on a test vm. |
| 11:57 |
dans-datalogics |
Dyrcona: ah, well i can bump it up to 4 then. the system requirements said only 1 GB was needed, so i figured 2 was safe. |
| 11:57 |
dans-datalogics |
also, restarting the client is now giving me a failed status check. i might chalk that up to the memory issue. |
| 11:57 |
Dyrcona |
dans-datalogics: Where are these system requirements? They should be changed, I think. |
| 11:58 |
|
brahmina joined #evergreen |
| 11:58 |
dans-datalogics |
http://docs.evergreen-ils.org/dev/_system_requirements.html |
| 11:58 |
|
Christineb joined #evergreen |
| 11:59 |
bshum |
Change is good. |
| 11:59 |
bshum |
Change is very good. |
| 12:00 |
|
barbara joined #evergreen |
| 12:03 |
* bshum |
feels like 4 GB of RAM is a good "test server" these days |
| 12:03 |
bshum |
And hey, probably at least 2 GB or more of RAM for a client workstation too. 512 MB? No...... |
| 12:04 |
* bshum |
drops the line for "XP, Vista, or 7" |
| 12:07 |
|
jihpringle joined #evergreen |
| 12:08 |
bshum |
Doc change pushed to master and backported to rel_2_11 and rel_2_10 (as the two most recent versions) |
| 12:09 |
bshum |
dans-datalogics++ # thanks for the pointer |
| 12:10 |
pinesol_green |
[evergreen|Ben Shum] Docs: Update base system requirements for Evergreen - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=1b92116> |
| 12:17 |
bshum |
Maybe 2 GB is too conservative and I should have changed that to 4 GB too for clients. |
| 12:18 |
bshum |
https://wiki.evergreen-ils.org/doku.php?id=system_requirements is ancient too |
| 12:22 |
dans-datalogics |
that feels much better -- Mem: 5.8G 2.2G 3.6G |
| 12:22 |
dans-datalogics |
no wonder 2GB available wasn't enough. |
| 12:23 |
dans-datalogics |
i'm still seeing that "commonStrings" error every time i try logging into the staff client, though |
| 12:24 |
Dyrcona |
dans-datalogics: Did you build this client or download it? |
| 12:25 |
dans-datalogics |
downloaded |
| 12:29 |
|
hbrennan joined #evergreen |
| 12:38 |
Dyrcona |
dans-datalogics: I wonder if the client is really compatible with what you installed. |
| 12:42 |
dans-datalogics |
Dyrcona: yeah, probably not. the installer script put the web files into a directory called 0master[some hex string] rather than a real version number. |
| 12:43 |
Dyrcona |
Yeah. You'll probably need to build the client on the server and download it from there. |
| 12:45 |
Dyrcona |
dans-datalogics: https://wiki.evergreen-ils.org/doku.php?id=mozilla-devel:building_the_staff_client |
| 12:46 |
dans-datalogics |
i know i'm bouncing around a bit here, but i just went back to our original server that we thought we had working and bumped up its memory as well. |
| 12:46 |
Dyrcona |
dans-datalogics: OK. |
| 12:46 |
dans-datalogics |
that server has an evergreen version that actually is compatible with the client i have. |
| 12:46 |
Dyrcona |
That's good. |
| 12:47 |
dans-datalogics |
and i was able to authenticate one patron in my user application, but then the second one failed. i'm back to seeing a ton of errors in osrfsys.log. |
| 12:47 |
Dyrcona |
I'll check the IRC logs to see if the script you used made a client. There's a standard place you can download it from if it did. |
| 12:50 |
Dyrcona |
Nope. Doesn't look like those scripts build a staff client, unless they're all different in that respect. :) |
| 13:03 |
|
rlefaive joined #evergreen |
| 13:04 |
hbrennan |
Does CREATE_PERM means create permission group (or create permission?)??? The docs give the definition of CREATE_PERM = CREATE_PERM (and UPDATE_PERM = UPDATE_PERM), so it's not so helpful with clarification... |
| 13:09 |
Dyrcona |
hbrennan: They allow you to create or update permissions, i.e. add a new permission. Doesn't look like there's anything to do with groups. |
| 13:10 |
Dyrcona |
Oh, wait. Spoke too soon. They do both! |
| 13:10 |
hbrennan |
Dyrcona: hmm.... when I click "New Child" when attempting to create a new permission group, the screen flashes red... normal? |
| 13:10 |
jeff |
the IDL references CREATE_PERM as the required create perm for both permission.perm_list and permission.grp_tree. |
| 13:10 |
hbrennan |
jeff: gotcha. So I just don't have the permission to create a permission group |
| 13:10 |
hbrennan |
ha |
| 13:11 |
Dyrcona |
hbrennan: Could be you need it consortium-wide, i.e. depth 0. |
| 13:11 |
hbrennan |
I just pulled up my perm list and I don't have it checked :( |
| 13:12 |
hbrennan |
We run on a "don't check it til you explain why you need it" process |
| 13:18 |
|
gsams joined #evergreen |
| 13:22 |
|
rlefaive joined #evergreen |
| 13:27 |
|
rlefaive joined #evergreen |
| 13:27 |
|
gsams joined #evergreen |
| 13:44 |
|
miker joined #evergreen |
| 13:44 |
|
graced joined #evergreen |
| 13:44 |
|
Shae joined #evergreen |
| 13:46 |
|
jyorio joined #evergreen |
| 13:51 |
Dyrcona |
hbrennan: You've probably sorted your permissions out, but for the benefit of the logs, you do need CREATE_PERM at the root of the org tree. It is global_required="true" in the IDL. |
| 13:51 |
|
ericar joined #evergreen |
| 13:52 |
hbrennan |
Dyrcona: Good to know! Thanks! |
| 13:52 |
hbrennan |
Dyrcona++ jeff++ |
| 13:54 |
|
mmorgan1 joined #evergreen |
| 14:01 |
|
rhamby joined #evergreen |
| 14:35 |
|
akilsdonk joined #evergreen |
| 14:36 |
|
abneiman joined #evergreen |
| 15:47 |
|
mmorgan joined #evergreen |
| 16:13 |
phasefx |
Dyrcona: bshum: I'm not here, but the FAQ's also mention some system requirements that probably need to be updated |
| 16:21 |
|
jvwoolf left #evergreen |
| 16:21 |
Dyrcona |
phasefx: Thanks. I found one such reference and updated it. |
| 16:28 |
|
tsbere_ joined #evergreen |
| 16:35 |
bshum |
Dyrcona++ # good edits ; phasefx++ # good finds |
| 16:47 |
mmorgan |
So it looks like, in order to Undelete bib records, the staff user just needs UPDATE_RECORD, true? |
| 16:49 |
Dyrcona |
mmorgan: Yes. |
| 16:50 |
bshum |
And then the devil gave him wings. |
| 16:50 |
Dyrcona |
And they need that permission at their workstation org. unit. |
| 16:51 |
Dyrcona |
Though it can be granted at a higher org. unit, of course. |
| 16:51 |
mmorgan |
Dyrcona: Thanks. I was hoping to allow undeleting records, but not editing them. |
| 16:52 |
mmorgan |
But that's not an option :-( |
| 16:52 |
Dyrcona |
mmorgan: That would require a new permission and a change to Cat.pm around line 364. :) |
| 16:52 |
bshum |
Dyrcona: That precision is both awesome and scary. |
| 16:52 |
mmorgan |
:) |
| 16:53 |
* tsbere |
wonders why you would trust someone to undelete records but not edit them, given that records may be deleted for reasons such as being horrible ;) |
| 16:53 |
* mmorgan |
wonders if that would be a useful new permission for others as well. |
| 16:53 |
Dyrcona |
Well, I had it open to answer the original question. :) |
| 16:53 |
Dyrcona |
Best way to find out is to open a Launchpad bug. |
| 16:54 |
mmorgan |
tsbere: We delete the bib records when the last item is deleted. |
| 16:54 |
Dyrcona |
I can see allowing someone to undelete records who can't edit them. |
| 16:54 |
tsbere |
mmorgan: I can understand that aspect. Doesn't mean all deleted bibs were deleted that way. |
| 16:55 |
Dyrcona |
I don't see allowing someone to edit records who can't also undelete them. |
| 16:55 |
mmorgan |
It has happened more than once that the item was deleted but a new one needs to be added. |
| 16:57 |
mmorgan |
But the bib has gone poof. I think users who can edit records should be allowed to undelete, but I want some users to be able to undelete that can't edit. |
| 16:57 |
Dyrcona |
Right. |
| 16:58 |
mmorgan |
If they deleted it by mistake, they should be able to get it back. |
| 16:59 |
* mmorgan |
will open that launchpad bug. |
| 16:59 |
Dyrcona |
Right, and delete records is its own permission. |
| 17:00 |
Dyrcona |
Makes sense to me, at least. |
| 17:00 |
* Dyrcona |
signs out. |
| 17:01 |
mmorgan |
Dyrcona++ |
| 17:04 |
|
mmorgan left #evergreen |
| 17:19 |
dans-datalogics |
hey all, i think my system is working a lot better after re-installing and increasing the memory, but now whenever i try to authenticate a patron through an HTTP request, i get a JSON parser error in my logs. |
| 17:20 |
dans-datalogics |
i'm not sure where it's getting the JSON, so i'm sure there's an intermediary step i'm not seeing. |
| 17:21 |
dans-datalogics |
anyone seen that before? the error shows up at the very start of the log for a new request in gateway.log |
| 19:44 |
|
abneiman joined #evergreen |
| 19:44 |
|
akilsdonk joined #evergreen |
| 19:44 |
|
Christineb joined #evergreen |
| 19:44 |
|
berick_ joined #evergreen |
| 19:44 |
|
book`_ joined #evergreen |
| 19:44 |
|
ejk joined #evergreen |
| 19:44 |
|
sard joined #evergreen |
| 21:46 |
|
finnx1 joined #evergreen |
| 22:55 |
dbs |
@later tell dans-datalogics maybe share the error you're getting to a pastebin site? |
| 22:55 |
pinesol_green |
dbs: The operation succeeded. |
