firstyear
- Login: firstyear
- Email: william.brown@suse.com
- Role: Developer
- Connect profile: 1
- Registered on: 2020-01-06
- Last sign in: 2020-01-06
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 9 | 9 | 18 |
Reported issues | 3 | 4 | 7 |
Projects
Project | Roles | Registered on |
---|---|---|
openSUSE admin | Developer, private ticket access | 2023-11-13 |
Provo | Developer, private ticket access | 2023-11-13 |
Activity
2025-05-31
- 14:12 openSUSE admin tickets #165102: Reduce kanidm-unixd logging
- That's why I'm saying, it's a bug and we need to get quinn to help us with the filter.
- 14:12 openSUSE admin tickets #165102: Reduce kanidm-unixd logging
- No because then you break error and warning logs.
- 14:10 openSUSE admin tickets #165102: Reduce kanidm-unixd logging
- No, you can't.
The issue is to do with how the logging works to *nest* things. You need *at least* one span (loggi...
2025-05-17
- 08:12 openSUSE admin tickets #182534: kanidm-unixd causes OOM on machines with low RAM
- Yes, it should not use so much. I'm finally awake enough to investigate this today.
2025-05-14
- 05:45 openSUSE admin tickets #182282: kanidmd crashed
- Permanent fix upstreamed and released as part of 1.6.3
Would that mean kanidm is marked as reboot safe then? Like... - 01:44 openSUSE admin tickets #182282: kanidmd crashed
- I think this is a reason why docker/podman is better for this, because then we can control when we update, and we hav...
- 01:43 openSUSE admin tickets #182282: kanidmd crashed
- Ahh It's a new issue. I've fixed the config manually and started both instances. I'll put in a PR to resolve that cas...
- 01:32 openSUSE admin tickets #182282: kanidmd crashed
- There is already a fix, it's in 1.6.2.
2025-05-13
- 00:13 openSUSE admin tickets #182249 (Resolved): mirrorcache-us-west mirror is spitting out an html 500 error
- Resolved (if it wasn't clear that I had already resolved this)
2025-05-12
- 22:27 openSUSE admin tickets #182249: mirrorcache-us-west mirror is spitting out an html 500 error
- DB was using 30GB, truncate stat cleared 4GB, vacuum full cleared another 18GB or so.
Also available in: Atom