Skip to main content
Ex Libris Knowledge Center

The selfchk binary is confusing its messages with its logs

  • Article Type: Known Issue
  • Product: Voyager
  • Relevant for Installation Type: Dedicated-Direct; Direct; Local; Total Care

Symptoms

*Selfcheck sends logging messages to the client and logging SIP2 data where the date should be in the log file

Defect Status

Issue VYG-6523 is resolved for Voyager 9.2.0 and higher.

Replication Steps

1. Connect to selfchk, note that messages are correctly sent:
BEGIN Login
SENDING: 9300|CNdemo|COdemo|CPCIRC
RECEIVING: 941
SENDING: 9900802.00
RECEIVING: 98YYYYYN99800320150306 1427092.00AO|BXYYYYYNYYYNYNNNYN|
END Login

BEGIN Stanza Loop
SENDING: 6300120140804 140800 Y AO|AA11RITA|AC|AD|BP|BQ|
RECEIVING: 64YYYY 00020150306 142710000000000000000000000000AO|AA11RITA|AE|BLN|AFPatron barcode not found|PT|
END Stanza Loop

2. Activate logging in Pselfchk:
export LOGSELFCHK=1
exec $VOYAGER_BIN/selfchk -s$CIRCSVRHOST -p$CIRCSVRPORT -t$TIMEOUT -b$SELFCHKCONFIG "$@"

3. Connect again and note that it actually sends "Begin Session" and "End Session", instead of SIP2 messages:
BEGIN Login
SENDING: 9300|CNdemo|COdemo|CPCIRC
RECEIVING: Begin Session

SENDING: 9900802.00
RECEIVING: 940
END Login

BEGIN Stanza Loop
SENDING: 6300120140804 140800 Y AO|AA11RITA|AC|AD|BP|BQ|
RECEIVING: End Session

END Stanza Loop

4. Check the generated log, and see that the 99 message that it received was sent to the log in lieu of the date portion of the timestamp:
log.selfchk
Fri Mar 6 11:55:12 2015 Went through ProcessArgs

9900802.00 11:55:12 2015 Received from client: 9300|CNdemo|COdemo|CPCIRC|

Workaround

Use logging for testing, but not for production.

Category: Voy SelfCheck V.2.0