I handle support for PaILS, and we recently had two SPARK libraries report the issue within days of each other. We're on 3.1.6.
Dale at Equinox checked our logs and found double checkin scans on the items in question. When the items were checked in, Evergreen only closed one of the transit records and tried to place the items into transit to send them home. Since an open transit record was already present, Evergreen could not create another transit record and the error message caused it to bail out of the entire checkin. Here is one of the error messages:
[INFO:6560:Circulate.pm:587:1541261361169722946] circulator: pushing event DATABASE_UPDATE_FAILED
osrf_sys.09.log.gz:2018-11-05 09:31:16 node3.grp10.v31 open-ils.circ [INFO:6560:Circulate.pm:573:1541261361169722946] circulator: BAILING OUT
osrf_sys.09.log.gz:2018-11-05 09:31:16 node3.grp10.v31 open-ils.circ [INFO:6560:Circulate.pm:293:1541261361169722946] circulator: bailing out with events: DATABASE_UPDATE_FAILED
I handle support for PaILS, and we recently had two SPARK libraries report the issue within days of each other. We're on 3.1.6.
Dale at Equinox checked our logs and found double checkin scans on the items in question. When the items were checked in, Evergreen only closed one of the transit records and tried to place the items into transit to send them home. Since an open transit record was already present, Evergreen could not create another transit record and the error message caused it to bail out of the entire checkin. Here is one of the error messages:
[INFO:6560: Circulate. pm:587: 154126136116972 2946] circulator: pushing event DATABASE_ UPDATE_ FAILED 09.log. gz:2018- 11-05 09:31:16 node3.grp10.v31 open-ils.circ [INFO:6560: Circulate. pm:573: 154126136116972 2946] circulator: BAILING OUT 09.log. gz:2018- 11-05 09:31:16 node3.grp10.v31 open-ils.circ [INFO:6560: Circulate. pm:293: 154126136116972 2946] circulator: bailing out with events: DATABASE_ UPDATE_ FAILED
osrf_sys.
osrf_sys.