p_publish_04: Segmentation Fault; apostrophe / double dash in Collection names
- Article Type: General
- Product: Aleph
- Product Version: 18.01
Description:
p_publish_04 fails. The $data_scratch p_publish_04.cycles file has:
0001 + 001800000 001849999
$
0002 ! 001850000 001899999
$
0003 + 001900000 001900000
$
while the $data_scratch p_publish_04.err file has:
FAILURE Fri Mar 4 11:57:49 EST 2011 ==================
step 1
Cycle: 2
b_publish_04_b: failure
Job Suspended !!!
To identify this error in your log files use the command:
grep "FAILURE Fri Mar 4 11:57:49 EST 2011" $data_scratch/*.log
We see two logs in the abc01 $data_scratch: p_publish_04_b_1.log and p_publish_04_b_2.log.
The p_publish_04_b_1.log has this at the end:
50001 READING DOC 001849999 AT 12:06:57
Java VM is destroyed ...
50001 END READING AT 12:06:57
2011-03-04 12:06:57 [log] B-PUBLISH-04 B NORMAL END
Fri Mar 4 12:06:57 EST 2011
Exiting due to job suspension.
end
while the The p_publish_04_b_2.log has this:
28268 READING DOC 001878266 AT 11:57:48
28269 READING DOC 001878267 AT 11:57:48
Segmentation Fault
Fri Mar 4 11:57:49 EST 2011
FAILURE Fri Mar 4 11:57:49 EST 2011 ==================
step 1
Cycle: 2
b_publish_04_b: failure
Job Suspended !!!
=======================================================
Exiting due to job suspension.
end
Resolution:
[From site:] The abc50 tab40.eng Collection display names were the problem. The segmentation fault was produced by the use of an apostrophe and a double dash in the names. Once we adjusted the table to remove them, the problem went away.
- Article last edited: 10/8/2013