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

Error when parsing kernel version in proc background reader #1136

Closed
2opremio opened this issue Mar 7, 2016 · 2 comments · Fixed by #1165
Closed

Error when parsing kernel version in proc background reader #1136

2opremio opened this issue Mar 7, 2016 · 2 comments · Fixed by #1165
Assignees
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Milestone

Comments

@2opremio
Copy link
Contributor

2opremio commented Mar 7, 2016

<probe> ERRO: 2016/03/07 12:20:57.204694 getNamespacePathSuffix: cannot get kernel version: Malformed version: 4.3.5-300.fc23.x86_64

Full logs https://gist.github.com/janwillies/54083a50358718a4fb21

@2opremio 2opremio added the bug Broken end user or developer functionality; not working as the developers intended it label Mar 7, 2016
@2opremio 2opremio added this to the 0.14.0 milestone Mar 8, 2016
@paulbellamy
Copy link
Contributor

From semver.org, 4.3.5-300.fc23.x86_64 is not a valid version, as the pre-release section contains the _ character. Based on googling, I'm assuming this is for Fedora 23?

@2opremio
Copy link
Contributor Author

I have no idea, this came from user jcw on scope-public: https://weaveworks.slack.com/archives/scope-public/p1457352064000743

I am getting a similar error in the Weaveworks ECS AMI:

<probe> ERRO: 2016/03/11 13:49:24.314985 getNamespacePathSuffix: cannot get kernel version: Malformed version: 4.1.17-22.30.amzn1.x86_64

My bad, for not looking into more version examples (and not adding a unit test).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants