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

exec error #45

Open
SparkHao opened this issue Aug 8, 2024 · 1 comment
Open

exec error #45

SparkHao opened this issue Aug 8, 2024 · 1 comment

Comments

@SparkHao
Copy link

SparkHao commented Aug 8, 2024

  • sudo ./target/release/supra-seal-demo 512MiB
    sector size: "512MiB"
    Initializing spdk using config supra_seal.cfg
    sectors 2
    coord 8 hashers 1
    sectors 4
    coord 8 hashers 2
    sectors 8
    coord 8 hashers 4
    sectors 16
    coord 8 hashers 8
    sectors 32
    coord 8 hashers 14
    coord 16 hashers 2
    sectors 64
    coord 8 hashers 14
    coord 16 hashers 14
    coord 24 hashers 4
    sectors 128
    coord 8 hashers 14
    coord 16 hashers 14
    coord 24 hashers 14
    coord 32 hashers 14
    coord 40 hashers 8
    TELEMETRY: No legacy callbacks, legacy socket not created
    Unable to attached to all specified NVMe. Ensure spdk scripts/setup.sh was run and drive list is up-to-date in .cfg

➜ spdk-v22.09 git:(v22.09) sudo ./scripts/setup.sh
0000:21:00.0 (8086 0b60): Active devices: holder@nvme0n1:md127,mount@nvme0n1:md127, so not binding PCI dev
0000:22:00.0 (8086 0b60): Active devices: holder@nvme1n1:md127,mount@nvme1n1:md127, so not binding PCI dev
0000:23:00.0 (8086 0b60): Active devices: holder@nvme2n1:md127,mount@nvme2n1:md127, so not binding PCI dev
0000:24:00.0 (8086 0b60): Active devices: holder@nvme3n1:md127,mount@nvme3n1:md127, so not binding PCI dev
./scripts/setup.sh: line 555: Warning: your password will expire in 99301 days.
263698804: syntax error in expression (error token is ": your password will expire in 99301 days.
263698804")

@simonatsn
Copy link
Contributor

That looks like an error from the spdk setup script. Try running that in isolation to root cause the issue. It generally expects sudo to work without requiring a password so if that's not enable it could be the cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants