Comment 14 for bug 1697029

I have been seeing this problem as well since upgrading to Opensrf 2.5.0 and Evergreen 2.12.2 last week. This morning one of my bricks was not returning search results. The log file showed these errors:

2017-06-22 05:24:29 brick2 open-ils.search: [ERR :1821:System.pm:122:] server: d
ied with error Can't use an undefined value as a symbol reference at /usr/local/
share/perl/5.20.2/OpenSRF/Server.pm line 307.

2017-06-22 05:24:36 brick2 gateway: [ERR :24153:EX.pm:66:14980738542415364] Exce
ption: OpenSRF::EX::Session 2017-06-22T05:24:36 OpenSRF::Transport /usr/local/sh
are/perl/5.20.2/OpenSRF/Transport.pm:83 Session Error: router@brick2-private/ope
n-ils.search IS NOT CONNECTED TO THE NETWORK!!!

Regarding the patch to fix the spelling of SIGALRM, that is already part of 2.12.2 and my system has that. I have also noticed a lot (50 or so) messages in the error logs per day for the various bricks with the NOT CONNECTED TO THE NETWORK message. The bricks are otherwise still online.

For what it's worth, I ran debian Jessie updates just prior to the upgrade. There were a number of erlang updates: erlang-asn1 erlang-base erlang-crypto erlang-eunit erlang-inets erlang-mnesia erlang-odbc erlang-public-key erlang-runtime-tools erlang-ssl erlang-syntax-tools erlang-tools erlang-webtool erlang-xmerl.