• Product: Aleph
• Product Version: 20, 21, 22, 23
• Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

Description:
After starting upgrade_util, 2. Install Customer Data, on our 18 gig ./data/a_20_1.tar.gz file, we found that after half an hour it still showed this:

Opening tar file ...

No /logs directory had been created.

Resolution:
We killed the process and tried submitting it again.
After perhaps 40 minutes, we got these errors: 
Opening tar file ...
tar: a20_1/alephe/www_f_eng: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/u20_1/alephe/www_r_eng: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/u20_1/alephe/www_f_eng: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/u20_1/alephe/www_s_eng: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/u20_1/alephe/www_c_eng: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/u20_1/alephe: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/u20_1: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/a20_1/alephe/www_r_eng: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/a20_1/alephe/www_f_eng: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/a20_1/alephe/www_s_eng: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/a20_1/alephe/www_c_eng: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/a20_1/alephe: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/a20_1/pds/html_form: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/a20_1/pds: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/a20_1/aleph/www_n_eng: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/a20_1/aleph/www_g_eng: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/a20_1/aleph/www_x_eng: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/a20_1/aleph: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph/a20_1: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris/aleph: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs/exlibris: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache/htdocs: Directory renamed before its status could be extracted
tar: a20_1/alephe/apache: Directory renamed before its status could be extracted
tar: a20_1/alephe: Directory renamed before its status could be extracted
tar: a20_1: Directory renamed before its status could be extracted
tar: Exiting with failure status due to previous errors
<end log of errors>

We then did the following to clear out the previously-loaded stuff so we could have a clean run:
> cd /exlibris/aleph/upgrade_express_2001_2101/data
> rm -r a20_1
Then we submitted upgrade_util, 2. Install Customer Data, again. 
Though it took an hour for it to do the "Opening tar file ..." and create the logs directory (with /log/install_utree.log), it *did *then run successfully.

The moral: Don't kill "Opening tar file ..." for a big file -- even if it doesn' seem to be doing anything.

• Article last edited: 12-Mar-2016