[Bug 41678] New: Add a warning when max servers are reached
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41678 Bug ID: 41678 Summary: Add a warning when max servers are reached Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs@lists.koha-community.org Reporter: ryan.henderson@openfifth.co.uk QA Contact: testopia@bugs.koha-community.org Hi All, We've been investigating an issue with a SIP configuration with a library who have multiple SIP units. It took us a while to find out that the issue was due to the max servers being reached. What would be a nice enhancement is adding a warning / error message into the sip logs to say that the max servers were reached. SIP2 is using prefork which from reading it seems to be able to provide this message which we currently don't seem to be doing. Kind regards, Ryan. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41678 Ryan Henderson <ryan.henderson@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Add a warning when max |Add a warning when max |servers are reached |servers are reached in SIP2 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41678 Martin Renvoize (ashimema) <martin.renvoize@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.renvoize@openfifth.c | |o.uk Assignee|koha-bugs@lists.koha-commun |martin.renvoize@openfifth.c |ity.org |o.uk -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41678 Ryan Henderson <ryan.henderson@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ryan.henderson@openfifth.co | |.uk -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41678 Martin Renvoize (ashimema) <martin.renvoize@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41678 --- Comment #1 from Steven Raith <steven.raith@openfifth.co.uk> --- For some flavour, we discovered this when we hadn't set a max_server config in the SIPConfig.xml as we were of the (apparently false!) impression that no max server statement = no limit. It appears that the underlying subsystem Net::Server::PreFork has a default of 50 connections, but that's not apparent from the sip.log Ideally it would just pop a simple MAX SERVERS REACHED or similar - it doesn't have to be fancy! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41678 Martin Renvoize (ashimema) <martin.renvoize@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |Needs Signoff Patch complexity|--- |Small patch -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41678 --- Comment #2 from Martin Renvoize (ashimema) <martin.renvoize@openfifth.co.uk> --- Created attachment 191809 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=191809&action=edit Bug 41678: Add warning log when SIPServer reaches max_servers capacity This enhancement adds logging to warn administrators when the SIP server reaches its configured maximum number of child processes. The warning is logged periodically (once per second) when the current child count equals or exceeds the max_servers configuration value. The implementation uses the pre_loop_hook to check capacity in the parent process and logs using the existing SIP logging system at WARNING level. -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org