History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CIB-1512
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Alex Chapman
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Pulse

I/O error zipping directory artifact: External archiving process returned code 15

Created: 30/May/08 06:15 PM   Updated: 12/Dec/08 04:11 AM
Component/s: Web UI
Affects Version/s: 1.2.34
Fix Version/s: x.x

Environment:
Linux susrallnx1 2.6.13-15.16-bigsmp #1 SMP Fri Jun 8 15:35:39 UTC 2007 i686 i686 i386 GNU/Linux


 Description  « Hide
I've read the documentation on the use of external archiving, and I've searched this JIRA for similar issues. I'm sure this is just a setup thing, but I can't figure out what I'm doing wrong. Sorry if this is documented somewhere that I've missed.

I have a build which has a directory artifact called "logs". There are 7 files in that directory which I would like to download in one zip file. I can successfully download each of the files separately from the artifacts of the build. But when I click on the zip icon I receive the message: "I/O error zipping directory artifact: External archiving process returned code 15"

I've looked in my /repos/pulse-data/config/system.properties and the only entry there is "pulse.agent.ping.timeout=180". From the command line I've tested out the default archive command "zip -qry test.zip test.log" and it works fine. I don't see anything appear in the pulse0.0.log or the event0.0.log when this error happens.

Since I'm not specifying a pulse.archive.command in my system properties, and the default zip command works from the command line, I'm not sure what else I can do to figure out what is happening. Can you suggest some troubleshooting that I can do at my end?

 All   Comments   Change History      Sort Order:
jason - 30/May/08 08:42 PM
Hi Alex,

According to the man page for zip, code 15 means that zip could not create a file for writing (most likely the archive file). I wonder if there may be a permissions problem. Pulse will try to create an archive in:

$PULSE_HOME/versions/<build>/system/tmp

Could you check the permissions on this directory? Are there any files within it? Does the filesystem have space?