https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27151
Bug ID: 27151
Summary: SIP2 server doesn't handle broken connections which
then kills SIP2 server
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: critical
Priority: P5 - low
Component: SIP2
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected]
Koha SIP2 server doesn't handle the situation where a client unexpectedly
closes socket, this leads to the SIP2 server processes being killed and
therefore SIP2 service being unavailable.
sip-error.log when this happens:
koha3-koha-sip: client (pid 1181) killed by signal 13, stopping
More info on this issue I found from the perl website manual
(https://perldoc.perl.org/perlipc):
"Be careful to check the return values from both open() and close(). If you're
writing to a pipe, you should also trap SIGPIPE. [...]"
Another problem we have is that the koha-common service doesn't start the
process if it gets killed, but let's focus here only on the SIGPIPE issue.
This has happened now 2 times in around 1 month period on our Koha SIP
instances.
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
