Comment 6 for bug 1697029

No other ERR or WARN logs for PID 2738 -- it was running smoothly and continuously for at least 30 minutes prior to the error. This is the last log entry before the error:

open-ils.search: [INFO:2738:Server.pm:309:] RT46742: writing to child 29658

Looking at that child PID in the logs, I see this interesting sequence:

open-ils.search: [INFO:2738:Server.pm:309:] RT46742: writing to child 29658
open-ils.search: [INFO:29658:Application.pm:159:149762023328860628] CALL: open-ils.search open-ils.search.facet_cache.retrieve open-ils.search_5ccd5bc2eb51c170cb61d443575c39b0_facets
open-ils.search: [WARN:29658:Application.pm:624:149762023328860628] open-ils.search.facet_cache.retrieve: No such signal: SIGALARM at /usr/local/share/perl/5.18.2/OpenILS/Application/Search/Biblio.pm line 1411.
open-ils.search: [INFO:29658:Transport.pm:163:149762023328860628] Message processing duration: 0.035
open-ils.search: [INFO:2738:Server.pm:309:] RT46742: writing to child 29658

The "child has been reaped!" error message immediately follows these messages. So perhaps the "No such signal: SIGALARM" error points to the underlying cause? I haven't applied Jason Boyer's fix for bug 1689576 on our system yet - maybe I should try that?