- Article Type: General
- Product: Aleph
- Product Version: 20
In trying to correct the problem described in KB , we did a compile_all. It went OK on the Test server
and seemed to go OK (logs in ./alephm/proc) on Production, but aleph_startup got many errors, such as these:
Execution error : file '/exlibris/aleph/a20_1/aleph/exe/load_library_relation.gnt'
error code: 115, pc=0, call=7, seg=0
115 Unexpected signal (Signal 4)
The problem seems to have to do with something in create_alephe_file_name (./com_c/file_handle.c)....
We were able to copy the ./aleph/exe from the Test server to Prod. After doing this, we were getting messages like this:
/exlibris/aleph/a20_1/aleph/exe/rts32: The file access permissions do not allow the specified action..
/exlibris/aleph/a20_1/aleph/exe/get_symbol: The file access permissions do not allow the specified action..
/exlibris/aleph/a20_1/aleph/exe/set_symbol: The file access permissions do not allow the specified action..
The permission in ./aleph/exe was changed in doing the copy from Test to Prod. We did this to correct it:
chmod 777 rts32
chmod 777 submit
chmod 777 get_symbol
chmod 777 set_symbol
("777" may give more permissions than necessary, but it works.)
There were errors in connection with tab_library_group, such as "managed by NO_SUCH_SYMBOL". We needed to change the permissions on *library_group* .
One lesson: Before doing a compile_all, save the existing ./aleph/exe in a different directory.
- Article last edited: 10/8/2013