Open szanati opened 6 years ago
This issue is similar to https://github.com/daitss/core/issues/802. I reset the package, E1JC9A9LC_4EJQWG/AA00012381_00001, and received the same error. I aborted the package and resubmitted the refresh package and received the same error. I also received the same error for packages: E1MF9V84T_MCIMUU/AA00013476_00001 and E1IHQGEVD_FKAF2T/AA00013233_00001.
This is a different problem than issue #802 though it may appear so. In issue 802, the tar file was a bogus tar (0 byte) so I added a tar validation step before extracting the tar to skip invalid tar.
The problem this time is the tar validation return xmlres-0.tar as being valid, but when daitss try to extract the file, it says the tar 'contain obsolescent base-64 headers". It looks to be a valid tar and I can the tar extraction is creating a directory for it, but it returns an error code.
[cchou@fclnx30 ~]$ tar -tf xmlres-0.tar E1MF9V84T_MCIMUU/manifest.xml E1MF9V84T_MCIMUU/http/digital.uflib.ufl.edu/metadata/sobekcm/sobekcm.xsd E1MF9V84T_MCIMUU/http/www.fcla.edu/dls/md/daitss/daitss.xsd E1MF9V84T_MCIMUU/http/www.loc.gov/standards/mets/mets.xsd E1MF9V84T_MCIMUU/http/www.loc.gov/standards/mods/v3/mods-3-4.xsd E1MF9V84T_MCIMUU/http/www.loc.gov/standards/mods/xml.xsd E1MF9V84T_MCIMUU/http/www.loc.gov/standards/xlink/xlink.xsd E1MF9V84T_MCIMUU/http/www.w3.org/2001/xml.xsd E1MF9V84T_MCIMUU/http/www.w3.org/2001/XMLSchema.xsd E1MF9V84T_MCIMUU/http/www.ukoln.ac.uk/repositories/eprints-application-profile/epdcx/xsd/2006-11-16/ E1MF9V84T_MCIMUU/http/www.w3.org/2001/03/xml.xsd
[cchou@fclnx30 ~]$ tar -xf xmlres-0.tar tar: Archive contains obsolescent base-64 headers tar: Skipping to next header tar: Error exit delayed from previous errors
Searching on the internet seems to suggest it mostly likely caused by file transfer error or hardware failure. Can you curl the package tar directly and put it on daitss-test?
Carol,
I was able to curl the tar. I put both E1MF9V84T_MCIMUU.tar and E1JC9A9LC_4EJQWG.tar on daitss-test. I change the permissions so you should be able to down load them.
Given my contract is ending, James, can you take this issue over?
Thanks Carol for all your help. I let James know.
Yes, I will be taking over this issue
I received the following error while refreshing a batch of packages:
could not expand tarball=/var/daitss/data/work/E1JC9A9LC_4EJQWG/xmlresolutions/xmlres-0.tar into dir= /var/daitss/tmp/d20180925-2919-11zrlhc: pid 3131 exit 2 /opt/web-services/sites/core/releases/20180510000001/lib/daitss/proc/wip/tarball.rb:50:in
block (3 levels) in make_tarball' /opt/ruby-1.9.3-p545/lib/ruby/1.9.1/tmpdir.rb:83:in
mktmpdir' /opt/web-services/sites/core/releases/20180510000001/lib/daitss/proc/wip/tarball.rb:47:inblock (2 levels) in make_tarball' /opt/web-services/sites/core/releases/20180510000001/lib/daitss/proc/wip/tarball.rb:40:in
each' /opt/web-services/sites/core/releases/20180510000001/lib/daitss/proc/wip/tarball.rb:40:inblock in make_tarball' /opt/web-services/sites/core/releases/20180510000001/lib/daitss/proc/wip/tarball.rb:16:in
chdir' /opt/web-services/sites/core/releases/20180510000001/lib/daitss/proc/wip/tarball.rb:16:inmake_tarball' /opt/web-services/sites/core/releases/20180510000001/lib/daitss/proc/wip/refresh.rb:24:in
block in refresh' /opt/web-services/sites/core/releases/20180510000001/lib/daitss/proc/wip/journal.rb:16:instep' /opt/web-services/sites/core/releases/20180510000001/lib/daitss/proc/wip/refresh.rb:24:in
refresh' /opt/web-services/sites/core/releases/20180510000001/lib/daitss/proc/wip/process.rb:82:inblock in spawn' /opt/web-services/sites/core/releases/20180510000001/lib/daitss/proc/wip/process.rb:66:in
fork' /opt/web-services/sites/core/releases/20180510000001/lib/daitss/proc/wip/process.rb:66:inspawn' /opt/web-services/sites/core/current/bin/pulse:161:in
block in start_wips' /opt/web-services/sites/core/current/bin/pulse:158:ineach' /opt/web-services/sites/core/current/bin/pulse:158:in
start_wips' /opt/web-services/sites/core/current/bin/pulse:194:inblock in ' /opt/web-services/sites/core/current/bin/pulse:192:in
loop' /opt/web-services/sites/core/current/bin/pulse:192:in `