Sasha CLI failed to archive some workunits

Description

Using Command line interface, I ran this command:

sudo sasha server=. action=archive wuid=W2017*

It prompted that 120 WUs would be archived and I answered Y.

About 23 of the workunits were successfully archived, the remaining 97 failed with a message like this:

{{ARCHIVE: W20170629-141221 assert(memcmp(buf.str()+p+2,wuid,l)==0) failed - file: }}

I tried
{{ sudo ./sasha server=. action=archive wuid=W20170629-141221}}

and got the same failure message.

Conclusion

None

Activity

Show:

Jim DeFabia September 18, 2017 at 2:51 PM

The *Archive *action is not available via ECL Watch. The WsWorkunit/WUAction method does not have *Archive *as an option.
AFAIK, the CLI is the only way to manually archive a workunit.

Jacob Cobbett-Smith September 18, 2017 at 1:29 PM

- is the behaviour different if not via CLI ? 

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Point

Fix versions

Affects versions

Created September 18, 2017 at 12:31 PM
Updated March 20, 2018 at 12:18 PM
Resolved October 25, 2017 at 9:29 AM