Details
-
Task
-
Resolution: Done
-
Major - P3
-
None
-
None
-
Fully Compatible
-
TIG 17 (07/15/16)
Description
The FTDC upload step can fail for a few reasons:
1 - There are no diagnostic.data directories to archive
2 - /data/db does not exist
The code should be made more robust to handle these scenarios.
[2016/06/28 13:49:21.336] tar cvzf diagnostic-data.tgz $(find /data/db -type d -name diagnostic.data)
|
[2016/06/28 13:49:21.343] tar: Cowardly refusing to create an empty archive
|
[2016/06/28 13:49:21.343] Try `tar --help' or `tar --usage' for more information.
|
[2016/06/28 13:49:21.344] Command failed: exit status 2
|
[2016/06/27 19:33:48.079] tar cvzf diagnostic-data.tgz $(find /data/db -type d -name diagnostic.data)
|
[2016/06/27 19:33:48.080] find: `/data/db': No such file or directory
|
[2016/06/27 19:33:48.081] tar: Cowardly refusing to create an empty archive
|
[2016/06/27 19:33:48.081] Try 'tar --help' or 'tar --usage' for more information.
|
[2016/06/27 19:33:48.081] Command failed: exit status 2
|
Attachments
Issue Links
- is related to
-
SERVER-21148 Upload FTDC data from Evergreen test runs
-
- Closed
-