Diagnostics command » History » Version 1
Tom Clegg, 06/11/2021 03:29 PM
| 1 | 1 | Tom Clegg | h1. Diagnostics command |
|---|---|---|---|
| 2 | |||
| 3 | Initial work is on #17609 |
||
| 4 | |||
| 5 | "arvados-client diagnostics" |
||
| 6 | |||
| 7 | Current level of functionality: |
||
| 8 | * reveal common problems that can be hard to notice/recognize, especially for someone who is new to installing arvados |
||
| 9 | * produce output that can be shared with others to help with troubleshooting |
||
| 10 | |||
| 11 | Desired features: |
||
| 12 | * download data using s3 protocol |
||
| 13 | * run config-check (if cluster config file is accessible) |
||
| 14 | * check all health endpoints (if cluster config file is accessible) |
||
| 15 | * make internal/external client recognition mandatory (or at least default to expecting one) |
||
| 16 | * enable debug/trace mode for a single test number |
||
| 17 | * more verbose errors/explanations |
||
| 18 | * for each service, report version currently running |
||
| 19 | * for each service, report version currently installed ("/proc/self/exe -version"?) |
||
| 20 | * for each service, report md5/timestamp of config file that is currently being used (not necessarily same as one currently on disk) |
||
| 21 | * for each service, report md5/timestamp of config file on disk |