Skip to content
This repository has been archived by the owner on Dec 1, 2022. It is now read-only.

-v does not return version information #1066

Closed
study-day opened this issue May 24, 2021 · 5 comments · Fixed by #1230
Closed

-v does not return version information #1066

study-day opened this issue May 24, 2021 · 5 comments · Fixed by #1230
Labels
good first issue Community: perfect as the first pull request question Type: question about the product

Comments

@study-day
Copy link

Please check the FAQ documentation before raising an issue

Please check the FAQ documentation and old issues before raising an issue in case someone has asked the same question that you are asking.

Describe the bug (must be provided)

A clear and concise description of what the bug is.

Your Environments (must be provided)

  • OS: Linux hadoop-node-2 3.10.0-1062.el7.x86_64 Enable customized nebula-common repo url and tag #1 SMP Wed Aug 7 18:08:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  • Compliler: g++ --version or clang++ --version

  • CPU: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 64 On-line CPU(s) list: 0-63 Thread(s) per core: 2 Core(s) per socket: 16 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family: 6 Model: 85 Model name: Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz Stepping: 7 CPU MHz: 1136.663 CPU max MHz: 3900.0000 CPU min MHz: 1000.0000 BogoMIPS: 4600.00 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 1024K L3 cache: 22528K NUMA node0 CPU(s): 0-15,32-47 NUMA node1 CPU(s): 16-31,48-63 Flags:

  • Commit id (e.g. a3ffc7d8)

How To Reproduce(must be provided)

Steps to reproduce the behavior:

[nebula@hadoop-node-4 scripts]$ ./nebula.service -v status all
[INFO] nebula-metad: Exited
[INFO] nebula-graphd: Exited
[INFO] nebula-storaged: Exited
[nebula@hadoop-node-4 scripts]$ ./nebula.service -v
Usage: ./nebula.service [-v] [-c /path/to/config] <start|stop|restart|status|kill> <metad|graphd|storaged|all>

Just upgraded to 2.0.1

Expected behavior

A clear and concise description of what you expected to happen.

Additional context

Provide logs and configs, or any other context to trace the problem.

@Aiee
Copy link
Contributor

Aiee commented May 24, 2021

To check the version of nebula service, run ./bin/nebula-graphd --version

@study-day
Copy link
Author

That's good, it is recommended to modify the command prompt

@wey-gu
Copy link

wey-gu commented May 24, 2021

That's good, it is recommended to modify the command prompt

Sorry for the confusion, the -v in the service scripts stands for the option of output in VERBOSE level.

@Aiee
Copy link
Contributor

Aiee commented May 24, 2021

That's good, it is recommended to modify the command prompt

Sorry for the confusion, the -v in the service scripts stands for the option of output in VERBOSE level.

Actually, binary files are used to check version info instead of service scripts. I believe this change is doable.

@wey-gu
Copy link

wey-gu commented May 24, 2021

That's good, it is recommended to modify the command prompt

Sorry for the confusion, the -v in the service scripts stands for the option of output in VERBOSE level.

Actually, binary files are used to check version info instead of service scripts. I believe this change is doable.

agreed, this should be improved, maybe something like the daemon binary(binaries) version(s) to be returned in a service status query or from a new query option?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Community: perfect as the first pull request question Type: question about the product
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants