Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]Strugling to get HP SmartArray controller work with scrutiny #700

Open
kotso opened this issue Oct 6, 2024 · 1 comment
Open

[BUG]Strugling to get HP SmartArray controller work with scrutiny #700

kotso opened this issue Oct 6, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@kotso
Copy link

kotso commented Oct 6, 2024

I have 1x raid array made of 12x disks.

Here is my configuration file:

version: 1

host:
  id: "***"


devices:
  - device: /dev/sda
    type:
      - 'cciss,0'
      - 'cciss,1'

When running collector from command line to see whats happening in debug, I see that device info is collected correctly but smarty attributes are collected with wrong parameters, it uses device sat every time so It cant get any smart attribute.

root@90c6238da1f2:/opt/scrutiny# /opt/scrutiny/bin/scrutiny-collector-metrics run
2024/10/06 19:07:53 Loading configuration file: /opt/scrutiny/config/collector.yaml

 ___   ___  ____  __  __  ____  ____  _  _  _  _
/ __) / __)(  _ \(  )(  )(_  _)(_  _)( \( )( \/ )
\__ \( (__  )   / )(__)(   )(   _)(_  )  (  \  /
(___/ \___)(_)\_)(______) (__) (____)(_)\_) (__)
AnalogJ/scrutiny/metrics                                dev-0.8.1

INFO[0000] Verifying required tools                      type=metrics
INFO[0000] Executing command: smartctl --scan --json     type=metrics
INFO[0000] Executing command: smartctl --info --json --device cciss,0 /dev/sda  type=metrics
INFO[0000] Generating WWN                                type=metrics
INFO[0000] Executing command: smartctl --info --json --device cciss,1 /dev/sda  type=metrics
INFO[0000] Generating WWN                                type=metrics
INFO[0000] Sending detected devices to API, for filtering & validation  type=metrics
INFO[0000] Collecting smartctl results for sda           type=metrics
INFO[0000] Executing command: smartctl --xall --json --device sat /dev/sda  type=metrics
ERRO[0000] smartctl returned an error code (2) while processing sda  type=metrics
ERRO[0000] smartctl could not open device                type=metrics
INFO[0000] Publishing smartctl results for 0x5000cca26fe8bd79  type=metrics
INFO[0000] Collecting smartctl results for sda           type=metrics
INFO[0000] Executing command: smartctl --xall --json --device sat /dev/sda  type=metrics
ERRO[0000] smartctl returned an error code (2) while processing sda  type=metrics
ERRO[0000] smartctl could not open device                type=metrics
INFO[0000] Publishing smartctl results for 0x5000cca270c3bb14  type=metrics
INFO[0000] Main: Completed                               type=metrics

If I change --device sat to correct --device cciss,0 (0 and 1 and others) then all data is displayed correctly by smartctl, but what I see is scrutiny calls smartctl with wrong parameters in second part.

@kotso kotso added the bug Something isn't working label Oct 6, 2024
@kotso
Copy link
Author

kotso commented Oct 6, 2024

All running in docker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant