Evergreen ILS Website

IRC log for #evergreen, 2025-01-02

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Turn on filtering by nick Enable summary mode
Time Nick Message
7 more elements. Show/hide.
09:02 Dyrcona Wow! An open-ils.trigger drone using 3.3g of RSS.
09:04 Dyrcona Looks like it is a run pending trigger runner, likely working on leftover AutorenewNotify events from Tuesday.
09:07 Dyrcona And, it's gone. Must've hit the request limit.
09:07 * Dyrcona checks logs for what berick said about how many requests it is set to allow on the utility server.
09:08 Dyrcona OK. That was pcrud and storage.
09:10 Dyrcona So, my max_requests settings for pcrud, storage, and trigger are 1000.
4 more elements. Show/hide.
10:53 berick Dyrcona: i have trigger set to 50 max requests on the util server
10:53 berick some of those big jobs can really hoard ram
10:55 Dyrcona OK. I was thinking about dropping it to 100 on the dev system.
10:57 Dyrcona If I change that in opensrf.xml, I only have to restart settings and the affected service, right?
10:57 * Dyrcona should just know.
10:58 Dyrcona We should probably have a document on settings tweaks for production systems....
11:00 Dyrcona I'll wait until after the current run-pending trigger_runner to restart the service.
2 more elements. Show/hide.
13:04 Dyrcona heh. "Swapon, Wayne." Swapon, Garth."
13:04 Bmagic Dyrcona++
14:48 smayo joined #evergreen
14:51 csharp_ the bots are celebrating a new year by picking on me
14:53 Bmagic bots--
14:53 Dyrcona bots--
14:53 Dyrcona Bmagic++
14:53 Dyrcona ansible++
14:53 Dyrcona learning++
14:57 csharp_ ansible++
15:04 * Dyrcona added plays to our Ansible playbooks to make sure that the memory and swap settings happen when we ever build new dev or utility vms.
15:05 Dyrcona plays? tasks? Same thing, right?
15:06 Bmagic Are you referring to the result line after the book played?
15:08 Bmagic Ansible can reachout and execute a playbook across hundreds of servers, so, I believe "plays" is more in line with number of servers that received the playbook. Whereas tasks is the individual pieces of the playbook that are executed. And if the playbook uses IF statements, it's possible the number of tasks differ from server to server
15:08 Dyrcona No, there was an error message at one point that said 'x is not a valid play' or something like that. Then, there's the tasks key in the playbook.
15:09 Dyrcona OK. That makes sense, too: a play is a run of a playbook, and a task is something you don in a playbook...
15:09 Bmagic If each task is named, then it should give you your "user friendly" name back to you when it's executing.
15:11 Dyrcona Yeah. It does. What I got was "ERROR! 'lineinfile' is not a valid attribute for a Play" Which clued me in that something was missing, i.e. the "tasks" attribute.
15:12 Dyrcona Copy and paste is not always your friend.
15:12 Bmagic ah yes, the header needs some setup logic
7 more elements. Show/hide.
23:35 tiime Hi

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat