-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Sensord not able to start up on both master and 201911 branches #4021
Comments
keboliu
changed the title
Sensord not able to start up on both master and 201911 brach
Sensord not able to start up on both master and 201911 branches
Jan 14, 2020
@jleveque, would you please help to confirm is this only happened on the Mellanox platform or you also observed on other vendors' platforms? |
This issue is the same on Broadcom platform. The pmon docker can't run "service sensord start" in script lm-sensors.sh. |
CharlieChenEC
added a commit
to CharlieChenEC/sonic-buildimage
that referenced
this issue
Apr 1, 2020
… container - This commit fixes the issue sonic-net#4021 (Sensord not able to start up on both master and 201911 branches) - Add the new patch file for "lm-sensors" to perform dh_installinit to include sensord.init in the packed deb. So that the missing init script file for 'sensord' will be included in the created 'sensord' deb. Signed-off-by: Charlie Chen <charlie_chen@edge-core.com>
jleveque
pushed a commit
that referenced
this issue
Apr 3, 2020
… container (#4354) - This commit fixes the issue #4021 (Sensord not able to start up on both master and 201911 branches) - Add the new patch file for "lm-sensors" to perform dh_installinit to include sensord.init in the packed deb. So that the missing init script file for 'sensord' will be included in the created 'sensord' deb. Signed-off-by: Charlie Chen <charlie_chen@edge-core.com>
abdosi
pushed a commit
that referenced
this issue
Apr 7, 2020
… container (#4354) - This commit fixes the issue #4021 (Sensord not able to start up on both master and 201911 branches) - Add the new patch file for "lm-sensors" to perform dh_installinit to include sensord.init in the packed deb. So that the missing init script file for 'sensord' will be included in the created 'sensord' deb. Signed-off-by: Charlie Chen <charlie_chen@edge-core.com>
tiantianlv
pushed a commit
to SONIC-DEV/sonic-buildimage
that referenced
this issue
Apr 24, 2020
… container (sonic-net#4354) - This commit fixes the issue sonic-net#4021 (Sensord not able to start up on both master and 201911 branches) - Add the new patch file for "lm-sensors" to perform dh_installinit to include sensord.init in the packed deb. So that the missing init script file for 'sensord' will be included in the created 'sensord' deb. Signed-off-by: Charlie Chen <charlie_chen@edge-core.com>
Blueve
pushed a commit
that referenced
this issue
Oct 21, 2022
Why I did it #4021 describes an issue that is still being observed on master image whereby sensord does not start in pmon due to missing service. How I did it Updated the lm-sensors install patch with a case for systemd How to verify it Verified that sensord is up in pmon after boot Co-authored-by: Boyang Yu <byu@arista.com>
yxieca
pushed a commit
that referenced
this issue
Oct 25, 2022
Why I did it #4021 describes an issue that is still being observed on master image whereby sensord does not start in pmon due to missing service. How I did it Updated the lm-sensors install patch with a case for systemd How to verify it Verified that sensord is up in pmon after boot Co-authored-by: Boyang Yu <byu@arista.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Sensord inside PMON container failed to boot up in current master and 201911 branches, the error log as below:
Steps to reproduce the issue:
Describe the results you received:
Sensord failed to start up
Describe the results you expected:
Sensord should work properly
Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: