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.

Sign up for GitHub

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

Jump to bottom

Restart systemd-journald also restart kubelet and kube-proxy services #57711

Closed
lzlicd opened this issue Dec 29, 2017 · 2 comments
Closed

Restart systemd-journald also restart kubelet and kube-proxy services #57711

lzlicd opened this issue Dec 29, 2017 · 2 comments
Labels
sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@lzlicd
Copy link

lzlicd commented Dec 29, 2017 •
edited

When I change journald.conf from volatile to persistent, restart systemd-journald will also restart kubelet and kube-proxy. The kubelet.service and kube-proxy.service does not requires(depends) on journald. Not sure what caused these two services restarted as well. docker.service seems fine without restart.

CentOS Linux 7 (Core) with 3.10.0-514.2.2.el7.x86_64

Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.4", GitCommit:"793658f2d7ca7f064d2bdf606519f9fe1229c381", GitTreeState:"clean", BuildDate:"2017-08-17T08:48:23Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.4", GitCommit:"793658f2d7ca7f064d2bdf606519f9fe1229c381", GitTreeState:"clean", BuildDate:"2017-08-17T08:30:51Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

sh-4.2# rpm -qa | grep systemd
systemd-sysv-219-30.el7_3.6.x86_64
systemd-219-30.el7_3.6.x86_64
systemd-libs-219-30.el7_3.6.x86_64```
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Dec 29, 2017
@lzlicd
Copy link
Author

lzlicd commented Dec 29, 2017

/sig node

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Dec 29, 2017
@lzlicd lzlicd changed the title Restart systemd-journald will also restart kubelet and kube-proxy Restart systemd-journald also restart kubelet and kube-proxy services Dec 29, 2017
@lzlicd
Copy link
Author

lzlicd commented Jan 8, 2018

I think this is an issue for systemd systemd/systemd#2236, close this one.

@lzlicd lzlicd closed this as completed Jan 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@k8s-ci-robot @lzlicd